Four kinds of work.
Most projects are one of these. A few are two stitched together, which is usually where the interesting part is. Each section below ends at the real project that proves it.
Start a projectApps
Software for someone who is not at a desk. A phone in a pocket or a tablet in a truck, used in bad light with one hand, often with no signal at all. That last constraint changes everything about how the thing is built — data lives on the device first, and syncing is something the app does when it can, not something it needs to function.
- The people using it are in the field, not the office
- A connection cannot be assumed
- It replaces paper, a camera roll, or a group chat
- The output has to leave the app as a normal file
You getBuild A native Android applicationStore Play Console listing, assets and releaseSource Full repository, yoursDocs Support and privacy pages, written
Built, published on Google Play, and priced at US$4.99 one-time. Core reporting works offline; the output is an ordinary PDF.
Websites
Marketing sites built as files rather than as a content platform. No CMS, no database, no monthly bill, nothing to patch on a Tuesday. That is not a cost-cutting measure — a business that publishes a few times a year gets a faster, safer, cheaper site out of it, and the pages that matter get written properly because nobody is generating them from a template.
- Customers search for something specific before they buy
- The site's job is a call, a form, or a visit
- You publish occasionally, not daily
- You are tired of renting your own website
You getBuild Hand-written HTML, CSS, JavaScriptContent Page structure and copy, written with youForms Lead capture, spam-filtered, to your inboxHosting Set up on your own domain and server
75 pages, each written rather than generated. Live since April 2026. Disclosed related-business work.
Web apps
The thing a spreadsheet stopped being able to do. Logins, roles, records, scheduling, state that more than one person changes at the same time. The hard part is almost never the interface — it is deciding who is allowed to see what, and enforcing that on the server rather than by hiding buttons.
- Several people need the same information at once
- Different roles should see different things
- The spreadsheet has started producing wrong answers
- Someone is retyping data from one system into another
You getBuild A deployed application on your own domainAccounts Roles, permissions, invitesData A real database, backed upTests Automated coverage of the rules that matterSource Full repository, yours
Two roles over one schedule, with installer visibility re-derived on the server on every request.
Internal tools
The process that only works because one person remembers it. These projects start with a conversation about how the work actually flows — which is usually different from how anyone thinks it flows — and they succeed or fail on whether the crew will use the thing at 7am. Small, fast, and shaped around an existing habit beats comprehensive every time.
- The process lives in one person's head
- Onboarding someone new takes weeks of shadowing
- The same information gets entered more than once
- Off-the-shelf software almost fits, but not quite
You getDiscovery A written description of the actual processBuild A tool scoped to one job, done wellRollout Deployed, with the people who use itSource Full repository, yours
Built in a two-day window for a real scheduling operation, and running as an internal pilot.
What we are not.
- We are not an agency. There is no account manager, no resourcing meeting, and nobody the work gets handed to after you say yes.
- We do not do retainers for their own sake. Fixed scope, fixed number, delivered. Ongoing work happens when there is ongoing work.
- We will tell you not to build it. Sometimes the answer is a process change, a tool you already pay for, or nothing. That conversation happens before you commit to anything.
Not sure which of these it is?
That is a normal place to start, and there is a “not sure” option on the form for exactly this reason. Describe the problem and we will tell you what it actually needs — including if the answer is nothing.
Start a project