Outbound Wiki

Client-agency operating cadence

Running recurring meetings, approvals, feedback loops and decision processes between the client and the agency.

An outsourced SDR agency and its client need a shared operating rhythm. The cadence should show what happens when leads arrive, are contacted, qualified, handed off and reviewed. Agency cost can expose cracks across the lead-to-revenue process.1 A meeting that grades agency activity alone can miss failures on the client side. Start with a baseline, set obligations for both sides, inspect raw performance, and give each decision an owner. This lets the agency flag a blocked handoff before the discussion turns into an argument about output.

The operating cadence

  1. Baseline
  2. Contract
  3. Handoff
  4. Review
  5. Decision

The cadence moves from measurement to execution and then to a decision. Each stage should focus on the information needed for the next one.

Stage What you are trying to learn Example question
Baseline What performance looks like before changes What is happening today?
Contract What each side must provide and complete Who acts, and by when?
Handoff Where a lead moves and what qualifies it to move What has to be true before sales accepts it?
Review Which channel, process or dependency is affecting results Where did the work slow down?
Decision What changes next and who owns the change What will we change before the next review?

Set the baseline

Start the relationship with a measurement everyone can see. A baseline lets the team judge a process change against the starting point instead of the loudest anecdote in the meeting.

Get a baseline KPI before changing process or staffing.2 That baseline is usually SLA compliance for calling and booking meetings with inbound leads and outbound prospects.3 Make the result visible across the client and agency teams, since that visibility can help build the case for intervention.4

A client example found that the inside team ignored 60% of inbound leads and met the SLA 16% of the time.5 Use that comparison to separate an agency execution problem from a client response problem. The review should show where the lead stalled, who owned the next action, and what happened after the handoff.

Define the operating contract

A recurring meeting works when everyone arrives with a clear obligation. Put the responsibilities in the working agreement, then use the meeting to resolve exceptions instead of reopening the agreement each time.

An agency that commits to client work should get client commitments on turnaround and other responsibilities too.6 SLA obligations apply to both sides, including timely list uploads after events or campaigns.7 Put client supplied lists, approvals, internal updates and agency actions on the same operating view.

Settle the process before performance becomes the argument:

  • "Have you defined the lifecycle stages?".8
  • "Are the handoffs crystal clear across your documentation, automation, and sales teams?".9
  • "Do you agree on BANT criteria, or what an Opportunity even is? Are rejection reasons standardized? Who creates the Opportunity once it’s qualified?".10

Decide whether the workflow uses Leads, Contacts or both, and how Leads match to Accounts.11 Set lead assignment rules and decide whether large list uploads from content syndication or events need to be paced.12 Check that the data is clean and complete before asking the agency to explain a result.13

Set the SLA and feedback loop

An SLA should tell the team what to do when a lead arrives and what to inspect when the response misses. Set the target from observed performance, then review it alongside the dependencies that affect it.

Define a new SLA carefully using performance data.14 Speaking with a lead by phone within the first 24 hours was the most predictive factor for finding an Opportunity in one operating example.15 Show the response window in the review, with the arrival time, attempted action and handoff outcome recorded together.

Capacity can differ sharply between teams. Some teams have met 8-minute SLAs, while some reps have considered 48 hours too tight.16 Agree on a response window the agency can execute and the client can support. When a target changes, keep the absolute target visible beside the movement from baseline. In one case, 25% SLA compliance was treated as an improvement over baseline, which eased pressure on the agency.17 Track progress and attainment as separate fields.

Feedback should point to a change in execution. If the agency misses the SLA, ask whether the lead arrived late, the list was incomplete, the assigned person lacked capacity, or the handoff rule was unclear before changing messaging.

Run the review

Make the recurring review a working session with raw activity and outcome detail. It should leave the team with a decision, a dependency to clear, or a question to answer with better data.

Look for vendors that conduct weekly pipeline reviews using raw data.18 Reporting should give clear visibility into volume, attribution and velocity.19 Review results by channel, since channel-specific performance data gives more information than an aggregate number.20 A vendor that reports an average reply rate without channel detail can hide meaningful variance.21

