← All sample plans Get my plan & price →
Example

An illustration of the document we send within 24 hours of your call, so you can see the detail, the structure and the way we price. Yours would be about your business, with your numbers.

The Build Plan

Docket & Invoice
Reconciliation for a transport operator.

Everything we would build, everything we deliberately would not, what it connects to, how long it takes and exactly what it costs.

Written forA 40-vehicle transport operator
IndustryTransport · Logistics
FromOne 30-min call
Valid for30 days
01

What you told us

“We know we’re being overcharged. We just can’t prove it on every load, because checking a docket against an invoice takes longer than the error is worth.”

Finance Manager · 40 vehicles, ~900 loads/week

Dockets arrive in every possible form — photographed on a phone, scanned at a depot, emailed as a PDF, and sometimes handwritten. Subcontractor invoices arrive separately, weeks later, with their own reference numbers.

Someone in finance spot-checks a sample. Everything else is paid on trust, because the time cost of checking exceeds the average discrepancy.

You were explicit that this must not block payments or create friction with subcontractors. It flags, it does not withhold.

02

What this is costing you now

Numbers from your own figures on the call, not industry averages. These are the basis for the plan, so if any of them are wrong, tell us and the plan changes.

This is the clearest return of the four plans on this site, because the saving is arithmetic rather than estimated — but only if the document quality holds up, which is why testing runs on your real paperwork before anything goes live.

03

What we would build

A document pipeline plus an exception queue. Your accounting system does not change, and nothing is paid or withheld automatically.

Part 01

Document capture

Dockets and invoices from email, depot scanners and driver phone photos, read regardless of format, orientation or handwriting quality.

Part 02

Line-by-line matching

Each docket matched to its purchase order and invoice on load, date, weight, distance and rate — not just on totals.

Part 03

The exception queue

Only the mismatches reach a person, ranked by value, each with the source documents side by side and the difference highlighted.

Part 04

Recovery trail

Every discrepancy, what was claimed, what was agreed and what was recovered — so disputes have evidence attached.

04

What a reconciliation week looks like after

Today

  • Finance spot-checks a sample, pays the rest on trust
  • Dockets sit in three formats across two inboxes
  • Disputes rely on finding the paperwork weeks later
  • 22 hours a week spent, most volume still unchecked

After

  • Every load checked, every week, without more staff
  • All documents captured and matched automatically
  • Disputes open with the evidence already assembled
  • Finance reviews a ranked exception list, not a pile
05

What it connects to

06

What is not in scope

Listed as plainly as what is, because this is the part that quietly becomes an extra invoice elsewhere. None of the below is in the price. All of it can be quoted separately later.

07

Timeline — 21 days from approval

Days 1–4

Documents and rules

We take a real sample of your worst paperwork, agree what counts as a discrepancy, and set the thresholds worth a human's attention.

Days 5–12

Build

Capture, matching, the exception queue and the system connections. Working version at the end of week one on your own documents.

Days 13–17

Testing on live volume

It runs on real loads alongside your existing process, so you can compare what it found against what your team found.

Days 18–21

Go live and handover

Switched on across the volume. Walkthrough for finance, documentation, accounts in your name.

08

What you get at handover

From that point it is yours. You can extend it, hand it to another developer, or take it in-house. There is no licence and nothing stops working if you stop talking to us.

09

The price

One number.
Fixed · + GST · scope exactly as written above

On a real plan, this is where your figure sits — one number for everything above, agreed before a line of code is written. We do not publish it on the samples, because a price list would mean pricing your business before we have spoken to you.

On approval50%before we start
At handover50%when it is live and yours

This number does not move. If the build takes longer than we estimated, that is our problem, not your invoice. If you want something added mid-build, we quote it separately and you decide — it never arrives as a surprise line item.

Ongoing is optional. After the included 30 days, hosting, AI usage, monitoring and improvements are a monthly if you want them. Cancel whenever you like; you keep the software either way.

10

What we need from you

That is the whole commitment. No workshops, no specification documents to review, no weekly status meetings.

11

Assumptions and risks

Stated up front, because the ones nobody mentions are the ones that blow up a fixed price.

Other sample plans

Same structure, different businesses — so you can see how the scope and the number move with the job.

Your plan would look like this.
It would just be about you.

One 30-minute call. A document like this within 24 hours, with your numbers and your fixed price. Free, and yours to keep whether you go ahead or not.

Get my plan & price →

Figures are illustrative. The structure, the level of detail and the pricing approach are exactly what we send real clients. M3 — Brisbane & Vancouver.

Your plan, your numbers, within 24 hours. Free, whether you go ahead or not.

Get my plan & price →