Vertical software — built for a specific industry rather than a general audience — is one of the strongest categories in SaaS today. But most vertical SaaS ideas fail not because they are bad, but because they are not validated before money is spent. A proper validation process takes 2–4 weeks, costs €2,000–€5,000 (if you do a paid Discovery), and answers the only question that matters: is there a market willing to pay for this?
This article walks through a five-step validation framework that separates ideas worth building from ideas worth abandoning.
What vertical software actually means
Vertical software serves a specific industry — construction management, dental clinic scheduling, restaurant inventory, logistics routing, compliance tracking for financial advisors. It solves problems that are too niche for horizontal SaaS (like Salesforce or Asana) to address properly.
Why vertical ideas are compelling right now:
- Large horizontal markets are dominated by incumbents. Vertical niches are often underserved.
- Industry insiders understand the pain better than any generalist product team.
- Customers in the same vertical talk to each other — word-of-mouth distribution is built in.
- Switching costs are high once a vertical tool is embedded in a workflow.
For examples of vertical software we have built, see our articles on software for construction companies, software for restaurants, and software for real estate.
The 5-step validation framework
Step 1: Size the market
You do not need a €100M total addressable market. You need enough customers willing to pay enough per month to build a sustainable business.
Quick formula:
- Number of potential customers in your target geography × price you can charge per month × 12 = annual revenue potential
- If the result is below €500,000, the market may be too small for a standalone SaaS business (though it may work as a side product or a consultancy-backed tool).
Sources for market sizing: industry associations, chamber of commerce data, LinkedIn Sales Navigator (count companies in the vertical), government business registries.
Step 2: Map the competitor landscape
Search for existing solutions — not just software, but also spreadsheets, manual processes, and industry-specific workarounds. Ask:
- Who are the direct competitors? (Other software tools solving the same problem)
- Who are the indirect competitors? (Spreadsheets, paper, and WhatsApp groups)
- What do existing solutions get wrong? (This is your opportunity)
If there are zero competitors, be cautious — it may mean there is no demand. The best position is 2–5 competitors doing a mediocre job.
Step 3: Talk to 20 potential users
Not 5. Not 3. Twenty. The pattern only becomes clear after enough conversations.
Questions to ask:
- “How do you currently handle [the problem]?” (Understand the status quo)
- “What is the most frustrating part of that process?” (Find the pain)
- “How much time/money does it cost you per month?” (Quantify the pain)
- “Would you pay €X/month for a tool that solves this?” (Test willingness to pay)
- “If this existed today, would you sign up this week?” (Test urgency)
Red flag: If 15 of 20 people say “it’s annoying but we deal with it,” the pain is not acute enough to drive purchase decisions.
Step 4: Run a willingness-to-pay test
Conversations lie. Behaviour does not. Before building anything:
- Create a landing page describing the product with a pricing page and a “join waitlist” or “pre-order” button.
- Run a small ad campaign (€500–€1,000) targeting your vertical on Google or LinkedIn.
- Measure: How many people visit? How many click the pricing page? How many sign up or pre-order?
A conversion rate above 5% from visitor to waitlist is a strong signal. Below 2% suggests the positioning or the idea needs work.
Step 5: Define the MVP scope
Once demand is validated, define the minimum version that tests the core hypothesis. Not the full product — just enough to deliver the main value.
Use the “one hypothesis” test: for every feature, ask “If I remove this, can I still test whether customers will pay for the core value?” If yes, remove it from the MVP and put it in v2.
For the full MVP framework, see what is an MVP and how to build one in 12 weeks.
Red flags that kill vertical ideas
- Market too small. Fewer than 1,000 potential customers at €50/month means a ceiling of €600,000/year — before churn, before costs.
- Incumbents are too strong. If the market leader has 70%+ share and deep pockets, entering is expensive.
- Regulation is a barrier. Some verticals (medical devices, financial instruments) require certifications that cost €50,000–€200,000 before you can legally operate. See building software for regulated industries.
- The pain is not acute. “Nice to have” does not sell. The problem must cost enough (in time or money) that the solution sells itself.
How much validation costs
| Activity | Cost | Duration |
|---|---|---|
| Market research (DIY) | €0–€500 | 1 week |
| User interviews (20 calls) | €0 (your time) | 2 weeks |
| Landing page + ad test | €500–€1,500 | 1–2 weeks |
| Paid Discovery sprint | €2,000–€5,000 | 1 week |
| Total | €2,500–€7,000 | 3–5 weeks |
Compare this to the cost of building a product nobody wants: €30,000–€80,000 and 4–6 months. Validation is the cheapest insurance in software.
Frequently asked questions
Can I skip validation if I am the target user? You can shorten it, but do not skip it. Your experience is one data point. Twenty data points from others reveal patterns you cannot see from inside the problem.
What if the validation shows weak demand? That is the best possible outcome — you saved €30,000+ and months of work. Either pivot the idea (different angle, different vertical, different price point) or abandon it and move to the next one.
Should I validate before talking to a development agency? Ideally, yes. But a good agency can also help you validate — a Discovery sprint includes validation as part of the process.
Related articles
- From industry expertise to software product — The playbook for turning domain knowledge into a product.
- What is an MVP and how to build one in 12 weeks — What to build after validation.
- Niche B2B SaaS: how we partner with industry insiders — Our partnership model for vertical software.
Have a vertical idea worth testing?
Book a free 30-minute call. We will help you assess the market, identify the validation steps, and decide whether a paid Discovery sprint is the right next move.
Reach out at [email protected] or via the form on our homepage.