Weekly program reportSpecimen
Program 2026-114, week 3 of 8
- TAL accounts reached
- Roles covered, tier 1
- Accepted leads against plan
- Acceptance rate
- Make-goods open
- SAL and SQL, from CRM
- Pipeline influenced
Signed off by the delivery owner
Home / Coverage and conversion
Coverage first, conversion next, and every number in your board's language.
A buying group of 14 doesn't sign off on one form fill. This page shows how we measure coverage on target accounts, where our responsibility ends, and how closed-loop CRM data carries the report through to pipeline.
Roles coveredPer account, against the roles you name
Accounts reachedAgainst the target account list, by tier
ConversionAccepted lead to SAL, SQL and opportunity
Cost per opportunityOnce CRM outcomes flow back
An account counts as covered when the people who sign the deal have heard from you.
You name the roles that matter for each tier. We track every account against that list and show the gaps, so the next program goes where coverage is thin.
| Account | Tier | CIO | VP infrastructure | CISO | Platform lead | Procurement | Finance | Coverage |
|---|---|---|---|---|---|---|---|---|
| Account A | 1 | 4 of 6 | ||||||
| Account B | 1 | Open opportunity, suppressed | ||||||
| Account C | 2 | 3 of 6 | ||||||
| Account D | 3 | 1 of 6 |
Accepted lead in this roleEngaged, not yet a leadSuppressed, live deal or customerNot yet reached
Specimen, not a real program. Coverage counts a role as covered once an accepted lead holds it; engaged roles show momentum but don't count yet.
We own the result up to the accepted lead, and we report everything after it once your CRM talks back.
Target accountsMatched to the TAL, by tier
Accounts reachedAt least one role touched in-language
Roles coveredAccepted leads per named role
Accepted leadsPassed your criteria and our ten checks
SALSales accepted, from CRM status
SQLSales qualified, from CRM status
OpportunityOpportunity created on the account
Pipeline influencedValue of opportunities on covered accounts
We deliver it and stand behind itWe report it from your CRM outcomes, and your sales team owns it
Every closed-loop week makes the next week's leads better.
- We deliverLeads land in your MAP or CRM with role, source and answers
- SDRs work themYour team accepts, qualifies or rejects with a reason
- Outcomes flow backStatus and reason codes, shared under the DPA
- Checks tightenRejection reasons tune targeting, questions and checks
Outcome sharing is optional and covered by the data processing agreement. Without it, we report up to the accepted lead and coverage per account.
Every number in the report has one definition, agreed before the program starts.
Marketing, sales and finance read the same page, so each metric is defined once, sourced once and never redefined mid-program.
| Metric | Definition | Where it comes from |
|---|---|---|
| TAL match rate | Share of target accounts we can reach in the agreed markets and roles | Feasibility check |
| Accounts reached | Target accounts with at least one role touched in-language | Saravus engine |
| Roles covered | Named buying-group roles holding an accepted lead, per account | Saravus engine |
| Acceptance rate | Accepted leads as a share of leads delivered | Saravus engine and returns |
| Make-goods | Returned leads replaced or credited inside the window | Returns log |
| SAL and SQL | Leads accepted, then qualified, by your sales team | Your CRM, when shared |
| Opportunities | Opportunities created on covered accounts | Your CRM, when shared |
| Pipeline influenced | Value of opportunities on accounts the program covered | Your CRM, when shared |
| Cost per opportunity | Program cost divided by opportunities created | Invoice and CRM |
The weekly report, on one page you can forward to the board.
One page, the same layout every week, forwardable as it stands. Figures fill in as the program runs; the gray bars are placeholders.