How it works
We don't start with software. We start with the person whose head holds the rules — and we don't write a line of code until they've signed off on what we wrote down.
Seven steps, in order
-
Discovery, recorded
One on-site session with the owner and the people who do the work. We open with the question every engagement starts with — what's the most painful thing in your business? — then ask "walk me through it like I'm the new hire," and let the knowledge-holder talk. We leave with the tickets, the spreadsheets, and the red-pen corrections.
-
Capture everything
Every artifact scanned. Written evidence outranks anyone's memory — including ours.
-
The rule book
Each rule written with its source and tagged observed, inferred, or gap. A numbered list of what nobody has written down yet. The arithmetic checked by machine against your real jobs.
-
Validation
The knowledge-holder re-derives their own corrections out loud and signs one line: "These rules, as written, produce outputs I would release without reviewing." Nothing ships inferred.
-
The spec and the quote
Inputs, engine, output, rollout — and a fixed price. We quote before we touch your data.
-
The build
Rules live in an editable config, not buried in code, so when a rule changes we change data. Every open gap is a hard stop: the tool says "ask the owner" instead of guessing. Your corrected jobs are the test cases.
-
Parallel run, then handoff
Your team generates, the owner reviews on paper as always. Every red mark becomes a patch. When the red pen goes quiet, the tool is done — and it's yours.
The rules we work by
One rock per engagement: every other wish goes on a written parked list so it's never lost and never sneaks into scope. Estimates stay human: a field measurement triggers a work order, never an auto-scrape. Money paths are deterministic — no raw AI deciding a cut or a price. The red pen stays the authority until sign-off.
And the tool keeps improving after it: because it's custom, a team member's "this would be better if…" becomes a patch, not a feature request to a vendor.
Terms and timing
Fixed fee. Half at signing, half at delivery. No per-seat, no per-order, no license.
Discovery is one or two visits. A first build is measured in weeks, not months, and paced by how fast your team can review it.