Customer Support Platform

Illustrative case Fictional example

This fictional business case demonstrates decision analysis and approval-document design. The organization, figures, benefits, and outcomes are illustrative; they are not evidence of work performed for a real client.

Domain
Customer operations software
Delivery approach
Agile, with incremental funding gates
Scenario
Reduce avoidable support demand while testing which self-service capabilities customers will adopt and successfully use.
Decision sought
Approve discovery and conditional staged funding for an integrated self-service and support platform.
Investment scale
USD 450,000 Year 0 ceiling; USD 1.28 million modeled total
Planning horizon
Three operating years after initial investment
Primary constraints
Adoption uncertainty, integration complexity, service quality, and limited cash-releasing benefits.
Evidence basis
Illustrative contact volumes, handling costs, adoption targets, and staged product assumptions.
Demonstrates
Outcome-based product funding, evidence-led backlog decisions, benefit classification, and stop-or-scale governance.

Document Control

Field Value
Status Approval draft, version 1.0
Sponsor role Director of Customer Operations
Product owner Head of Support Products
Approving body Customer Support Platform Investment Review
Decision requested Approve discovery and conditional staged funding, up to USD 450,000 in Year 0
Appraisal horizon 3 operating years after initial investment
Base date 1 January 2027
Discount rate 8% nominal; year-end cash flows
Next review Gate 1 review on 12 February 2027, after six-week discovery

Executive Summary

The fictional operation receives 240,000 assisted contacts annually at USD 8.50 each: USD 2.04 million of handling effort. Sixty percent concern repeatable issues, yet self-service resolves only 8% of eligible journeys.

Approval is sought for an incremental platform integrating knowledge, guided resolution, case creation/status, and analytics. A USD 1.28 million investment avoids 196,000 contacts in the base case, generating USD 1.666 million gross value, USD 233,000 NPV, and discounted payback in month 29.

Only USD 790,000 is cash-releasing; the remainder is growth and service capacity. Agile delivery fits stable outcomes but uncertain adoption, behavior, integration, and solutions. It is evidence-driven investment with gates—not absent governance.

Strategic Case and Current State

The outcome is lower customer effort and growth without proportional support cost. Discovery must validate these management estimates before MVP funding:

Baseline measure Current estimate
Assisted contacts 240,000 per year; forecast to grow 6% annually without intervention
Repeatable contacts 60% of volume
Average handling cost USD 8.50 per contact, including labor and variable supplier charges
Annual gross handling cost USD 2.04 million
Eligible journeys resolved through self-service 8%
Median first response / resolution 18 / 42 hours
Post-contact satisfaction 72% positive

Fragmented knowledge makes customers repeat details or request status; manual work obscures failed journeys.

Objectives and Success Measures

Release an accessible MVP within six months. Within 12 months, achieve 25% eligible-user adoption, 20% verified self-service resolution, 78% satisfaction, and at least 15% avoidance against the fixed 240,000-contact baseline. By Year 2, target 30% avoidance against that same baseline (72,000 annually) without weakening escalation or quality.

“Resolution” requires confirmed success or no same-issue contact within seven days; views and bot sessions are not benefits.

Constraints and Dependencies

Existing identity, case, analytics, privacy, accessibility, and retention controls apply. Staffed routes remain for vulnerable, complex, disputed, or high-risk cases. Benefits depend on classification, content, telemetry, APIs, security review, and workforce action; legacy replacement is not assumed.

Options

  1. Status quo: maintain channels and local content. Low disruption; growth and fragmentation continue.
  2. Buy fixed-feature SaaS: configure a packaged portal for an indicative three-year USD 1.05 million. Faster standard capability, but weaker identity/case fit and less scope flexibility.
  3. Incrementally build and integrate: combine managed components with custom journeys, integrations, and measurement. Evidence can redirect uncertain scope and funding.

Options Appraisal

Scores are 1 (poor) to 5 (strong), based on current evidence rather than false precision.

Criterion Weight Status quo Fixed SaaS Incremental platform
Strategic alignment 20% 1 3 5
Customer value and testability 20% 1 3 5
Financial potential 20% 2 3 4
Delivery and integration feasibility 20% 5 3 3
Flexibility / reversibility 10% 2 2 5
Risk and governance 10% 2 3 4
Weighted score 100% 2.2 3.0 4.3

The incremental platform exposes uncertainty early and preserves stopping choices. Scoring does not replace discovery or due diligence.

Recommended Option and Staged Scope

Discovery (six weeks): validate taxonomy and unit cost; test needs and content; prove interfaces; establish privacy, accessibility, and MVP requirements.

MVP (four months): search and knowledge for five journeys, guidance for two, authenticated case creation/status, escalation, and measurement.

Follow-on increments: fund evidenced improvements such as more journeys, agent knowledge reuse, status notifications, or bounded automation.

Exclusions are CRM replacement, unrestricted generative AI, channel migration, international rollout, voice replacement, and a fixed backlog. Approval covers outcomes, an MVP hypothesis, constraints, and limits—not every feature.

Financial Case

Figures are rounded nominal USD; revenue and satisfaction are not monetized.

Incremental cost Year 0 Year 1 Year 2 Year 3 Total
Discovery, product, and design USD 75k — — — USD 75k
Software and integration delivery USD 250k USD 180k USD 40k USD 40k USD 510k
Subscription, cloud, security, tooling USD 45k USD 90k USD 110k USD 115k USD 360k
Change, content, and support readiness USD 50k USD 60k USD 25k USD 25k USD 160k
Internal backfill and contingency USD 30k USD 50k USD 45k USD 50k USD 175k
Total cost USD 450k USD 380k USD 220k USD 230k USD 1.280m

