Apps · built in-house
The software we build when a website isn't enough.
Field tools, dashboards, calendars and phone apps — drag to spin, click to open. Each one is labelled for what it is: a live product, a tool we run our own work on, or a concept.
Drag to spin · click to open · arrows to move through
How an app gets built
The one screen that matters, first.
- 01A 15-minute callWhat the app has to do, who uses it, and where a spreadsheet or an off-the-shelf tool stopped working.
- 02The one screen that mattersWe build the screen the business lives in first — on your phone, working — before anything is signed.
- 03Built, launched, looked afterIt goes live on your own accounts, with a 30-day fix window after launch, the same as a website.
Custom app work is quoted after scope. It sits under the Commerce / Custom tier on the
websites page — a floor, not a ceiling — because an app's price
is set by what it has to connect to, not by how it looks.
Nothing on this page is for sale as-is. Some of it is a tool we run our own work on, some of it is a concept, one or two are live products. They're here so you can see how we think about software, not so you can buy a copy.
Nothing on this page is for sale as-is. Some of it is a tool we run our own work on, some of it is a concept, one or two are live products. They're here so you can see how we think about software, not so you can buy a copy.
How it starts
Start with a concept, not a contract.
Tell me what the app has to do and I'll build the first screen around it. If it's the right direction, we finish it. If not, no harm done.