I'm James Harvey

Why I built it

My business runs on phones, vans and group chats, not desks. I needed to coordinate recurring services, send subcontractors to several sites in a day, get proposals signed on a phone, and bill customers without an admin team. Nothing on the market covered that loop without three integrations and a spreadsheet. So I built one, and I used every workflow on a real job before it became a feature. The proposal flow was signed by a real client in a carpark. The contractor agreement was signed by a real subcontractor before his first work order.

How I built it

I am not a programmer. I am a business owner who directs AI agents to build, test and run the system, and who insists on the discipline a business depends on: every action audited, every number reconciled, every test kept green, and the engineering written up in public. That combination, an owner's judgement with an agent's hands, is what I bring to other businesses now.

Built in Australia

Biloh is built and operated from Gladstone, Queensland. Customer data is hosted in the Sydney AWS region via Supabase. I default to the Australian Privacy Principles, and I treat ABN, GST and Australian banking conventions as first-class rather than as locale settings bolted onto a US-shaped product.

MCP-first, on purpose

Every action in Biloh, from creating a client to closing the quarter, is also a tool an AI assistant can call through the Model Context Protocol (MCP). That is how I run my own business as an operator: by typing what I want to an assistant that has the tools, and checking what it did. It is included for every business I set up, not sold as an add-on.

Honest about the stage I'm at

Biloh runs one business fully: mine. I take on other businesses deliberately, one at a time, after a call and an X-ray of how they run, because that is the only way I know to make it work on day one. I publish a build log of what shipped, what broke and what is next in the engineering notes.