The user case is more important than the tech when working with AI

I was wondering about what to write after creating this website. This subject was by far the most important that I got in my head after the first one that I wrote (link here).

And I want to write about this because it’s something I’ve seen a lot in the last few months. An imbalance between the tech behind the idea and the idea itself. I think this is the worst case scenario for someone working with AI.

I want to be very clear about this: it’s the best use of your time to create a value proposition without coding or without using any n8n node, that to focus only in the tech that will allow you to come up with the solution. Spend as much time as you can designing the solutioin and then take care about the tech behind it. That part will be a problem that you will solve easily. The tech behind agents and automations is moving very fast, so if something is not already developed, someone will do.

But as any business that I’ve been part of, the most important side is to be able to solve a problem for a customer in the most cost-efficient way possible. If you are not solving a real problem, wheter is to improve the benefits of an job that the customer has to do and/or diminishing the pains related to that same job (a framework developed by C. Christensen, read more here), you won’t be creating value. And if you don’t create value, any tech would be innecesary.

How to create value while using AI with your automations

First, try to understand the problem that the user is having.

The best way to do this is to create automations for yourself before solving anyone else’s problems.

In my case, I wanted to solve an issue with my SEO knowledge and actions, and I was able to solve it through n8n. I was so impressed about hte customization and the nodes available for me that I came up with the idea of this website so more people can understand the power of AI and automation. But first, I solved a problem for myself. That’s the first part.

Second, check if this is a problem that lots of people have or if IT’S a niche has but they are willing to pay plenty to solve this issue. You have to be able to sell this solution to lots of people. This is very important. It’s OK to have a niche solution to a problem, but then you have to “cross the chasm” and sell it to the mass market. If not, it won’t be something that would scale. More on that later.

Third, does the solution really solves the problem? Maybe you are solving a small problem and your solution covers everything that the client needs. This is by far, the best scenario while solving client’s problems. If something else is necessary, it would be smart to include all the rest of the workflows so the client can solve all his or her needs with your AI solution. Again, this is the best scenario possible, but it’s not always feasible. So have to incorporate that tradeoff.

Lastly, try to scale that solution as much as you can. If everything works out while putting this solution into the market, you will be flooded with requests. And if you are not prepared to scale your operationm the one you built for yourself, you won’t be able to solve clients’ problems as much as you like. Remember, you’re trying to create value not make money. Money will come after the value creation, value delivery and value capture.

Conclusion

So. What to do first?

Solve a problem for yourself.

Check if more people have this same problem.

Check if this problem can be completely solved with your solution. If not, try to increase its value.

Then, scale the solution.

NEVER start with the tech. Only incorporates the tech after you have a solution to a problem.

It sounds obvious, but believe me, there are plenty discussions focusing more on the tech rather than the value creation. And that’s a mistake.

Feel free to contact me if you want to further discuss this!