ServiceCPQ
Platform·Service Finance Intelligence

Your service business, live and traceable.

A live financial view over your service operation — WIP, parts, labour, margin, warranty and contract profitability — where every number is current and every number decomposes to the transaction behind it. Three personas, one event-sourced graph.

$2.2M
Unclaimed warranty surfaced for recovery
$1.2M
Contract margin flagged at risk before renewal
$33.8K
Average margin leak caught per losing contract

Illustrative figures

The problem

Your service P&L arrives late, and no one can trace it.

The service margin number lands weeks after the work is done, stitched together from the ERP, a warranty spreadsheet, a parts system and a few exports. By the time anyone sees it, the losing contract has renewed and the recoverable warranty has been written off.

And when someone asks “why is margin down on this account?”, the honest answer is a week of reconciliation — because no single number can be opened up to the transactions that made it.

What it is

One graph. Three lenses. Every number traceable.

Your operational systems — work order, CPQ, order hub, warranty, asset health — emit canonical events. A single event-sourced graph assembles them into a live financial picture, and three personas each read it their own way: the service manager sees jobs, the VP sees leakage, finance sees true margin and cost.

Not a rip-and-replace. Not another ledger. A lens over what you already run.

Lens 1 · Service Manager / Supervisor

“Are my jobs on track?”

The floor-level lens: work-in-progress by job, what will convert to a bill, what’s ageing, and the true cost of parts and labour as the work happens — not reconstructed at month-end.

WIP by job

Work-in-progress value per job, live — what's booked, what's billable and what's stuck ageing.

Parts cost & demand

Parts consumed and forecast per job, costed against the plan instead of discovered at close.

Labor & parts costing

Labour hours and parts roll into true job cost as the work happens, not weeks later.

“For the first time a supervisor can see which jobs are quietly turning into losses while they can still do something about it.”

Service Manager view — WIP conversion, ageing buckets and worst-margin job board
Service Manager — WIP, ageing & job board
Lens 2 · VP Service

“Where is money leaking?”

The portfolio lens: contract profitability ranked, warranty and supplier leakage surfaced before it’s written off, and a margin advisor you can simply ask where the money is going.

Contract profitability

Every service contract ranked by margin — which ones earn, which ones quietly bleed.

Warranty leakage

Recoverable warranty and supplier cost surfaced before it's silently written off.

Ask a question

A natural-language margin advisor — ask where money is leaking and get the traversal, not a ticket.

Service VP view — money at risk cards, contract health and margin advisor
VP Service — money at risk & contract health
Lens 3 · Finance

“What’s my true margin and cost?”

The controller’s lens: service P&L with a margin waterfall, COGS matched to the revenue that earned it, and exposure — every figure decomposing to the transactions beneath it for the close and for audit.

Asset lifetime P&L

Revenue, cost and margin per asset across its entire service life, not just this quarter.

COGS matching

Parts and labour cost matched to the exact revenue event that earned it.

Audit-grade decomposition

Every number opens to the transactions beneath it — ready for audit and the close.

CFO view — service P&L stat cards, margin waterfall, revenue quality and exposure
Finance — service P&L & margin waterfall
The differentiator

Every number decomposes to the transaction.

A dashboard shows you a total. This shows you the total and the exact events that made it — the parts consumed, the hours logged, the warranty claimed, the invoice raised — because the number is a traversal, not a stored figure.

That’s the difference between a report you have to trust and a number you can prove.

See the event stream

The canonical events every operational graph sends to finance.

Work order, CPQ, order hub, warranty, asset health and rebuild programs each emit a small, canonical set of events. The finance graph subscribes to them — nothing is re-entered, and the trail is the source of every figure.

Ops simulator — numbered canonical-event cards and the live event log
Ops simulator — canonical events & event log
How it fits

A layer over your ERP, not a replacement.

Agents and apps read through a knowledge API into one event-sourced graph, which sits across your business services and the ERP that remains your ledger of record.

React / AI agents→
Knowledge API→
One event-sourced graph→
Your business services→
ERP — ledger of record
Why a graph

Cross-domain questions become one traversal.

“Which contracts are losing money because of warranty repairs we never recovered?” touches contracts, work orders, warranty and parts. In a stack of separate systems that’s a data project. On one graph it’s a single traversal — which is why the answer is live instead of a quarter late.

Outcomes

What you get in the first weeks, on one subgraph.

Recover unclaimed warranty

Surface warranty and supplier cost that would otherwise be written off, with the evidence attached.

Catch losing contracts before renewal

See which contracts bleed margin while there's still time to reprice or walk away.

Real WIP visibility

Know what's booked, billable and stuck across every open job — live, not at month-end.

Self-serve performance

Managers, VPs and finance each get their own lens without waiting on a BI request.

Audit-grade trust

Every figure decomposes to its transactions, so finance can stand behind the number.

You don’t boil the ocean. Start with one subgraph — usually warranty leakage or contract profitability — prove the number, then let each additional graph compound on the same foundation.

FAQ

Common questions

What is service finance intelligence?

A live, traceable financial view over your service business — WIP, parts, labour, margin, warranty and contract profitability — built on an event-sourced graph rather than a nightly report. Every number is current and every number decomposes to the transaction that produced it.

Does it replace my ERP?

No. The ERP stays the ledger of record. This is a layer over it: operational graphs (work order, CPQ, order hub, warranty, asset health) emit canonical events, the graph assembles them into a financial view, and postings still settle in your ERP. It's a lens over what you already run, not another ledger.

How can every number be traceable to a transaction?

Because the financial view is event-sourced. A margin figure isn't a stored total — it's a traversal over the events that created it (parts consumed, labour logged, warranty claimed, invoice raised). Open any number and you see the underlying events, which is what makes it audit-grade.

What is warranty leakage recovery?

Warranty leakage is recoverable cost — supplier back-charges, in-warranty repairs billed as paid work — that gets written off because no one connected the repair to the entitlement in time. The graph surfaces it against the exact machine and claim, so it can be recovered instead of lost.

How fast is it to get value?

You start with one subgraph — often warranty leakage or contract profitability — rather than a platform migration. Because it reads events from systems you already run, the first lens can be live in weeks, and each additional graph compounds on the same foundation.

Related solutions

See your service margin, live and traceable.

Book a live walkthrough and we'll trace a real number — WIP, warranty or contract margin — back to the events that made it.

Book a demo