Sample case

Field service scheduling modernization

A $6.1M, five-year investment to replace spreadsheet and phone-based dispatch across 14 branches and 600 technicians. Follow it from the business need to the value it returned.

A representative case built in Arivue. Company, vendors and actuals are illustrative.

Business caseField service scheduling modernization✓ Baseline captured
The Ask
$6.1M
total investment
NPV
$1.3M
discounted return
ROI
44%
horizon, realistic
IRR
26%
Payback
34 mo
Recommendation
Proceed. Recommended: Vendor A field service suite, buy
Every cost line tagged QuoteGroundedEstimate

Sample case

1  Define

Start from the business need.

Two lines on the need and the details the team already has. Adaptive questions fill the gaps, the ones that move the case most first, grounded in the company’s strategy, stack and policies.

New caseDefine: context and discovery
Replace our spreadsheet and phone-based dispatch with a field service scheduling platform, rolled out in phases across our 14 branches. 600 technicians, 62% utilization today, overtime about $6M a year.
Company context applied
Adaptive discovery, ranked by impact
1
Which branches go first?High impact
2 pilot branches, then 3 rollout waves
2
What is the budget envelope?High impact
About $2.4M over the rollout
3
Who owns the first-time-fix target?Medium impact
Answer

Sample case

2  Build

Solution options, compared on your stack and priorities.

Cited research on peers, vendors and approaches. Each option with its pros, cons and assumptions, screened on budget, architecture and policy, then ranked on a weighted scorecard.

Research and options3 options, 1 recommended
Peer move

Competitors are moving dispatch off spreadsheets onto mobile platforms. [E-4]

Risk signal

Low first-time-fix rates drive costly repeat visits. [E-14]

Scorecard, weighted 1 to 5. Screened on budget up to $5.2M
Vendor A field service suite, buy ★4.24
Vendor B, configure on existing CRM2.99
Vendor C, custom build2.33
Weights from the priorities stated at intake: cost, time to value, risk, stack fit and strategic fit.

Sample case

2  Build

Every number traces to the line it came from.

Cost built bottom-up. Each line is a vendor quote, a grounded reference or a flagged estimate, and the Ask is the sum of its lines in every view and every export.

Biggest lever: replace the implementation estimates with a vendor quote. The coach says so too.

Efforts and costs16 lines, 7 shown
The Ask, 5-year totalOne-time $2.19M plus recurring $790K a year$6.1M
How firm each dollar is
Quote 33%Grounded 6%Estimate 61%
One-time
L45Architecture and detailed designinternal labor~ Estimateweak$76K$ Quote
L41Pilot implementation, 2 branchesinternal labor~ Estimateweak$33K$ Quote
L38Rugged tablets, 600 technicianshardwareGrounded · good fitstrong$384K$ Quote
L43Change management and trainingtraining~ Estimateweak$251K$ Quote
Recurring (per year)
L25Suite subscriptions, 640 × $641licenseQuote · good fitdefinitive$410K/yr
L29Support, SLA and maintenanceother~ Estimate · good fitweak$219K/yr$ Quote
L46Post-implementation run effortinternal labor~ Estimateweak$259K/yr$ Quote
↳ Reference: annual run and maintain is about 15 to 20% of the original build

Sample case

2  Build

Benefits modeled by type, tied to the P&L.

Cost reduction, productivity and avoidance each modeled their own way, adjusted for adoption, attribution and time to value, and mapped to the P&L line where the value lands.

Value driversTied to P&L lines
Value driverTypeP&L line
Overtime reductionCost reductionLabor cost
Utilization 62% to 72%ProductivityService capacity
Shorter drive timeCost reductionFleet cost
Fewer repeat visitsCost avoidanceService cost
Adjusted for
AdoptionAttributionTime to value
Benefit, year 1 to year 3$583K to $2.10M

Sample case

2  Build

The ask, the return, the recommendation.

NPV, IRR, ROI and payback come from a deterministic engine on the company’s rates. The figure on the first page is the figure in the cash flow.

From cash flow to NPVMost-likely scenario, 10% discount rate
UndiscountedAt 10%
Benefits, years 1 to 5$8.84M$6.48M
Recurring cost, years 1 to 5−$3.95M−$3.00M
One-time cost, year 0−$2.19M−$2.19M
Net$2.70M$1.30M = NPV
IRR26%vs 15% hurdle
ROI, 5-year
44%
Payback
34 mo
Hurdle
15%

Sample case

2  Build

How the NPV moves when the inputs change.

Each swing shows its base, so a reviewer can redo the math. Returns outside a plausible range are flagged for review.

NPV sensitivityBase NPV $1.30M
Benefits ±20%, of $6.48M discounted±$1.30M
Recurring cost ±20%, of $3.00M discounted±$599K
One-time cost ±20%, of $2.19M±$437K
Discount rate 8% to 12%±$223K
What-if sliders move benefits and costs and re-price ROI, NPV, IRR and payback together, on the same numbers.

Sample case

1 Define and 2 Build

A coach that strengthens your case.

As the team defines and builds the case, the coach points to what will matter most to the people who approve it: the questions your CFO or board will likely ask, the inputs that need a source, and the checks to clear before the case goes for approval.

Suggested next steps: firm up the cost with a vendor quote, address technician adoption, name a benefit owner.

Coach and checksProceed with conditions
Your CFO or board will likely ask
How firm is the $2.19M one-time cost?
What happens to payback if adoption runs a quarter late?
Checks before submission: 2 to resolve
Recommended option is the option financed
The Ask equals the sum of its cost lines
Benefits and costs on the same basis
A hard requirement conflicts with the optionOffline mode for technicians: confirm Vendor A
A projection has no sourceYear-1 adoption at 95%: add a reference

Sample case

3  Decide

Every choice along the way is on record.

Approved as version 3, with finance and architecture sign-off. The record keeps the options considered, the estimates, the value definitions and the approval: who chose, when, and on which numbers.

Review and decisionDecision recorded
Decision: approved, version 3
Ask $6.1M, NPV $1.3M. Baseline captured
Mar 12
Review: finance
Approved. One-time cost confirmed against vendor quotes
Mar 10
Review: architecture
Approved. Stack fit confirmed for Vendor A
Mar 6
Submitted for review
Routed through the reviewer chain
Mar 3
Top risks
HIGHTechnician adoption of the mobile app
HIGHIntegration delays with your CRM and ERP

Sample case

4  Measure

Value against what was approved.

Monthly actuals recorded against approved version 3. The gap is explained by timing, execution or external causes, and every change request links to its approval.

Outcomes and change controlAgainst approved version 3
Approved benefit, year 1
$583K
from the case
Realized to date
$512K
monthly actuals
Realization
88%
Gap: timing, wave 2 moved one quarter$41K
Gap: execution, adoption below plan$30K
Change control
CR-1 Rollout wave 2 moved one quarterLinked to approval v3

Sample case, illustrative actuals

See your own case in Arivue.

We build one of your current decisions with your team, at a level of detail you are comfortable sharing. Then a scoped pilot on one portfolio.

Start with a working session.

Bring a decision coming up in your next funding cycle.