The current 240,000-contact annual volume is the fixed denominator for all avoidance targets: Years 1–3 avoid 40,000 (16.7%), 72,000 (30%), and 84,000 (35%) contacts. Although assisted contacts are forecast to grow 6% annually without intervention, the benefit model conservatively excludes that growth and values only these fixed-baseline volumes at USD 8.50 each. Benefits start after launch and require verified resolution.

Base-case value Year 1 Year 2 Year 3 Total
Avoided contacts 40,000 72,000 84,000 196,000
Gross avoided handling value USD 340k USD 612k USD 714k USD 1.666m
Of which cash-releasing USD 100k USD 300k USD 390k USD 790k
Of which capacity / service value USD 240k USD 312k USD 324k USD 876k
Net economic cash flow USD (40k) USD 392k USD 484k USD 836k

Including Year 0, NPV is USD 233,000, modeled with Year 1–3 net cash flows at each year-end. For payback timing only, interpolation assumes costs and benefits accrue evenly through each operating year; on that convention, undiscounted payback is around month 27 and discounted payback month 29. Cash-releasing benefits alone produce negative USD 514,000 NPV; approval therefore explicitly values growth-absorbing capacity. Cumulative cost is USD 6.53 per avoided contact versus USD 8.50 handling cost.

Sensitivity NPV Approximate outcome
Base case USD 233k Discounted payback month 29
Avoided contacts 25% lower USD (120k) No payback within horizon
All costs 20% higher USD (1k) Approximately break-even
Avoided contacts 20% higher USD 515k Undiscounted payback about month 22

Sensitivity NPVs retain the year-end cash-flow convention. Any within-year payback timing shown in the table uses the same even-accrual interpolation as the base case.

Commercial and Delivery Approach

Select components and specialist integration competitively under capped work orders. Retain content, taxonomy, telemetry, and code; require portability, security evidence, service levels, exit support, and price protection.

A cross-functional team will release, measure, and prioritize hypotheses. Scope may change within controls; material cost, risk, architecture, or benefit changes require gate approval.

Product Roadmap and Funding Gates

Gate Evidence required Funding decision
0: Discovery Sponsor approval of this case Release up to USD 75k
1: MVP Baseline within ±10%; task success ≥70%; Year 0 integration estimate ≤USD 250k; no critical security issue Release remaining Year 0 funding, up to USD 375k
2: Scale At 8 weeks: adoption ≥20%; resolution ≥15%; satisfaction ≥75%; integration forecast within 15% Release next increment, up to USD 200k
3: Continue After 6 months: adoption ≥25%; verified resolution ≥20%; satisfaction ≥78%; cost per avoided contact ≤USD 12 and trending toward <USD 7 cumulative Approve remaining Year 1 work
Annual renewal Year 2 target: ≥72,000 avoided contacts; cumulative cost per avoided contact ≤USD 7; cash-release plan on track Approve Years 2 or 3 run funding

Failure at a gate triggers a stop, redesign, narrowed experiment, or revised business case; it does not automatically trigger more scope.

Risks, Disbenefits, Responses

Risk or disbenefit Response
Customers cannot resolve complex cases and repeat contact Start with bounded journeys; measure seven-day repeat contact; preserve staffed escalation
Poor content causes harm Owners, approval workflow, review dates, and audit history
Integration is slower or costlier than estimated Technical spike in discovery; capped work orders; stop if Gate 1 ceiling is exceeded
Digital exclusion Accessibility testing, assisted route, and no forced self-service
Automation shifts customer effort Track effort, complaints, abandonment, and satisfaction
Capacity value never becomes cash Quarterly workforce/supplier plan with Finance validation; report cash separately
Vendor lock-in or data leakage Portability clauses, minimal data sharing, security review, and tested exit plan

Benefits Realization

Measure Owner Cadence
Adoption among eligible exposed users Product owner Fortnightly after launch
Verified resolution and seven-day repeat-contact rate Support analytics lead Monthly
Avoided contacts against the fixed 240,000-contact baseline Customer operations lead Monthly
Satisfaction, effort, complaints, accessibility failures Customer experience lead Monthly
Unit cost, gross capacity value, and cash released Finance business partner Quarterly
Platform cost and cost per avoided contact Product owner and Finance At each gate

Finance recognizes cash only when budgets, hours, vacancies, or supplier commitments reduce. Operations records capacity redeployment and service impact.

Governance and Review Triggers

The sponsor chairs a monthly investment review with Product, Operations, Finance, Technology, Security, and Customer Experience. The product owner orders the backlog within approved outcomes; Finance validates benefits and control functions retain authority.

Review is triggered by any forecast above an applicable approved ceiling, integration cost above threshold, two months below adoption or resolution thresholds, satisfaction below 70%, a material privacy/security event, or excluded-scope expansion. In particular, any Year 0 forecast above the USD 450,000 authorization ceiling requires reapproval by the approving body before further commitment; no overrun tolerance applies. Re-baselining requires recorded approval.

Decision Required and Approval Conditions

Approve Option 3 and USD 75,000 for discovery. Release the remaining USD 375,000 Year 0 ceiling only after Gate 1. Years 1–3 assumptions of USD 380,000, USD 220,000, and USD 230,000 are not commitments.

Conditions are validated baselines, named benefit owners, Finance-approved cash plans, security/accessibility review, competitive selection, pre-launch measurement, and gate compliance. Reapproval is required if discovery makes NPV negative, removes horizon payback, or adds an excluded item to MVP.