Use a question that forces the agency to match its result to the target segment: "what's your reply rate on cold email specifically, for companies in [your vertical], targeting [your title]?".22 A legitimate vendor can answer that with specificity.23

Keep the discussion close to the work. Ask what changed, where the process broke, what the client needs to supply, and what the agency will test next. Record the decision and the owner in the same place as the metric so the next review can inspect the outcome.

Manage approvals and client updates

Client decisions can slow an agency even when it is executing its own work. Give approvals and internal changes a fixed place in the cadence so they do not appear as unexplained performance gaps.

Let the executive own the communication cadence while making sure the cadence is established.24 Agency work involves client approvals.25 The client should keep the agency updated about internal events and organizational updates.26

Use the approval discussion to answer what is waiting, who can approve it, and what work remains blocked until the decision arrives. When the client changes an offer, target or internal process, bring that change into the next review before judging the agency's results.

What not to do

These mistakes turn a recurring review into a cycle of explanations. Remove them before asking the agency for more output.

  • Do not treat outsourcing as a shortcut around a defined ICP, a tested offer and a vendor accountability structure.27
  • Do not expect the vendor to develop the messaging from scratch.28
  • Do not send meetings into an outsourced team when there is no sales process for the handoff.29
  • Do not assume generated meetings will convert without a repeatable close process.30
  • Do not accept monthly summaries only when reviewing an agency's pipeline.31

Sources

  1. 1
    “the cost of the agency will shine a glaring light on every crack in your lead-to-revenue process:”
  2. 2
    “Before embarking on any changes to process or staffing, get a baseline KPI.”
  3. 3
    “That’s usually SLA compliance rates for calling and booking meetings with inbound leads and outbound prospects.”
  4. 4
    “The transparency was a shock to the system, and it helped build a case for radical intervention.”
  5. 5
    “Our client’s inside team completely ghosted 60% of all inbound leads 🤯, and only met the SLA 16% of the time.”
  6. 6
    “if you’re going to commit to clients, be sure they make commitments to you (about turnaround and other responsibilities)”
  7. 7
    “And remember, SLAs go both ways! How timely will lists be uploaded after events or campaigns?”
  8. 8
    “Have you defined the lifecycle stages?”
  9. 9
    “Are the handoffs crystal clear across your documentation, automation, and sales teams?”
  10. 10
    “Do you agree on BANT criteria, or what an Opportunity even is? Are rejection reasons standardized? Who creates the Opportunity once it’s qualified?”
  11. 11
    “Are you using Leads, Contacts, or both? How do you match Leads to Accounts?”
  12. 12
    “How are leads assigned? Do you “pace” large list uploads from content syndication or events?”
  13. 13
    “Is your data clean and complete?”
  14. 14
    “Define your new SLA carefully, using performance data.”
  15. 15
    “Speaking on the phone within the first 24 hours was the most predictive factor to finding an Opportunity.”
  16. 16
    “we’ve seen teams who can crush 8-minute SLAs, and we’ve seen reps protest that 48 hours is too tight!”
  17. 17
    “It also eased the pressure on the agency when they hit 25% SLA compliance because, after all, it was an improvement.”
  18. 18
    “Weekly pipeline reviews with raw data”
  19. 19
    “Do you have clear reporting into volume, attribution, and velocity?”
  20. 20
    “Ask for channel-specific performance data, not aggregate numbers.”
  21. 21
    “A vendor who says "we average 15% reply rates" is hiding variance.”
  22. 22
    “Ask: what's your reply rate on cold email specifically, for companies in [your vertical], targeting [your title]?”
  23. 23
    “Legitimate vendors can answer this with specificity.”
  24. 24
    “But that way, they're owning the cadence. But the cadence is set.”
  25. 25
    “Agency work involves client approvals.”
  26. 26
    “To keep X Agency updated with internal events and organizational updates.”
  27. 27
    “It fails when companies treat it as a shortcut around those fundamentals.”
  28. 28
    “You expect the vendor to figure out your messaging from scratch”
  29. 29
    “You have no sales process for the outsourced team to hand off into”
  30. 30
    “If you don't have a repeatable close process, you'll generate meetings you can't convert.”
  31. 31
    “Monthly summaries only”