A 10-point diagnostic for B2B sales leaders
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.
Mark Colgan · B2B Sales Strategy Consultant
My outbound team is:
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.
Chapter 01
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
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.
Chapter 02
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
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.
Chapter 03
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
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.
Chapter 04
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
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.
Chapter 05
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
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.
Chapter 06
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
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.
Chapter 07
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
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).
Chapter 08
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
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).
Chapter 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
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.
Chapter 10
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
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.
Conclusion
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.
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.