No. C
Process / Playbook
Discovery, prototype,
ship, operate.
The same playbook for every engagement, scaled up or down. No project managers, no status decks, no Gantt charts.
-
01
Week 1–2
Discovery
A two-week paid sprint with the people who will actually build. We work with your data, your stakeholders, and your constraints. We deliver an architecture memo, a clickable prototype, and a phased plan.
- Architecture memo
- Working prototype
- Phased estimate
- 90-day plan
-
02
Week 3–6
Prototype
A working slice of the product, deployed to a real environment, used by real operators. We measure what matters to you and rip out what does not.
- Deployed slice
- Eval suite
- Telemetry dashboard
-
03
Week 7–14
Ship
Production hardening, content, integrations, and launch. We are in your standups, your repo, and your incident channel. Two-week iterations, working software at the end of each.
- Production launch
- Runbook & playbooks
- Hand-over to your team
-
04
Optional retainer
Operate
For systems that warrant it, we stay on under a small monthly retainer — running evals, refreshing models, and improving the surface. Otherwise we exit cleanly and your team takes the wheel.
- Monthly evals
- Quarterly review
- On-call coverage (optional)
∇
Principles
What we will and won't do.
We will
Push back when an idea is wrong. Tell you what you can build. Tell you what you should buy. Tell you what you should kill.
We won't
Run discovery for free. Ship without evals. Hand off to junior contractors. Sign exclusivity agreements that don't earn their weight.
We will
Be in your repo on day one and out of it cleanly when the work is done. Document everything we touch.
We won't
Lock you into our infra, our partners, or our retainer. The exit ramp is part of the deal.