Since I’ve joined the IH community about 9 months ago, I’ve noticed that a lot of attention is put heavily on the tech part of creating a SaaS.

I’ve come to the conclusion that it’s time to adjust the perspective.

Here is why

Numerous lists of tools that teach you how to build a SaaS without code, with low code, or get it quickly deployed with seamless backend solutions are paving the path.

I have gone down this road myself and have tried to create products which were supposed to be the fruitful beginning of a potential SaaS.

Then, I noticed I was doing it all wrong.

As funny as it sounds, but the best way to create a SaaS seems to be not to create a SaaS.

Or, as Patrick McKenzie puts it

if you can possibly avoid it don’t start in SaaS

What are the implications?

Well, in short:

Rather than leaping directly into the technological part of a business, the first priority should be to create a service/consulting that actually has a repeatable positive output that is visible to the client.

This is not only the best way to get a deep understanding of your clients' needs but also sharpens your business senses.

From this point on of having a service clients actually need, pay for and are happy with you can continue to start thinking about how to take over parts of the clients pains by automating processes the clients are already paying for.

Real life example

A picture book version of how this leads to success has been done by @Andrewpierno who is a software developer who cracked 10k$ in only 3.5 months by doing exactly this:

Service first approach, ditching code.

As I am currently on the path of learning to code this realization has both: a relieving and frustrating effect on me.

On the one hand I think: Oh my gawd! Why am I bothering about code then anyway??!!!!11

On the other hand I think: OK, great: So I don’t have to worry about coding too much after all.

Concluding thoughts

I have seen many success stories in the Indie Hacker scene are being technology-focused.

This is not bad, but creates a false assumption namely: focus on code.

The opposite of the first assumptions seems to be the way to go: focus on service.

Yes, code and tech is important, but get the business straight first and then start to code.

Obviously, there will be examples where this methodology will not apply.

But I think especially if you are starting out on your journey of figuring out how to build a profitable business it is highly valuable to focus on the right things.

I am still on the road of creating my path if you are interested

in more real-life updates feel free to join me on twitter.

Have a good one.