Work
Run on real jobs first
The operating system for field-service businesses, run by talking to your AI assistant. Nothing goes to a customer that has not run in a working business first. So the first case study is the business Biloh was built inside, told plainly, with the numbers read live from the system.
- 396
- jobs completed in the field
- 247
- invoices issued
- 4
- months closed by chat
- 571
- tools an AI agent can call
Read live from the platform that runs my own business. Test data excluded.
Case study one
A property-services business in Central Queensland, run from a phone
The problem
Commercial cleaning programs, window cleaning, pressure washing and property presentation across a regional city: recurring work for some clients, one-off jobs for others, subcontractors doing most of it. Every job meant a quote, a schedule, a work order for the contractor, a completion, an invoice, a payment to chase and a bill to pay. None of the software on the market covered the loop without three integrations and a spreadsheet, and the gaps were where the evenings went.
What was built
One system for the whole loop, driven by chat. A proposal is built on the road and signed by the client on their phone. A recurring service spawns its own jobs on the right dates. A subcontractor accepts a work order and signs their agreement before the first visit. Completion becomes an invoice. The bank feed is reconciled, spend is coded with its GST evidence, and the month, quarter and BAS are closed by typing a sentence to an AI assistant that has every tool it needs.
The code was written by AI agents under direction. Every workflow was tested on a real job before it became a feature, and kept the discipline that a business depends on: every action audited, every number reconciled, every test kept green.
What changed
- Quotes go out and come back signed without an email chain.
- Contractors get their paperwork and their work orders on the phone they already carry.
- Invoices leave the day the job closes, and the books are closed monthly rather than in a panic each quarter.
- Business goals that were out of reach while the owner was the admin department are now being reached.
What we would tell you
The technology was the easy half. The hard half was deciding how the business should actually run: which jobs need a signed quote, when a contractor is allowed on site, what the month-end has to prove. Biloh carries those answers as settings you can change, because every one of them had to be answered in a working business first.
Case study two
A subcontractor signs on their phone
The first time a new contractor works for you is the moment the paperwork usually fails: no agreement, no insurance on file, a work order sent as a text message. On Biloh the contractor gets one link. They read the agreement, sign it on their phone, upload their compliance documents, and accept the work order. The system will not dispatch them until the documents are in. Nobody chases anything.
It is a small workflow. It is also the one that costs a business a client when it goes wrong.
How the system is built and why is written up in public, in the docs. The engineering notes are the unvarnished version.
Want this for your business?
Pick a plan and start today. A done-with-you set-up is an optional add-on, never a requirement.