Notes

Products and new ventures

One order is a poor reason to launch a new business line

We built a system for a customer and got paid. The next thought is understandable: now we can sell it to the whole industry. That is where I would slow down. The customer paid to solve their problem. Nobody has paid for the future product business yet.

I have opened new business lines too early

In a 2024 ER10 interview, I described opening new business lines before strengthening the core business. Income from existing projects did not cover the expansion.

So “we know how to build it” is not enough for me. Being able to develop a system is useful. A business around it also needs buyers, development money and someone working on it every day. Sailet currently does custom development and automation. Products may grow out of client work, but each transition needs testing separately.

What will the second customer buy?

Suppose the first company paid for handling enquiries. The second also loses enquiries. It looks like the same market. Then it turns out to have different approvals, integrations and permissions. Half the system needs rebuilding.

You can earn money that way too. You just need to keep the cost of people who analyse each new job and deliver a custom project in your calculation. If you expect product economics but keep paying for a project team, the money will run out quickly.

I would first find out which part of the solution different companies will buy without a complete rebuild. Who decides, what have they tried and why would they change how they work? What will the person do after the demo: pay for a test, provide data, assign staff? “Looks cool, keep me posted” is not enough.

You cannot spend all the revenue

A simple hypothetical calculation: an order brings in 10 units and costs 6 to deliver. That leaves 4. Testing the product costs 12. With the same contribution from each following order, three buyers are needed just to cover that test: 12 ÷ 4 = 3.

Overheads, support, rework and the time needed to make a sale are not included yet. But it already shows why you cannot spend the first 10 on a new product: six are needed to deliver the work you have already sold.

Who will work on it?

Suppose buyers exist and the numbers work. Who will sell, collect feedback, choose changes and answer for spending? If the answer is “somehow between our main projects”, I would hold off calling it a new business line.

We need someone with time and the ability to make decisions. Before starting, agree how much money and time the test gets, what result we expect and when we stop. Otherwise, it becomes another idea the founder has to keep rescuing.

Keeping the solution as a custom project is a perfectly reasonable result. If other buyers turn up and there is a clear way to serve them profitably, we can go further. The announcement of our new product can wait.

Do you see a business behind a client's problem?

Tell me who else would pay for it, what would need changing for the next buyer and which work you would take on.

Discuss the idea

Reasons to get in touch

Already have a defined implementation project? Talk to the Sailet team