Most proposals to bring in an offshore Salesforce partner stall in the same place: the approval meeting. Someone in finance asks what the real savings are, someone in security asks what could go wrong, and someone in the business asks how it affects delivery dates. If the answers are vague, the request is shelved.
A strong business case answers those questions before they are asked. It compares realistic options on total cost, quantifies the risks, and shows how you will know whether the decision is working. This guide gives you a section-by-section template, a worked example with the math shown, and tips for getting it approved.
What Decision-Makers Actually Want to See
Different approvers read the same document with different questions in mind:
APPROVER | THEIR CORE QUESTION |
Finance | What is the total cost, and what is the return against the alternative? |
IT / Salesforce owner | Will quality, architecture standards, and delivery pace hold up? |
Security and legal | Is our data protected, and are we compliant? |
Business sponsors | Will the roadmap move faster, and will users notice a difference? |
Procurement | Is the commercial structure sound, and are exit terms clear? |
Build the case so each of these can find their answer in under a minute.
The Business Case Template
Use these eight sections. Keep the whole document to a few pages, with details in an appendix.
- Executive summary (half a page)
State the decision you are asking for, the recommended option, the headline cost comparison, the main risks and how they will be handled, and the timeline. Write this last, but put it first.
Template: “We request approval to engage [partner type] to deliver [scope] over [period]. Compared with [current approach], we estimate [X] to have a lower total cost over [period] and [benefit]. Key risks are [A, B], mitigated by [controls]. We will review results at [milestones].”
- Problem and objectives
Describe the current situation in measurable terms: backlog size, delivery delays, vacancies, support response times, or the cost of the current model. Then define success.
- What is the roadmap or support demand over the next 12 to 24 months?
- What is the gap between demand and your current capacity?
- What outcomes matter most: cost, speed, coverage, skills, or flexibility?
- Scope of work
Be specific about what the partner will and will not do. Examples: new builds, enhancements, integrations, data migration, admin and managed services, testing, and release management—Mark which work stays in-house, such as business analysis, product ownership, or architecture sign-off.
- Options considered
Always compare at least three options so the recommendation looks reasoned and not predetermined:
- Status quo: continue as you are
- Hire in-house or use an onshore partner
- Offshore or hybrid partner
(See our guide to offshore vs onshore vs nearshore Salesforce team)
- Financial analysis
This is the section that wins or loses approval. Include:
- Direct delivery costs: hours multiplied by blended rates, by role
- Internal costs: management, review, governance, and meeting time, using a loaded cost per hour
- One-time costs: onboarding, knowledge transfer, security review, tooling, contract setup
- Risk allowance: a contingency for rework, delay,s and change requests
- Benefits: cost avoided, capacity added, faster delivery, coverage hours, reduced vacancy cost
- Sensitivity: What happens to the numbers if your assumptions are wrong
- Risk assessment and mitigation
List the risks honestly. Approvers trust a case that names its weaknesses.
RISK | LIKELIHOOD | IMPACT | MITIGATION |
Quality or rework is higher than expected | Medium | High | Acceptance criteria, code review, quality gates, pilot first |
Data security or compliance gap | Low to medium | High | Least-privilege access, masked sandboxes, contract clauses, security review |
Communication delays due to time zones | Medium | Medium | Overlap window, written handoffs, named leads |
Key-person dependency or attrition | Medium | Medium | Documentation, backup resources, replacement terms |
Vendor lock-in | Low to medium | Medium | Knowledge transfer, code ownership, and exit plan |
- Implementation plan
Show phases, owners, and dates: partner selection, security and legal review, pilot, transition, steady state. Include how you will manage knowledge transfer and governance.
- Success measures and review points
Define how you will judge the decision, and when. Examples:
- Cost per delivered story point, or cost per release
- Defect rate and rework percentage
- On-time delivery against plan
- Backlog reduction
- Support response and resolution times
- Stakeholder satisfaction
Set review points at 30, 9,0 and 180 days, with agreed criteria for continuing, adjusting, or stopping.
Worked Example: A Mid-Size Company's 12-Month Roadmap
Important: every number below is a hypothetical assumption chosen to illustrate the method. They are not market benchmarks. Replace each input with your own rates, hours, and internal costs.
Scenario: A company runs Sales Cloud and Service Cloud. Its 12-month roadmap and support needs equal about 6,000 hours of delivery effort. It is comparing two options.
- Option A: fully onshore partner
- Option B: hybrid model, with onshore leadership and architecture plus offshore build and support
Assumptions
INPUT | OPTION A (ONSHORE) | OPTION B (HYBRID) |
Onshore hours | 6,000 | 1,200 |
Onshore blended rate | $150 / hr | $150 / hr |
Offshore hours (before overhead) | none | 4,800 |
Offshore blended rate | none | $60 / hr |
Offshore coordination overhead | none | +10% extra hours |
Internal management time | 150 hrs | 250 hrs |
Internal loaded cost | $90 / hr | $90 / hr |
One-time transition cost | $0 | $25,000 |
Risk allowance (contingency) | 5% of partner cost | 10% of partner cost |
Notice that the example deliberately gives Option B more overhead, more internal management time, a transition cost, and a higher contingency. A business case that justifies the more expensive option by its extra friction is far more credible.
The math
Option A
- Partner cost: 6,000 × $150 = $900,000
- Internal management: 150 × $90 = $13,500
- Contingency: 5% × $900,000 = $45,000
- Total: $958,500
Option B
- Onshore cost: 1,200 × $150 = $180,000
- Offshore hours with overhead: 4,800 × 1.10 = 5,280 hours
- Offshore cost: 5,280 × $60 = $316,800
- Partner cost subtotal: $180,000 + $316,800 = $496,800
- Internal management: 250 × $90 = $22,500
- Transition (one-time): $25,000
- Contingency: 10% × $496,800 = $49,680
- Total: $593,980
The comparison
COST LINE | OPTION A | OPTION B |
Partner delivery | $900,000 | $496,800 |
Internal management | $13,500 | $22,500 |
One-time transition | $0 | $25,000 |
Risk allowance | $45,000 | $49,680 |
Total (year 1) | $958,500 | $593,980 |
Difference | $364,520 lower (about 38%) |
Stress-testing the result
A single estimate invites challenge, so show what happens when assumptions are less favorable. In this downside case, the offshore rate is $75 an hour, and coordination overhead rises to 20%:
- Offshore hours: 4,800 × 1.20 = 5,760
- Offshore cost: 5,760 × $75 = $432,000
- Partner cost subtotal: $180,000 + $432,000 = $612,000
- Contingency (10%): $61,200
- Total: $612,000 + $22,500 + $25,000 + $61,200 = $720,700
The saving versus Option A narrows to $237,800, or about 25%. The case still holds, but the range is now honest: roughly 25% to 38% under these assumptions.
What this example does not include: the value side. A hybrid model may also add capacity, shorten the backlog, extend coverage hours, or reduce vacancy costs. Those benefits are real but harder to price, so estimate them separately and conservatively, and label them as upside rather than baking them into the headline saving.
Putting a Value on the Non-Cost Benefits
If your approvers care about more than savings, add a simple benefits section using this structure:
BENEFIT | HOW TO MEASURE IT | EVIDENCE TO GATHER |
Faster delivery | Average lead time per request | Current backlog age and release cadence |
Added capacity | Hours or story points per sprint | Current throughput vs. demand |
Wider coverage | Hours of support coverage per day | Current response times outside business hours |
Access to skills | Certifications and cloud experience available | Gaps in your current team |
Reduced hiring risk | Time-to-fill and vacancy cost | Open requisitions and recruiter fees |
Use your own figures. If you cannot measure a benefit, describe it qualitatively and say so.
Common Mistakes That Sink a Business Case
- Comparing rates instead of totals. Include internal time, transition, and risk allowance.
- Using a single best-case estimate. Show a range and a downside scenario.
- Ignoring security and compliance. Involve those teams early and include their requirements.
- Hiding the risks. Naming and mitigating them builds credibility.
- No success measures. If you cannot define how to judge the decision, approvers will hesitate to make it.
- Skipping a pilot. A short paid pilot reduces risk and gives you real data for the full case.
- Leaving out the exit plan. Show how you would transition away if needed.
A Practical Way to Get It Approved
- Gather your real numbers first: demand, current costs, vacancies, backlog.
- Request comparable proposals from two or three partners using the same scope.
- Run the three scenarios: expected, upside, and downside.
- Pre-brief each approver with the section that matters to them before the formal meeting.
- Propose a staged commitment: a pilot or initial phase with clear review criteria, not an open-ended contract.
- Document the decision criteria, so success is judged on agreed measures.
Bottom Line
A good business case for an offshore Salesforce partner is not a sales pitch. It is a fair comparison of realistic options, with total costs, honest risks, sensitivity ranges, and clear success measures. If the numbers hold up under a downside scenario and the risks have named owners, approval conversations become far easier.
Use the template above, replace the example assumptions with your own, and let the analysis make the argument.
Need help building the numbers for your own Salesforce roadmap? Talk to our team about a discovery conversation and a comparable scope estimate.
