Engineering · Sydney · Austin · Los Angeles

We build the software your business runs on.

Custom AI systems, internal tools, and the integrations between them.

For businesses running on software they cannot take offline. Working software in week one, handover in about six weeks.

Tell us your bottleneck → See how we work

What we take on

Three kinds of problems.

We make your existing software work harder

Most businesses don’t need new software. They need what they already pay for to talk to each other — and to do the things it never offered.

We take ideas from napkin to finished product

Off-the-shelf software cannot solve every problem. You bring the idea or the pain point; we scope it, prototype it, and build it into a product.

We work inside the systems others won’t touch

Marine services, dental practices, finance — the same pattern every time: ageing, business-critical software nobody wants to break. We modernise it and build around it live.

Engineering

What you get that you wouldn’t elsewhere.

True of every build we hand over.

  • We work in the stack you already have

    QuickBooks Desktop, ServiceM8, DocuWare, Airtable, Slack. No rip-and-replace, no migration you did not ask for.

  • Nothing goes live unproven

    Feature flags, a staging environment that mirrors production, and an end-to-end run against real records before anyone depends on it. Then the flag goes on.

  • You own what we build

    The code, the environments, the credentials, the written procedures. Nothing about the handover depends on keeping us.

  • Three cities, one team

    Sydney, Austin and Los Angeles. As one city signs off, the next is already awake on your problem.

  • You talk to the engineers

    No account manager relaying questions, no ticket number where a name should be.

How we work

Our process.

The same six steps every time. What changes is how long step three takes.

  1. Discovery

    Map the handoffs nobody documented.

    We trace the real path work takes between people and tools, including the steps that only live in someone’s head.

  2. Scope

    Pick the unglamorous bottleneck first.

    One choke point, defined tightly enough to build against. Everything else is written down for later rather than argued about now.

  3. Build

    Working software in week one.

    Real software in front of real people in the first week, so feedback shapes the build instead of arriving after it.

  4. Integrate

    Meet the systems where they already live.

    QuickBooks Desktop, ServiceM8, DocuWare, Airtable, Slack — none of them designed to be connected to. We build around them live rather than asking you to take one offline.

  5. Harden

    Prove it before you switch it on.

    New behaviour ships behind a flag into a staging environment that mirrors production, and runs end to end against real records before anyone depends on it.

  6. Run

    Handover is a start, not an exit.

    Changes keep landing after launch. On Onboard Marine, a mid-service variation flow was built because the client asked for it in a morning meeting.

Handover typically lands around six weeks in. One integration is shorter; five services and a desktop accounting package is longer. We tell you which you have after discovery, not before.

Systems in production

Two we can talk about by name.

Both are still under NDA. This is the part each has cleared us to describe.

Salco Equipment Supply

Equipment distribution · United States

  1. QuickBooks
  2. Airtable
  3. DocuWare

Six services keep QuickBooks Desktop, Airtable and DocuWare in step.

  • The whole sales workflow. Quotes, sales-order conversion, invoicing, vendor purchase orders and proof of delivery.
  • Margin QuickBooks will not apply. The customer and vendor margin hierarchy runs on the estimate, which QuickBooks cannot do on its own.
  • On premises where it has to be. Five cloud services plus a Windows sync for the accounting package the business is not moving off.
  • Node
  • Airtable
  • QuickBooks Web Connector
  • DocuWare
  • Railway

Five cloud services plus an on-premises sync

Koton Kraft

Textile manufacturing · Sydney

  1. Artwork library
  2. Airtable
  3. Print-ready TIFF

An order arrives as artwork and leaves as a file the printer can run.

  • 3,491 designs, searchable. Filter by artist or theme. 993 are licensed from 20 credited artists and carry their own royalty price, so the right rate is applied at the point of sale rather than reconciled afterwards.
  • The order composes its own print file. Artwork is positioned against that product’s real cut, sewn and safe margins, then written out as a 300 dpi RGB TIFF at the panel’s cut size — the format the factory’s Epson Monna Lisa ML-8000 takes. The spec lives on the product record, so a new fabric or size ships without touching the code.
  • Wholesale behind an approval gate. Resellers request an account, the office approves it, then they see their own order history and reorder in one click.
  • The office keeps one list. Prices, fabrics, print zones and which designs can go on which product all come from the Airtable base staff already maintain.
  • Node
  • Express
  • Airtable
  • Supabase
  • Railway

Live at kotonkraft.com.au (opens in a new tab)

Tell us the bottleneck. We’ll show you the software.

A first call is 30 minutes and costs nothing. You describe where the work gets stuck; we tell you whether it is worth building — and say so when it is not.

Let’s talk → [email protected]

We are hiring a Machine Learning Engineer. See the role →