How to validate a SaaS idea before you build.

Validating a SaaS idea before building is structurally different from validating a marketplace, a mobile app, or a consumer product. SaaS has a specific failure pattern: founders build a tool that solves a real problem for a buyer who has no budget to pay for it, or who has the budget but cannot get the procurement approved.

This is a playbook for testing a SaaS idea against the five dimensions that matter. Each dimension can be tested in days, not weeks, with the right discipline.

A SaaS buyer is a specific person with a specific job title at a specific company size in a specific industry. "Mid-market HR managers" is not a buyer; it is a persona. "The VP of People at a 200-to-500-person SaaS company in the US who currently runs offer-letter generation through a contractor" is a buyer.

The test: write down five real people who match the description, contact them, and ask whether the problem you are solving costs them measurable time or money. If you cannot find five people in two weeks of outbound, the persona is too narrow or the buyer is not real.

Three independent signals are needed:

- **Comparable pricing.** What do similar tools charge for similar buyers in the same segment? Look at competitor pricing pages, G2 listings, and Capterra data. - **Substitute cost.** What does the buyer currently spend to solve the problem (human hours, contractor cost, manual processes)? - **Buyer language.** When you talk to five real candidates, do they describe the problem in terms that suggest active budget? "We are looking for" and "we have evaluated X and Y" are budget signals; "it would be nice" is not.

If all three triangulate to a price band you can defend, the idea has WTP. If two of three say one number and the third says something very different, the read is mixed and more research is needed.

A wedge is the one thing your SaaS does materially better (10×, not 10%) than the alternatives for a specific buyer in a specific job. The wedge is not a feature list; it is the one claim you would put on the landing page if you could only have one.

The test: write the wedge as a single sentence. Then write the strongest counter-argument an existing competitor or substitute could make. If the counter-argument does not embarrass the wedge, the wedge holds. If it does, the wedge is decorative and needs to be reframed.

A typical reframe path: from "feature parity with X plus our own twist" to "specifically built for buyer-segment Y, with workflow Z that X cannot accommodate". The reframe makes the wedge structurally narrower and harder for the incumbent to copy without disrupting their main business.

The reachable buyer pool times the realistic conversion rate times the realistic price has to clear the cost of running the business plus the founder's salary. The minimum bar is whether the SaaS can pay the founder.

A rough back-of-envelope:

- 5,000 reachable buyers - 2% lifetime conversion (very generous for cold outbound, reasonable for owned content) - $100 a month average price - $120,000 annual recurring revenue at peak

That math works for a side project but does not pay a salary in a high-cost-of-living market. Either the price has to be higher, the pool has to be larger, or the conversion has to be better. Doing the back-of-envelope first prevents months of building a product that cannot economically support the founder.

Most SaaS dies because no one finds it. The right time to identify the distribution channel is before the build, not after.

The test: name the specific channel you will use to acquire the first 100 paying customers. Not "content marketing" or "outbound"; the specific channel. "A weekly newsletter to HR managers via Hampton's audience" is a channel. "Posting in r/SaaS" is a channel. "We will figure out marketing later" is not a channel.

If you cannot name the specific channel, the idea has a distribution risk you should address before building.

The idea: a SaaS that automates shift scheduling for healthcare staffing agencies with 50 to 200 contractors.

- **Buyer:** the Operations Director at a staffing agency. Five named candidates found within a week through LinkedIn outbound. Each one runs scheduling on a mix of spreadsheets and one of three legacy tools. - **WTP:** comparable tools (When I Work, Deputy) charge $4 to $8 per active employee per month. The substitute cost is a $60K Operations Manager spending 30% of her time on scheduling. Buyer language in five calls included "we have actively evaluated Connecteam" (active budget signal). Triangulates to a $7 to $10 per employee per month band. - **Wedge:** "Healthcare-specific compliance tracking built in" (which the horizontal tools do not have). The 10× test: a competitor could counter with "we have a checklist users can configure". Reply: configurable checklists do not produce a defensible audit trail for state inspectors. The wedge holds. - **Unit economics:** roughly 2,500 US-based staffing agencies in the 50-200-contractor segment. 5% conversion to paid tier at $8 per employee per month with an average 100-contractor agency = $1.2M ARR. Not venture-scale, but enough to pay two founders. - **Distribution channel:** outbound to named Operations Directors via LinkedIn plus presence at one industry conference per year (Staffing World).

All five dimensions clear. This SaaS idea is worth building.

The free Verdikt produces a Verdikt Score plus the top three named risks across the same five dimensions in minutes. The Single Report at $49.99 ships the full memo with 40+ cited sources, all four sub-scores, named risks with thresholds, and a build outline including the recommended stack.

The playbook above is the manual version. Verdikt compresses the timeline.