[drop_cap]A[/drop_cap]sk a SaaS founder to describe their customer and you’ll get a job title and a company size: “ops managers at 50–200 person companies.” It has a role and a headcount range, so it feels like an answer. It’s a description of a segment, not a person — and you can’t write an onboarding flow for a segment. Your real buyer isn’t one person either. It’s three: the champion who found you and signed up on their own credit card, the economic buyer who has to approve the annual invoice, and the end user who has to actually live inside your product every day whether they asked for it or not. Write for the segment and you get marketing that describes everyone in the bracket and persuades none of them. Write for the three real people and every later stage gets sharper for it.
That gap — between the firmographic bracket and the three specific humans behind the signup, the approval, and the daily login — is the whole subject of this lesson.
Demand Here Is Made by Events, Not by You
Most marketing tries to create desire. In B2B software, almost nobody is talked into starting a trial cold. A trigger event happens first: a spreadsheet finally buckles under its own row count, a manual process eats an afternoon that used to take ten minutes, a compliance requirement lands with a deadline attached, an existing tool gets acquired and its roadmap goes quiet, a new hire arrives and asks “wait, we don’t have a tool for this?” You don’t create the need. You win the search that follows the trigger.
That changes the target. It isn’t a firmographic segment sitting still; it’s an event firing, and each event carries its own urgency and its own channel:
- The spreadsheet breaks — a champion hits a hard ceiling (row limits, version conflicts, no audit trail) and searches “[category] software” from their desk, mid-workday. Urgency high, evaluation compressed into days.
- A compliance or security deadline lands — usually surfaced to the economic buyer, who now needs a defensible vendor before an audit date, not the cheapest or flashiest one.
- A tool gets sunset or acquired — the whole team is displaced at once, searching “[competitor] alternative” with genuine urgency and real switching-cost anxiety.
- Headcount growth outpaces the current process — slower-building, usually noticed by the end user first, who complains to the champion long before anyone opens a vendor’s website.
- A new hire imports a habit from elsewhere — “we used [tool] at my last job and it was so much better” — low urgency, but a durable seed that often becomes the champion’s whole case internally.
Read the event and you already know the urgency, the buyer sequence, and the register. Miss it and you’re writing a calm, feature-led homepage for someone whose dashboard just went down mid-quarter.
Why the Depth Pays
Most SaaS marketing sites are built from the firmographic bracket and stop there, because a job title and a company-size range fits neatly in a targeting field. A thin avatar produces generic marketing, and generic marketing is the expensive kind — it has to shout, because it failed to resonate. “The all-in-one platform for growing teams” is what you write when you don’t know which fear is keeping this specific champion up at night before the renewal conversation.
The avatar earns its hour because it doesn’t add to your later stages — it multiplies them. Your onboarding flow answers the champion’s real time-to-first-value anxiety instead of a generic tour. Your pricing page speaks to the economic buyer’s actual approval friction instead of hiding behind “contact sales.” Your in-app messaging respects the end user’s real complaint instead of adding one more notification they’ll learn to dismiss. Get the three avatars wrong here and every one of those stages inherits the error. Get them right and each stage inherits the same precision at once, every time it runs.
The Customer Avatar Grid
The Customer Avatar Grid is the tool of this lesson — a 3×3 that forces you past the firmographic bracket into the person. Three layers down the side (what’s observable, what drives them underneath, where they’re trying to go) and three orientations across (who they are, what they fear, what they want). Nine cells, and together they produce a portrait complete enough to write every later stage from.
Each layer buys you something different. Observable reality hands you the targeting and the exact words to use in your copy. Underlying drives hand you the emotional truth — the fear your marketing has to meet and dissolve. Future state hands you the transformation the customer is really after, which is the only honest ground a case study, a renewal, and an expansion deal are ever built on.
| 1. Identity & Context | 2. Pains & Fears | 3. Goals & Aspirations | |
|---|---|---|---|
| A. Observable Reality | Role, team size, the tool they’re replacing, the event that started the clock, the platforms they search | Stated frustrations in their own words — the support tickets, the trial-abandonment survey answers | The outcome they say they want: activation on day one, the report that finally runs itself |
| B. Underlying Drives | How they see this purchase — a career-defining fix, a chore, political capital on the line | The fears beneath the complaints: looking foolish for recommending the wrong tool, a migration that goes badly, being stuck with a bad contract | Dominant need: Certainty — that this tool will still be here, working, in a year |
| C. Future State | Watering holes — where they ask “what do you use for this?” before they trust a landing page | Cost of inaction: the spreadsheet keeps growing, the manual process keeps eating hours | Vision: the tool just works, nobody asks about it in standup anymore, it quietly earns its renewal |
Work it top to bottom. Row A is evidence — you should be able to point at a support ticket, a churn survey answer, or a sales call note for every cell. Row B is inferred from that evidence. Row C is the projection forward, into the consequence of doing nothing and the outcome they’re actually chasing.
Three Avatars, Not One
Your Company lesson named your ICP. This lesson turns that into three distinct people, because the buying committee in B2B software is rarely one person, and collapsing them into a composite is the single most common way a SaaS avatar goes wrong.
The Champion. The person who found you, ran the trial, and is staking some personal credibility on the recommendation. A1: an individual contributor or team lead, searching from their own desk after the trigger event fired, often on a free or self-serve tier before anyone else knows they’re evaluating. A2: “does this actually save me time or just add another tab,” “will I look bad if I recommend this and it doesn’t stick,” “how long until my team is actually using it.” A3: activation fast enough to feel the win before the trial expires, and a tool the rest of the team adopts without a fight. B1: they’re often quietly ambitious — this is a chance to be the person who fixed something, and that’s exactly why a slow, confusing trial reads as a personal risk, not just a product flaw. B2: the fear of championing a tool that flops in front of their manager or their team. B3: certainty that the tool will actually get adopted, not just approved. C1: peer communities, Reddit threads for their specific role, “what do you use for X” posts. C2: if the trial doesn’t click fast, they quietly go back to the spreadsheet and never mention you again. C3: they’re the one who suggested it in the retro, and the team never wants to go back.
The Economic Buyer. The person who signs the invoice or approves the budget line, and who may never log into the product at all. A1: a manager, director, or finance approver, usually one step removed from daily use, evaluating cost against a budget cycle. A2: “is this actually going to get used or shelf-wared in six months,” “what happens to our data if we cancel,” “why is this line item growing every quarter.” A3: a predictable cost, a vendor that survives an audit, no surprise invoice. B1: accountable for the spend without necessarily understanding the workflow it replaces — which is exactly why ROI has to be stated in terms they can defend upward, not in feature language. B2: approving a tool that turns into a wasted line item nobody uses, or a vendor that disappears and takes the team’s data with it. B3: certainty that this spend is defensible at the next budget review. C1: peer conversations at their level, industry reports, the vendor’s own security and compliance page. C2: the request sits in a queue, the champion loses momentum, and the team quietly reverts to the old process. C3: the line item renews without a fight, because the usage numbers already make the case.
The End User. The person who has to live inside the tool every day, whether or not they were part of choosing it. A1: often the largest group and the least consulted, inheriting the tool after someone else decided. A2: “why did we switch, the old way worked fine for me,” “this is one more login I have to remember,” “nobody trained me on this.” A3: a tool that doesn’t get in the way of the work they were already doing. B1: mild resentment at a change they didn’t ask for, which curdles into real churn risk if the first weeks feel harder than the tool it replaced. B2: being forced to learn something new for no personal benefit, and being blamed when it goes wrong. B3: certainty that this won’t make their job harder than it already is. C1: internal Slack channels, the champion’s own rollout messaging, in-app help. C2: quiet workarounds and shadow-spreadsheet reversion that never shows up as a support ticket but shows up as unused seats at renewal. C3: six months later they’ve forgotten the old tool existed.
Build each of these its own grid — a champion evaluating on their own initiative and a reluctant end user inheriting the decision are not the same person, and one composite avatar would mislead every stage downstream, especially onboarding.
How to Gather the Intelligence
You don’t need a formal interview program to start — most SaaS businesses already have an honest corpus sitting in tools they already pay for.
Support tickets are the first source. Read them for the exact language a frustrated user reaches for — that vocabulary is your A2, written by the people living the pain in real time.
Lost-deal and churn-exit notes are the richest source of all. A prospect who chose a competitor, or a customer who cancelled, is telling you exactly what they didn’t get. A pattern — “too complicated to set up,” “support never responded,” “we outgrew the free tier and the paid plan didn’t make sense” — is the position you can credibly occupy against that same competitor next time.
Review sites (G2, Capterra) surface both your own customers’ language and, just as usefully, your competitors’ one-star reviews — read those the way you’d read a competitor’s churn notes, because that’s exactly what they are.
Sales call recordings are a live feed of A2 and B2 in real time — the objections a rep actually hears, in the buyer’s own tempo, not a tidied paraphrase of them written up after the fact.
What You’re Actually Hunting For
Before you sit down with the grid, set the aim: you’re hunting for tension, not just information. The most useful thing in a SaaS avatar is always a gap — between the champion who wants to move fast and the economic buyer who needs six weeks of due diligence, between the end user who resents the change and the same end user who’ll defend the tool at renewal once it’s saved them real time, between “we could build this ourselves” and the maintenance cost nobody wants to say out loud in the room. That tension is where your marketing and your onboarding both live.
And a good share of any avatar is inference — a confident word for guessing carefully. Row A you can cite: a ticket, a call, a review. Rows B and C are conclusions you reached by reading between the lines of what people actually said. That’s legitimate; it’s the whole job. It’s only honest if you keep the seam visible — fill what you know before you reach for what you assume, and mark the cells you’re less sure of, so you know exactly what to listen for as more tickets and more calls come in.
AI Earns Its Place Here
Once you’ve pulled your raw material — ticket extracts, churn-survey answers, the objections your sales team hears on repeat — the chat tutor beside this lesson can compress the synthesis fast. Feed it the actual language, not a summary of it, and ask it to map what you’ve gathered onto the nine cells for each of the three avatars. The verbatim quotes are the one thing it cannot invent, so paste them in whole.
Then apply the judgment a model can’t. It will reach for generic “buyers want ROI” filler where your evidence says something sharper — push it back to your customer’s own words. It will happily invent a fear you never actually heard in a ticket or a call — cut it. The tutor organizes and deepens your evidence fast. You make the final call on which cell is grounded and which is still a careful guess, and you’ll capture the finished grids on the worksheet that saves alongside this lesson.
What Good Looks Like
The deliverable is three completed avatars — champion, economic buyer, end user — with Row A grounded in a ticket, a call, or a review you can point to, and Rows B and C inferred close enough to that evidence that you could defend each cell out loud. The test isn’t whether the grid feels full. It’s whether reading a cell fires a downstream decision: B2 should hand you an objection your sales page needs to answer, B3 should set the register for your onboarding emails, C1 should hand you a channel list for the next stage. When the grid is coherent — when the stated pain in A2 points at the fear in B2, and the fear resolves into the need for certainty in B3 — the avatar is finished.
What’s next
You now have two of the Foundation’s pillars: your market and the three people buying inside it. Each is useful alone, but the value is in the synthesis — and in one specific question. Does what you offer, what your market rewards, and what your champion, buyer, and end user actually need all point the same way? A product that positions on enterprise-grade security, spends its ad budget chasing the cheapest self-serve clicks, and faces an economic buyer who cares most about a clean audit trail is pulling against itself, and no tactic downstream will fix that incoherence. Resolving it — deciding which pillar governs when they disagree — is the work of the next stage: Alignment.