What second-time founders do differently when building a B2B SaaS

Executive overview

Building a general product and hoping to retrofit it to enterprise needs is a losing strategy. Brandon Foo and Ishmael Samuel learned this at Polymail — strong consumer adoption but no B2B traction because the product was never designed around a specific business problem.

At Paragon, they reversed the process: identify a concrete unsolved problem first, validate willingness to pay before writing code, then build. Within two months of launching, they had hockey-stick growth.

If you can get five paying customers before building, you should build the thing you're marketing.

The Polymail lessons

• Hit 20–30k daily active users but couldn't convert that into B2B traction
• Tried to retrofit a consumer email product to enterprise use cases — didn't work
• Built go-to-market strategy too late; product came first, distribution was an afterthought
• Key mistake: started from a solution and searched for problems, rather than starting from the problem

Finding the right problem for Paragon

• Reflected on pain felt as developers: every integration required writing custom code from scratch
• Saw that no scalable solution existed — developers had to manually connect each of thousands of SaaS APIs
• Conviction: build the "Stripe for integrations" — a single layer developers install once to connect their product to any SaaS app
• Rebuilt the entire product around customer-facing integrations; within two months saw clear product-market fit

Validating before building

• Try to get your first five paying customers before writing a line of code
• Spin up a landing page, run a few ads or cold emails — no engineering required
• Test real willingness to pay: would they pay $30? $50? $100?
• Paying customers validate that the problem is real; unpaid sign-ups do not
• The sales conversations themselves are valuable — customers reveal adjacent or unexpected problems worth solving

Pricing as a signal and a discipline

• B2B SaaS pricing is straightforward: monthly subscription, start at $30/month
• If a company won't pay $50/month, you probably aren't solving a big enough problem
• Raise prices incrementally as you add customers; it tests product-market fit strength
• Charge early and as much as possible — even pre-orders show intent and validate value
• Two reasons businesses pay: you save them money or you make them money; if neither, they won't pay

Reading customer signals correctly

• Customers already spending time and resources trying to solve the problem themselves are your ideal early users — they've self-validated the pain
• Bug reports from engaged customers are a positive signal, not a failure — they're using the product and want it to improve
• Distinguish between customers who are frustrated because the product is weak versus customers who are excited and want more