How to define your SaaS target market

Most target market documents in SaaS are written to be agreed with, not used. They describe a company that would obviously benefit, everyone nods, and the media plan stays exactly as broad as it was the week before. A target market definition earns its place in SaaS marketing when it causes somebody to turn down revenue, cut a campaign, or refuse a segment the sales team likes. That is the bar this page works to.

Four filter types that make a target market usable

A usable definition has four layers of filter, and most teams write only the first. Firmographic filters describe the company, technographic filters describe what it already runs, behavioural filters describe what it does before buying, and situational triggers describe why it is looking now.

The fourth row is the one that changes results and the one most teams omit. Firmographics tell you who could buy. Triggers tell you who is buying this quarter, and a trigger-led account list converts several times better than a firmographic one at the same spend, because you are arriving during the window when somebody has a budget and a problem in the same week.

Behavioural filters are the ones you can only build from your own data, which makes them the most defensible and the last to arrive. A company with under 200 customers rarely has enough signal to claim that two comparison page visits predict a deal. Start with the three filter types you can source externally, and add the behavioural layer once you have 40 or so closed won accounts with clean session history attached.

Gartner puts six to ten decision makers in a typical complex B2B software purchase, which means your filters are describing an account rather than a person. That distinction matters when you get to channels: you are not trying to reach one operations manager, you are trying to be findable by six people who will compare notes in a room you are not in. The wider SaaS marketing definition covers why that shapes so much of the discipline.

Mine closed won and churned accounts before you write a word

The pattern is already in your CRM. Export the last 40 closed won accounts and the last 20 churned ones into a single sheet with columns for employee count at signup, industry, the tool being replaced, the title of the person who signed, the acquisition source, days from first touch to close, and whether the account was still paying at month twelve.

Then do one thing: look for the attribute that separates the two groups, not the attribute that is most common in the winners. Those are different questions. Everyone has 60% of their customers in one industry because that is where the first sales rep had contacts. The attribute that predicts retention is usually less obvious, and it is often a technographic or structural one, like whether the account had a dedicated operations hire before buying.

Be careful with one trap in this exercise. The attribute most common among your winners usually records where your first salesperson had contacts, not a property of the market. Look for attributes present in the retained group and absent from the churned one, and stay suspicious of anything appearing at roughly the same rate in both, however satisfying the story around it is.

Twenty churned accounts is a small sample and it will not give you statistical certainty. It will give you a hypothesis sharp enough to change next quarter’s spending, which is the actual job. Waiting for a defensible sample size is how companies spend two more years marketing to everyone.

The negative ICP saves more money than the positive one

A positive ICP tells you where to spend, and spending takes months to show results. A negative ICP tells you where to stop, and stopping shows up in the bank account this month. That asymmetry is why the refusal list belongs on page one, not in an appendix.

Four exclusions show up repeatedly in B2B SaaS, and each has a specific tell:

• Accounts under a size threshold that close easily and churn by month five, usually because there is nobody to own the tool internally
• Buyers who arrive through a discount trigger, such as a deal site or an annual sale, and then anchor every renewal against that price
• Agencies or consultancies reselling your seats under a pricing model designed for a single company
• Regions where your data residency, language or support hours answer is weak enough that the deal dies at security review anyway

Each exclusion should name the evidence. Not “small companies churn” but “accounts under 50 employees show 41% logo churn by month twelve against 9% above that line, across 61 accounts”. That sentence survives a meeting. The adjective version does not.

The evidence requirement cuts both ways, and that is what makes a refusal list credible. If you cannot produce a number, the exclusion is a preference and should be labelled as one. Preferences belong in the document as long as they are marked, because the next person to read it needs to know which lines were derived from data and which were asserted in a meeting.

Refusals need a review date as much as the positive criteria do. A segment that churned badly two years ago may be servable today because onboarding improved or the product shipped the missing integration, and nobody reopens an exclusion unless the document tells them to.

Size the segment by counting named accounts, not slicing TAM

