Skip to content

Out of the queue.

Whole systems, each built around how one business already works, then our own products. Shown running.

Between us, we've built operations software for field-service, marine and venue businesses in the US.

A walkthrough on sample data.
Field operations, for an equipment companyBuilt end to end at a US agency

LiftOps

Built end to end at a US agency

Who it's for

A company that sells, services and inspects heavy-duty vehicle lifts. Technicians work from phones on customer sites; the office dispatches, quotes, orders and invoices in the same system.

Before

Inspections ran on the company's own paper forms, one checklist for every lift. The supplier's price list was a PDF.

The pain, in numbers

Up to about thirty lifts at a single location, and about thirty pages of paper for the visit.

The build

One engineer, eleven weeks from the first commit. 39 screens, 36 database tables, every one behind row-level security, and four PDF documents.

What was built

  1. Inspections on a phone

    The company's own checklists, a photograph on every deficiency, and one customer signature for the visit.

  2. Signed PDF reports

    One report per lift, or the whole visit as a single numbered document.

  3. A dispatch board

    Day, week and month views. Drag a job to another day, or to another technician.

  4. Quotes and purchase orders

    Lines come from an inspection's findings, two price lists, labor and a service call by distance.

  5. Invoices and payments

    An approved invoice goes on to QuickBooks, and the customer pays by card from a link.

  6. A sales pipeline

    Leads from trade shows and cold calls, followed up until they become customers.

  7. An equipment register

    Every lift at every customer site: maker, model, serial number and capacity.

  8. Automatic reminders

    A daily sweep flags what is overdue and raises next year's inspection for each site.

  9. An owner's board

    Jobs, crew hours, inspections, quotes and invoices on one screen. Every count opens its records.

A walkthrough on sample data, under a stand-in name.
Vessel operations, for a marine businessBuilt end to end at a US agency

Port Haven

Built end to end at a US agency

Who it's for

A yacht management company, shown here under a stand-in name: crew who look after the boats at the dock, an office that plans and bills the work, and owners who want to know their boat is cared for.

Before

What each boat needed every month, and the checklist for every job, lived with the owner. The system was built so he would not have to hold it all in his head.

The build

One engineer, under eight weeks from the first commit. 68 screens, 60 database tables, every one behind row-level security, and 1,177 automated database tests.

What was built

  1. A crew app, offline too

    A job is worked one line at a time: done, needs attention, or broken. With no signal it waits and sends later.

  2. Reviewed reports

    The office reads every report, checks its photographs and signs it off before it counts.

  3. Versioned checklists

    The office builds each boat's checklist. Publishing one freezes that version.

  4. Next month, drafted

    The schedule is drawn from each boat's agreement. One approval puts it on the crew's phones.

  5. An owner's portal

    Read-only. Owners see their own boat's monthly reports and invoices, and nothing else.

  6. Estimates to invoices

    Estimates, charges, purchases with their receipts, and one invoice for a boat's month.

  7. An audit trail

    Every insert and update is written, before and after, to an append-only log.

Our own productpixtex.dev

Pixtex

Who it's for

Anyone who builds or sells n8n automations and has to show a workflow to someone else.

What was built

  1. A free editor

    Turns n8n workflow JSON into a share-ready diagram.

  2. A render API

  3. A CLI

  4. An n8n community node

More case studies are being written up with each client's sign-off.

  • In the queue
  • In the queue