"Product Risk vs. Market Risk: How to Know Which One Will Kill You"
The Framework
Most founders treat startup risk as one blob. "Will this work?" But Girish Redekar, who built Sprinto to 3,000+ customers and eight figures in ARR, breaks it into two distinct axes.
Product risk: "Can this be built?"
Market risk: "Will people buy it?"
Every startup sits somewhere on this graph. And your position on it should dictate your entire early strategy. Not generic startup advice. Not what worked for someone else. Your specific risk profile tells you what to do first.
The problem is most founders default to the same playbook regardless of where they sit. They either build too long without talking to customers, or they ship too fast without solving the hard technical problem. Both are wrong. They're just wrong for different reasons.
The Steps
1. Plot your position on the two axes.
Ask two questions. First: if we could build this perfectly, is there clearly a market? If people are already searching for solutions, asking in communities, and paying consultants for workarounds, your market risk is low.
Second: can this actually be productized? If the answer requires real technical innovation or process breakthroughs, your product risk is high. Girish gives a clean example: "A self-driving car. If somebody did build a self-driving car, it's pretty clear that you can take it to market. So that's not where the risk lies." Pure product risk.
On the other end, some products are easy to build but hard to sell. "The product building is relatively easy or simple. What you're really worrying about is how do you take it to market?"
2. Attack your biggest risk first.
This sounds obvious but almost nobody does it. If you have high product risk, don't waste months on GTM experiments. Prove the product can work. Girish spent months running audits before signing a single customer because "we realized what we were building was basically towards this line, which was there were higher product risk than market risk."
If you have high market risk, don't spend months perfecting the product. Ship something functional and test channels.
3. Choose your validation method based on risk type.
For product risk: simulate the end-to-end experience. Girish ran 10 audits to prove Sprinto's compliance process could be automated. The market was already there. He needed to prove the product could deliver.
For market risk: run cheap distribution experiments. Test ads, communities, outbound. See if anyone bites before you invest in building.
Real Numbers
Sprinto was high product risk, low market risk. Girish knew people needed compliance automation because he'd lived it himself at RecruiterBox, where getting certified cost "a few months and tens of thousands of dollars."
So he spent the early months on product validation, not market validation. By the time they launched, they had 10 completed audits worth of process knowledge baked into the product.
Result: 30 to 40 customers within months of launching. They didn't struggle to find buyers. The market was already searching.
Compare that to RecruiterBox, where they spent "two or three years trying different ideas" before landing on the right product. Different risk profile, different struggle.
When It Fails
This framework breaks down when both risks are high simultaneously. If you're not sure anyone wants what you're building AND you're not sure it can be built, you're in trouble. Pick one risk to tackle first, or find a different idea with at least one axis de-risked.
It also fails if you misdiagnose your position. Founders often think they have product risk when they really have market risk (because building feels more comfortable than selling).
Your First Move
This week, write down one sentence for each axis. "Our product risk is [high/low] because [reason]." "Our market risk is [high/low] because [reason]."
Then ask: am I spending my time attacking the right risk? If your product risk is high but you're doing cold outreach, stop. If your market risk is high but you're perfecting features, stop. Redirect your energy to the risk that will actually kill you.
Ready to build your SaaS with founders who get it?
Join thousands of SaaS founders getting weekly insights and proven strategies from real founder conversations.
Free weekly newsletter · No spam
