AI for builders and firms
Make repetitive work disappear.
For building companies and firms with an office to run. We set up Claude and train your people, review the software you already pay for, build dashboards and internal tools, and take supplier invoices off the desk. We do it one workflow at a time.
We scope it on a call with the people who do the work, and you get a fixed quote in writing before anything's connected.
The Taiger emblem, two white stripes and one orange, on black. A warm orange glow passes through each stripe in turn, left to right, then fades.
What we do for an office.
We start with one thing and get it working before we look at the next. The AI we build on is Claude.
Accounts payable
Supplier invoices get read, matched to the job and the purchase order, and held for a person to approve before anything's posted.
See it run belowClaude rollout and training
Claude set up for your firm with your templates, your terms and your way of writing, and your people trained on what to trust it with and what to check. A written guide stays with the team.
Software review
What you already pay for, what it's actually doing, what overlaps and where the double-handling is. A written review with the changes worth making, in order, before anything new is bought.
Dashboards
We pull the numbers a director looks at every week from the systems that already hold them, onto one screen that's right on Monday morning. Nobody has to build it in a spreadsheet.
Internal tools
When a spreadsheet, a paper form or a group chat is running part of the business, we build a small tool around how the work actually happens, like the test-report tool further down.
Take one supplier invoice.
It runs on its own until it needs your say-so. Press Approve when it stops.
- Supplier
- Corran Hire
- To
- Kessling Constructions
- Date
- 09 Sep 2026
- Purchase order
- PO-2041
| Description | Qty | Amount |
|---|---|---|
| Scissor lift, 10 m, weekly hire | 2 | $1,380.00 |
| Delivery and collection | 1 | $420.00 |
| Fuel and consumables | 1 | $160.00 |
| Total | $1,960.00 |
- Terms
- 30 days
- Supplier
- Corran Hire
- Job
- JOB-2041, Carrow Street Depot matched
- Purchase order
- PO-2041 verified
- Amount
- $1,960.00 within order
- Approval
- Awaiting a person
- Posted
- Accounting system, ref AC-2041
Dimension lines join the supplier, the purchase order and the total on the invoice to the matching rows on the record.
Nothing posts without a person.
What actually changes.
Here's the same supplier invoice, before and after. Your accounting doesn't change, only who does the typing and when someone steps in.
Today
- 01Invoice arrives by email, sits until someone has time.
- 02Someone opens the PDF and retypes the supplier, number, date and total.
- 03They hunt for the job and the purchase order to match it against.
- 04They code it, attach the PDF and enter it in the accounting system.
- 05The owner checks it later, sometimes after it's been paid.
With the workflow
- 01Invoice arrives by email.
- 02The fields are read from the PDF and matched to the job and its purchase order.
- 03The person responsible sees one screen: what was read, whether it matches, approve or query.
- 04On approve, it's coded, attached and queued for accounts.
- 05Anything that doesn't match waits for a person.
We don't quote a time saving here, because it depends on your volume and how you do it now. The pilot, the first workflow run on your real invoices, measures it.
One we've built.
The electrical test-report tool we built for Watmar Electrical is in use now: the sheet's filled in on a phone, signed on the screen, and the certificate's emailed before they leave site.
An illustrative electrical test sheet, filled on a phone, becoming an issued certificate that is signed on the screen and emailed from site.
A person approves anything that matters.
It cuts the retyping, but your people still make the calls. Whoever's responsible gets one review screen showing what was drafted or matched, and approves it, edits it or sends back a query.
- Before a payment is queued or an invoice is posted
- Before a quote, a report or a certificate goes to a customer
- Before any message is sent in your name
- Whenever a document doesn't match what the system expected
We agree these checkpoints with you while scoping.
From scoping to handover.
We scope it and build it ourselves. Whoever takes your job stays your contact from the first call, through the build and after it's handed over.
- Scoping call
- With the people who do the work: the workflow, the tools it touches and the approvals, written down
- Build and pilot
- One workflow built and tested on your real documents until it holds up
- After handover
- Changes quoted first, or billed by the hour at the rate in your agreement
It goes through the same stages as every project: discover, design, build and launch.
How a project runsQuestions people ask first.
If yours isn't here, ask us. You'll get a straight answer.
What does it cost?
We scope it first, on a call. Once the workflow, the tools it touches and the approvals are agreed, you get a fixed price in writing. There's no public price list, because two firms rarely have the same software or the same bottleneck, and a figure without a scope would be a guess.
Do we need to change the tools we already use?
Usually not. We start from the software and documents you already use, like email, accounting, job management and spreadsheets. A new tool only comes in where it clearly earns its place, and we'll tell you which in writing before you buy anything.
Who trains our people?
We do, as part of the handover. We show the people who'll use it how it runs, what to check and what to do when something looks wrong. A Claude rollout comes with the training sessions and a written guide your team keeps.
What happens to our data?
It stays yours. While we're scoping, we write down which systems the workflow can reach and what each one can see, and we agree that list with you before anything's switched on.
What eats the most time?
Pick the bit of office work that keeps coming back, and we'll say straight up whether it's worth automating first.