Run the weekly review with a real decision to make
The team, messages, counts and commercial decisions in this example are fictional.
Before the first send
A software supplier supports independent inspection firms with several sites in one region. Its sales lead approves the buyer definition and owns discovery. A named provider operator builds the list, writes to approved contacts and routes replies. The client appoints a backup with authority to approve exceptions. Until that backup accepts the role, the first batch stays on hold.
| Item | Decision and owner |
|---|---|
| List scope | The client approves multi-site inspection firms. Existing customers, single-site firms and unresolved overlaps stay out. |
| Message claims | The operator proposed “automatically fills every shift.” The client could verify scheduling visibility but not that promise. The client approves version 2 with the narrower wording. Version 1 stays blocked. |
| Access and stop rule | The client administrator grants only the permissions needed. The operator confirms the exclusion list works across the permitted channels. An access failure or an unprocessed refusal holds the affected work. |
A staffed role working under your daily direction needs your coaching and backup. A managed scope should say who provides those functions. Both still need a client decision owner for product facts and fit.
Inspect the first 30 minutes of evidence
| Time | What the team checks | Decision |
|---|---|---|
| First 10 minutes | One firm had three sites and a public hiring notice about assignments. A second record inferred multiple sites from a directory. A third message inferred a problem from a public announcement. | Keep the verified fit, hold the ambiguous firm and rewrite the unsupported inference. The operator records the reasons. |
| Next 10 minutes | Two replies were wrong-fit. Another had a technical question and waited for client input. The small sample supports two possible problems: list approval and response coverage. | The client compares the two wrong-fit records to the written rule. The sales lead checks who owned the pending question. |
| Last 10 minutes | No reason to widen the list yet. The operator will amend the two records and the client will name a backup for technical replies. | Review those actions at the next meeting. Resume the held segment only after the client approves the corrected rule. |
Coach on the work itself. In this example the operator learns to distinguish a source fact from a claim about buying intent. If a good reply stalls with the client, coach the handoff and client coverage before changing the copy.
Reconcile one cohort
Start with the contacts approved in the first batch and count each person once. Of 40 approved contacts, 32 were reached. Six replied: three relevant positives, two wrong-fit replies and one stop request. Two original bookings came from the relevant replies. One meeting moved dates. One has been held and met the written criteria; the other is pending. Sales has accepted no opportunity yet.
| Metric | Evidence |
|---|---|
| Reply rate | 6 ÷ 32 unique contacted people, or 18.75%, for this fictional cohort. |
| Booking | Two original booking IDs. The reschedule is linked to its original and adds no new booking. |
| Qualification | One held and qualified, one outcome pending. Keep any held-to-booked rate provisional. |
| Opportunity | No accepted opportunity yet. Record the client disposition separately from qualification. |
A booked call, a held call and a qualified meeting answer different questions. A small batch cannot establish demand or a return. Compare mature cohorts using the same rules.
Put the handoff in the CRM
Filled reply record
- Record and version
- Account A, contact 04, brief v2. The fit evidence is a verified multi-site operation. No confirmed need.
- Reply and ownership
- The contact asks if a particular scheduling system can connect. The operator logs the question, pauses automated follow-up and assigns it to the sales lead.
- Acceptance and next action
- Sales owns the product answer and the next discovery step. Link the original booking ID if booked. Record held status, qualification reason and opportunity disposition separately.
The CRM needs account and contact keys, brief version, evidence link, disposition, owner and next action. One operator owns each account across channels. Merge or hold duplicates before sending and apply a stop request across the approved workflow. No team restarts an affected segment until the designated approver confirms the fix.
Decide to keep, change, stop or transfer
| Choice | Evidence to require |
|---|---|
| Renew | The work meets the scope, handoffs are accepted and the client can support the next batch. |
| Redesign | Two failures share a correctable cause. Test the revised rule in a bounded batch and set a review date. |
| Pause | Stop handling is unverified, claims are unsupported or nobody can take replies. Resume after the responsible person checks the correction. |
| Transfer | The receiving operator has rights and access and can handle a routine reply and an exclusion exception. An export alone does not prove readiness. |
Handover acceptance record
- Inventory
- The CRM export, brief v2, response rules and exclusions are received. The client verifies the data rights and confirms which records may be retained.
- Rehearsal
- The receiver routes a routine reply but misses a stop request in a second channel. The current operator retains responsibility and verifies suppression.
- Decision
- Repeat the exception test before revoking access or transferring the queue. Set the next review owner and date.
Copy the meeting record
Weekly review record
- Date and cohort
- Which contacts, channels and reporting period are included?
- Evidence sampled
- Which account, message and handoff were inspected?
- Decision
- What continues, changes or pauses? Who owns it and when will we verify it?
- Uncertainty
- What cannot yet be concluded? What would change the decision?
For managed outbound, Beespoke can run agreed cold email and/or LinkedIn work. Your team owns list judgment, factual approval, expert replies, discovery and closing. Calling is separately quoted by market.
Set a responsibility map before launch
List every recurring decision and task, then assign one accountable owner. Shared responsibility without a final decision-maker creates slow approvals, inconsistent replies and unreviewable outcomes.
Keep solution claims, legal or compliance approvals, expert discovery, proposals and closing with qualified client personnel unless the contract explicitly and credibly covers them.
| Work | Provider owner | Client owner |
|---|---|---|
| ICP and exclusions | Draft, research and recommend | Approve commercial boundaries |
| Account and contact research | Execute and document evidence | Review samples and exceptions |
| Messages and sequences | Draft and test within approval | Approve claims, tone and prohibited language |
| Daily outreach | Execute agreed workflow | Maintain access and escalation availability |
| Replies | Classify, answer within scope and route | Handle expert, sensitive and sales replies |
| Qualification | Apply written standard | Accept or reject with reason |
| Discovery and closing | Provide context and handoff | Lead conversation and commercial process |
Run a 30-minute outsourced SDR evidence review
Use the same agenda every week so discussion produces comparable decisions.
Review sampled account evidence, messages, replies, meetings and handoffs—not only totals.
Compare stages, rejection reasons, response timing and sales follow-up by segment.
Approve, stop or redesign specific targeting, messages, responsibilities and tests with owners and dates.
Keep a decision log. Repeated discussions without recorded action are a management failure signal.
Create an approval system that does not stall
Agree which changes require approval, who can approve them and the service level for a response. Pre-approve factual company descriptions, proof, prohibited claims, common reply routes and escalation categories.
The provider should not invent urgency or technical assertions to keep activity moving. The client should not wait days to answer a qualified prospect. Operational speed comes from clear boundaries, not removing judgment.
- Named primary and backup approver
- Approved claims and evidence library
- Prohibited assumptions and wording
- Reply categories and escalation timing
- Rules for account, segment and message changes
- Incident path for platform, data or reputation risk
Review evidence, not just dashboards
A weekly review should examine a sample of account rationales, messages, replies, meeting notes and disqualifications. Aggregate activity is useful for capacity, but it cannot show whether the market premise is credible.
Ask what was learned, which assumption changed and what decision follows. If the meeting produces no targeting, message, process or sales action, it is status reporting rather than campaign management.
Use one funnel with observable definitions
Define researched account, approved contact, contacted person, reply, positive reply, booked meeting, held meeting, qualified meeting, accepted opportunity and pipeline. Do not allow the provider and client to use different meanings for the same word.
Record a reason when an account, reply or meeting is rejected. Review those reasons by segment and message so disqualification becomes a source of learning rather than a hidden argument about lead quality.
Manage access, continuity and handover
Use least-privilege access, named users, approved devices or workflows where appropriate and a current inventory of profiles, inboxes, tools and data sources. Define what happens when a provider employee changes.
Schedule exports and documentation during the engagement, not only at cancellation. The account list, research sources, messages, replies, dispositions, meeting context and test history should remain usable by the client.
- Access and credential inventory
- Data-source and consent or legitimate-interest records where applicable
- Versioned messaging and approval log
- CRM export and backup cadence
- Replacement and continuity plan
- Final handover checklist with access removal
Decide whether to renew, redesign or internalize
At each review horizon, compare evidence with the original market and economics assumptions. Renew when targeting quality, accepted conversations and learning justify continued investment. Redesign when a specific constraint can be corrected. Stop when the market, proof, channel or sales follow-up cannot support the motion.
Internalize when the campaign is durable, strategic volume justifies dedicated people and management can recruit and coach the function. Outsourcing is a model choice, not a permanent default.
Outsourced SDR governance scorecard
- Audit one sample before increasing volume.
- Track client response time as well as provider activity.
- Keep rejection reasons structured.
- Export assets and data regularly.
| Control | Good practice | Failure signal |
|---|---|---|
| Ownership | One accountable owner on each side | Several approvers and no decider |
| Evidence | Research and replies visible at record level | Activity dashboard only |
| Qualification | Written, observable and audited | Negotiated after each meeting |
| Response | Expert and sales replies have service levels | Interested prospects wait days |
| Learning | Decisions and test history documented | Provider knowledge disappears at exit |
Frequently asked questions
Who should manage an outsourced SDR team?
Use one client-side owner with authority over targeting, approvals, sales response and provider decisions. Senior experts can support replies and discovery, but one person must own the operating system.
How often should an outsourced SDR team meet with the client?
A weekly evidence and decision review is a practical default during launch and active testing. Mature programs may adjust cadence, but urgent replies and risk issues need defined routes outside scheduled meetings.
Which outsourced SDR metrics matter most?
Track research approval, replies by category, response time, booked meetings, attendance, ICP and qualification fit, sales acceptance, opportunities and disqualification reasons. Activity counts explain capacity but not commercial value.
Should the agency have access to our CRM?
Often yes, with least-privilege permissions and documented ownership, exports and removal. The required access depends on workflow; avoid unmanaged shared credentials and provider-only records the client cannot retrieve.
Sources and methodology
Provider and market guidance was reviewed for recurring management practices. The operating model distinguishes provider execution from the client's non-transferable ownership of claims, expert sales work and commercial decisions. These sources were checked on August 17, 2026.