What we build, and how you buy it

Deployed software at a URL your staff log into, carrying your real data, with admin access and the source code in your hands. The month-one artifact is a screen someone at your business opens every morning.

Example work product
An owner's operations dashboard: the week's jobs, revenue, and callback rate, pulled out of the systems you already use and put on one screen. This pattern is running in production today for a field-service operation, and the same build serves a practice, a shop, or a trades company without changing shape.

Not included
Seats on our product. There is no per-user license, no lock-in, and no platform you have to stay on to keep what you paid for. What we build runs on your own accounts and remains yours if we part ways. We give up recurring license revenue on purpose; it is the difference between a services firm and a software vendor.

A written assessment with decisions in it, billed per project: what to fix, in what order, what it costs, and what should not be automated at all. The document is specific enough to hand to any builder, including one that isn't us.

Example work product
A replace-or-keep assessment of your core operational software: what the current tool actually costs per month, which features your staff actually use, and either a written migration plan or a recommendation to keep what you have. We completed exactly this engagement this quarter, and the honest answer included keeping parts of the incumbent system.

Not included
Hours. We do not rent out developers by the hour, and the engagement ends when the document does. The document is permitted to conclude “don't build this,” including when the build would have been ours.

The retainer operation. Everything we have in production for you is monitored, failures are fixed, updates are applied, and each month you receive a written report: what ran, what failed, what changed. A named person answers within a stated response window.

Example work product
Say you have three automations and a dashboard live, and an integration breaks overnight. We catch it in the failure logs, patch it before your staff notice, and the monthly report records it with dates. That report is the artifact: you read exactly what your retainer did that month.

Not included
Mystery systems and heroics. We do not take over software we didn't build or formally assess first; onboarding someone else's stack begins with a paid assessment. And we do not promise 24/7 emergency coverage. The response commitment is a business-hours window we state publicly because we can actually meet it.