Skip to content

CONSTRUCTION & BUILDING — SOUTHWESTERN ONTARIO

The change happened on site. Make sure it happened on paper too.

A change gets agreed standing on site, confirmed with a nod and a phone photo. Three weeks later the invoice does not match what anyone remembers, and it is a dispute instead of a line item. We put the record where the memory used to be, so what got built and what gets billed are the same thing.

Book a pilot call

Free · 20 minutes · no commitment

The site remembers what happened. The office only sees what got written down.

Everyone on site knows what was agreed, because they were standing there when it was. The office was not, and it invoices from whatever reached it — a text, a call, a note made on Friday about Tuesday. None of it is bad faith. It is what happens when the only record of a change is what somebody meant to write down later.

The change order that was still real the day it happened.

What it costs right now.

None of these are measurements of your site — we have not audited it. They are the shape change takes on a job that is otherwise well run, because the only record of a change was ever somebody's memory.

Verbal only
is how a change order starts — on site, on a phone, agreed by a nod
Agreed on site, recorded nowhere
Three weeks later
is when the office finds out what was actually agreed
By the time the invoice goes out, memory has already drifted
Waits on one desk
is where a progress claim sits until someone assembles the backup
The person who holds the paperwork is the bottleneck
Written off
is what an undocumented change becomes once the client disputes it
Real work, absorbed instead of collected
Every job
not just the difficult ones — it is how change happens on a normal site
Not a failure. A gap where a record should be

Four problems, and what replaces the memory the job runs on.

Every one of these lives in a phone, a site diary and somebody's memory until the day a client asks for it in writing.

  1. 01

    A change is agreed standing on site — a wall moved, a fixture upgraded — confirmed with a handshake and a phone photo, and nobody writes it down as a change order.

    Sorting it out later

    Stopping to paper it feels like slowing the job down, and the site super's job is to keep the crew moving, not to do admin standing in the driveway. So the record becomes "we'll sort it out later" — and later, three different people remember it three different ways.

    See the station that closes it →
  2. 02

    A progress claim cannot go out until someone assembles the backup — photos, quantities, sign-offs — and that person is also running three other jobs.

    Assembling it at the end of the week

    The information exists. It is just scattered across a phone, a site diary and someone's memory, and assembling it into a claim the client will actually pay is a job in itself, done at the end of a long week instead of as the work happens.

    See the station that closes it →
  3. 03

    A client disputes a change order months later, and there is nothing but memory to point to — so the crew absorbs the cost instead of fighting it.

    Memory against memory

    Without a timestamped record from the day it happened, a dispute is one person's word against another's, and most contractors would rather eat the cost than damage the relationship over a fight they cannot prove they would win.

    See the station that closes it →
  4. 04

    The crew on site knows what actually happened. The office, doing the billing, only knows what made it into an email or a phone call — and a lot does not make either.

    Whoever remembers to call

    The site and the office run on different clocks. The crew moves at the pace of the job; the office finds out at the pace of whoever remembers to call. The gap between them is where the money goes missing.

    See the station that closes it →

WHAT IT LOOKS LIKE

Owner’s View

EXAMPLE FIGURES

Tuesday, 7:55 across the sites

YOUR COMPANY · 4 SITES · UPDATED 7:55 · SHOWN WITH LIVE REFRESH, A SEPARATELY QUOTED UPGRADE

  • Sites running today

    4

    31 people checked in

    The golf clubhouse is the busy one today.

  • Change orders not invoiced

    $12,400

    3 signed· Needs you

    The wider patio doors at the clubhouse are signed and not billed.

  • Progress claims due

    2

    This week

    Backup is built from the daily site reports.

  • Daily reports in

    4 of 4

    By 5 pm yesterday· On track

    Crew, weather, work done and photos.

Needs you today

  • Materials & POs

    Supplier confirmed by email · Back office & reporting

    Delayed
  • Bids & tenders

    1 addendum logged · Sales & intake

    Due soon
  • Crew & sub scheduling

    Drywall, Thursday · Operations

    Needs you
  • Change orders

    $12,400 · Operations

    Needs you
Construction & Building: the owner’s week on one screen, with the four numbers that matter in this trade and what needs the owner today. The same example business as the Owner’s View demo.

Open this dashboard in the demo →

CONSTRUCTION & BUILDING · OPERATIONS BLUEPRINT

Every process in the company. Lit where a system carries it.

Each floor is a department and each station a process. The bright line is the path one job takes, and the light travelling it is that job. Select any station to see what starts it, what the system does, and what stays with a person.