The top down version goes like this: the market is 40 billion dollars, we need 0.1%, that is 40 million dollars, next slide. Nobody has ever made a budget decision from that number, and everyone in the room knows it.

Count instead. Build the filtered list in a tool that returns actual company names, apply each filter in sequence, and record how many accounts survive each cut. What you want at the end is a number you could email to a sales leader as a spreadsheet, because a list of names can be worked and a percentage cannot.

The count does three things a TAM slide cannot. It tells you if the target market can support the plan at all, it tells you how many accounts each rep would need to cover, and it tells you immediately when a channel cannot possibly deliver the volume you are assuming, which is the calculation that kills most over-optimistic media plans. Two further numbers make the count defensible in a planning meeting. Coverage: how many of the qualifying accounts have been touched in the last 90 days by any channel. Engagement depth: how many have two or more known contacts engaged. Those two turn an account list from a marketing artefact into something a sales leader will use on a Monday, and they give you a weekly progress measure that has nothing to do with traffic.

Feed the resulting account count into the SaaS marketing budget calculator and the spend question tends to answer itself.

Worked example: an 18K dollar ACV workflow tool

Here is the full chain for a workflow automation product selling at 18,000 dollars average annual contract value into operations teams. Every cut below is a filter from the four types above.

Cut	Filter applied	Accounts remaining	Data source
Start	North America, 200 to 2,000 employees	9,400	Sales Navigator firmographic search
1	Field services or industrial distribution only	1,180	Industry codes plus manual review
2	Runs Salesforce or NetSuite as system of record	620	Technographic enrichment
3	No existing workflow automation platform in place	455	Technographic exclusion
4	Operations leadership hire in the last 12 months, or a second site opened	340	Job postings and press monitoring

Now the planning math. Those 340 accounts at 18,000 dollars each represent about 6.1 million dollars of addressable ARR. At a realistic 8% annual win rate against a defined list, that is 27 customers and roughly 490,000 dollars of new ARR in a year.

Two things make a count like this credible to a sceptical sales leader. Show which filter did the most work, which here is the industry cut taking 9,400 down to 1,180, and show the accounts lost at each stage so nobody suspects a number reverse-engineered to be comfortable. A list arriving without its filter history gets treated as marketing arithmetic and quietly ignored.

That number is small enough to be uncomfortable and useful enough to plan from. With 340 named accounts, a broad paid social campaign is obviously wrong, targeted outbound is obviously right, and a content programme aimed at the specific operational problem those 340 companies have is worth funding for two years because the audience will not change. Three channel decisions fall out of one count, which never happens with a TAM slide.

The uncomfortable part is the honest tradeoff. A tight count like this caps your growth ceiling, so you need a second segment identified before the first is half consumed, and you need to know which filter you will relax first. Usually it is the trigger filter, because dropping it takes you from 340 back to 455 accounts at a lower expected win rate, which is a decision you can model rather than stumble into.

When to add a second segment, and how to tell it is time

A single ICP is right until it can no longer carry the plan. The signal is arithmetic rather than emotional: when your named account list cannot support next year’s target at a win rate you have actually achieved, you need a second segment or a higher contract value.

Run the check once a quarter. Take the qualifying account count, multiply by contract value, multiply by your achieved win rate against that list, and compare the result with the plan. In the worked example above, 340 accounts at 18,000 dollars and an 8% win rate produces about 490,000 dollars a year, which supports a plan up to roughly that figure and not a dollar further.

When you do add a segment, give it a separate document with its own filters, refusal list and account count rather than widening the first one. Widening is how a sharp ICP decays into a vague one: a criterion gets relaxed to fit a deal, then another one does, and eighteen months later the document describes any company with employees. Two tight documents beat one loose one, and they make it obvious when a campaign is serving neither.

Order of expansion matters as well. Adjacent industry with the same job title is usually the cheapest move, because the message survives and only the proof needs swapping. Same industry with a different job title is harder, since it needs a new message hierarchy. A different size band is hardest of all, because it changes the motion, the pricing and the viable channel set at the same time.

What the ICP changes on your homepage

