Fixed scope. Expert time spent on corrections, not meetings.
What we need from you, what you get each week, and how the loop is handed over.
01 · WEEK 1
Scope
A thirty-minute call, then a one-page scope: the decision, the inputs, the tables you already use, and what a good answer looks like.
02 · WEEKS 2–3
First engine
The deterministic core: your tables and formulas, encoded and tested. It proposes; you review. Usually it is already useful.
03 · WEEKS 4–5
Loop
Review queue, rule capture, and the agreement dashboard. Corrections start compounding.
04 · WEEK 6+
Customer pass
Optional: a first-pass estimator your customers can use, bounded by the rules your expert approved.
What we need from your expert
- The tables and spreadsheets they already use, as they are. We do not need them cleaned up.
- Ten to twenty past jobs with the answer they gave. These become the first test set.
- About an hour a week, spent reviewing proposals in the queue. Every review is a training signal.
- A definition of done: what has to be true for a proposal to go out without a second look.
What you get
Engine core
A tested, deterministic module that reproduces your tables and formulas. Pure functions with a test per table row.
Review queue
A screen where the expert sees each proposal, accepts it, or corrects a line. Corrections are captured with their conditions.
Rule ledger
Every captured rule, who made it, when, and what it changed. Rules can be edited or retired.
Agreement dashboard
How often the expert accepts proposals unchanged, by job type, over time. The number that tells you when to trust it.
Customer pass (optional)
A bounded first-pass estimator for your customers, with the price and recipe gated by the rules your expert approved.
Pricing
Each engine is a fixed price agreed at scope. The first engine for a new client includes the review queue and rule ledger. Hosting runs on your accounts or ours at cost. Changes to scope are written up before the work, never after.
Request a scoping call