Skip to content

How it works

Software built around your business, and the one it's becoming.

We start from how you work today and build the system to match. As you take on new services or more staff, the system grows with you.

Where firms usually start

Most firms start with one of these four problems.

  1. 01

    You can't see the whole operation.

    Jobs, quotes and invoices sit in different places, so nobody has one view of where things stand. We start with one record for every job and the screens your office works from. Everything else is added to that record later.

    What we build first

    • One record for every client, job and invoice
    • The screens your office works from each day
    • Live figures in place of month-end reports
    • Each person sees what their role allows
    Elements: Data · Interface · Governance
  2. 02

    Your field team works outside the office system.

    Your people log in on their phone, see the next job and what it asks for, and record it as they go: photos, readings, the condition of a property, a signature. When they tap submit it lands straight in your system and the office knows at once, for example that Jimmy has finished job 214 and it is ready to invoice. The app keeps working with no signal and catches up when it's back, so a job in a basement or a remote farmhouse still gets done.

    What we build first

    • The next job and its instructions, on the phone
    • Photos, forms and signatures captured on site
    • The office notified the moment a job is submitted
    • Works with no signal, syncs when it returns
    Elements: Interface · Data
  3. 03

    Too much is copied and chased by hand.

    The same details get typed into two or three places, and jobs wait for someone to remember the next step. We make those steps happen when the work moves: the confirmation goes out when a job is booked, and the invoice is raised when it's signed off.

    What we build first

    • Confirmations and reminders sent when a job changes stage
    • Invoices raised when work is signed off
    • Quotes, reports and invoices built from what's already recorded
    • Figures passed to your accounts package, such as QuickBooks
    Elements: Automation · Output
  4. 04

    You want AI that knows your business.

    A general assistant can't tell you which jobs have stalled, because it can't see them. Once your records, permissions and workflows are in one system, AI can read incoming documents, answer questions from your own figures and draft routine replies for a named person to approve.

    What we build first

    • Questions answered from your live records
    • Incoming documents read and filed
    • Drafts that wait for a named person's approval
    • Every action logged against the person who approved it
    Elements: Intelligence · Governance

Wherever you start, it becomes part of one system.

See how a system is put together

The steps

From first conversation to working system

The first conversation is about how your business works, where it gets stuck and whether we're a sensible fit.

  1. 01

    See how the business runs

    We sit with the people doing the work and follow real cases through, including the exceptions and the workarounds. You don't need to write a specification first.

  2. 02

    Design

    Map the system and how each person will use it

  3. 03

    Build

    The first working version reaches your team in weeks. We stay close to the work and improve it from real use, in short rounds with a check-in after each one.

  4. 04

    Go live

    Go live with your team trained, then keep improving the system together

If you're not nearby, that can mean screen-sharing and walking through real cases together, with visits where they're useful.

What stays

You keep the tools that still earn their place.

Your accounts package, your email and the tools your team already relies on can connect to the system, so nothing has to be thrown out on day one.

Technology

For whoever checks the technical side: we build on widely used, well-supported tools.

Data
Supabase · PostgreSQL · Prisma · Railway · Dexie
Interface
Next.js · React · Tailwind CSS · Node.js · Python · Vercel
Intelligence
Anthropic · OpenAI · Gemini
Automation
n8n
Output
Resend · DocRaptor
Governance
Role-based access · Full audit trail · Named approvals

Tell us how your business runs today.

We'll show you what you'd see with it all in one place, and what you might be missing now.

Bring your three most awkward cases and we'll start from those.

Start a conversation