A business case for AI outbound that survives a CFO and a procurement review needs seven fixed sections — problem statement, baseline, intervention, financial model, risk register, decision criteria, exit plan — and one honest number up front: The Bridge Group’s 2025 survey of 351 B2B companies found average SDR ramp time is 3.0 months, so any model that books revenue before then is guessing.
The short answer: Build the case as a template — problem, baseline, intervention, financial model, risk register, decision criteria, exit plan — and use an honest financial model with clearly labelled placeholder inputs, not real numbers dressed up as a forecast. The two things that get a business case rejected are claiming revenue that would have arrived anyway and measuring closed-won inside a window shorter than your sales cycle. A procurement team will want a risk register covering brand, compliance (TCPA, Spam Act, DNC), data privacy and vendor lock-in before infosec even opens the questionnaire.
Most AI outbound pitches die in the same meeting: not because the champion couldn’t sell the idea internally, but because they walked in with a slide deck and walked out needing a document. A CFO does not fund enthusiasm. A procurement team does not sign off on a vendor demo. An infosec reviewer does not care how good the voice model sounds. Each of them wants a specific artefact, and if you haven’t built it before the meeting, you’re building it live, badly, under questioning.
This page is that artefact. It’s a template you can copy into your own document, a financial model you can rebuild with your own numbers, and a risk register procurement will recognise because it’s the same shape as the one they already use for every other vendor. Send it to a colleague who’s about to have the same fight you just had.
The document structure procurement actually wants to see
Internal business cases that get approved on the first pass tend to share a structure. Skip a section and you invite the exact question it would have pre-empted. Use the table below as a build order — each row is a heading in your own document.
| Section | What belongs in it |
|---|---|
| Problem statement | One paragraph, no adjectives. What capacity gap exists today — leads not followed up, dormant CRM records, after-hours enquiries, tier-3 accounts nobody calls — stated as a fact with a number attached, not a feeling. |
| Current-state baseline | What you already spend to run outbound today: headcount, fully-loaded cost per rep, current connect and conversion rates, current pipeline generated per rep per month. This is the number everything else gets measured against. |
| Proposed intervention | What specifically changes — additional conversation volume, coverage of accounts reps don’t reach, after-hours response — and what stays the same (reps still own discovery, negotiation and close). |
| Financial model | The arithmetic connecting the intervention to revenue, with every input labelled and every assumption stated. See the worked example below. |
| Risk register | Every way this can go wrong, how you’d know, who owns the mitigation. Procurement will ask for this whether you offer it or not — better to arrive with it built. |
| Decision criteria | What success and failure look like, defined before the pilot starts, with a named metric, a threshold and a date. |
| Exit plan | What happens if it doesn’t work — and, less obviously, what happens if it does and you want to leave the vendor later. Data ownership, notice period, portability. |
The financial model, done honestly
The fastest way to lose credibility with a CFO is to hand over a model where every number happens to be flattering. The fix isn’t fewer numbers — it’s showing your working with inputs labelled as exactly what they are: placeholders. Replace every figure in the table below with your own before you present it. None of these are LeadsNow figures and none of them are a forecast of what any vendor will deliver — they exist so the structure of the arithmetic is visible.
| Input (illustrative — replace with your own) | Placeholder value |
|---|---|
| Current SDR fully-loaded cost | $150,000/year |
| SDR ramp time to full productivity | 3 months |
| Conversations per rep per day | 25 |
| Connect rate | 8% |
| Conversation-to-meeting rate | 20% |
| Meeting-to-opportunity rate | 40% |
| Opportunity-to-win rate | 25% |
| Average contract value | $40,000 |
| Sales cycle length | 90 days |
Walking the arithmetic through: say the proposed intervention adds 400 conversations a month that current headcount structurally can’t reach — dormant database records, after-hours enquiries, tier-3 accounts below the threshold where a rep’s time is justified. At a 20% conversation-to-meeting rate that’s 80 meetings. At 40% meeting-to-opportunity, 32 opportunities. At a 25% win rate, 8 new deals a month. At $40,000 average contract value, that’s $320,000 a month of gross new revenue attributable to the added conversations.
Do not present that $320,000 figure to a CFO as the business case. It is the gross output of the funnel before you’ve asked the two questions that determine whether any of it is real money.
The two mistakes that get business cases rejected
The first is claiming incremental revenue that would have arrived anyway. Some share of those 8 deals were prospects who’d have converted eventually through another channel, a different rep, or their own initiative — the funnel math can’t tell you which ones. The CFO’s real question isn’t “how much revenue is attributed to this channel,” it’s “how much revenue exists because of this channel that wouldn’t exist otherwise.” Attribution and incrementality are different numbers and the gap between them is usually where a business case falls apart under scrutiny. Our guide to running an incrementality test on lead gen spend walks through holdout and spend-down designs that turn the gross funnel number into a defensible one — run one before you present the final figure, not after someone in the room asks for it.
The second is modelling closed-won revenue inside a period shorter than the sales cycle. With a 90-day illustrative cycle above, an 8-week pilot cannot show closed revenue — the deals it generates are still moving through legal review when the pilot report is due. Measuring “revenue generated” in that window and getting zero doesn’t mean the intervention failed; it means you measured the wrong thing at the wrong time. This compounds badly at enterprise deal sizes, where cycles routinely run two to three quarters longer than the pilot itself. The fix is to measure leading indicators — qualified meetings, documented opportunities — inside the pilot window, and closed revenue on a longer, separately agreed timeline. Our pages on structuring a falsifiable AI outbound pilot and on what changes between SMB and enterprise lead generation both cover this timing mismatch in more detail than belongs here.
The risk register a procurement team will ask for
If you don’t bring this table, procurement builds their own version of it and you lose control of the framing. Bring it first.
| Risk | How it shows up | Mitigation | Who owns it |
|---|---|---|---|
| Brand risk from an AI agent speaking to prospects | Off-brand tone, a bad interaction screenshotted and shared publicly, a prospect who feels misled about talking to a bot | Approved script library, disclosure policy, human escalation path, recorded-call QA sampling | Marketing / brand lead |
| Compliance exposure — consent, DNC-equivalent lists, TCPA/Spam Act | Regulator complaint, opt-out not honoured, contact outside permitted calling windows | Timestamped consent capture, suppression list synced in real time, jurisdiction-aware calling hours | Legal / compliance |
| Data privacy — where prospect data sits | Data residency unclear, sub-processor list incomplete, no answer on whether your data trains a shared model | Written data flow map, residency commitment in the contract, sub-processor disclosure | Infosec / DPO |
| Deliverability damage to the corporate domain | Shared sending domain or number, spam complaints tank sender reputation, marketing email starts landing in spam | Dedicated sending domain/number, warm-up schedule, ongoing reputation monitoring | Marketing ops / IT |
| Vendor lock-in and data ownership on exit | Discovering on cancellation that transcripts, consent records or the suppression list aren’t portable | Exit terms negotiated before signing — export format, timeframe, cost — and tested with a real export request | Procurement / legal |
| The pilot being unfalsifiable | No predefined failure condition, so any outcome gets reinterpreted as a qualified success | A stop condition fixed before launch: a number, a metric, a date | Sales leadership / the champion running this |
The vendor lock-in row deserves its own homework before you sign anything. Our page on what you own when you leave a lead gen vendor lists exactly what to specify — contact records, full conversation transcripts, consent evidence and, easy to forget, the suppression list itself, since losing it means you’d be contacting past opt-outs without consent evidence on file.
What infosec will ask before they sign off
This section is deliberately just the questions, not the answers — your infosec team will ask them in their own order and won’t take a vendor’s prepared answer as a substitute for asking. Expect all of the following:
- Where does data live — call recordings, transcripts, contact records, backups — and in which region?
- Who are the sub-processors, and is there a current, disclosed list?
- What’s the retention period, who sets it, and can we force earlier deletion?
- Who has access — internally and via offshore contractors — and how is that access controlled and logged?
- Does our data train a model that other customers benefit from?
- What’s the breach notification SLA?
- Is there real isolation between our account’s data and every other client’s?
Our page on data privacy and AI sales agents for enterprise buyers goes through each of these in more depth — useful to read before the review, not during it.
Decision criteria: define success and failure before you start
Write this section before the pilot begins, not after the results come in. A decision criterion has three parts in one sentence: a named metric, a threshold, and a date. “It went well” is not a decision criterion. “Fewer than 18 qualified meetings booked against our written qualification standard by [date]” is. Fix the metric to something the vendor can’t redefine mid-pilot — booked-and-held meetings against a written standard, not dials, not conversations, not revenue inside a window shorter than your sales cycle allows. Our guide on structuring a pilot that can actually fail sets out the full mechanics: control group, minimum volume to detect an effect, and a duration long enough to separate signal from setup noise.
Where LeadsNow fits
The template above is deliberately vendor-neutral — it works whether you’re evaluating us, a competitor, or an internal build. Where LeadsNow fits into it: we’ve booked 50,769+ AI-driven sales appointments and generated 1M+ leads since 2017, with 25 filmed client case studies you can watch rather than take our word for. We serve corporate and enterprise sales teams specifically — see our page on lead generation for corporate sales teams for how the intervention slots alongside an existing team rather than replacing it. But the page you’re reading isn’t a pitch. Its job is done if you can take the structure above into a CFO meeting for any vendor and come out with a decision instead of another meeting.
Frequently asked questions
How long should an AI outbound pilot run before we judge it?
Long enough to separate signal from setup noise and short enough to get a decision. Six to eight weeks is a reasonable floor, with the first one to two weeks excluded from measurement because that’s ramp and calibration, not steady-state output. Judge leading indicators — qualified meetings, documented opportunities — inside that window, and reserve closed-revenue judgement for a separately agreed date matched to your actual sales cycle.
What’s a realistic fully-loaded cost for an in-house SDR, for comparison?
Published estimates vary by market and team size. SalesHive’s vendor breakdown puts the fully-loaded cost of an in-house SDR at roughly $110,000–$210,000 a year once benefits, tooling, management overhead and turnover are included — typically two to three times base salary alone. Treat this as vendor-published data, not independent research, and rebuild it with your own payroll numbers.
How long does it actually take a new SDR to become fully productive?
The Bridge Group’s 2025 survey of 351 B2B companies — the closest thing this space has to an independent benchmark — found average ramp time of 3.0 months, the lowest figure the survey has recorded since 2010. Any headcount comparison in your financial model should account for this delay; a newly hired rep isn’t a fair comparison to a channel that’s already at capacity.
Are B2B sales cycles actually getting longer?
Ebsta and Pavilion’s 2024 benchmark analysis, covering 4.2 million opportunities across 530 companies and over $54 billion in revenue, found sales cycles running 38% longer than in 2021. That trend is exactly why measuring closed revenue inside a short pilot window is increasingly likely to produce a false negative.
What’s the single biggest reason internal business cases for AI outbound get rejected?
In our experience it’s not the financial model — it’s the absence of a risk register and decision criteria defined before the pilot starts. A CFO can forgive a rough revenue estimate. A CFO cannot approve a proposal with no stated failure condition, because that reads as a proposal nobody can be held accountable to.
Do we need a formal incrementality test before presenting the business case, or can that come later?
Present the business case with incrementality flagged as an open question and a named test design, not with a made-up incrementality percentage. Run the actual test during the pilot itself, using a holdout or matched-cohort design, and bring the result to the renewal decision rather than the approval meeting.
Does this template work for a build-vs-buy decision, not just a vendor pilot?
Yes — the structure doesn’t assume a vendor. Swap the financial model’s cost inputs for engineering and infrastructure cost if you’re evaluating an internal build, and treat the risk register the same way; brand risk, compliance exposure and data residency questions apply whether the AI agent is bought or built.
See if we’re a fit
A few quick questions. If it’s a fit, our live calendar loads on the next screen. If it isn’t, we’ll point you to free resources instead — you won’t have to sit through a sales call to find out.
We get paid a performance fee equivalent to 10–20% of the sales we help you generate.
Are you OK with that?
If you’re not willing to pay 10–20% as a performance fee, are you happy to pay a $4,000+ per month retainer?
Check If You Qualify 👇
How many leads per month do you currently get?
What’s your current advertising spend or marketing budget (Meta, Google, SEO, etc.)?
What’s the average sale worth to you over that customer’s lifetime?
Given your business currently gets less than 10 leads per month, we’d need to do much more groundwork to set up end-to-end sales systems. Are you OK with a $2,000/mo retainer to do so? (no lock-in)
What’s your work email?
Hey! We might be able to add $100k+ / mo... Enter your email to choose a time!
We’re probably not the right fit — yet
Our model is pay-on-performance — we only win when you’re making sales, and it works best alongside an active marketing engine with advertising budget to get seen. Booking a call now would waste your time, and we’d rather be straight with you.
Grab the free stuff instead — it’s the same playbook we use:
Read the growth blog · Lead-gen FAQ
When the timing’s right, come back — the calendar will be waiting.