run on the system
5run on the system
keep a person at the gate
5keep a person at the gate
built only for a pilot
0built only for a pilot
added by you
0added by you
01Work arrives02Somebody promises it03Somebody does it04The customer is told05The money is collectedSALES & INTAKECUSTOMER SERVICEOPERATIONSQUALITY & COMPLIANCEFINANCEBACK OFFICE & REPORTINGLead to site visitBids & tendersCrew & sub schedulingChange ordersDaily site reportsSafety & WSIBMaterials & POsClient updates & close-outProgress billingHoldback & collections
All 10 stations as a list

YOUR ADDITIONS · THE MAP IS YOURS TO EXTEND

Missing a process? Put it on the map.

Anything you run, or wish you ran, that is not drawn above. Name it, say where it sits, and it appears on the model with a blueprint sheet of its own. It travels with your pilot-call booking, so the call starts from your map, not ours. No price is attached; it is scoped on the call.

Start from

Who decides

Kept in this browser. Sent only if you book a call, or ask for its plan.

Blueprint sheet · live preview

APPROVESCHEDULEDPOSTED · EACH CHANNEL

Marketing · Work arrives · A person approves each one

Social media automation

A poster is drafted from the week's work, a person approves it, and it is scheduled and posted to each channel on a calendar.

Starts when
A week's work is done, or a date on the calendar arrives.
The system
The poster and caption are drafted from it and queued.
A person
A person approves each one before it goes out.
On record
Every post, its channel, and when it went out.
Book a pilot call

Twenty minutes. No deck.

What this does not do

  • It does not replace your estimating software, your accounting system, or your site super's judgement. It puts a record where a memory used to be.
  • It will not win a dispute that already happened without a record. It only helps from the day it starts running.
  • It does not decide what counts as a billable change and what does not. That stays a judgement call — it just makes sure the call gets recorded.
  • It is not legal or contractual advice. A holdback dispute or a lien deadline is a conversation for your own counsel, not for us.
  • A Diagnostic is measured against your numbers — your change-order count, your progress-claim timing — and nothing else.

Written from the fundamentals, not from an audit of your jobs. How work gets agreed, recorded and collected does not change much from trade to trade; what changes is the operation, and that is what the first call is for. So the board above describes mechanisms, not measurements, and every figure the calculator shows is your own.

WHY US

We run this on our own vehicles.

We are not a consultancy that read about AI and wrote a deck. We build and operate the automation behind our own Ontario transport operation — built inside our own business first — and it runs every day whether or not anybody is watching it.

  • Vehicles tracked by geofence on the 401 corridor.
  • Arrival and departure times recorded without anyone typing them.
  • Delay alerts that hold their tongue until they are certain.
  • An AI voice agent that calls drivers before an early start.
  • A dispatch desk that runs on all of it.

That operation carries passengers. Yours runs sites and crews, and the business is genuinely different — we are not going to pretend a fleet and a jobsite are the same problem.

What transfers is the machinery, and the expensive mistakes that come with it. The vehicle that clipped a geofence while driving past and marked a stop it never made. The stale data feed that hid whole trips. The alert that fired on one bad GPS reading. Every one of those is a way an automated system embarrasses you in front of a customer, and every one was found and fixed on our vehicles, not yours.

If this is your week, twenty minutes settles whether a Diagnostic would find anything worth fixing.

Book a pilot call

Put your own numbers through it.

How many change orders you handle, what one is worth, how much never gets formally invoiced, and how much time goes into assembling progress-claim paperwork. The calculator works from those and nothing else — every figure it shows is yours.

OPEN THE CONSTRUCTION LEAK CALCULATOR →

QUESTIONS WE GET ASKED

How do you capture a change agreed with a handshake on site?

On the phone already in the site super's hand, at the moment it is agreed — who, when, and what it looked like — so what gets built and what gets billed are the same thing from day one. Stopping to paper it later is how three people come to remember it three different ways.

Can it assemble the backup for a progress claim?

The backup builds itself as the work happens — photo, quantity, sign-off, captured at the moment — so the claim is a printout, not a reconstruction at the end of a long week by the person also running three other jobs.

Will it help with a change order a client disputes months later?

Only for changes recorded from the day it starts running. Each of those carries its own timestamped record, so a dispute becomes a five-minute lookup instead of a written-off invoice. It will not win a dispute that already happened without a record.

Does it replace my estimating or accounting software?

No. It works on top of what you already run, not instead of it. It puts a record where a memory used to be, alongside your estimating software, your accounting system and your site super's judgement. What counts as a billable change stays your call — it makes sure the call gets recorded.

Is this legal or contractual advice, and how does it start?

It is not: a holdback dispute or a lien deadline is a conversation for your own counsel. The first engagement is an Operations Diagnostic of the whole business, with one number taken from the part that costs most — change orders and progress claims — measured against your own numbers: your change-order count and your progress-claim timing, and nothing else.

Bring us one bad week.

Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.

The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.

Free · 20 minutes · no commitment