Modeled scenario
Civil engineering firm: a Savings Map in practice.
A 210-person civil engineering firm opened a second office and accumulated overlapping collaboration, design, project, and reporting tools.
Modeled 2026-09-06210 employees
scenario profile
$610K annual software spend
modeled baseline
$153.4K combined opportunity
scenario estimate
All figures are hypothetical and do not represent past performance.
Savings Map
The decision matters as much as the dollar.
Vendor / capabilityBaselineDecisionYear 1 netRisk
Core project platform$185KKeep
Required capability; no change$0High
Required capability; no change$0High
Collaboration suite$74KCut
Remove unused and duplicate seats$31KHigh
Remove unused and duplicate seats$31KHigh
CRM$126KRenegotiate
Rightsize seats and renewal terms$42KMedium
Rightsize seats and renewal terms$42KMedium
Reporting workflow$88KReplace candidate
Pilot lower-cost workflow; net gate required$49K netMedium
Pilot lower-cost workflow; net gate required$49K netMedium
Design tools$137KKeep
Required for licensed production workflow$0High
Required for licensed production workflow$0High
Engineering takeaway
Growth makes overlap visible across the stack.
- A second office can create overlap across collaboration, design, project, and reporting tools.
- Keep decisions protect the core project and licensed design workflows.
- Rightsizing collaboration seats and renegotiating CRM terms improve the stack while preserving core workflows.
- A reporting-workflow pilot can proceed once migration, support, and rollback costs are priced.