De-identified, step by step, including what each one puts in front of a person. The decision logic between the data and the output is where the value hides, and it is the part a template would skip.
These are working builds, de-identified so we can show you the inside. The steps and the outputs are the real ones. Internal reporting lands straight in your team's inbox; nothing reaches a client, or anyone outside the business, without a person approving it first.
Partners make pricing, resourcing and scope calls in the 10 to 12 day blind window after month-end, before the numbers are in.
Fires at 6:30am, daily through close, weekly otherwise.
Reads live P&L, cash, receivables, utilisation, WIP and margin.
Finds every variance and ranks it by dollars.
Turns the ranked numbers into a plain-English decision note.
Phone-formatted, a 30-second read. No new dashboard.
Fires at 6:30am, daily through the close window and weekly the rest of the month, so it never becomes noise people learn to ignore.
Reads live P&L, budget, bank position, receivables and bills due, plus utilisation, WIP and project margin, and the same window last month and last year for context.
Works out every variance, flags what has moved outside its normal pattern, and ranks by what matters in dollars. If everything is notable, nothing is.
Turns the ranked numbers into a short, decision-flavoured note in plain English: what is landing, what is still rescuable, what is already locked in.
Arrives before the partners are at their desks, formatted for a phone, a 30-second read. No new dashboard, nothing to log into.
Month landing around 3% below forecast. Two live issues worth a look today.
It looks like a lot because it is. The scheduling, the ranking, the tone, the part between the raw numbers and a sentence a partner will act on, that is the build. It is also why a prompt box on its own will not get you here.
The same agent handles extension-of-time claims, variations, notices of delay and RFIs.
A person describes the delay event in one sentence.
Finds the qualifying cause and pins the governing clause.
Builds the clause-cited claim document in under a minute.
Saved owner-only to your drive. It cannot send or lodge anything itself.
Asks the owner to approve. It cannot decide to send.
A person describes the delay event in a sentence and hands it to the claim drafter. No forms, no template wrangling.
Reads the job facts and the stored contract, identifies the qualifying cause, and pins the exact governing clause it relies on.
Builds a branded, clause-cited claim document with the chronology, the entitlement basis and the attachments, in under a minute.
Saves it to your own drive, sharing hard-blocked in code, and returns a private link. It cannot send or lodge anything itself.
Ends with a plain-English summary and asks the owner to review and approve. The system can do the work, it cannot decide to send it.
Claim summary
A formal claim for an extension of time under Clause 34.3 of the General Conditions, following the notice of delay issued under Clause 34.2.
The clause is the whole job. Anyone can generate a document. Reading the contract, choosing the right clause, and being honest about the assumption it rests on is the part that decides whether the claim survives scrutiny.
Instead of a single all-purpose bot, a coordinator runs a team of specialist workers; we first proved the pattern on a construction back office, here it is on everyday client admin.
Sends each request to the right specialist worker.
Cheapest capable model for each task, no lock-in.
Drafter builds the pack while the clerk updates records.
Workers pass tasks along, carrying shared memory across jobs.
Nothing outbound ships without the owner signing off.
Receives a request and sends it to the right specialist worker by type. One front door, a team behind it.
Sets the cheapest capable model for each task, with no lock-in: a frontier model for the careful drafting, a cheap fast one for the clerk.
The document drafter builds the client-facing pack while the records clerk updates the CRM and the internal registers.
Workers pass tasks between them and carry shared memory of the account, prior documents and where things were left, across jobs.
Results come back on screen. Same rule as everything else: nothing outbound ships without the owner signing off.
This is the shape of the bigger builds. A coordinator, specialist agents, shared memory, and one human gate. It is how a back office scales without handing over the decisions that need a person.
Book a strategy call and we will map the one build that would pay for itself first in your business.