The Outbound Sales Audit
A self-assessment framework covering ICP, personas, account tiering, signals, messaging, channel strategy, tech stack, rep productivity, measurement, coaching, and team structure. Built from 250+ B2B SaaS engagements.
Before You Start
Most outbound functions are not broken in one place. They are broken in the connections between places. The signal detection works, but the response is manual. The tiering model exists, but every account gets the same treatment. The coaching is strong in one region and absent in another. The tools are there, but reps have built workarounds because the workflow has too many steps.
That is the pattern I see across the 250+ B2B SaaS companies I have worked with. The individual pieces are rarely the problem. The system is the problem. And you cannot fix a system you have not diagnosed.
This guide gives you a structured way to look at your own outbound function and identify where the gaps actually are, rather than guessing or defaulting to the loudest complaint. It is not exhaustive (a full audit takes weeks, not pages), but it covers the areas where I most consistently find the problems that matter.
How to use this guide: Work through each section in order. For each area, ask the diagnostic questions of your team (not just leadership; talk to reps and RevOps too). Tick the questions where you are confident the answer is solid. The unticked questions are your diagnostic. The light recommendations at the end of each section point you toward the first thing to fix. If you find problems in multiple areas (you will), start with ICP and personas. Everything else depends on it.
A note on methodology: When I run a full outbound audit, I interview BDRs, managers, RevOps, and leadership separately. The answers rarely match. That gap between what leadership believes is happening and what reps actually experience is usually where the most important findings live. If you run this internally, talk to the people doing the work, not just the people designing it.
Ideal Client Profile and Personas
Whether you have defined the right companies and the right people within those companies tightly enough for outbound to work.
This is the foundation everything else is built on. If the ICP is too broad, reps waste time on companies that will never buy. If the personas are too shallow, reps default to generic messaging that does not land. Getting this right does not guarantee results, but getting it wrong guarantees wasted effort.
Questions to Ask
- Is your ICP defined tightly enough for outbound specifically (not just "who we sell to" but "who we should proactively reach")?
- Is there a floor (a minimum company size below which outbound is not worth the effort)?
- Does your ICP definition work across all regions, or are some markets too different for a single model?
- Have you segmented your ICP by industry or vertical? Different segments talk about the same problems in different ways.
- Are there specific technologies in a company's stack that correlate with buying? If so, are you using them as a targeting signal?
- Have you analysed your closed-won deals to identify which firmographic and technographic patterns actually predict conversion, rather than relying on assumptions?
- Are your personas defined at the sub-function level, or are you treating broad departments (e.g. "Operations," "Finance") as single personas? A Head of Procurement has fundamentally different concerns from a VP of Supply Chain, even though both sit within the same function.
- For each persona, can your reps articulate the specific problems that person faces, the language they use to describe those problems, and the messaging angle that resonates? Or do they just know the job title?
- Does your persona information change by company size? The problems a Head of Engineering faces at a 300-person company are different from those at a 2,000-person company.
- Is there a translation layer between knowing the persona and knowing the message? Reps may have access to persona documentation, but when they look at a prospect's LinkedIn profile, can they quickly answer: "What do I need to say to this person, right now?"
- Have you mapped which persona is typically the entry point vs the decision-maker in your closed-won deals? Does that inform who reps target first?
- Is your social proof matched by persona and company size, or are you using the same case studies for everyone?
The ICP is defined with exclusion logic (not just "who fits" but "who does not fit") and segmented by vertical where the problems differ meaningfully. A floor exists below which outbound is not worth the manual effort. Personas are defined at the sub-function level with specific pains, language, and messaging angles documented for each. Social proof and case studies are matched by persona and company size. Reps can look at a prospect's LinkedIn profile and quickly identify the right message, not just the right sequence.
The ICP is a broad description of "who we sell to" rather than a precise definition of who to target with outbound. No floor exists, so reps spend time on companies too small to justify the effort. Reps treat entire departments as one persona ("this person works in operations, so add them to the operations campaign") without distinguishing between sub-functions that have completely different priorities. Persona documentation exists but is too long to be practical.
Run a closed-won analysis to identify which firmographic patterns, personas, and entry points actually predict conversion. If the data shows that deals entered through one persona convert at a different rate or deal size than those entered through another, that directly informs who reps should target first. Ask three reps to describe the top three problems their primary persona faces. If the answers are vague or inconsistent, the persona work has not landed.
- Analyse your closed-won deals for ICP patterns. Which industries, company sizes, and technologies show up repeatedly? Use this to sharpen the definition rather than relying on assumptions.
- Set a floor. Define a minimum company size or deal value below which outbound is not worth the manual effort.
- Build a persona matrix that maps function, sub-function, and seniority to specific pains, language, and messaging angles. Make it practical enough that a rep can use it in the moment, not just during onboarding.
- Cross-reference: if your messaging (Section 04) is generic, the root cause is almost always here. Persona depth drives messaging quality.
Account Tiering, Selection, and Prioritisation
How accounts are scored, ranked, and allocated to reps, whether the tiering model drives different levels of outbound execution, and whether accounts arrive in a state where reps can actually work them.
Most companies have a tiering model. Very few have a tiering model that drives different execution. The tiering exists on paper, but every account gets broadly the same treatment: similar sequences, similar manual process, similar channel approach. A tier one enterprise account and a tier three account receive the same outbound motion. That means reps are spending the same effort on accounts with very different likelihood of converting.
Questions to Ask
- Are accounts arriving clean and enriched, or are reps spending the first weeks of each quarter cleaning their book?
- How many accounts in your TAM are unassigned and unworked? Do you know?
- What percentage of revenue comes from accounts your system was actively prioritising vs accounts reps found through their own initiative?
- Do your best reps self-source rather than work assigned accounts? If so, why?
- What is the rejection rate when reps receive assigned accounts? What are the reasons?
- Does a tiering model exist? Is it documented and understood by reps?
- Does the tier drive different execution (different channels, different personalisation depth, different automation levels)?
- Does the model incorporate potential account value (estimated deal size), not just ICP fit?
- If you have multiple scoring systems (fit, intent, engagement), do reps know which one drives which action?
- Are there competing scoring models that create confusion?
- What percentage of a rep's proactive effort goes to tier one vs tier two vs tier three?
Accounts arrive enriched with current tech stack, headcount, recent activity, and key contacts already populated. Reps spend their time working accounts, not cleaning them. Tier one accounts receive dedicated, multi-threaded outreach with deep research. Tier two gets semi-automated outreach with lighter personalisation. Tier three runs through fully automated sequences. When a lower-tier account shows new intent, it moves up.
Reps spend five or more weeks at the start of each quarter cleaning their book before meaningful outbound begins. A significant portion of revenue comes from accounts the system was not prioritising. Thousands of high-fit accounts sit unassigned. Multiple scoring systems coexist and compete. A 250-seat account and an 800-seat account both sit in tier one and receive the same treatment.
Pull your closed-won data and cross-reference it against your tiering or prioritisation model. If a significant share of revenue comes from untiered or unassigned accounts, your model is not capturing where revenue actually comes from. Ask three reps how they spend their first two weeks of a new quarter. If the answer involves data cleaning, you have an account quality problem.
- Audit your closed-won deals against your tiering model. How much revenue came from accounts the system was actively prioritising?
- Identify how many high-fit accounts are currently unassigned. These are accounts nobody is watching.
- Apply the principle: make reps responsible for working good accounts, not for cleaning bad ones.
- If multiple scoring systems exist, consolidate them into a single framework or clearly document which score drives which action.
- Define what each tier receives in terms of outbound treatment. Write it down. If a rep cannot tell you the difference in execution between tier one and tier three, the tiering is not working.
- Add account value as a dimension. Two accounts may both fit the ICP and show intent, but if one represents ten times the deal size, the outbound investment should differ.
- Cross-reference: if your measurement (Section 08) rewards volume equally across all tiers, reps will not differentiate their effort regardless of what the tiering model says.
Signals and Intent
What trigger events and intent data you are tracking, how they are surfaced to reps, and whether the gap between detecting a signal and acting on it is minutes or days.
Signal-based prospecting is the direction the best outbound teams are moving. Instead of asking "which VP of Engineering should we contact?" the question becomes "which VP of Engineering should we contact right now, and why?" The timing and the context change the conversation from cold to relevant.
But signal-based prospecting only works if the gap between detecting a signal and acting on it is short. If your reps receive an alert and then spend 30 minutes researching, finding contacts, selecting a sequence, and personalising the message, the signal may be hours or days old by the time the first touch goes out. Detection without automation is just noise.
Questions to Ask
- What signals are you currently tracking? List them.
- How are signals surfaced to reps? Email alerts? Slack? A dashboard? A task queue?
- What happens after a signal is detected? Is the response automated or manual?
- What is the actual time from signal detection to first outbound touch?
- Do you distinguish between first-party signals (website visits, content engagement) and third-party signals (intent data from external providers)?
- Is signal monitoring continuous, or does it run as periodic snapshots (e.g. bi-weekly)?
- Do you stack signals (treating multiple converging signals on one account as higher priority)?
- Does each signal type map to a defined play, or are reps expected to interpret the signal and decide what to do?
When a signal fires, the system enriches the account, identifies contacts, generates personalised messaging, and enrols the prospect into the appropriate sequence based on the signal type and account tier. The rep receives the prospect ready to review and call, not an alert asking them to go and do the research themselves. Signal monitoring runs continuously. Multiple converging signals escalate the account to a higher tier of attention.
Signals are detected and delivered as email alerts or Slack messages. The rep must then open a separate research tool, review the account, find the right contacts, select a sequence, personalise it, and enrol the prospect. The detection happens in near real time, but the response does not. By the time the rep acts, the timing advantage is lost. Accounts are monitored at the point of selection but not afterwards.
- Map each signal type to a specific play: what this signal means, why it matters, what the rep should do next, what message angle fits, and what the SLA is for response time.
- Separate detection from response. Most companies have reasonable detection. The gap is almost always in the response layer.
- Automate as much of the response as possible (enrichment, contact sourcing, personalisation, sequence enrolment) so that reps are reviewing pre-prepared context, not building it from scratch.
- Cross-reference: if your tech stack (Section 06) cannot automate the response layer, that is the bottleneck. If your messaging (Section 04) does not have signal-specific variants, automation alone will not help.
Messaging and Sequences
What reps say, how they say it, and whether the messaging is built around the prospect's problems or the company's product.
The messaging problems I see most often are not about writing quality. They are structural. The sequences are built around the company's product capabilities rather than the prospect's problems. The same template is used across personas who have fundamentally different concerns. And there is no connection between what the signal tells you about the account and what the email says.
Questions to Ask
- Does your messaging lead with the prospect's problem or with your product's capabilities?
- Are sequences differentiated by persona, company size, and signal, or is it one-size-fits-all?
- Does a CEO at a 30-person startup receive the same template as a VP at a 2,000-person company?
- When multiple signals overlap on one account, is there documented logic for which sequence to use?
- Are there dead variants still running (emails with consistently low performance that have not been retired)?
- What do your actual reply rates, bounce rates, and open rates look like? How do they compare to benchmarks?
- Do your emails include links, images, or HTML signatures? (These often hurt deliverability.)
- Does your competitor displacement messaging ask the prospect to admit they made a mistake with their current provider?
- How many sequences exist? Can every rep tell you which sequence to use for which scenario?
Messaging is problem-first and persona-specific. A Head of Procurement receives different messaging from a CFO, because their concerns are different. Sequences have signal-specific variants: the email a prospect receives after a funding round is different from the one they receive after a leadership change. Dead variants are retired quickly. Reply rates sit above 2% for targeted outbound. Bounce rates stay below 2%.
Reps are treating broad functions (like "Operations" or "Finance") as single personas and using one template for all of them. The messaging opens with the company's value proposition rather than a specific, relevant problem. There are dozens of sequences and no clear guidance on which to use. Newer reps default to whichever sequence they used last.
- Audit your top five sequences. For each one, ask: does the first line reference a problem the prospect is facing, or does it describe what your product does?
- Build a persona matrix that maps function, sub-function, and seniority to specific pains, language, and messaging angles. Operations is not one persona. Finance is not one persona.
- Kill dead variants. If a sequence or variant has been consistently underperforming for a full quarter, retire it.
- Strip unnecessary formatting from cold emails (HTML signatures, images, multiple links). Plain text outperforms formatted email for cold outbound.
- Cross-reference: if your reps cannot distinguish between personas (Section 01) and your signals do not connect to messaging variants (Section 03), the messaging will remain generic regardless of how well it is written.
Channel Strategy
Which channels (phone, email, LinkedIn) are actually booking meetings, whether the outbound motion is designed around that evidence, and how the channels work together.
Most outbound teams know which channel books the most meetings. Very few have designed their entire motion around that knowledge. If phone is responsible for 70-90% of meetings booked (which is common), but reps are spending more time on email sequences than on the phone, the channel strategy is misaligned with the evidence.
Questions to Ask
- What percentage of meetings come from phone vs email vs LinkedIn? Do you actually track this?
- Does a cold call framework exist that reps can reference and adapt?
- Are email and LinkedIn being understood as channels that work in isolation, or as activity that primes a prospect for the call?
- What is your connect rate? Your conversation-to-meeting rate? How do they compare to benchmarks?
- Are reps encountering AI call screening? What percentage of dials hit virtual assistants? Is there any training or talk track for this?
- Is there a voicemail strategy?
- Does the channel mix in your sequences match where meetings actually come from?
- For LinkedIn: are reps using it strategically (warming, multi-threading) or just adding it because the sequence template has a LinkedIn step?
The channel that books the most meetings receives the most rep time and the strongest enablement investment. Reps understand that channels work together as a system: a cold call is warmer when preceded by relevant email and LinkedIn touches, even if those touches did not generate a reply. A cold call framework exists and is coached regularly. AI call screening is acknowledged and reps have tested techniques for navigating it.
Sequences are weighted toward email (8 emails, 1 call, 1 LinkedIn step) even though phone books the majority of meetings. No cold call script or framework exists. When asked about their approach, reps describe something self-developed rather than trained. Voicemails are not set up or are generic. LinkedIn steps say "connect" with no guidance on what to say or why.
- Pull the data on which channel books meetings. If phone dominates, restructure sequences to front-load calls and use email as a support channel around a phone-led motion.
- Build a cold call framework. Not a script. A framework: how to open, how to earn the right to ask a question, how to handle the first objection, how to close for a next step.
- Cross-reference: if phone is your dominant meeting source, your enablement (Section 09) should be investing heavily in call coaching, objection handling, and conversation skills. If the enablement programme is focused on email writing, it is aimed at the wrong channel.
Tech Stack
The tools your outbound team uses (or is supposed to use), where they overlap, where the gaps are, and whether the stack enables reps or creates friction.
The most common tech stack problem is not missing tools. It is overlapping tools, underused tools, and tools that do not connect to each other. Companies tend to add tools to solve individual problems without stepping back to ask whether the existing stack could do the job if it were configured properly.
Questions to Ask
- List every tool your outbound team uses (or is supposed to use). Now ask reps which tools they actually use daily.
- Where do you have overlap? (For example, are multiple tools doing website visitor identification?)
- Where do you have gaps? (For example, no automated contact sourcing, no real-time signal notifications.)
- Have reps built workarounds because the approved stack does not meet their needs? Are any reps paying for their own tools?
- How many steps does it take for a rep to go from "I want to contact this person" to placing the first call?
- Is your data quality from primary providers (contact enrichment, phone numbers, email addresses) still reliable?
- Are there tools in the stack that nobody currently owns or maintains?
- Are you hitting API limits from too many integrations connected to the same system?
Each tool has a clear, non-overlapping purpose. Rep workflow is streamlined: the number of steps and context switches between "I have a prospect" and "I am calling them" is as short as possible. Data quality is monitored and the team knows which providers are performing. Tools that are not being used are either fixed or removed.
Reps describe a multi-step manual process involving five or six different tools just to place a single call. Export limits, disabled integrations, and sync failures add friction. Some reps are paying for their own tool subscriptions. Tools exist that were set up by someone who has since left and nobody currently owns or maintains them.
- Before building new tools or buying new subscriptions, ask whether the existing tools are being used, reinforced, and measured consistently. Many gaps already have solutions in the current system.
- Map the actual rep workflow from prospect identification to first touch. Count the steps and context switches. If it is more than four or five steps, the workflow needs simplifying.
- Evaluate data quality from your primary providers. If phone number coverage or email accuracy has declined, explore waterfall enrichment approaches.
- Cross-reference: if reps have built workarounds (Section 07), that is direct evidence that the stack has gaps. The workarounds tell you exactly where.
Rep Productivity and Workflow
How reps actually spend their day, how much time goes to selling vs administration, and whether the system is doing the work or the rep is doing the work.
The question is not whether reps are working hard. In most outbound teams I audit, the reps are working extremely hard. The question is how much of that effort is spent on activities that actually create pipeline (calling, qualifying, building relationships) vs activities that feel productive but do not move the number (research, admin, data entry, deciding what to do next).
Questions to Ask
- How much of a rep's week is spent on pipeline-generating activity vs non-selling tasks?
- Are reps maintaining personal spreadsheets, custom GPTs, or manual tracking systems alongside the official tools?
- When a rep receives an account with multiple signals, do they know immediately what to do, or do they need to interpret the data and decide?
- How long does stakeholder mapping take per account? Is any of it automated?
- Is there a defined daily or weekly operating rhythm, or does each rep structure their own day?
- Are newer reps taking significantly longer to execute the same tasks as experienced reps? If so, what is the bottleneck?
Reps are spending the majority of their time on selling activities: calling, qualifying, multi-threading, and building relationships. Research, enrichment, contact sourcing, and sequence selection are handled by the system. The rep's job is to review context, understand the angle, and make the call. New reps can execute at a reasonable level within weeks because the system makes the decisions, not the rep.
Reps have roughly one dedicated day per week for actual pipeline generation. The rest is consumed by data cleaning, manual research, stakeholder mapping, and workflow navigation. The strongest reps succeed by building personal workarounds, which means performance depends on individual resourcefulness rather than operational design. Newer reps are significantly slower because they lack the institutional knowledge.
- Ask reps to walk you through their actual workflow for a single account, step by step. Time it. If it takes more than five minutes from account selection to first touch, there is friction to remove.
- Apply a consistent test to every tool and process: "will reps actually use this under quota pressure, without leaving their core workflow?" If the answer is no, simplify it.
- If your best reps have built workarounds, study those workarounds. They are a free diagnostic of where the system is failing.
- Cross-reference: productivity improvements come from two sources. Reducing the number of manual steps (tech stack, Section 06) and reducing the number of decisions reps need to make (tiering, Section 02 and signals, Section 03).
Performance and Measurement
What you are measuring, whether those metrics reward the behaviour you actually want, and where the outbound funnel is leaking.
Measurement shapes behaviour. If reps are measured on meetings booked, they will optimise for meetings booked, regardless of whether those meetings are with the right people at the right companies at the right time. The question is whether your measurement model rewards the behaviour you actually want.
Questions to Ask
- What are your primary outbound metrics? Are they weighted toward volume (meetings booked) or quality (qualified pipeline, accepted opportunities)?
- Is outbound being measured against the same conversion benchmarks as inbound? (If so, that is a structural mismatch.)
- What does your SQL-to-SAO (or equivalent) conversion rate look like? Is there a significant gap between regions or reps?
- Where is the biggest drop-off in your outbound funnel? Connects to conversations? Conversations to meetings? Meetings to accepted opportunities?
- What are the top reasons opportunities are lost? Do they point to upstream quality problems?
- Do reps know what "good" looks like at the daily activity level, or only at the outcome level?
- Does your attribution model capture outbound's influence on deals that ultimately arrive through inbound?
Measurement is weighted toward qualified pipeline and conversation quality, not just meeting volume. Outbound has its own set of leading indicators (conversations opened, multi-threaded accounts, progression from early-stage to active pipeline) rather than being judged against inbound conversion benchmarks. Reps know the behavioural standard that produces results, not just the target number.
Activity metrics dominate and can be gamed. A significant proportion of booked meetings are rejected at the SAO stage or die in discovery. The top lost reasons are "unresponsive" and "stayed with current provider," both pointing to meetings booked before genuine interest was established. Volume looks healthy at the top of the funnel, but quality leaks out before deals can close.
- Separate demand creation from demand capture in your measurement. Outbound-sourced opportunities will naturally have longer sales cycles and different engagement patterns. Measuring both against the same benchmarks creates a structural mismatch.
- If meetings are being booked but not converting, the problem is upstream (targeting, timing, qualification depth), not downstream (AE execution). Fix the inputs.
- Define what good looks like at the daily and weekly activity level. Reps need to know the operating rhythm that produces the right outcomes, not just the outcome target.
- Cross-reference: if phone is your dominant meeting source (Section 05) but you are not tracking conversation quality per rep, you are missing the highest-leverage coaching opportunity (Section 09).
Enablement and Coaching
How reps and managers are developed after onboarding, whether coaching is consistent or dependent on individual manager quality, and whether training reflects the challenges reps are actually facing.
The pattern is remarkably consistent: strong onboarding, then a cliff. Companies invest heavily in getting reps through their first few weeks, then ongoing development either stops or becomes entirely dependent on the individual manager. Where the manager is strong, coaching is strong. Where they are not, the gap is significant. Even the best systems design will underperform if manager reinforcement is inconsistent.
Questions to Ask
- Is coaching consistent across managers, or does it vary significantly by team and region?
- Is there a structured post-onboarding ramp plan (30, 60, 90 days) with clear milestones?
- Can your reps articulate not just what your product does, but what problem each capability solves, why it matters commercially, and how that changes by persona?
- Is ongoing training responsive to current challenges (e.g. AI call screening, new competitor tactics), or is it a static curriculum planned months ago?
- When you look at your top performer's conversation-to-meeting rate, how does it compare to the team average? Is the gap explained by talent, or by a coachable process difference?
- Are your best reps informally coaching newer reps on top of their own quota because formal coaching is insufficient?
- Does enablement exist for non-core personas? If your reps are expected to engage with finance, IT, or operations buyers, are they trained to have those conversations?
Coaching is built into the operating rhythm, not left to individual manager discretion. The best managers' approaches are codified and rolled out across all teams. Training is driven by what the data shows (the specific conversion gaps, the specific objection patterns) rather than generic skills sessions. When a top performer operates at 2x the team average, the organisation studies their process and teaches it.
No cold call framework exists. When asked about their approach, reps describe something self-developed. Manager behaviour varies significantly across regions. BDRs are informally coaching newer reps because formal support is insufficient. No training exists for emerging challenges like AI call screening, despite it affecting 30-40% of dials. Enablement sessions lose engagement because the content does not feel practical.
- Identify your top performer's approach to the channel that books the most meetings. Codify it. Train it. If one rep converts conversations to meetings at 2x the team average, the difference is almost certainly a coachable process, not innate talent.
- Make coaching expectations explicit for managers: expected dashboard usage, expected coaching frequency, expected workflow reinforcement.
- Build training around the evidence from your performance data (Section 08), not around a generic curriculum. The data tells you exactly where the gaps are.
- Cross-reference: if you found that phone is the dominant meeting source (Section 05), the enablement programme should be weighted heavily toward call skills, objection handling, and live conversation practice.
Team Structure and Territory
How the team is organised, whether account loads are realistic, whether the structure matches the selling motion, and whether the career path retains the people you want to keep.
Team structure tends to get less attention than it deserves. The questions are straightforward but the answers often reveal mismatches: account loads that are not realistic given current levels of automation, pod models that do not match the selling motion, and territory splits that create wasted effort.
Questions to Ask
- How many accounts does each rep carry? How many do they actually work in a given week?
- Is the account load realistic given the current level of manual effort per account?
- Is the team structured by segment (SMB vs mid-market vs enterprise), by geography, or both?
- Does the team structure match the selling motion? (Enterprise accounts need a different approach from SMB.)
- Are territory mismatches causing wasted effort (accounts assigned to one region turning out to be in another)?
- If you have regional performance gaps, are they caused by the people, the process, or the market?
- Is there a BDR career path that retains top performers, or do your best people leave as soon as they can?
Account loads are calibrated to match the automation level. If accounts arrive fully enriched, prioritised, and with stakeholder mapping completed, a rep can handle a larger book. Segments receive different motions (enterprise gets multi-threaded, high-touch; SMB gets automated with human intervention for hot signals). A tiered career path exists that keeps top performers engaged for longer than 12 months.
Reps carry 250+ accounts but actively work 5-10 per week. Large portions of the book sit untouched, and pipeline is lost without anyone noticing. The same outbound motion is applied to enterprise and SMB. Regional performance gaps are widening and nobody can explain why. Top performers leave after 12-18 months because promotion criteria do not align with what they actually contribute.
- Do not start by reducing account loads. Fix the inputs first (enrichment, prioritisation, stakeholder mapping), then reassess what the right account load is. The number of accounts a rep can handle is a function of how ready those accounts are when they arrive.
- If you have significant regional performance gaps, investigate before intervening. The gap could be account quality, coaching quality, market maturity, or all three.
- Build a BDR career path where compensation and measurement evolve with level. Early-stage reps are measured on meetings and conversions. Senior reps are measured on pipeline and deal contribution.
- Cross-reference: this section depends heavily on Sections 01 and 02. If account selection and tiering are not working, no team structure change will fix the performance gap.
What Comes Next
If you have worked through all ten sections, you now have a clearer picture of where your outbound function is strong and where it is not. That picture is worth more than most companies ever get, because the default is to guess, react to the loudest complaint, or buy another tool.
A few principles that hold regardless of what you found:
Start with ICP and account selection. Everything else depends on it. If the accounts are wrong, better messaging, better coaching, and better tools will not fix the outcome.
Fix adoption before building new. The default response to an operational gap is to build a new workflow. It should be to ask whether the existing workflow is being used, reinforced, and measured.
Talk to reps. The gap between what leadership believes is happening and what reps actually experience is usually where the most important findings live.
Connect the pieces. The most common failure mode is not missing pieces. It is pieces that do not connect to each other. Signal detection that does not connect to automated response. Tiering that does not connect to differentiated execution. Performance data that does not connect to coaching priorities.
Before You Start
With a smaller outbound team, the challenge is fundamentally different from a larger function. You are not optimising a complex system. You are building one, often with limited people, limited data, and limited time before someone asks whether outbound is worth the investment.
The questions in this guide are designed for that reality. You will not find questions about signal stacking, automated response layers, or tiering models that drive differentiated execution. Those come later. What you will find are the foundational questions that determine whether your outbound motion has a chance of working before you scale it.
The most expensive mistake at this stage is scaling before the motion is validated. The second most expensive is spending three months on an approach that was never going to work because nobody asked the right diagnostic questions upfront.
How to use this guide: Work through each section honestly. Tick the questions where you are confident the answer is solid. The unticked questions are the gaps to address before you invest further. This is a diagnostic for whether the foundation is strong enough to support what you are building on top of it.
Ideal Client Profile and Personas
Whether you have validated who you sell to through actual deals, or whether your ICP is still a hypothesis you are testing with outbound.
With a smaller outbound team, the ICP is often still a hypothesis rather than a documented, validated definition. The question is whether you have closed enough deals to know who you actually sell to, or whether you are still guessing. If the answer is guessing, outbound is an expensive way to find out.
The persona work is thinner at this stage because you are usually selling to one persona, maybe two. But the risk is the same: defining personas from theory rather than from conversations you have actually had.
Questions to Ask
- Have you closed enough deals to know who your ICP is, or are you still testing a hypothesis?
- Can you name at least three firmographic characteristics that your closed-won customers share?
- Is there a floor (a minimum company size below which outbound is not worth the effort)?
- Have you validated that the companies you are targeting with outbound can actually afford your product and have a genuine need?
- Is your ICP narrow enough that you could build a list of 200 to 500 specific accounts that fit, and explain why each one is on the list?
- Can you name the one or two personas you are targeting? Not job titles, but the specific person who feels the problem your product solves.
- Can you describe your primary persona's biggest problem without mentioning your product?
- When you have had conversations with prospects, what language do they use to describe their problem? Is that language reflected in your outbound messaging?
- Do you know whether your entry-point persona is the same person who signs the deal, or are they different? Does that affect how you approach them?
The ICP is based on evidence from actual deals, not assumptions about who should buy. The team can name the characteristics of the companies that have closed and explain why those characteristics mattered. The primary persona is defined from real conversations, not from a template. The team can describe the prospect's problem in the prospect's own language, not in product language.
The ICP is a broad aspiration ("mid-market SaaS companies") with no evidence to support it. No floor exists, so outbound is being attempted on companies too small to justify the effort. The persona is defined from leadership's theory about who should care, not from patterns in actual conversations. When asked about the prospect's problem, the team describes the product's capabilities.
Look at your closed deals (even if there are only a handful). What do those companies have in common? If you cannot name at least three shared characteristics, your ICP is still a hypothesis. Ask yourself: can you describe your primary persona's biggest problem without mentioning your product? If not, you are too product-first.
- If you have fewer than ten closed deals, your ICP is a hypothesis. Treat it as one. Run outbound as a validation exercise, not a pipeline machine.
- Define a floor. There is a minimum company size below which outbound does not make sense. Find it and stop wasting effort below it.
- Build your persona from the conversations you have actually had, not from a template. Record the language prospects use to describe their problems. That language is your messaging.
- Cross-reference: if your messaging (Section 04) sounds like a product pitch, the root cause is almost always here. You have not spent enough time understanding how the prospect describes the problem in their own words.
Account Selection and List Quality
Whether you have a focused, reasoned list of target accounts, or a scraped database with no logic behind it.
At this stage, there is no tiering model because there are not enough accounts to tier. The real question is simpler: do you have a list of 200 to 500 accounts that you believe fit your ICP, and can you explain why each one is on the list?
Most companies at this stage get this wrong in one of two directions. Either they have a massive scraped list with no logic, or they have a tiny list of dream accounts they will never close. The right answer is a focused, evidence-based list that matches the ICP you have validated (or are validating).
Questions to Ask
- Do you have a defined target account list? How many accounts are on it?
- Can you explain why each account is on the list (beyond "they are in our industry")?
- Is the list based on characteristics shared by your closed-won customers, or is it aspirational?
- Are accounts arriving with enough data that your rep (or you) can start working them immediately, or does every account require manual research first?
- Have you included accounts that are too small, too large, or too different from your closed-won customers? What is the rejection rate when someone reviews the list honestly?
- Is the team spreading itself across too many accounts rather than going deep on a focused set?
A focused list of 200 to 500 accounts exists, each with a clear reason for being on the list that connects to validated ICP characteristics. Accounts have been enriched with enough context (contacts, basic company information, relevant signals) that the person doing outbound can start working them without spending the first hour on research.
The list is either a massive export from a database with no filtering logic, or a short wish-list of brand-name companies. Nobody can explain why a given account is on the list beyond "they are in our space." The team is spreading outbound effort across 2,000 accounts rather than going deep on 200. Every account requires 30 minutes of manual research before the first touch can happen.
Review 20 random accounts on your list. For each one, can you explain why this company would buy from you right now? If the answer is vague for more than half of them, your list needs tightening.
- Shrink the list rather than grow it. At this stage, 200 deeply researched, well-matched accounts will outperform 2,000 loosely matched ones.
- Apply the characteristics from your closed-won deals (even if you only have a handful) to filter the list. Remove anything that does not match.
- Make sure every account on the list has the basic information needed to start outbound without additional research: a named contact, their role, and one reason this company might care.
- Cross-reference: list quality depends entirely on ICP clarity (Section 01). If the ICP is a hypothesis, the list is a hypothesis too. That is fine, but treat it as a test, not a target.
Signals and Timing
Whether you are using trigger events to give your outreach timing and relevance, even without enterprise-grade intent platforms.
You do not need expensive intent data platforms at this stage. But you do need a reason to reach out that goes beyond "you are on my list." The good news is that lightweight signal tracking tools are widely available now. Tools like Google Alerts, LinkedIn Sales Navigator saved searches, free tiers of signal platforms, and even simple Clay or Make automations can surface trigger events (funding rounds, leadership changes, job postings, company news) without any manual monitoring.
The question is not whether you are tracking signals manually (you should not be in 2026). It is whether you have set up even basic automated tracking for the events that matter, and whether those events are connected to your outreach.
Questions to Ask
- Are you tracking any trigger events on your target accounts (funding, hiring, leadership changes, product launches)?
- Have you set up lightweight automated monitoring (Google Alerts, LinkedIn Sales Navigator saved searches, a basic Clay table, or a free signal tool), or are you relying on stumbling across news by accident?
- When a trigger event surfaces, do you have a clear approach for how to reference it in your outreach?
- Are you reaching out to accounts with a specific reason and timing, or is every email sent on the same schedule regardless of what is happening at the company?
- Do you know which types of trigger events have led to your best conversations so far?
Lightweight signal tracking is in place and running automatically. The team receives alerts when target accounts hit a trigger event (funding, hiring, leadership change, relevant job posting). When a signal surfaces, there is a clear connection between the event and the outreach. The best conversations have been traced back to specific triggers, and that informs which signals to prioritise as the team grows.
No signal monitoring exists. Every email goes out on the same cadence regardless of what is happening at the account. The outreach feels random because it is random. When asked why they are reaching out to a specific company today, the answer is "they were next on the list" rather than "something changed at their company that makes this relevant." Lightweight tools are available but nobody has set them up.
- Set up automated signal tracking this week. Start simple: Google Alerts for your top 50 accounts, LinkedIn Sales Navigator saved searches for job changes, and a free signal tool for funding rounds. This takes an hour, not a day.
- When a trigger surfaces, reach out within 48 hours. The timing is the value, not the signal itself.
- Keep a simple log of which trigger events led to the best conversations. Over time, this tells you which signals to prioritise when you invest in more sophisticated tooling.
- Cross-reference: signals only work if your messaging (Section 04) connects the trigger to the prospect's problem. A funding round is not a reason to pitch. A funding round is a reason the prospect's existing problem just became more urgent.
Messaging and Sequences
Whether your outbound emails describe a problem the prospect recognises, or whether they read like a product pitch.
With a smaller team, the messaging problem is almost always the same. The emails are too long, too product-first, and too focused on what the company does rather than the prospect's problem. The question is not whether your sequences are differentiated by persona and signal (they will not be). It is whether your first email describes a problem the prospect recognises and is under 75 words.
Questions to Ask
- Does your first email lead with a problem the prospect faces, or with what your product does?
- Is your email under 75 words?
- Would the prospect understand why they specifically are receiving this email, or could it have been sent to anyone?
- Does the email end with a soft question that invites a reply, or a hard ask for a meeting?
- Have you tested different messaging angles, or are you running the same email to everyone?
- Are you sending plain text emails, or emails with HTML formatting, images, and links?
- If you read your email from the prospect's perspective, would you reply?
- How many follow-up emails are in your sequence? Are the follow-ups adding new value or just "bumping" the original?
The first email is under 75 words, leads with a specific problem the prospect is likely facing, and ends with a soft question. It reads like a message from a human, not a marketing email. Follow-up emails add new angles or value rather than restating the same pitch. Plain text, no images, minimal links. The team has tested at least two or three different problem angles to see which generates the most replies.
The email opens with the company's story or product capabilities. It is 150+ words. It contains multiple links, an HTML signature, and reads like a newsletter rather than a conversation. Every follow-up says "just bumping this to the top of your inbox." Nobody has tested alternative messaging angles because the first version "feels right."
- Rewrite your first email in under 75 words. Lead with the prospect's problem, not your product. End with a question, not a meeting request.
- Strip all formatting. Plain text, no images, no HTML signatures, no more than one link (ideally none in the first email).
- Test two or three different problem angles against the same list. The one that gets replies is the one that resonates, regardless of which one you think is strongest.
- Cross-reference: if your messaging sounds like a product pitch, the root cause is usually Section 01. You have not spent enough time understanding how the prospect describes the problem in their own words.
Channel Strategy
Whether you are picking up the phone, or hiding behind email because it feels safer.
With a smaller team, channel strategy is not about orchestrating a sophisticated multi-channel sequence. It is about one question: is the team actually picking up the phone?
Most small teams default to email because it is less scary and feels more scalable. But the same data holds at every stage: phone books the meetings. A rep who makes 20 calls a day and sends 20 emails will book more meetings than one who sends 200 emails and makes zero calls.
Questions to Ask
- Is anyone on the team making cold calls, or is outbound entirely email-based?
- If you are calling, do you have a basic framework for the first 30 seconds (how to open, how to earn the right to ask a question)?
- Are you using LinkedIn to warm prospects before calling or emailing, or are you ignoring it?
- Do you leave voicemails? Do they reference the email you sent?
- Are you tracking which channel is generating your best conversations and meetings?
- Is the team avoiding the phone because it is uncomfortable?
The team is making calls daily. A basic call framework exists (even if it is just a few bullet points on how to open and what question to ask). LinkedIn is being used to warm prospects before the call. Channels are being used together: email and LinkedIn create familiarity, the call converts it to a conversation. The team knows which channel is booking meetings.
Outbound is entirely email-based. The team says they "plan to add phone" but has not started. When they do call, there is no framework, no opening, and no plan for the first objection. LinkedIn is unused or used only for connection requests with no message. Nobody knows which channel is producing results because only one channel is being used.
- Start calling. Today. Even 10 calls a day alongside your email outbound will change the results. The first few calls will be uncomfortable. That is normal.
- Write a simple call opening: who you are, why you are calling, and one question that earns you the right to a conversation. Keep it under 20 seconds.
- Use LinkedIn to send a short, relevant message before you call. When you reach them on the phone, "I sent you a message on LinkedIn earlier this week" creates enough familiarity to buy you 30 more seconds.
- Cross-reference: if the team is avoiding the phone, no amount of email optimisation (Section 04) will compensate. Phone books meetings. Email supports the phone. Not the other way around.
Tech Stack
Whether you have the basics in place, and whether you have avoided the trap of over-investing in tools you do not know how to use yet.
The risk with a smaller team is the opposite of a larger company. Instead of overlapping tools, you have either got nothing (sending from Gmail with a spreadsheet) or you have over-invested in platforms you do not know how to use yet because a sales advisor told you to buy them.
At this stage, you need three things: a way to send sequences, a way to find contacts, and a CRM. Everything else is premature until the motion is validated.
Questions to Ask
- Do you have a sequencing tool, or are you sending emails manually from Gmail?
- Do you have a reliable way to find contact details (email addresses, phone numbers) for your target prospects?
- Are you tracking your outbound activity and results in a CRM, or in a spreadsheet (or nowhere)?
- Have you bought tools that you are not using, or not using fully? What did you spend on them?
- Is your sending infrastructure set up correctly (secondary domain, SPF, DKIM, DMARC, warmup)?
- If you are using AI tools for outbound, are they producing output that sounds like you, or output that sounds like AI?
Three tools are in place and being used consistently: a sequencing tool for email and follow-ups, a contact data provider for finding prospects, and a CRM for tracking conversations and pipeline. Sending infrastructure is properly configured (secondary domain, authentication records, warmup completed). Nothing has been bought that is not being used.
Emails are being sent manually from Gmail. No CRM exists, so conversations are tracked in someone's head or a spreadsheet. Alternatively, five different tools have been purchased based on recommendations but none are configured properly. Emails are being sent from the primary domain, risking deliverability for the whole company. AI tools are generating emails that sound generic and robotic.
- If you do not have a sequencing tool, get one. Sending outbound manually from Gmail does not scale past 20 emails a day and burns out quickly.
- Set up a secondary domain for cold outbound immediately. Never send cold emails from your primary company domain.
- Do not buy anything beyond sequencing, contact data, and CRM until you have validated the motion. The tools should follow the process, not the other way around.
- Cross-reference: the best tech stack in the world will not help if the messaging (Section 04) is wrong. Fix the message first, then worry about the tools.
Time and Focus
Whether outbound is getting dedicated, protected time, or whether it is being squeezed between everything else.
With a small team, the productivity question is not about workflow friction (there is not enough infrastructure for friction yet). It is about whether outbound is getting dedicated time or being bumped by customer calls, product meetings, investor conversations, and everything else that feels more urgent.
Outbound dies from neglect more often than from poor execution. A team that dedicates two focused hours every morning to outbound will outperform a founder who "does outbound when there is time" every single time.
Questions to Ask
- How many hours per week are actually spent on outbound activity?
- Is that time protected (blocked on the calendar, treated as non-negotiable), or does it get bumped by other priorities?
- If you have hired reps, are they spending their time on outbound, or are they being pulled into customer success, demos, and other tasks?
- Is there a daily or weekly rhythm for outbound (e.g. pipeline generation power hours in the morning, dedicated prospecting days, time-blocked call sessions), or is it ad hoc?
- Can you sustain this level of outbound effort for six months, or is it a burst that will fade?
Outbound has a dedicated, protected block of time every day (typically morning). This time is treated as non-negotiable. The team has a clear daily rhythm: call block, email block, research block. Outbound effort is consistent week over week, not a burst that fades after two weeks when other priorities take over.
Outbound happens "when there is time," which means it does not happen consistently. The team has good weeks and bad weeks. Reps are being pulled into demos, customer calls, and other tasks. There is no daily rhythm. Outbound gets two hours on Monday, nothing on Tuesday, an hour on Thursday. The inconsistency makes it impossible to measure whether the motion is working or not.
- Block two hours every morning for outbound. Protect it. Nothing else goes in that slot.
- If you have hired reps, their job is outbound. If they are being pulled into customer success, demos, or other tasks, you have not hired enough people for those functions, and outbound will suffer.
- Set a minimum sustainable pace. Ten calls and ten emails a day is better than 50 calls on Monday and nothing for the rest of the week. Consistency beats intensity.
- Cross-reference: if outbound is not getting dedicated time, no improvement in messaging (Section 04) or channel strategy (Section 05) will matter. The constraint is not the approach, it is the time.
Measurement Basics
Whether you can answer the basic conversion questions about your outbound motion, or whether you are flying blind.
With a smaller team, most companies are measuring almost nothing about their outbound. They might know how many emails they sent. They probably do not know their reply rate, connect rate, or conversation-to-meeting conversion. Without these numbers, you cannot tell whether the motion is working, getting better, or getting worse. You are flying blind.
Questions to Ask
- Do you know your email reply rate? (Not open rate. Reply rate.)
- Do you know how many calls it takes to reach a live conversation?
- Do you know how many conversations it takes to book a meeting?
- Do you know how many meetings it takes to create a qualified opportunity?
- Can you tell me, right now, the conversion rate at each stage of your outbound funnel?
- Are you tracking these numbers weekly, or guessing?
- If someone asked you whether outbound is working, could you answer with data or only with a feeling?
The team can state, with data, the conversion rate at each stage: emails sent to replies, dials to conversations, conversations to meetings, meetings to opportunities. These numbers are tracked weekly. When something changes (reply rate drops, connect rate improves), the team notices and investigates. Decisions about whether to continue, adjust, or stop outbound are based on evidence, not gut feeling.
Nobody can state the conversion rates. The feeling is that "outbound is not working" but there is no data to support or disprove it. When asked whether outbound is worth continuing, the answer is based on anecdote ("we have not booked many meetings recently") rather than data. The motion could be improving and nobody would know.
- Start tracking five numbers this week: emails sent, replies received, calls made, conversations had, meetings booked. Calculate the conversion rate between each stage.
- Review these numbers weekly. The absolute numbers matter less than the trend. Are they improving, declining, or flat?
- Do not judge outbound based on meetings alone. If your email reply rate is 3% but your conversation-to-meeting rate is 2%, the problem is the call, not the email. The numbers tell you where to focus.
- Cross-reference: without measurement, you cannot tell whether improvements in ICP (Section 01), messaging (Section 04), or channel strategy (Section 05) are actually working. Measurement is not optional, it is the foundation for every other decision.
Knowledge Transfer and Readiness
Whether the knowledge of how to sell lives in one person's head or in a document that someone else can use.
Usually there is no coaching infrastructure at this stage because there is no manager layer. The founder or a senior leader is the one who knows how to sell the product, but they have not documented how they do it. When reps are hired, the knowledge transfer is verbal and inconsistent.
The test is simple: if your first SDR started on Monday, could you hand them a document that explains who to target, what to say, and how to handle the first three objections?
Questions to Ask
- Has anyone documented the outbound approach in a way that someone else could follow?
- If you hired an SDR tomorrow, could you hand them a one-page guide covering: who to target, what to say, which channel to use, and how to handle the three most common objections?
- Is the selling approach based on repeatable patterns, or does every conversation go differently because there is no structure?
- When someone has a great call, do they write down what worked, or does it stay in their head?
- Have you documented the specific language prospects use to describe their problem? This is the foundation for messaging that a rep can use.
- If your most experienced seller stopped doing outbound tomorrow, would the motion stop entirely?
Someone has documented a simple, practical playbook covering: target accounts (and why), primary persona (and their problems), messaging (first email, call framework, LinkedIn message), objection handling (top three objections and the responses that work), and what a good conversation looks like. A new rep could read this document and start executing within a week. When the team learns something new from a conversation, it gets added.
Everything lives in one person's head. When new reps join, onboarding is a series of verbal conversations that differ each time. New reps are told to "shadow calls" but there is no structure to what they should learn from shadowing. When that person goes on holiday, outbound stops. Nobody has written down the objections they hear most often, let alone the responses that work.
- Write a one-page outbound playbook this week. It does not need to be perfect. It needs to cover: who we target (ICP and persona), what we say (first email and call opening), and what we say when they push back (top three objections).
- Every time you have a conversation that works, write down what you said and why it worked. This is your coaching material for future reps.
- Record the language your prospects use. Not your language. Theirs. This is the single most valuable asset for scaling outbound beyond the people currently doing it.
- Cross-reference: this section is the bridge between ad hoc outbound and scalable outbound. If you cannot document it (this section), you cannot hire for it (Section 10).
Scaling Readiness
Whether the outbound motion has been validated enough to scale, or whether you are adding headcount to something that has not been proven.
This is the question most companies skip at this stage. They hire one or two SDRs because they want to "get outbound going" without first proving that the outbound motion works. The reps then fail, not because they are bad reps, but because the motion was never validated.
The rule is straightforward: has the outbound motion been validated through enough closed deals to prove it works before you add more people to it? If the answer is no, scaling is premature.
Questions to Ask
- Has the outbound motion been tested and proven to book meetings consistently?
- Have deals been closed that originated from outbound? Is there a pattern, or were they one-off wins?
- Can anyone on the team describe a repeatable outbound motion (not just one or two lucky breaks, but a pattern that works consistently)?
- Were your current reps hired to scale a validated motion, or to figure out whether outbound works?
- Do you have enough pipeline from other sources (inbound, referrals, partnerships) that outbound reps will not be expected to carry the entire revenue target?
- Is the expectation for the first SDR realistic? Do they have a fair quota, a clear playbook, and enough support to succeed?
The outbound motion has been tested, validated, and documented. The team can describe the motion that works: who to target, what to say, which channel books meetings, and what the common objections are. New hires are being brought in to scale something that already works, not to discover whether it works. The quota is realistic for a new rep in a new role at a new company.
Reps have been hired before the motion has been validated. They are expected to figure out outbound from scratch: find the ICP, build the list, write the messaging, and book meetings. When they struggle, the conclusion is "we hired the wrong reps" rather than "we asked them to do something we had not proven was possible." The quota is based on a Board model, not on evidence from actual outbound performance.
- If the outbound motion has not been validated, do not add headcount yet. Spend 30 days proving it works with the people you have. What you learn will be worth more than any hire.
- When you do hire, hire to scale a validated motion, not to build one. The first rep should be executing a playbook, not writing one.
- Set a realistic quota for the first SDR. They are joining a company with no brand recognition, no inbound leads to supplement outbound, and no established motion. Their first 90 days should be measured on activity quality and learning velocity, not on meetings booked.
- Cross-reference: this section depends on everything that comes before it. If the ICP (Section 01) is unvalidated, the messaging (Section 04) is untested, and the playbook (Section 09) is undocumented, the first hire will fail regardless of how talented they are.
What Comes Next
If you have worked through all ten sections honestly, you now know whether your outbound foundation is solid enough to build on, or whether there are gaps to close first. At this stage, that clarity is worth more than any tool, any hire, or any playbook, because the cost of building on a weak foundation is months of wasted effort.
A few principles that hold regardless of what you found:
Validate before you scale. Prove the motion works before scaling it. New reps should be hired to execute something that already works, not to discover whether it works.
Document everything. Every conversation that works, every objection that comes up, every piece of prospect language. This is the playbook. It does not need to be polished. It needs to exist.
Measure the basics. Five numbers, tracked weekly: emails sent, replies, calls made, conversations, meetings. Without these, you cannot tell whether the motion is working or not.
Protect the time. Outbound dies from neglect. Two focused hours every morning, protected, non-negotiable. Consistency beats intensity every time.
Want this done properly?
This guide covers the questions to ask. A full outbound audit covers the answers, the evidence, the benchmarks, and the specific recommendations for your team.
Book a call Free sequence review