How to Build a CRM Business Case Your CFO Will Sign

A CRM business case is the internal proposal that gets a CRM approved: today’s cost in hours and missed follow-ups, the specific measures the CRM will move, its total cost including setup and admin time, the risks worth naming, and a 90-day checkpoint to prove the numbers, built from your own baseline, not an invented ROI percentage.

Most CRM pitches lead with a percentage: more pipeline, higher win rate, faster onboarding. A CFO who has sat through a dozen software pitches discounts every one of those numbers on sight, because none of them came from your data. The business case below skips the percentage and works from five sections instead, each filled in with your own team’s numbers.

What five sections does a CRM business case need?

A business case that survives a budget review has five sections, in this order. Skip one and the reviewer asks for it anyway, which costs you a second meeting.

1. Today’s cost. What the current process costs in hours and in deals that stall from missed follow-up, calculated below, not estimated.
2. The three measures you will move. Named in advance, with the formula for each, so the checkpoint has something specific to check.
3. Total cost. License, setup and the admin time a CRM actually takes to run, not just the price on the pricing page.
4. Risks. What could go wrong, named before it happens rather than explained after the fact.
5. A 90-day checkpoint. A date on the calendar when the three measures get reported back, whether they moved or not.

How do you calculate today’s cost of not having a CRM?

Today’s cost has two parts: the hours your team spends on manual tracking, and the revenue at risk from follow-up that never happens. Calculate both from your own week, not an industry average: a number you cannot defend in the room is worse than no number.

Manual-tracking cost: hours per rep per week spent updating spreadsheets, hunting for the last email thread, or rebuilding a forecast from memory, multiplied by a fully loaded hourly cost and by 52 weeks.

Missed-follow-up cost: the deals that go quiet because nobody set a reminder, multiplied by your average deal value and a conservative estimate of how many would have closed. State it as an estimate: a defensible estimate is enough to make the case.

Example (illustrative numbers): a 12-rep B2B SaaS team in Austin puts its own numbers through both formulas.

That total is what goes at the top of the business case: your own number, not a vendor’s average.

Which three measures should the business case commit to move?

Pick three, no more. A business case that promises to move eight numbers proves none of them by day 90. Our guide to the benefits of a CRM defines eleven measures, each with its numerator and denominator in plain words: choose three that match what you just calculated.

• Time to first response on a new lead, if missed follow-up was the bigger cost driver above.
• Admin hours per rep per week, measured the same way you measured it in the table, checked again three months in.
• Forecast accuracy (what the pipeline said would close against what actually closed), if the real objection in the room is trusting the forecast. Gartner’s February 2020 release on its State of Sales Operations survey found only 45% of sales leaders and sellers had high confidence in their organization’s forecasting accuracy, which is why this measure carries weight with finance reviewers on its own.

Write down how each measure will be calculated before you buy anything. A measure with no defined formula cannot be checked at the 90-day mark; it can only be argued about.

How do you calculate the total cost of a CRM, including admin time?

License cost is the easy part, and the part every vendor pitch leads with. The number that decides whether the case survives is the one under it: what it costs to set the system up and keep it running.

Total cost = license (seats × price) + setup hours × hourly cost + ongoing admin hours per month × hourly cost × 12. Senitix CRM’s pricing page has the per-seat price and seat minimums for each plan; put that figure into the license line rather than typing a number that will be out of date by the time the case is reviewed.

Example (illustrative numbers): the same 12-rep team budgets one week of an administrator’s time to configure pipelines and import existing records, then two hours a month afterward to maintain fields and reports. At $50 an hour, that is $2,000 to set up and roughly $1,200 a year to maintain, on top of the license.

What risks should a CRM business case name?

Naming a risk under-promises rather than over-promises, and a finance team notices the difference between a pitch and a plan.

• Adoption risk. A CRM the team does not use produces none of the three measures above. Our guide to CRM cost per user covers what an unused seat actually costs.
• Migration risk. Existing spreadsheets and past deal history take real hours to import correctly: put that time in the setup line above, not in a footnote.
• Wrong-tier risk. Buying a plan that lacks a feature the case depends on. Check the feature list against the plan before committing to a number someone else will hold you to.

How do you set a 90-day checkpoint?

1. Day 0. Record the baseline for all three measures, the same way you will measure them at day 90.
2. Day 30. Confirm the data migrated correctly and the team is logging activity in the new system, not a parallel spreadsheet.
3. Day 60. Read the fastest-moving measure, usually time to first response, and flag it early if it has not moved.
4. Day 90. Report all three measures against the baseline to whoever approved the business case, including any that did not move.

Reporting a measure that did not move is what makes the next business case easier to approve. A case that only ever reports wins starts to read like marketing the second time around.

What mistakes weaken a CRM business case?

• Leading with an industry ROI percentage instead of your own baseline from the table above.
• Leaving admin time out of the total cost, so the real number appears for the first time after the contract is signed.
• Committing to more than three measures, so none of them get a clear formula.
• Naming no owner for the 90-day report, so it quietly does not happen.
• Treating the checkpoint as optional once the budget is approved, rather than as part of the approval.

How does Senitix CRM fit into a CRM business case?

None of the calculations above depend on which CRM you choose, which is the point of building the case first. If Senitix CRM is one of the options, the numbers for the total-cost section, including seat price and seat minimums, are on the pricing page. Piloting the calculations costs nothing on Free while you build the case, and our guide to choosing a CRM covers the criteria to compare once it is approved. When the case is ready for a budget conversation, talk to us and we will work through the numbers with you.

Frequently asked questions

How long should a CRM business case be?

Short enough to read before a meeting: one page per section, five sections, so two to three pages total. A CFO reviewing a software request wants the five numbers and the checkpoint date, not a narrative about the product. Put supporting detail, like the full calculation behind today’s cost, in an appendix rather than the main page.

Do I need an ROI percentage to get CRM budget approved?

No. An ROI percentage borrowed from a vendor or an industry report describes someone else’s team, not yours, and an experienced reviewer discounts it accordingly. Your own today’s-cost and total-cost numbers, even rough ones stated as estimates, carry more weight because they can be checked against your actual pipeline at the 90-day mark.

Who should own the 90-day checkpoint?

The manager who requested the CRM, not IT and not the vendor. Ownership means calendaring the day-90 date when the case is approved and being the one who reports the three measures, including any that did not move. A checkpoint with no named owner is the part of the plan most likely to be skipped.

What if the CFO asks for a payback period?

Wait until you have 90 days of real data rather than estimating one before you buy. Once the three measures have a first reading, divide total cost by the monthly value each measure represents (for example, hours saved per month times hourly cost) to get a payback period built from your own numbers instead of a guess made before the system existed in your workflow.