Solutions · Subcontractors bidding & claiming· Brisbane & SEQ
Win the work on paper. Get paid on paper.
Tender and prequalification answers, variation claims, extension-of-time notices and payment claims — drafted from your own past submissions and your own rates, with a sign-off trail. You review and send.
Type five lines about the job. Get back the finished document, priced from your list, in your voice, ready to send after you approve it.
Sound familiar?
The prequal closes Thursday, the question schedule runs nine pages, and the only person who can answer it is the same person who has to price the job.
The variation was agreed on site five weeks ago. Nobody wrote it up. You are quietly absorbing it.
The payment claim went in thin, the payment schedule came back short, and by the time anyone read it properly the window to do anything about it had closed.
Scope & privacy: read this first
Nothing here connects to your job-management system, your document register or your ledger. There is no simPRO, AroFlo, ServiceM8, Tradify, Procore or Xero integration, and none is being built. We hold what you deliberately hand over — your rates, your past submissions, your project history — and nothing else.
Use case 01
Tender & prequalification answers
Today
Head contractors buy on paperwork. Capability statements, methodology, safety and quality systems, referee projects — every package is an evening or three, so you bid on a fraction of the work you could actually deliver, and you bid worst on the packages that arrive in a busy week.
Instead
Paste the question schedule. Get back a full draft built from your own past submissions, your project register, your accreditations and your insurances — and every claim your evidence does not cover is flagged rather than smoothed over. You edit for an hour instead of writing for eight.
With the default assumptions shown here, that's worth $29,830 a year. Slide the numbers to yours.
Your numbers: adjust them
Assumes drafting drops to about 1.5 hours of review per submission, and that bidding more wins at least one extra package a year. Set the margin to $0 if you would rather count only the hours.
Use case 02
Variation claims, written while it is still fresh
Today
The variation you did not document is the variation you paid for. Writing it up properly — cause, scope delta, cost impact, the wording your contract actually uses — loses every time to whatever is louder that night. Weeks later it is a conversation about memory instead of a claim about a document.
Instead
A site note goes in; a formal variation claim comes out the same day. Cause and category, itemised cost straight from your rates, the response-by date, in the wording your past approved variations used. Documented while the site conversation is still fresh enough to reference.
With the default assumptions shown here, that's worth $55,440 a year. Slide the numbers to yours.
Your numbers: adjust them
Counts only the variations currently absorbed or waived because the claim never got written — not the ones you already claim and win. The recovery share is deliberately below 100%: some were always going to be argued.
Use case 03
Extension-of-time notices inside the notice period
Today
Most EOT entitlements are lost on the clock, not on the merits. The delay event happens, everyone is busy dealing with it, and the notice period in the subcontract quietly runs out while the site is still being sorted. What is left is a liquidated-damages conversation you had a defence to.
Instead
Describe the delay event in a few lines. Out comes a notice that states the event and dates, the works affected, the cause category, the days claimed with the reasoning shown, and the revised completion date — factual and contractual, not apologetic. Sent inside the window because writing it stopped being a whole evening.
With the default assumptions shown here, that's worth $12,000 a year. Slide the numbers to yours.
Your numbers: adjust them
Exposure means liquidated damages or absorbed acceleration cost on events you had grounds to claim and did not notify in time. It is not a promise of entitlement — the notice still has to be right, and your contract still governs.
Use case 04
Payment claims, and the response when the schedule comes back short
Today
A payment claim that does not identify the work properly is a payment claim that invites a short payment schedule. Then the reply has to be written under time pressure by whoever is free, which is how a legitimate claim turns into a discount.
Instead
The claim is drafted against the work actually done, priced from your schedule of rates, identifying the construction work clearly and stating it is made under the Act. When a payment schedule comes back for less, the response is drafted the same day against the reasons given — line by line, with your contemporaneous records attached to each one.
With the default assumptions shown here, that's worth $26,880 a year. Slide the numbers to yours.
Your numbers: adjust them
Counts only amounts currently written off because nobody had time to respond properly. It assumes nothing about adjudication outcomes, and it is not legal advice — the drafting helps you respond on time and on the record, which is the part that usually goes missing.
The edge case
The prequal that arrives the same week as two site problems
Nine pages of question schedule, closing Thursday. In the same week a latent condition stops a slab pour and a head contractor's payment schedule comes back $14,000 light. All three have deadlines and only one of them is negotiable.
All three drafted from the same library: the prequal from your past submissions and project register, the EOT from the delay dates, the payment-schedule response line by line against the reasons given. Each one waits for the contracts manager to approve it, and each carries a record of who approved what and when. The week stops being a choice about which deadline to lose.
How it starts
01
A free Answer Gap Report on a package that is open right now: the questions where your published evidence does not cover the answer. We ask you for nothing to produce it.
02
One real submission written with you for A$1,500, credited in full against setup if you go on. You keep the response either way.
03
The Bid & Claim Library Build: your rates, submissions, accreditations and project register loaded and governed, an approver set, one inbox rule armed. Then the office keeps writing.
It drafts; you approve. Nothing is ever sent, signed or submitted without a person reviewing it first.
Fair questions
We already use simPRO / AroFlo / Procore. Where does this sit?+
Beside them, permanently. There is no integration with any of them and none is planned — that is the guarantee, not a gap. They own the job, the document register and the ledger. None of them writes the tender answer, the variation claim or the payment claim, because none of them was built to. Keep every one of them.
How is this different from asking a chat tool to write a tender answer?+
A chat tool will happily invent a past project, an accreditation or a certification number, and it will do it in fluent, confident prose that reads fine until a head contractor checks it. This drafts only from evidence you have actually supplied, and anything it cannot ground it flags instead of writing around. In a market where procurement fraud is a live fear, refusing to invent is the feature.
Is this legal advice on our contracts or on the Act?+
No, and it is not written to sound like it is. It drafts documents from the facts, dates and figures you supply, in the wording your own past correspondence used. Whether you have an entitlement is a question for your contract and, if it matters enough, your lawyer. What it changes is that the notice actually gets written and sent on time, which is where most entitlements are lost.
Who ends up signing off what?+
Whoever you decide. A common setup is estimators and site staff drafting, and the contracts manager approving. Nothing is sent, filed or submitted until someone approves it, and every document carries a record of who approved it, when, and what it was drafted from. That trail is usually the first thing a head contractor's procurement team asks about.
Where do the rates and past projects come from?+
From your own documents, loaded once. Schedule of rates, past submissions, capability statements, insurances, accreditations, project register. Figures are quoted exactly with the source line shown next to them, and it is told never to invent a price — it flags a missing one instead.
Does it send anything by itself?+
No, and it can't. Every document is a draft until a person approves it. Even connected email and calendar actions wait in an approvals inbox for a human click. That's how it's built, not a setting.
Who owns what we put in, and what happens to our price list?+
You do, outright. Uploaded documents are deleted within 24 hours of processing. Your price lists and reference documents sit in your own account, locked away from everyone else, downloadable at any time, and never used to train anyone's model. Cancel and you keep everything. Delete and it's gone immediately.
Ready-made for subcontractors bidding & claiming.
Nothing here starts with a subscription. It starts with a free gap report on a package that is open right now, and you decide what happens after you have read it.