Add-on · one-time · $7,500–15,000

We turn your business
into SKUs.

Most operators have never productised their revenue and cost lines. A job is a job, a price is whatever it was last time, and the install hours live in someone's head. Decomposing that into SKUs with cost, install time and sales effort attached is the highest-leverage work on the account — and nothing else we sell works until it is done.

01 · What it actually is

Not setup. SKU-ification.

“Implementation” usually means someone configures a tool and hands you a login. This is different work: we read your job, cost and invoice history and come back with a productised model of how your business actually earns money.

WHAT YOU HAVE INV-4471.xlsx “Pallet order — Rive-Sud” $48,200 · no breakdown job-notes-march.docx “2 guys, most of a day, truck, plus the forklift” pricing_v7_FINAL.xlsx “standard = cost + 22%” last edited 14 months ago — and the rest in Yves’ head 3 wks WHAT YOU GET — ONE SKU, DECOMPOSED SKU · PLT-48-HT / delivered & installed price$48,200.00 material− 18,400.00 freight− 3,500.00 install · 11.5 h @ $58− 667.00 equipment · forklift day− 340.00 sales effort · 6.2 h to close− 620.00 true contribution$24,673.00 · 51.2% the “cost + 22%” rule implied18.0% — off by 33 pts
The last line is the point. Every operator has a pricing rule they believe; almost nobody has checked it against a fully-costed unit.
02 · What happens

Four steps. Three weeks, typically.

01
Read
Your job, cost and invoice history through Connect. A file export is enough to start — no integration project, no IT ticket.
02
Decompose
Revenue and cost lines become SKUs, with install time and sales effort attached rather than absorbed into overhead.
03
Reconcile
The model is checked against what you actually invoiced and collected. Where they disagree, you see why before anything goes live.
04
Set the floors
You set the margin floor — house-wide, and per account where it differs. From then on nothing prices below it without escalating to you.
You keep the model. It is your SKU set, in your workspace, exportable. If you leave, the decomposition goes with you — which is the opposite of how implementation usually works, and deliberate.
03 · What it costs, and why separately

$7,500 to $15,000, scaled to your band.

Priced as a one-time fee rather than absorbed into the subscription, because it is real work by real people and hiding it in the monthly would mean charging every operator for it forever.

Your bandImplementationWhat drives it
under $10M revenue$7,500Fewer SKUs, usually one price book, file-based import
$10M – $50M$10,000Multiple price books, a real cost model to reconcile
$50M – $200M$12,500Several entities or divisions, more history to read
above $200M$15,000Scoped per engagement
Two things sometimes sit alongside it. A named connector build (from $12,000) if you run a system we do not yet support — and it becomes standard for every operator after you. And master-data cleanup (from $6,000) where years of part-number drift have made inventory genuinely untrackable. Neither is assumed; both are quoted only if the read finds them. See full pricing.
04 · Why it is the moat

A competitor can copy the software. Not this.

Once your business is a productised SKU set with real costs attached, every module we sell gets sharper — and so does every conversation you have with a lender. The decomposition is the asset. The software is what acts on it.

See the number before you commit. It is free.

A Margin Scan reads the same history an implementation would and returns what your pricing is leaking. If the figure is small, do not buy from us.