A finished target market definition should be visible above the fold within a week of being signed off. If your homepage would read identically before and after the work, the work did not happen.

Three things change in practice. The qualifier in the headline gets specific, so “workflow automation for growing teams” becomes “workflow automation for field service operations teams running NetSuite”. The social proof block gets re-cut so the logos shown match the segment rather than showing the three biggest names you ever sold. And the self-qualification content gets added, usually a short line naming who the product is not for, which reads as confidence and removes bad-fit demo requests before they consume a sales hour.

The proof assets change too, and this is where most teams stop short. A homepage aimed at 340 field service operations companies should show a customer from that segment saying something specific about that job, rather than a generic quote about great support from whichever customer replied fastest to the request. One precise testimonial from the right segment outperforms four vague ones, because the reader is checking for somebody like themselves before they read anything else.

Naming who you are not for feels risky and it is the single fastest way to raise demo quality. Buyers outside the profile leave, buyers inside it recognise themselves and believe the rest of the page more. The mid market SaaS marketing playbook covers how far to push that on pages that have to serve two segments at once.

When to re-cut the ICP, and what breaks it

Re-cut every two quarters as a standing habit, and immediately after four specific events: a price change, a move up or down market, a new product line, and the arrival of a competitor who serves one of your segments better than you do.

The early warning signal is a widening gap between the segment that converts best and the segment your campaigns are aimed at. Track close rate and month twelve retention by segment monthly on one chart. When the best performing segment has not been your primary target for two consecutive quarters, the document is stale regardless of the date on it.

Product changes break an ICP quietly too. Ship a feature that removes an implementation barrier and a segment that was previously unservable becomes servable overnight, and nobody thinks to tell marketing. Put a standing item in the roadmap review asking which ICP criterion each shipped feature relaxes, and you catch it in the same quarter rather than two quarters later.

A second failure mode is quieter. The ICP stays accurate but stops being used, because the people who wrote it left and the new demand generation hire inherited campaigns rather than criteria. That is why the document needs a named owner and a review date, and why the criteria belong in the campaign brief template rather than in a strategy folder. B2B SaaS ideal customer profile goes deeper on the scoring model if you need to encode the filters into a system.

Write the refusal list first

Open a document, write four headings for the filter types, and fill in the firmographic row from memory in five minutes. Then stop and write the refusal list, because that is the half you will be tempted to skip and the half that changes spending this quarter.

Put one number at the top of the finished document: the qualifying account count. It is the figure people will remember, it makes the definition falsifiable, and it turns a strategy document into something that can be checked next quarter against what actually closed.

Then take it further in two directions. SaaS target market covers segmentation across multiple products and regions, and product market fit for SaaS marketers covers what to do when the data says your best segment is not the one the product was built for. The ICP template for SaaS has every field above laid out, so the first draft is an afternoon rather than a project.

Turn segment selection into a testable commitment

A target market should be narrow enough that the team can describe a recognizable customer task and the conditions required for adoption. Industry, company size and geography can help organize the account list, but they do not explain suitability by themselves. Two companies in the same category can have different workflows, authority and integration constraints.

Compare need, readiness and reach separately

Need describes the work the customer wants to improve. Readiness describes the people, access and capacity needed to implement. Reach describes whether the business can contact the relevant audience through a suitable channel and offer. A segment can score well on one dimension and poorly on another. Keep the evidence visible rather than averaging unknowns into an attractive score.

Use a weighted model only after the team agrees what the dimensions mean. Weights are management assumptions, not universal market facts. Test whether a modest change in a weight reverses the choice. If it does, the next step is to investigate the uncertain input rather than present the ranking as a precise answer.

Record the first segment and the exclusion rule

Write which accounts belong in the first evaluation and which do not. Explain the reason for each exclusion, such as an unsupported workflow or an unavailable implementation dependency. Do not use the negative profile to dismiss evidence that the offer itself is weak. Review rejected, stalled and adopted accounts together.

The category field guides provide different buying contexts. Use them as planning prompts and verify the actual segment through your own evidence.