The Unified Insights Method™

One question in. A board-ready briefing out.

Most AI stops at the answer. BusinessOS keeps going — running a Resolution Pathway that names the problem, investigates the root cause, and models the options, each one costed. Like a senior consultant, it hands leadership the full story — not a verdict. Every number stays traceable to its source.

Framework Approximately 9 minutes Worked example: Overtime Cost Optimization

A single business function answers one question. Ask "where is overtime creating the greatest financial risk?" and overtimePressureReview() returns a number. Useful — but a city manager's next question is always the same: why — and what are my options?

The Unified Insights Method (UIM) is how BusinessOS answers that second question. It orchestrates the deterministic functions you already trust into a Resolution Pathway — a reusable investigation that carries a leader from the opening question all the way to a clear, costed set of options. The example below is a real pathway: Overtime Cost Optimization.

Step 1 · The executive question

Where is overtime creating the greatest financial risk?

The pathway opens with a deterministic function and a receipt for every figure.

ƒ overtimePressureReview()
$482,000
Public Works overtime this fiscal year — 43% of all municipal overtime.
● Measured Confidence: High · straight from payroll
Provenance receipt
ƒ overtimePressureReview()
via UKG Payroll
via Tyler ERP
via CityWorks
Every number is computed by a deterministic function from your data. The AI never invents figures.
Data sources analyzed: UKG Payroll & Timesheets · Tyler ERP (departments, cost centers, budgets) · CityWorks (work orders).

The pathway follows the data — not a hunch.

"Overtime is high in Public Works" isn't a conclusion; it's the start of an investigation. The next step asks why, and here's the important part: BusinessOS doesn't guess which cause to chase. A diagnostic pass attributes the overtime to a set of mutually exclusive causes and ranks them, so the branch it follows is the one the data makes largest — and that choice is logged.

Decision point 1 · the branching

One question branches into four candidate causes

Each cause is a distinct, non-overlapping share of the $482,000 — they sum to 100%, and the data decides which branch to walk.

Decision point 1Why is overtime concentrated in Public Works?
A

Staffing capacity

ƒ staffingGapAnalysis()
Six unfilled maintenance positions push recurring work onto overtime.
✓ Followed → Workforce Resolution
B

Emergency & unplanned

ƒ emergencyResponseImpact()
Storm response and main breaks — reactive and largely irreducible.
→ Asset Reliability
C

Outsourceable work mix

ƒ workMixAnalysis()
Low-complexity seasonal work (tree, asphalt, sign) done on overtime.
→ Sourcing Strategy
D

Scheduling & routing

ƒ scheduleEfficiencyReview()
Crews spend ~19% of paid time traveling between work orders.
→ Scheduling Optimization

→ Emergencies are larger but largely irreducible, so the pathway walks the biggest addressable branch first: Staffing (A).

The four causes are defined to be mutually exclusive, so their shares add to 100% and no dollar is counted twice.

Inside a branch: investigate, then model the options.

A branch is its own small investigation. It confirms the cause, then models the realistic fixes — and crucially, it distinguishes what it measured from what it projects. The staffing branch runs five deterministic steps.

Branch A · Staffing capacity

From cause to costed options

01
Can staffing absorb the load? ƒ workloadCapacityModel()
Capacity 82% vs required 101% — a 19% gap. Measured
02
Would hiring beat overtime? ƒ hireVsOvertimeAnalysis()
Two technicians (salary, benefits, training in) cut OT by ~$214K and response times 17%. Projected
03
Which option wins? decision node
Hire: −$214K/yr  vs  Status quo: $482K/yr in OT. Both outcomes are modeled.
04
What's left after hiring? ƒ contractorOptimizationReview()
Shift low-complexity seasonal work to contractors: −$76K of the remaining OT. Projected
05
Squeeze the residual? ƒ crewSchedulingOptimizer()
Re-sequence routes on what's left: −$52K, no added headcount. Projected
Steps 4 and 5 act on the residual overtime — the hours hiring didn't already remove — so no saving is counted twice.

The number that survives scrutiny: a savings waterfall.

Here's where most "AI savings" fall apart — they stack three fixes on the full overtime bill and claim an impossible total. An overtime hour can only be removed once. So the pathway models the levers as a waterfall on the residual, and it's honest about the slice that can't be removed: genuine emergencies.

Resolution modeling

Where the $482,000 actually goes

Four non-overlapping slices. Three are recoverable; one is not.

$482,000measured annual overtime
$214KHire 2 techs
$76KContractors
$52KRouting
$140KIrreducible
Hire 2 technicians $214K · 44%
Outsource seasonal work $76K · 16%
Optimize routing $52K · 11%
Irreducible emergencies $140K · 29%
$342,000 recoverable — a 71% reduction $140,000 (29%) is genuine emergency response and stays.
Each lever removes its own slice; they never touch the same hour. The remaining 29% is left honest rather than optimized away.
Measured vs. projected — always labeled.

The $482,000 is measured — it comes straight from payroll. The savings are projected — modeled from your data with stated assumptions (salary, benefits, productivity). BusinessOS tags every figure so a finance director always knows which numbers are fact and which are forecast. That distinction is the difference between a demo and a number a city will put in a budget.

Executive briefing

The options, each costed and sourced

Overtime Cost Optimization

71% of Public Works overtime is recoverable.

Root cause: a six-position staffing gap ($214K, the largest addressable driver). The rest is a mix of outsourceable work, routing, and irreducible emergencies.

$482K measured · $342K projected savings · $140K irreducible
1 Hire two maintenance techniciansCloses the 19% capacity gap −$214Kprojected / yr
2 Outsource seasonal low-complexity workTree, asphalt, sign maintenance −$76Kprojected / yr
3 Optimize crew routingRe-sequence the residual work −$52Kprojected / yr
One question became a costed, sourced, board-ready picture of the options — that is a Resolution Pathway.

Why this is the moat.

Connectors get you the data. Deterministic functions get you a trustworthy number. The Unified Insights Method is what turns those numbers into judgment — a growing library of Resolution Pathways that encode repeatable executive consulting into software. Each new pathway makes the next investigation faster, and every one of them shows its work.

The winning civic AI product won't be the one that talks the most. It will be the one that connects the right systems, follows the data, and equips leadership to make the call — with every number they can defend. The Unified Insights Method™

See a Resolution Pathway run on your data.

Bring one question your leadership keeps asking. We'll show the full pathway — problem, root cause, and costed options — with every figure tagged measured or projected and traceable to its source, so your team can make the call.

Book a walkthrough Read-only. Nothing connects to your systems until you decide to move forward.