What we set out to build
To remove the single most-avoided job in a trade business: chasing money. The founder wanted it to happen without the owner having to be the bad guy, and without touching their funds.
What was built
- Automated invoice chasing that reads as the business, not as a debt collector
- Reconciliation the moment a payment lands
- A job-management wedge: connect the field service platform and the accounting system, and the loop closes itself
- A seven-phase AI account-manager agent loop, live in production
- Read-only access by design, so the product can never move a customer's money
What it achieves
- Runs offline against mocks for development, so a demo never depends on a client's live data
- The safety invariants of the agent loop are documented as non-negotiable rather than left to code review
- Read-only is a structural guarantee, not a policy: the integration scopes do not permit movement of funds
The stack
TypeScript, Xero, ServiceM8, React.
Common questions
How was this built?
A founder brought the idea and the domain knowledge. We brought the team. The founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.
What state is it in?
In production. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.
Can you build something like this for us?
That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.
Where to next
If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.