The structure is the deliverable. Every headline, paragraph and question on this page is placeholder written to brand voice at realistic length — the promise, the cost list and the two doors need Lourens's words before it goes live. No statistic on this page is ours: the annual figure in the dark band is worked out from numbers the reader types, seeded with a plausible example, and the only fixed price is the real $49 platform one.
Ask what a job was quoted at and you get three answers. The spreadsheet, the system and somebody's memory all say something different, and the only way to settle it is for a person to go and check.
Nobody calls it a problem, because nobody is ever wrong for long. Somebody checks, the meeting moves on, and the checking never turns up as a line anywhere. It is the most expensive thing in the business nobody has ever costed.
And it is not the checking that hurts most. It is what happens when nobody checks. A number that was true last month gets used as though it were true today — and a decision gets made on it before anyone notices.
Then it stops being about numbers. Once a team has been wrong in front of a customer twice, they stop quoting the system at all — they phone the one person who actually knows. That person becomes the system, and they cannot take a holiday.
The only figures anyone trusts are the ones that were reconciled, and reconciling happens after the month ends. So every decision you make is about a month you can no longer change.
Everyone knows who to ask. That is the tell. What they know is not written down anywhere, so the business cannot grow past them and cannot run without them.
Being quoted one figure and invoiced another is not a rounding error to the person paying. It is the moment they start reading everything else you send twice.
Somebody asks what a job is worth and three people open three different things. If "let me check and come back to you" is the honest answer to a question about your own work, this is the page.
If everyone already reads off one screen and it is current, the numbers are fine — the leak is the typing that keeps them current. Try everything typed twice instead.
Not another screen to keep up to date. One record per job that changes when the job changes, and that everything else reads off.
What it was quoted at, what has been paid, what stage it is at, who touched it last. Not a copy of the answer — the answer.
Money arrives, a quote is accepted, a stage moves — the record is already right before anybody thinks to update it.
What is out, what is owed, what is waiting on us. You read it instead of asking three people and adding it up yourself.
Nobody is at a desk, and by Monday morning everybody already knows. The shape is a real sequence; the names and the amount are illustrative.
The hard part is not the screen. It is agreeing what a job is, what its stages are and which number wins when two disagree. We do that with you, then bring your spreadsheets and history across. Quoted before it starts.
Income Mavericks is where the jobs, the payments and the one screen live. If you would rather set it up and move your own records across, that is the same system without us in it.
Mostly you do not. The spreadsheet stops being the place the number is decided and becomes a place it is read — so the version you send out and the version somebody edits on Thursday cannot disagree any more.
It comes across. Old jobs, contacts and what they were worth move in as records, which is usually the first time anyone can see last year in one place. Where two sources disagree we ask you which one wins, once, rather than guessing per row.
That is the whole design question, and it is why the record changes off things that already happen — a payment clearing, a quote being accepted. Anything that still needs a person to remember is a thing we have not finished building.
Yes. We build on Income Mavericks and only on Income Mavericks — it is the one platform we know well enough to be accountable for. Your contacts and history come across, and what you are paying your current CRM stops.
Less than you would expect, because most of them only ever read. The people who enter things learn one screen instead of three, and we walk them through it rather than sending a document.
Most businesses have two of these at once, and fixing one usually exposes the next.
An hour. We go through what it is meant to answer and what keeps making it wrong.