Groundwork
Book an assessment
Approach

A build takes six weeks because the scope is decided first.

The sequence is what prevents this becoming an eighteen-month project.

The build

Six weeks, from first meeting to live.

WEEK 1

Observe the work

Half a day observing how the work is actually done, producing a map of every hand-off and re-keyed field.

WEEK 1

Determine what will not be built

The value concentrates in a small number of screens. Those, and what is excluded, are named in writing.

WEEK 2

A working version

A working version containing your data, before significant expenditure. Accurate feedback requires something to react to.

WEEKS 3–5

Build against correction

Short cycles with production data introduced early. Software that only handles clean examples is not finished.

WEEK 6

Hand over

Live on your domain, staff trained, source delivered. The handover creates no continuing obligation.

AFTER

Continue only if you wish

Some clients take a Care plan; others take the code and continue independently. Pricing assumes the latter.

Principles

Principles we hold to.

Fewer moving parts

Almost no dependencies and no build step. A system delivered a year ago still starts with a single command.

No invented facts

Generation operates on supplied records only. A confident incorrect answer is worse than an empty field.

Human approval before anything external

Nothing reaches a client until a named person has approved it, and the approval is recorded.

Your data remains yours

Your database on your deployment, downloadable in full. Not pooled and not used for training.

Deterministic where it matters

Invoices are produced from a fixed template. Client-facing figures are computed identically every time.

Legible by design

Written to be read by whoever maintains it next. Obscurity is not a retention strategy.

Before you hire us

What to buy instead.

Most businesses considering a build should buy off the shelf. Better established now than in week three.

If your process is a standard version of a common one

Mature, supported products that address the general case for a fraction of our fee. Where one fits, it is the right choice.

If you're…BuyWhat it does better than a build
A trades or field business
Dispatch, jobs, invoicing
Jobber, from $29/mo
Housecall Pro from $59/mo
Scheduling, dispatch and invoicing, maintained by a vendor dedicated to it.
A property manager
Units, tenants, accounting
Buildium, $62–$400/mo
AppFolio $1.40–5.00/unit, $280/mo min
Manages 200 units for less per month than an hour of custom development.
An agency or consultancy
Projects, time, profitability
Productive, $9–28/user/mo
Project and time tracking with margin reporting, at a cost immaterial against payroll.
Willing to build it yourself
And you enjoy that sort of thing
Base44 $16–160/mo
Retool, Glide, Replit, Power Apps, Airtable
A functioning internal tool can now be assembled for a nominal monthly fee.

Prices checked August 2026 and published by the vendors themselves — check them, they move.


When a build is the right decision

The process is genuinely yours

The practice no competitor shares and no product accommodates, which you would not abandon to adopt one.

An incorrect record costs money

A missed renewal, an unbilled job, a settlement that will not reconcile. No vendor warrants a configuration you assembled.

Ownership rather than tenancy

Where the system is an asset presented during diligence, a configuration rented inside another platform is the wrong structure.

A previous attempt was abandoned

An abandoned no-code attempt is the clearest indicator. The internal option has already been tested.

Several subscriptions, partly used

A fraction of each in use, with data still exported to a spreadsheet. The subscriptions eventually exceed the cost of replacement.

Someone becomes the support desk

The subscription cost is real, as is the obligation to maintain it. Failures become your responsibility.

Said plainly

The trade-off, stated plainly.

A build costs 75–250 times an AI application builder. That difference is real and we will not argue it away.

The difference purchases software shaped to your actual process, logic for which someone is accountable, and an asset you own outright.

Where those do not justify the difference, the lower-cost option is the correct one.

Fit

Who this is for.

A good fit

  • 5–200 people, and a process that runs on a spreadsheet somebody maintains by hand
  • Paying for several platforms and using a fraction of each
  • A workflow specific enough that no off-the-shelf tool quite fits
  • One person who can decide, without a committee
  • Real deadlines or real money riding on records being correct
  • You already tried building it yourself — a stalled no-code base or an AI-built app nobody dares touch. That's the strongest signal there is, and it's the easiest conversation we have.

Not a fit

  • A generic need a $30/month tool already solves — we keep a list
  • A consumer app needing millions of users on day one
  • Work that's really a staffing gap rather than a software gap
  • A decision that needs five stakeholders to agree before week one starts
Start small

One week, fixed fee, and you keep everything it produces.

A workflow map, a working prototype and a fixed quote, retained regardless of outcome.