If You need to get from one end of the city to the other, You have three fundamentally different options. You can buy a car: pay once and it is yours, with all its advantages and all its breakdowns. You can call a taxi: You own nothing, You buy a driver's time and skill for one trip. Or You can use car sharing: You get access to a car that someone else maintains, fuels, insures and repairs, and You pay for using it.
These are the three types of value a company can sell: a product, a service and a product-service. It sounds like a dull classification from a marketing textbook. But I have seen many times how not understanding what exactly You sell breaks a company's strategy, pricing, hiring and even relationships with clients. So I will go through each type not by the textbook but by how it feels from the inside.
Product: You sell a result
A product is something You can create once and sell many times. Boxed software, a mobile app with a one-off purchase, a book, a recorded course. Its main feature: the main costs happen before the sale. You spend a long time and a lot of money creating it, and then each additional copy costs almost nothing.
Hence the strengths and weaknesses. A product scales: selling a thousand copies is almost as easy as selling a hundred. But the risk is entirely yours: You can invest a year and all your money, and the market may not buy. And a product has no natural connection with the client after the sale. The person bought it, left, and You know nothing more about him until You release the next version and try to sell it again.
Service: You sell time and competence
A service is work done specifically for a client. Consulting, custom development, design, legal support, outsourcing. Ingello Systems is by nature a service: we sell the competence of an engineering bureau and the time of our people.
A service has almost no upfront risk: You start earning money from the first client without investing years in development. You understand each client deeply because You work with him closely. But a service scales linearly: to serve twice as many clients You need twice as many people. Your ceiling is set by your team, and a team cannot be copied like a file. And the main trap of a service: when people get tired or leave, part of your value leaves with them.
A product sells what has already been made. A service sells what will be done. A product-service sells what will keep working.
Product-service: You sell access to a living system
The third type did not appear yesterday, but it was the cloud and the internet that made it mainstream. SaaS, cloud services, subscriptions, everything ending in "as a Service". The client neither buys software nor hires people. He gets access to a working system that You constantly maintain, update and improve. He pays regularly for as long as he uses it.
This hybrid takes the best of both worlds. From the product, scalability: one system serves thousands of clients. From the service, a continuous connection with the client: You see how people use the system, what gets in their way, what needs to be added. And You get what every entrepreneur dreams of: regular, predictable revenue.
But the hybrid has its own obligations. You cannot sell and forget. If the system goes down at night, it is your problem right now. If the client stops liking it, he leaves next month and all revenue from him stops. The key metric here is not sales but retention: how many clients stay with You month after month.
Why this matters
Almost everything else depends on the type of value. How You set prices: per copy, per hour of work or per month of access. Whom You hire: product developers, expert practitioners, or a team that both develops and supports. How You sell: broad marketing, personal relationships or a trial period. Which metrics You track: copies sold, team utilisation or client churn.
The most common mistake I see is mixing them without realising it. A service company decides to "build its own product" and develops it on a leftover basis, in the gaps between client projects. The product stays unfinished for years because client tasks are always more urgent. Or the reverse: a product company takes on custom development to cover a cash gap, and a year later the whole team is busy with other people's projects while its own product is abandoned.
At Ingello we resolved this dilemma through separation. Systems honestly remains a service and earns money. Fractal and Forma are developed as products, and Systems uses them in client work, which makes the service faster and cheaper. That does not mean everyone should do the same. It does mean the decision was made deliberately rather than just happening.
What to do tomorrow
Answer this question for yourself: if your company stopped working tomorrow, what would the client lose? If he would lose a thing he already bought but could not buy a new one, You are a product. If he would lose the people who worked for him, You are a service. If he would lose access to a system he cannot work without today, You are a product-service. Then check whether your prices, team and metrics match that answer. If they do not, You have most likely found the reason something has long been holding back your growth.
