The Procurement Problem
You know your team needs an immersive development experience. You've seen the data. You've read the case studies. You're convinced this is the right investment.
Then the request hits procurement. They see a number. They compare it to cheaper alternatives. They ask why you can't do this with an internal facilitator and a conference room. They suggest a half-day workshop instead of a full experience.
This happens because you submitted a request for an expense. What you needed to submit was a business case for an investment. The language difference changes everything.
Expense vs. Investment
An expense is a cost with no measurable return. Office supplies. Coffee for the break room. Most procurement processes are designed to minimize expenses. Find the cheapest vendor. Negotiate the price down. Cut the scope until it fits the budget.
An investment is a cost with a projected return. Nobody asks the cheapest vendor to manage the pension fund. The question for investments isn't "how do we spend less?" It's "what's the expected return?"
When you present team development as an expense, procurement does their job and minimizes it. When you present it as an investment with projected returns, the conversation shifts from "can we do this cheaper?" to "is the projected return credible?"
Building the Business Case
Step 1: Quantify the current cost of dysfunction. Every team has measurable dysfunction costs. Decision delays cost meeting hours multiplied by loaded labor rates. Rework costs the hours spent redoing work that could have been done right the first time. Team dysfunction's hidden costs include turnover, lost productivity, and missed opportunities.
Calculate these for your team. Be conservative. Use real numbers. If your team of 12 leaders (average loaded cost $150/hour) spends an extra 5 hours per week in unnecessary meetings, that's $9,000 per week. $468,000 per year. In meetings that don't need to happen.
Step 2: Project the improvement. Learn2 clients provide the benchmarks. When ArcelorMittal put 710 leaders through the Save the Titanic experience with Duke Corporate Education, decision-making speed improved 30-40%. Freedom Mobile's save rates went from 47% to 86%, representing $4M in annual value. Bell MTS grew revenue from $800M to $1.4B.
You don't need ArcelorMittal-sized results. If the experience reduces your team's unnecessary meeting time by 20% (a conservative estimate), that's $93,600 per year in recovered productivity. The experience pays for itself in the first quarter.
Step 3: Compare alternatives honestly. Procurement will ask about cheaper options. Help them compare apples to apples.
A half-day workshop costs less. It also produces less. Lecture-based formats show 5-10% behavior change. Immersive experiences show 60%+ behavior change. If the workshop costs $5,000 and changes nothing, the real cost is $5,000 plus the ongoing cost of the dysfunction it didn't fix.
A full immersive experience costs more upfront and produces measurable, lasting change. The cheaper option that doesn't work is the most expensive choice.
Step 4: Define the measurement plan. Procurement respects what gets measured. Present your measurement framework upfront. "We'll measure decision velocity before and after. We'll track meeting productivity ratios for 90 days. We'll report the results to leadership at the 90-day mark."
This signals that you're serious about returns, not just requesting a feel-good event. It also gives procurement the accountability they need to approve a premium investment.
The One-Page Business Case Format
Procurement doesn't read long proposals. They scan one-pagers. Here's the format that gets approved:
Current state: Quantified dysfunction costs. Real numbers from your team. "Our 12-person leadership team spends an estimated $468K/year in decision delays and unnecessary meetings."
Proposed investment: The experience, the cost, and the timeline. "A 3.5-hour Save the Titanic immersive team experience for 12 leaders. Investment: [amount]. Timeline: single half-day."
Projected return: Conservative estimates based on client benchmarks. "If we achieve a 20% improvement in decision speed (vs. 30-40% benchmark), projected annual savings: $93,600. ROI: [X]% in year one."
Measurement plan: How you'll prove the return. "Baseline measurements begin 2 weeks before the experience. 30-day and 90-day check-ins. Report to leadership at 90 days."
Risk of inaction: What happens if you don't invest. "Current dysfunction costs continue compounding. Team development ROI compounds over time — each quarter of delay increases the cumulative cost of inaction."
Handling Common Objections
"Can we do a half-day instead?" "A half-day workshop produces lecture-based information transfer. The results we need require behavior change, which requires immersive practice under pressure. The full experience is the minimum effective dose."
"What about doing this internally?" "Internal facilitators can run effective programs for many topics. This specific simulation requires certified facilitators and proprietary materials that create the pressure environment where behavior change happens. Like flight simulators for pilots, some things require specialized equipment."
"Can we do a pilot with one team first?" "Yes. We recommend starting with one team, measuring the results, and using that data to justify broader investment. A successful pilot makes the case for scaling."
The business case for team development is strong when it's built on numbers, not feelings. Procurement approves investments with projected returns. Give them the numbers and the measurement plan, and the conversation changes.
Book a 20-minute walkthrough and I'll help you build the specific business case for your team with numbers that speak procurement's language.
Read next: Why the Cheapest Team Event Costs the Most