
[drop_cap]O[/drop_cap]pen a SaaS founder’s browser tabs during a “competitive research” session and you’ll find the same ritual everywhere: eleven pricing pages, a G2 comparison grid, a spreadsheet of feature checkboxes. It feels like diligence. Mostly it produces a list of features to copy and a vague, unresolvable anxiety about whether the checkboxes are the same shape as the reasons people actually buy. Matching a competitor’s feature table tells you what they shipped. It tells you nothing about why a buyer chose them, or why a buyer might choose you instead. Software has a gift most categories don’t, though: the competitive field has a fixed shape. Once you can name the six tiers a buyer is actually shopping across, mapping your own market stops being a fishing trip and becomes an afternoon’s honest work.
Your Company stage gave you internal clarity — your ICP, your pricing model, the mechanism that makes your product work, the voice you intend to speak in. That clarity is real, and it means nothing to a buyer typing your category into a search bar. The moment someone opens a new tab and searches “[category] software,” you are lined up against everyone else who answers that query, judged inside ninety seconds by someone who has already read three “vs” pages and doesn’t trust any of them. This stage completes the second pillar of the Foundation: Market Awareness. Treat it as reconnaissance, not a shopping list of things to imitate.
The Six Tiers Your Buyer Actually Shops
Every buyer evaluating your category is weighing options that fall into one of six tiers. They don’t compete with each other on the same axis, and knowing which tier a rival sits in tells you how to beat them before you’ve read a line of their landing page.
- The incumbent suite — the big horizontal platform that already owns the budget line (think of the category leader everyone’s finance stack already pays for). It competes on “we already have a seat for this” and bundling. Its weakness is that the feature is usually a bolted-on afterthought inside a much bigger product, slower to improve and never the vendor’s real focus.
- The category leader — the company that defined this space and still gets named first in every “best tools for X” list. It competes on brand trust and the safety of the obvious choice. Its weakness is usually price, bloat from serving every segment at once, and a support queue that has stopped feeling founder-close.
- The cheap point tool — a narrow, focused product that does one job well at a low price. It competes on being fast to adopt and easy to justify. Its weakness is that it stays narrow — the buyer who grows past the one job has to go shopping again, and it rarely integrates cleanly with anything else in the stack.
- Open source / self-hosted — the free-if-you-run-it-yourself option, usually maintained by a community or a thin commercial layer around it. It competes on cost and control. Its weakness is the hidden cost of running it: someone on staff has to own the server, the upgrades, the security patches — the total cost of ownership the sticker price never shows.
- The internal build — the buyer’s own engineering team, quietly convinced they could build this in a sprint or two. It competes on “we don’t have to trust a vendor” and sunk enthusiasm. Its weakness is the one every engineering leader eventually says out loud: maintaining it forever, after the interesting part is built, is a cost nobody budgeted for.
- Spreadsheet or nothing — the status quo, where the job gets done badly by hand or not at all. It competes on inertia and “we haven’t gotten around to it.” You beat this tier not on price or features but on urgency: naming the cost of staying here loudly enough that doing nothing stops feeling free.
Place the real companies and the real internal habits in your market into these six slots, and the competitive picture that takes most founders weeks of scattered research is mostly done in one sitting.
The Market Awareness Grid
Work the same disciplined instrument that governs every stage of this Foundation: the Market Awareness Grid, a three-by-three matrix. Three rows — the competitive set, the market forces, and the channels. Three columns — observe what is simply there, analyze the gaps it exposes, respond with the position you’ll take. Move left to right, every row, every time: see clearly, then think, then decide.
| Observe — what is there | Analyze — the gaps | Respond — your position | |
|---|---|---|---|
| A. Competitive Set | The 2–4 rivals your ICP names most often, sorted into their six-tier slot, each with its stated pitch. | Where they fall short: G2/Capterra complaints, a missing integration, a segment their pricing ignores. | How your mechanism or your pricing answers a named weakness. The honest answer to why you. |
| B. Market Forces & Trends | The 2–3 forces genuinely moving your category — a platform shift, a pricing-model trend, a new regulation, an incumbent’s neglect of a segment. | The openings each force creates that no single rival controls yet. | Which forces to ride, which to brace against; how your roadmap and pricing adapt. |
| C. Channels | Where your ICP actually spends attention — communities, comparison sites, integrations marketplaces, the search terms of an active evaluation. | Which channels are saturated by rivals; which your ICP uses but competitors have neglected. | Where to concentrate first, and which expansion keyword your own rank data just exposed. |
Each cell is a small investigation. The value is in the rigour you bring, not the speed you fill it.
Row A — the Competitive Set, read from the evidence, not the homepage
Name the two-to-four products your ICP actually compares you against — not every tool in the category, the ones that come up on real sales calls and trial signups. Drop each into its tier. Then read the reviews, and read the negative ones closely: a G2 or Capterra one-star review is a competitor’s failure, documented for free by the customer they let down. A pattern — “support went silent after we signed,” “the onboarding took three weeks and we still don’t use half of it,” “billing surprised us” — is a map of the openings you can credibly claim.
Respond by aiming a verifiable strength at a named weakness, never an adjective. “We reply in under an hour, and here’s our public status page” beats “great support” every time, because a rival can copy the sentence but not the receipt.
Row B — the Forces Moving Your Market
Three forces genuinely touch a SaaS category, and reading them early beats reacting to them late.
Pricing-model shifts move faster in software than almost any other category. A market that was per-seat can tip toward usage-based within a couple of product cycles once one credible vendor proves it converts better; a market saturated with free tiers can tip toward paid-only once the CAC math stops working for everyone at once. Watch what your 2–4 rivals are doing to their own pricing pages, not what they said at launch.
Platform and integration shifts create and destroy distribution overnight. A marketplace opening an API, a browser deprecating an extension model, a major platform launching its own native version of what you do — each one either hands you a channel or takes one away. The response isn’t panic; it’s watching the platform’s own roadmap the way you’d watch a competitor’s.
Buyer fatigue with the incumbent is the quiet, durable force underneath most successful challengers. Every category leader accumulates a slow drift of neglected complaints — the bloat, the price creep, the support queue that used to feel founder-close. That drift is not visible in any single review; it shows up as a rising rate of “looking for an alternative to X” searches. It is the single most reliable tailwind a smaller vendor gets, and it costs nothing to read.
Row C — the Channels, and Reading Your Own Rank
Map the named surfaces where your ICP actually spends attention while evaluating. For B2B software the list is well-known: communities (a Slack or Discord the buyer’s peers already live in, a subreddit for the role, a niche forum for the practice), comparison and review sites (G2, Capterra, and the “alternatives to X” pages that rank for exactly the search terms an active evaluation produces), integrations and app marketplaces (listed inside the platforms your ICP already runs — often the highest-intent, lowest-competition channel there is), and the search terms of an active evaluation itself — “best [category] for [segment],” “[competitor] alternative,” “[competitor] vs [category].”
Analyze by asking, for each: is my buyer actually here, and is the competition already loud? The valuable ground is wherever those two answers diverge — where the buyer gathers but no rival has staffed the channel.
Reading Your Own Rank and Review Data
Your search rank and review presence are the closest thing SaaS has to ground truth, and reading them is a learnable pattern, the same one used in every trade this playbook covers. For each term that matters — your category name, “[competitor] alternative,” “[category] for [your ICP’s segment],” “[category] pricing” — note roughly where you land: on the first page, a few spots down but climbing, or effectively invisible.
Three bands fall out, and each means something different:
- Dominant terms — where you already rank or are already the named leader in review counts. Defend these; don’t spend scarce effort re-winning ground you own.
- Improvable terms — a few spots down, close enough that a sharper comparison page or a push for more reviews can climb them.
- Unranked terms — the searches where you’re invisible. This is the important one. An unranked term with real evaluation volume behind it is your expansion lane — often a segment-specific variant (“[category] for agencies,” “[category] for e-commerce”) that no rival has bothered to own, because it looked too narrow to write for. It rarely is.
Find yours from your own data. Never borrow a competitor’s rankings or review counts as your target — they earned those in their funnel, not yours.
Scoring Your Channels
A channel isn’t worth pursuing because it’s popular or because a growth blog said so. Score it against your own ICP and your own product, on a simple table you fill honestly rather than optimistically.
| Channel | ICP presence (1–5) | Competitive noise (1–5, lower = quieter) | Cost to enter (1–5, lower = cheaper) | Buying intent (1–5) | Total |
|---|---|---|---|---|---|
| Community X | |||||
| G2 / Capterra | |||||
| Integration marketplace | |||||
| SEO — comparison pages | |||||
| Paid search |
Score every row from what you observed in Row C, not from what “everyone says works.” A channel with real ICP presence, low noise, and high intent — even at a real cost to enter — outranks a loud, crowded, low-intent channel every time. The integrations marketplace inside a platform your buyer already runs is routinely the highest-scoring row on this table and the one founders skip, because listing an integration feels like engineering work rather than marketing work. It is both, and it is usually underpriced attention.
Mapping Your Buyer’s Awareness
A lens sits across the whole grid and sharpens it: buyers don’t all know the same thing about their own problem. The copywriter Eugene Schwartz observed that a market sits at different stages of awareness, and the stage your buyer occupies decides which hook lands.
| Awareness stage | What the buyer knows | The SaaS hook that fits |
|---|---|---|
| Unaware | Doesn’t know this is solvable by software yet | Not a target — don’t spend budget here |
| Problem-aware | ”This manual process is costing us hours every week” | Educational content naming the cost of the status quo |
| Solution-aware | ”There’s a category of tool for this” | Category comparison content: build vs buy, tool vs spreadsheet |
| Product-aware | ”I’m trialing you against two competitors” | Comparison pages, migration guides, a clear differentiator |
| Most aware | ”I want your product, on your paid plan, today” | A frictionless trial-to-paid path, a clear upgrade CTA |
This matters because the stage changes what “the competition” even is. For a problem-aware buyer your rival is the spreadsheet, not another vendor — you compete with education about cost. For a product-aware buyer you’re in a direct, named comparison, and Row A’s weakness analysis becomes the whole argument. Read where your funnel mostly finds people and the rest of the grid snaps into focus.
Differentiation on Trial
Here is where the internal work from Company goes on trial against the field. For every claim you make, run one test: could a competitor say this exact sentence too? If they can, it isn’t differentiation — it’s category noise every vendor’s homepage already makes.
Put your claims in two piles. “Powerful,” “easy to use,” “the all-in-one platform,” “loved by teams everywhere” — every SaaS company says these, in the same three fonts, and a buyer who’s read ten homepages this week has learned to skip them entirely. They fail the test. Now the other pile: your actual time-to-first-value (measured, not guessed), a specific integration a rival doesn’t have, a pricing mechanism that scales the way your ICP’s usage actually grows, a migration path from the named competitor that takes an afternoon instead of a quarter. A rival can’t copy these by editing a headline — they either built the integration or they didn’t, their onboarding either takes ten minutes or it doesn’t. That’s the difference between a claim and a mechanism, and only the mechanism survives contact with a buyer who has already read the comparison pages.
The Desk-Bound Read
One failure mode rots everything downstream, and it never announces itself: the founder who fills this whole grid from memory. Competitors described from the pitch they gave eighteen months ago. Reviews recalled instead of reread. Rank “known” from a gut feeling instead of pulled from Search Console. The cells get filled, the words look like findings, and every one is a projection of an old assumption wearing a finding’s clothes. The damage surfaces two stages later — a comparison page that attacks a weakness the rival fixed last quarter, an expansion keyword that turns out to have no real volume, a differentiation claim built on a competitor gap that no longer exists. The fix is uncomfortable and simple: go and look. Open the actual G2 page, not your memory of what it said at launch. Pull the actual rank data. Market Awareness is a research discipline before it’s a thinking one, and the thinking is only as good as the looking that fed it.
AI Earns Its Place Here
This is a stage where the tutor beside this lesson earns its keep — not by inventing your market read, but by organizing the research you gather far faster than you could by hand. You do the looking: sort your real rivals into their six tiers, pull their actual review complaints, check your own rank on the terms that matter. Paste that raw material into the chat panel, along with your Company Blueprint, and ask it to arrange the findings into the three grid rows, surface where your mechanism meets a rival’s documented weakness, and name the channel your own score table ranks highest.
The discipline is the one that governs every stage in this playbook: the tutor works from your observations, not its training data. Ask it to invent your competitive set and it will hand back a generic SaaS-category list that could describe any company in your space — confident, plausible, and useless. Feed it your real reviews, your real rank, your real channel scores, and it becomes a fast synthesizer of the looking you already did. It multiplies your thinking. It does not do your seeing, and it never invents a review count, a rank position, or a competitor’s weakness you haven’t verified — you’ll capture the real findings on the worksheet that saves alongside this lesson.
What’s next
You now know the field — who’s really in your competitive set and in which tier, which forces are moving the category, and where the channel ground is least crowded. But a field is only ever played for a buyer, and so far that buyer has been an abstraction: “the ICP,” weighed against rivals, drifting through pricing trends. Time to make them specific — a real champion, a real economic buyer, a real end user, each with a trigger event you can name and a fear you can answer. That portrait is the work of the next stage, the one that turns this reading of the field into something you can actually write marketing from: Customers.