How to choose a wedge for a SaaS product

Primary question

How narrow should a founder get when choosing the first wedge for a SaaS product?

Practical takeaway

A strong wedge is small enough to win, obvious enough to message, and painful enough that the first buyer can recognize themselves immediately.

Key points

Pick a workflow before you pick adjacent features.
Prefer obvious buyer recognition over theoretical market size.
Judge the wedge by defendability, not by how many cases it could maybe include.

Shape

A wedge needs one audience, one job, and one reason now

Good wedges are memorable because they collapse complexity. They say who the product is for, which workflow it improves, and why the user should care right now. The moment you need a long explanation, you are usually describing a platform, not a wedge.

This does not mean picking the smallest possible niche. It means picking the most legible entry point: a combination of audience and workflow where the product can plausibly be the obvious answer.

Audience without workflow is too broad.
Workflow without urgency is too weak.
Urgency without a clear buyer still makes distribution messy.

Wedge test

Dimension	Strong wedge	Weak wedge
Audience	One recognizable operator shape	Anyone doing knowledge work
Workflow	One repeated job with a clear trigger	A broad set of adjacent tasks
Promise	One sentence the buyer instantly understands	A bundle of maybe-useful improvements

Defendability

Choose the wedge you can actually defend as a small operator

Founders often choose the wedge that sounds biggest instead of the wedge they can actually serve well. A better filter is defendability: can you produce a cleaner product, tighter message, and faster iteration loop than the broader competitors in this one narrow case?

The wedge is good if you can imagine becoming the default recommendation for that audience and workflow with your current size. If that picture already requires a full sales team, a broad integration layer, or a huge roadmap, start smaller.