Guides › Starting a business
The two have opposite risk profiles, and the right answer depends on what you can fund and how certain you are about what customers need. Many strong businesses do both, in a specific order.
Short answer: Start a service business first if you need revenue from month one and want to learn exactly what customers will pay to fix. Services validate demand while being paid and supply the specification for a product, which many businesses then build once the pattern is clear. Products carry higher margins at scale but risk building something nobody wants.
A service can be sold before it exists, validates demand immediately and pays from month one — but revenue is tied to hours and growth means hiring. A product needs building before it earns, and once it works, an additional customer costs almost nothing.
The risk is differently placed: services risk your time ceiling, products risk building something nobody wants.
Selling a service teaches you exactly where customers struggle and what they will pay to fix. That is the specification for a product, learned while being paid rather than while burning savings.
A great many software businesses started as consultancies that automated the work they were repeatedly doing by hand.
This question routes to Startup Genius — one of 29 engagements the platform runs. It does not produce advice in general; it produces this analysis for your business:
✓ Sizes who could realistically buy this — not the size of the industry
✓ Estimates what a customer costs to acquire and what they are worth to you
✓ Tests whether the gap between those two survives contact with reality
✓ Models the cash you need and when break-even actually arrives
✓ Names the assumptions the whole idea rests on, ranked by damage if wrong
✓ Gives the cheapest test that would prove the riskiest one false
You watch the analysis get built before you pay anything. Read a complete report here if you would rather see the depth first.
Products have higher margins at scale; services have better margins early because there is nothing to fund. Over a five-year horizon a working product usually wins, but the majority of products never reach the point where that matters.
It is one of the most reliable paths there is. Do the work manually for enough customers to see the pattern, then build the thing that does the repetitive part. The customers you already serve become the first users.
Common and workable, though it needs discipline — the service revenue is immediate and the product work is not, so the product loses every scheduling conflict unless it is protected deliberately.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.