Process — state by state
How a project runs
Every project moves through the same states, in order. Nothing skips ahead: no build before a written scope, scheduling confirmed in writing, and no unattended high-impact action, ever.
- Draft — you describe the process, usually with the scoper. The brief is yours either way.
- Fit review — a person reads the brief and answers: fixed scope, workshop first, or an honest no.
- Scoped — both sides hold a written scope: trigger, systems, output, approval gate, acceptance criteria, delivery-hour bound.
- Contracted — the scope is signed before work starts. Payment does not replace the written scope.
- Payment — a one-time payment covers the agreed service. If you pay before fit and scheduling are confirmed, the refund terms apply; no second balance is charged automatically.
- Scheduled — a named delivery window is agreed. System access is arranged through a restricted process at this point — never through a web form.
- Delivered — the workflow is built and demonstrated against the acceptance tests, including a deliberately failed run to prove the error handling.
- Accepted — you accept in writing against the agreed criteria; the runbook is handed over.
- Support — questions after handoff go through the support path. Anything beyond the delivered scope is a new written scope, not an informal favor.
Start a fit review
The fit review starts from a brief. Build one with the scoper and send it from there — a person answers, in writing.