User guide
One bucket per job to be done, in the order you would actually do them. Each one says what it is for, the steps, and the thing people get wrong the first time.
If you only read one section, read this one. Load the files, say one sentence, and the platform runs a fixed twelve-stage process — stopping for your click at every gate.
“Create a compliant quote for this project.”
Close the browser, lose your connection, come back tomorrow — the project page always shows which stage the process is at and resumes from there. A stage it skipped is written on the panel with the reason.
01 · Once, before your first estimate
Everything you price comes from a database, and a database has two halves: resources (materials, labour, plant — each with a rate) and templates (the recipes that turn a quantity into a cost).
The thing people get wrong You are always editing a draft. Rates you typed but never published will not appear in an estimate, and people lose an afternoon to that. If you have made a mess, Discard puts it back.
02 · Once, before your first RFQ
You need suppliers on file before you can ask anyone for a price. A supplier can hold several contacts; the primary one is who an RFQ goes to by default.
The thing people get wrong Suppliers are the companies you buy from. The people you send quotes TO are clients, and they live on the project — the two lists are separate on purpose.
03 · Per job
A project is one job. It holds that job's documents, takeoffs and estimates, and everything else hangs off it.
The thing people get wrong Pin the right database before you start pricing. A project pinned to your UK book cannot be re-priced against your US book — the two share almost no codes, so a cross-database change re-prices nothing.
04 · Where the two days go
A tender set is hundreds of sheets and you need eleven of them. This is the part that normally eats two days, and it is the part the platform takes off your desk first.
The thing people get wrong Do not hunt through the thumbnails yourself out of habit. Asking for “the roof plans and any parapet details” is faster than scrolling, and the result carries the sheet numbers with it.
05 · Before you price anything
The scope is what you are agreeing to do. Everything after it — the estimate, the RFQ, the quote you send — is built on the saved scope, so it is worth ten minutes of your attention.
The thing people get wrong Anything the documents did not settle is shown as an open question rather than a filled-in guess. Those are the questions an experienced estimator would have raised — answer them now, not after you have quoted.
06 · Getting the numbers
Measure off the drawing on screen. Areas, lengths and counts, each one tagged with where it came from so a number can always be traced back to a line on a sheet.
The thing people get wrong A gap is not a failure — it is the software refusing to invent a number. Fill it with a dimension, or leave it open and price it as a provisional sum, but do not let it quietly become a zero.
07 · The money
The estimate is sections, items and build-ups. Your quantities meet your rates here, and your margin goes on the top.
The thing people get wrong Margin and markup are not the same number and the platform will not let you confuse them. A 30% margin on £70 of cost sells at £100; a 30% markup sells at £91 and earns you 23.08%. Pick the one you meant.
08 · When your book cannot price it
Anything your library cannot price is a named gap with its manufacturer. The platform drafts one consolidated request, you send it, and the returned prices come back into your book.
The thing people get wrong Nothing is applied automatically. Anything the matcher was unsure about is marked rather than written into your book, and a low-confidence match is a prompt to look, not a problem to ignore.
09 · What the client sees
Reports come out on your letterhead, with your company name, logo and colours — configured once for the whole company rather than fiddled with per document.
The thing people get wrong If the header on an export is wrong, it is a company setting rather than something to fix on the report — change it once and every future document is right.
10 · Throughout
The AI window sits alongside the job. It can read your documents, draft scope and assemblies, sort returned quotes and raise RFQs — under a set of rules that do not bend.
The rules that do not bend It proposes, you dispose — nothing priced changes without your click. It never invents a number: what it cannot resolve is shown as an open gap. And your rate library is yours alone — not pooled with other customers, not visible to them, not used to train any model.
There is no ticket queue and no chatbot on the other end. If something here does not match what you are seeing, tell us and we will fix the software or fix the guide.