SaaSMethodMVPSMEs
Vertical SaaS ideas: how to find a niche that pays
9 min read
Good vertical SaaS ideas do not come from lists of a hundred ideas. They come from one specific trade, where professionals still get by with spreadsheets, paper or a generic tool that does not fit, ideally at the moment a rule changes and forces them to get equipped. The method has four steps: start from a trade you know, look for workarounds, check who pays, then validate before you build.
This article does not hand out ready-made ideas. It gives you a way to assess your own, with an example we know from the inside: Izi-Devis, quoting and invoicing software for construction tradespeople that LPR Studio designs, builds and runs itself.
Vertical vs horizontal: what changes
| Criterion | Horizontal SaaS | Vertical SaaS |
|---|---|---|
| Target | One function in every company | One trade or industry |
| Typical needs | Accounting, messaging, projects | Tradesperson quotes, training schedules |
| Competition | Crowded, with large players | Often an ageing tool or spreadsheets |
| Acquisition | Broad and expensive | Targeted: associations, trade shows, referrals |
| Market size | Very large | Bounded, and worth counting before you start |
Vertical SaaS gives up most of the market in exchange for relevance. It uses its customers' vocabulary, knows their documents and obligations, and fits into their working day. That is what makes it hard for a generic tool to displace.
Step 1: start from a trade you know
The strongest starting point is an industry you have worked in, or whose professionals you know well. Three reasons:
- You know where it hurts: the evening paperwork, the double data entry, the document rebuilt from scratch every time.
- You speak the language: buyers judge vertical software by its vocabulary on the very first screen.
- You can reach the first customers: a network, a trade association, former colleagues.
Without that background, find a co-founder from the trade or recruit pilot users and involve them from the first design. Our guide to launching a B2B SaaS as a non-technical founder covers how to split the roles.
Step 2: look for the workarounds
The best niches show up in what people do instead of using fit-for-purpose software.
- A shared spreadsheet acting as a database, with one tab per year and formulas only one person understands. Our article on replacing Excel with a custom application lists the tell-tale signs.
- An internal tool that one company in the sector built for itself and that its peers envy. That can be the seed of a product: see turning an internal tool into a SaaS.
- Generic software bent out of shape: a CRM used as a scheduler, an invoicing tool patched with Word documents.
- Paper and phone calls in a business that is otherwise digital.
Ask ten people in the trade the same question: "What admin do you still do in the evening?" When the same answer keeps coming back, you have a lead.
Step 3: follow the rules that are changing
A new obligation with a fixed date turns a wish into a need. Affected businesses must get equipped, with budget, before a deadline they did not choose.
Electronic invoicing is a clear example in Europe. On 11 March 2025 the Council of the EU adopted the VAT in the Digital Age package, which makes VAT reporting on cross-border sales between businesses in the EU fully digital by 2030, based on e-invoices. Some countries move faster: according to the French tax authority's FAQ, every VAT-registered business in France must be able to receive e-invoices since 1 September 2026, and small and medium businesses must issue them from 1 September 2027. Every piece of business software that issues invoices has to adapt, as our article on the French e-invoicing mandate explains.
Where to look for these changes: official tax and labour authority sites, publications from trade associations, and the accountants who serve the industry, who usually see obligations coming before their clients do.
One caution: regulation triggers a wave of purchases, and then the wave recedes. The product needs to keep its value once the deadline has passed.
Step 4: check who pays, and how many customers exist
A niche with a real problem but no budget does not make a SaaS business. Four questions before any code is written:
- How many businesses are in this trade? Official statistics count businesses by industry code: in the United States, the Census Bureau's County Business Patterns gives establishment counts by industry and size; in the EU, Eurostat's structural business statistics break businesses down by activity and size class. The number you get is a ceiling, not a forecast.
- Who decides and who pays? The owner of a small business decides alone; in a larger one, several people need convincing.
- What do they pay today? An ageing tool, a generic subscription, hours of admin time: that is your price reference.
- How will you reach them? Associations, trade shows, specialist press, buying groups. If you cannot see how to find your first ten customers, the niche is too abstract for you.
Signs of a good niche, and of a bad one
| Usually a good sign | Usually a bad sign |
|---|---|
| A task repeated every week | A one-off need, once a year |
| Documents or rules specific to the trade | A need that is identical in every industry |
| Professionals already working from a smartphone | An audience that rejects any digital tool |
| A regulatory deadline ahead | An obligation already covered by installed tools |
| An active trade network to get known in | Scattered customers with nowhere to meet them |
Common mistakes
- Choosing a niche because it looks empty. A market with no competitor is sometimes a market with no budget. An ageing tool everyone complains about is often a better sign.
- Aiming too wide. "Software for tradespeople" is too vague; "quotes for plumbers who work alone" can be tested in a few interviews.
- Cloning horizontal SaaS with a new name. Vertical software earns its place through what it knows about the trade: documents, rules, vocabulary. Without that, the generic tool wins.
- Ignoring what is already there. Professionals already have an accountant, software and habits. A product that does not connect to them adds data entry instead of removing it.
What Izi-Devis illustrates
Izi-Devis ticks several boxes, and its case study documents them.
- A specific trade: plumbers, electricians, painters, masons and tilers who work alone or in small teams.
- An evening task: quotes, invoices and payment reminders, which office-oriented software makes painful on a job site.
- An answer built for the field: the tradesperson dictates the quote, then reviews and corrects it before sending.
- Bridges to existing tools: accounting export in the French FEC format for the accountant, and import from another quoting tool.
- A rule that is changing: French e-invoicing, which the software is being prepared for.
It also shows the cost of going vertical: you have to follow the trade's obligations closely, week after week. For very small businesses, the choice between an off-the-shelf tool and custom software is covered in custom software for small businesses.
Validate before you build
- Ten interviews with people in the trade, focused on their working day, not on your idea.
- A visual prototype of the core task, shown to the same people: reacting to a screen is easier than reacting to a description.
- A concrete commitment: a letter of intent, a pre-order, a booked trial. "Sounds interesting" is not a commitment.
- A narrow first scope: one task done very well, rather than a full suite that does everything halfway.
If the interviews do not surface the same problem, change track before you invest. A niche can be validated in a few weeks of conversations; software that never finds its market costs months.