Personas
In B2B sales, you don’t sell to a faceless organization; you sell to people within that organization. These people have job titles, goals, worries, and biases. They are the ones who will champion your product, sign the check, implement the solution, or potentially block your deal. Buyer personas are detailed, research-based archetypes of these key individuals involved in the purchasing decision. While your ICP defines which companies are a fit, personas help you understand who within those companies you need to win over and how to speak their language.
Most B2B purchases involve multiple stakeholders, commonly referred to as the “buying committee” or “buying group.” For example, if you sell a cybersecurity tool, the buying committee might include the CIO (who signs off), the CISO or security manager (who evaluates the tech), maybe an IT admin (who will use it day-to-day), and even procurement or finance (for contracts). Each of these roles cares about different things.
Defining buyer personas ensures your marketing and sales approach can address each stakeholder’s perspective. Companies that ignore personas risk having spot-on messaging for one role but completely missing the mark for another. A scenario from experience: a client selling marketing software had a great ICP (mid-market SaaS firms) but their messaging failed because they assumed the CMO was the buyer, when in fact it was the Marketing Operations Manager who drove the purchase—someone with very different priorities. The CMO cares about big-picture brand and ROI, whereas the ops manager cared about integration ease and workflow improvement. By pitching high-level strategic value, the startup wasn’t addressing the day-to-day pain of the real buyer, and deals stalled. Once they refocused the persona on “Ops Olivia” instead of “Executive Ed,” their outreach started resonating.
COSS startups often navigate a two-level persona structure: the end-user persona (typically a developer or technical practitioner) and the economic buyer persona (often a manager or executive who signs the check). Understanding both – and how they relate – is crucial in Phase 1 market definition, because your messaging and funnel will need to cater to each at different points. As Dave Kellogg might say, you have to sell to the person using the product and the person buying the product, and they ain't always the same.
Creating Effective Buyer Personas
Identify the key roles in the buying process for your product. Typically, these include: the economic decision-maker (e.g. VP or C-level who controls budget), the end-user or champion (the person whose daily work is most impacted and who often initiates the search for a solution), and any technical approvers or influencers (like the IT department, security, or an external consultant). In a smaller sale, one person might wear multiple hats; in larger enterprises, you might have 5-6 personas (e.g. user champion, manager, VP, procurement, IT, finance, etc.). List out who these people are by title/role.
For each persona, flesh out their profile in detail. A robust persona goes beyond title; it captures context and psyche. Here are key elements you should include for each buyer persona:
- Role and Responsibilities: What is their job and what does a day in their life look like? Essentially, what are they responsible for? (E.g., “IT Manager Mary – oversees all employee hardware and software, responsible for keeping systems running smoothly, manages a small team of 3 admins, reports on uptime and security incidents.”) By clarifying this, you understand their environment and pressures.
- Goals and KPIs: How do they measure success, and what objectives are they trying to achieve? Every persona has something that “keeps them up at night.” For instance, Mary the IT Manager might have a goal of reducing system downtime below X% or rolling out new technology faster. If you know what they’re targeted on, you can position your product as helping hit those targets. A marketer persona might live and die by lead volume or campaign ROI; a sales manager by hitting quota; a CFO by cutting costs or managing risk.
- Pain Points and Challenges: What specific problems or frustrations do they face (especially related to the area your product addresses)? This is critical: why would they care about your solution at all? List the pains. E.g., Mary might be frustrated by spending too much time manually provisioning accounts, or worrying about security breaches due to user error. Ideally, these pain points align with the problems your product solves. If they don’t, you either have the wrong persona or your product-market fit is off. Each persona might experience the core problem differently. For example, the marketing ops person, sales leader, and customer success manager in Zapier’s case all suffered from disconnected workflows, but in different ways (lead routing chaos vs. reporting headaches vs. manual data updates). Your persona descriptions should reflect those nuances.
- Decision-Making Authority: How much power does this persona have to make or influence the purchase? Do they have final signing authority, or do they need approval from someone else? It’s important to know if you’re dealing with a recommender vs. a decision-maker. For instance, an Operations Manager might be able to choose a tool up to a certain budget, but anything above $10k annual spend might require CFO approval. Knowing this helps your sales approach (you might arm your champion with ROI data to convince their boss, for example). Also, note if they are the gatekeeper for anything. Sometimes a mid-level IT person can veto a purchase on security grounds even if the VP wants it – that IT person becomes a key persona (the “blocker”) you must address.
- Information Sources & Buying Behavior: Where does this persona go to research solutions or educate themselves? Do they attend industry conferences, read certain blogs, hang out in specific online communities, rely on analyst reports, or simply Google around? Also, what format of info do they prefer – detailed whitepapers, quick demo videos, peer recommendations? Understanding this helps you reach them. For example, developers might avoid marketing-speak and instead trust technical documentation or peer reviews on Reddit/Stack Overflow. Executives might prefer thought leadership articles or referrals from colleagues. Map out how each persona likes to learn and what channels you’re likely to find them on (LinkedIn, Twitter, niche forums, trade magazines, etc.).
- Objections and Concerns: What reasons might this persona hesitate to buy your product? Common ones could be price (“Is this within my budget?”), implementation effort (“Will this be a headache to roll out?”), risk (“Will this disrupt my existing systems or could it get me in trouble if it fails?”), or skepticism (“Does this really work as advertised? Show me proof.”). Anticipating objections for each persona means you can proactively address them. For instance, if a likely objection from a CFO is cost, prepare ROI cases and flexible pricing options; if from a technical persona it’s security, have documentation and answers ready. Also consider personal fears – e.g., an IT admin might fear a new tool automating part of their job (job security concern). Acknowledge and plan for these in your approach.
To make this concrete, let’s say our startup sells a cybersecurity SaaS. We identify two main personas: “Security Steve” (the Director of Security, who cares about threat detection efficacy and compliance, has authority to choose vendors up to a point, gets info from security conferences and blogs, and whose typical objections are “will this integrate with our SIEM and is it proven?”) and “CIO Cindy” (the Chief Information Officer, who cares about overall risk reduction and cost, will sign off on the purchase if convinced, gets info from high-level reports and peer CIO networks, and whose objections are typically about ROI and not adding too much complexity). By detailing Steve and Cindy in this way, we ensure our marketing has whitepapers and case studies for Cindy highlighting ROI and strategic impact, while also having technical datasheets and demo videos for Steve showing integration and detection capabilities. Our sales discussions with Steve will drill into features and compliance checkboxes, whereas with Cindy they’ll focus on business outcomes and cost-benefit.
A quick pro-tip: give each persona a name and a story. For internal use, this makes them more memorable and “real.” E.g., “Operations Olivia: 35-year-old Marketing Ops Manager at a SaaS company, spends her day stitching together CRM data, gets frustrated by manual reports, needs everything to integrate, cautious of tools that lack Salesforce integration, etc.” It might feel a bit fluffy, but it helps your team empathize with the persona and keep messaging consistent. Some companies even have cartoon images or actual customer quotes to bring personas to life internally.
Once you’ve defined personas, share them with everyone: marketing, sales, product, customer success, etc. Everyone should be on the same page about who you’re targeting and what those people care about. This alignment ensures, for example, that your sales reps don’t go into a technical demo with a CFO persona who really wanted to hear about business value (misalignment like that can kill deals).
Negative Personas: Who NOT to Target
Equally important as knowing who your ideal customers are is knowing who your non-ideal customers are. These are sometimes called negative personas or exclusion profiles. A negative persona is a profile of a customer that you do not want to spend resources pursuing – because they are poor fits, unlikely to buy, or likely to churn quickly even if they do buy. It might sound odd (“Why would I ever turn away a customer?”), but focus is two-sided: it’s about where to focus and where not to. Especially in early-stage companies, chasing every possible lead is tempting, but some leads will do more harm than good. Defining negative personas helps your team recognize these in advance and avoid wasting time on them.
Negative personas can be entire companies (account-level disqualification criteria) or specific buyer types.
- At the company level, think about characteristics that signal a bad fit: - Too small or too large outside your serviceable range (e.g., if your solution requires a dedicated team to use properly, a 5-person company is a bad fit). - Certain industries you cannot support well or that have very specialized needs you didn’t build for. - Companies using a tech stack that is incompatible (e.g., if your software only runs in the cloud, a company that insists on on-premise only is a no-go). - Perhaps companies with a business model that clashes (maybe your product is for B2B companies, so a B2C company is a bad prospect, or vice versa). - Or those with a known high churn likelihood – for example, if you notice early on that clients in X situation never stick beyond a month, mark that as a “no-go” profile.
- At the persona or deal level, consider: - People who are “tire-kickers” – for instance, students or interns downloading whitepapers that will never turn into buyers. - Job roles that might love chatting but can’t actually influence a deal (e.g., an enthusiast lower-level user with no budget authority – without a pathway to a decision-maker, engaging heavily with them could be low ROI). - Also, any “red flag” behaviors: say a prospect who insists on a feature that your product doesn’t have and that’s not on your roadmap; that could indicate they’ll never be happy or will require a custom build – which you should avoid unless strategically worth it.
To define negative personas, look at past experiences or reasonable assumptions: “We don’t sell to government agencies because our product isn’t compliant with their requirements – government org = negative persona for now.” Or “Mom-and-pop shops churn from our SaaS quickly, probably because they have no time to use it – so very small businesses are a negative persona.” Some companies even create a funny character like “Freemium Freddy” – a persona who will use all your free resources but never pay. That reminds marketing not to overly cater to non-buyers.
By documenting these, you can keep your marketing and sales efforts focused on high-quality prospects. It also helps morale: your team won’t beat their heads against a wall chasing deals that are doomed from the start. As one marketing guide notes, understanding who is not a good fit is as important as knowing who is. In practice, you might maintain an “exclusion list” of criteria in your lead qualification. For example, if an inbound lead comes in and they match a negative persona (say, a student or a tiny company with no revenue), you might send them a polite no-thank-you or keep them on a low-touch nurture track, rather than passing to sales. This prevents burning cycles on leads unlikely to convert. One startup founder described how initially they’d get excited by any big logo that showed interest – until they wasted months on a Fortune 100 prospect that demanded custom features and a 9-month pilot, only to not buy. It nearly derailed the young company. After that, they set a rule: if a prospect required too much customization or wasn’t in their target use-case, they’d politely walk away – a painful but necessary discipline to protect the roadmap and resources.
In short, negative personas keep you honest. They remind you that not all revenue is good revenue. A hard-won sale to a bad-fit customer can turn into a support nightmare, a bad reference, or churn that drags down your metrics. By knowing who you don’t want to attract, you can actually improve overall customer satisfaction and economics – you’ll spend time on the customers who truly benefit and stick around.
Validating and Refining Personas
Creating personas involves some educated guesses. To ensure your personas remain accurate and useful, you should validate them with real data and feedback over time:
- Internal feedback: Share persona definitions with your sales, customer success, and product teams to get their input. These teams interact with customers daily and can tell you if, for example, the challenges you’ve listed ring true, or if they’re hearing different objections than you anticipated. A sales rep might say, “Actually, when I talk to Operations Olivia, she also frequently worries about data security – we should add that to her concerns.” Incorporate that feedback.
- Customer interviews: There’s no substitute for talking directly to your customers or prospects. Conduct occasional interviews specifically to validate persona assumptions. Ask them about their goals, what info sources they trust, what nearly stopped them from buying, etc. If you have a friendly customer that fits your ICP, say “Could I pick your brain for 30 minutes? We’re refining our understanding of folks in your role.” Their answers can reveal if you’re focusing on the right things. Perhaps you assumed CFOs care mostly about ROI, but an interview reveals they care even more about internal political risk – aha, you’d then adjust your persona write-up and sales approach accordingly.
- Survey and data analysis: If you have enough volume, survey customers or use analytics. For example, you might find via analytics that certain content pieces (e.g., technical blog posts) are only being read by certain titles – confirming that your technical persona does seek out detailed content. Or a survey might find that 80% of your champion users have one job title and they all share a certain pain. Use these insights to refine your personas’ descriptions and priorities.
- Test your messaging: This is a practical validation – run targeted campaigns (ads, email, etc.) that are tailored to a persona’s presumed pain point and see if they perform well. For instance, create two ad variations, one speaking to Persona A’s pain and one for Persona B’s, and target them accordingly. If one resonates (CTR, conversion) much higher than the other, it might mean your understanding of one persona is spot on while the other needs work (or that one segment is more receptive). Continuous A/B testing of persona-based messaging can fine-tune your approach.
- Keep personas updated: Markets and roles evolve. The priorities of a CIO today might differ in a year or two (think how quickly “concern about remote work tools” became a thing in 2020). Set a reminder to revisit persona definitions periodically (say every 6–12 months, or when you launch into a new segment). Update their pain points, add new objections you’re hearing, remove stuff that’s no longer relevant. One common mistake is letting personas get stale or treating them as a one-and-done exercise. Don’t laminate them; iterate them. Just as your ICP should evolve with data, your personas should evolve with feedback.
By validating and refining, your personas remain a reliable guide for crafting spot-on messaging and sales tactics. And when personas are accurate, the impact is tangible: marketing campaigns see better engagement, sales cycles shorten (because you’re talking their talk), and product features hit the mark more often. It all contributes to that holy grail of product-market fit feeling solid – because you truly understand your customer at both the organizational and personal level.
At this point, we’ve identified what market and segment we’re targeting, the ideal customer profile within that market, and the personas of buyers we need to persuade. The next consideration is the broader market dynamics in which these customers operate and how that context can influence your go-to-market approach.