About
Biloh — built by an operator, for operators
An Australian-built platform, dogfooded on real jobs before it ships to anyone else.
Our mission
Service businesses run on phones, vans, and group chats — not desks. The tools available to them were either built for desk-bound office staff at large enterprises or built for one specific trade. Biloh exists so any service business can run its full operation — quotes, dispatch, contractor management, invoicing — from the phone the owner already carries, with an AI assistant that can actually do the work rather than just chat about it.
Why we built it
Biloh started as the in-house operating system for an Australian facility maintenance business. The team needed to coordinate recurring services, dispatch contractors to multiple sites in a single day, capture signed proposals on a phone, and bill customers without an admin team — and there was nothing in the market that covered the full loop without three integrations and a spreadsheet. So they built one.
Every workflow you see in Biloh was used on a real job before it became a feature. The proposal-acceptance flow was tested by real clients signing on a phone in a carpark. The contractor SMA flow was signed by real subcontractors before their first work order. The MCP tools were used by the operator to dispatch work from a chat window before they were ever exposed to other tenants.
Built in Australia
Biloh is built and operated from Australia. Customer data is hosted in the Sydney AWS region (via Supabase). We default to Australian Privacy Principles for handling personal information, and we treat ABN, GST, and Australian banking conventions as first-class — not as locale settings bolted onto a US-shaped product.
MCP-first, on purpose
Every action available in Biloh — creating a client, sending a proposal, dispatching a contractor, recording a job completion — is also a tool callable by an AI assistant via the Model Context Protocol. MCP integration is bundled at every tier. There is no "AI add-on" pricing because the AI surface is the platform. If your assistant of choice (Claude, GPT, Grok, or any other MCP-compatible client) speaks MCP, it can drive your business.
Honest about the stage we're at
Biloh is in active build. The first tenant is the in-house trade business that started it — every shipped feature has at minimum one real operator using it daily. We onboard new tenants deliberately and we publish a build log alongside the product so you can see what shipped, what broke, and what we're working on next.