What the friction is costing.
median backlog at engineering firms, with a third turning work down for lack of staff
ACEC Research Institute, via Engineering Inc. (2026)of AEC firms are submitting more proposals this year than last, on top of the work they already hold
Unanet 2026 AEC Inspire Report (vendor survey), via BD+Cfor the average A&E firm to get paid, against 22 days for the best performers
Monograph 2026 A&E Business Benchmarks (vendor data)Where the time goes, and what we build instead.
We build the layer that turns every logged hour in Harvest, BQE Core or QuickBooks into an invoice line. Small jobs get batched into one monthly invoice per client, with the descriptions written for you. You approve the batch. The small work gets paid too.
We build a collections loop off your aging report. Reminders go out on a schedule, the agent drafts the firmer follow-up when an invoice passes 30 days, and the architect gets a polite, specific nudge about the owner payment. You see who is late before month end.
We build a proposal agent that drafts the scope, fee breakdown and qualifications from your past proposals and project sheets. The PE reviews, edits and signs. The first draft is ready in minutes.
We build an intake agent that logs every request from the inbox into one job list, with the deadline and the client attached. Clients get a status update when the job moves, so the phone stops ringing for it.
We automate the nudges and draft each engineer's timesheet from their calendar and project folders. They check it and submit. Billing runs on the hours each engineer logged.
We build a billing check that compares every active project against what has been invoiced and flags anything unbilled for a set period. You get a short weekly list. Every project gets billed within the period you set.
We take the billing, chasing and paperwork off the principal so the hours go back to engineering and winning work. The stamp stays with you. The admin around it leaves.
What to automate first.
You do not automate everything at once. You start where the time is worst and the payback is clearest. In a engineering firm, that order tends to look like this.
Start here. It is pure recovered revenue and the easiest win to measure. Every logged hour becomes an invoice line, small jobs get batched monthly per client, and the agent writes the descriptions so nobody has to remember what a two hour visit in March was for. You approve the batch. The work you were giving away starts getting paid.
Do this next, because it is the cash. The aging report drives the reminders, the agent drafts the firmer follow-up as invoices age, and the architect gets a specific nudge on sub-consultant fees. STRUCTURE magazine calls 60 to 90 day aging a sign of trouble for a small firm. This build tells you who is drifting there before it happens.
Then this. With backlogs near a year and more proposals going out, the first draft is where the principal's evenings go. The agent drafts scope, fee and qualifications from your past proposals and project sheets, and the PE reviews and signs. We build it once billing and collections are banked, because a firm that gets paid on time can afford to say yes to the right work.
What we will not automate.
Plenty of the work should stay human. If a tool promises to take this off you, close the tab.
The analysis, the design decisions and the PE seal. That is your licence and your liability, and AI has no place in it. We do not touch the CAD or analysis software, and nothing we build signs, seals or checks engineering work.
The answer to a contractor's RFI or the review of a shop drawing is engineering judgement on the record. We can log the request and track the deadline so nothing gets missed. The response itself stays with your engineers.
The call on what to charge, which architect to prioritise and when to push a slow payer hard. The agent drafts the proposal and the chase. The principal decides what goes out, and nothing reaches a client without a human check.
A tool, a hire, or a build?
Three ways engineering firms try to fix this. Here is what each one does.
| Off-the-shelf AI | An in-house hire | A Nifty build | |
|---|---|---|---|
| What it is | A general tool your team prompts by hand. | A full-time AI or ops person on the payroll. | Automation built into the tools you already use. |
| What it costs | Cheap per seat. The real cost is the hours spent steering it. | $80k to $120k a year, plus ramp and management. | Fixed scope from $3,000. You own it. |
| Time to value | Instant, but shallow. | Three months to ramp. | One agent or automation, live in days to weeks. |
| What it changes | Helps one person work faster. The process stays the same. | A lot, eventually, if you keep them busy. | How the whole team works. |
| Who runs it | Each person, every time. | Them, until they leave. | It runs itself. You keep it, we keep it sharp. |
What a build looks like here.
We are new, so this is the shape of a typical build. The firm below is an illustration. It is the pattern we build against in a small engineering consultancy, end to end.
A six-person structural engineering firm doing residential and small commercial work, much of it as a sub-consultant to local architects. The principal PE stamps the drawings, writes the proposals and does the billing in BQE Core and QuickBooks, with a part-time office manager.
Short site visits and quick checks for regular architects rarely get invoiced. Sub-consultant fees sit unpaid while the architect waits on the owner, and nobody chases until the principal notices at month end. Proposals get written in the evenings from old Word files, and timesheets arrive late, so the monthly invoices go out late too.
Two things, built on BQE Core and QuickBooks. A billing layer that turns every logged hour into an invoice line, batches the small jobs into one monthly invoice per client and writes the descriptions for approval. And a collections loop that runs off the aging report, sends the reminders and drafts the follow-ups to architects on sub-consultant fees. Live in days to weeks depending on scope, fixed price, success metric agreed first: small jobs billed and collections days down.
The small jobs go out on a monthly invoice, and every one gets billed. Late payers get chased on a schedule, and the principal sees who is drifting before month end. The office manager handles only the exceptions, and the principal's evenings go back to engineering and the next proposal.
Operator-led and built into how you work.
Book a free audit call and talk us through the one workflow eating the most time. We come back with a demo of what we would build and a straight worth-it or not.
A fixed-scope build. One agent or automation, live in days to weeks. We agree the success metric in writing first, in hours saved or dollars back. Then we build it into your tools.
Maintenance keeps it running after the warranty. The Embed puts us inside the business to keep improving it. Both optional. You run it. We keep it sharp.