Listen. Map. Build.
Ship. Run.
A boring process is a feature. After 18 years, I’ve stripped delivery down to five phases that don’t surprise anyone — clients or me. Below: the timeline, the deliverables, the principles, and the answers to every question I’ve ever been asked twice.
Listen
Week 0Before code, before design, a real conversation.
A 60-min discovery call. We map goals, buyers, the work that's breaking, the work you wish was happening. I take notes — actual notes — and come back with a written summary. If it doesn't fit, I tell you. If it does, we move.
- – Written discovery summary
- – Scope alignment doc
- – Honest fit assessment
- – No-pitch policy — ever
Map
Week 1Architecture before code. Always.
A working scope doc with flows, screens, data models, and a fixed timeline. You read it, you sign it, then we build to it. No surprises mid-project, no scope drift, no "actually it costs more now" emails.
- – Detailed scope doc
- – Architecture diagrams
- – Fixed timeline
- – Fixed price
Build
Weeks 2–NWeekly demos. Real, deployed, clickable.
I work in branches with daily commits. You get a Friday Loom showing what shipped this week and what's next. Claude Code, Codex, and GPT handle the volume — I handle the architecture, the taste, and the review of every output.
- – Weekly Loom demos
- – Live staging environment
- – Daily commit visibility
- – PR-level review on every change
Ship
Final weekLaunch is a checklist, not a prayer.
DNS cutover, schema markup, AEO/GEO setup, analytics live, monitoring on, redirects in place, error tracking firing, training session for your team, runbook documented. I've done this hundreds of times.
- – Pre-launch checklist (53 items)
- – AEO + schema + analytics
- – Team training session
- – Runbook + handoff doc
Run
Ongoing (optional)The retainer that pays for itself.
Most clients move to a small monthly retainer after launch. New flow builds, performance tuning, content ops, AI workflow upgrades. Like having a fractional CTO + ops lead, at a fraction of the cost.
- – Monthly review call
- – New flow builds (1–2/mo)
- – Continuous tuning
- – Priority access
Six non-negotiables.
No hourly billing. No surprise invoices. You always know what it costs.
Same person writes the spec, designs the screen, ships the code, fixes the bug. You email one address.
Agents do the volume. I review every output. Quality is non-negotiable.
If your project is wrong for me, I say so. I'll often refer you to someone better.
No account managers, no client services, no slide decks. Just work, demoed weekly.
Every project ships with a runbook. You're never stuck if I'm on a flight.
FAQ.
How long does a typical project take?
Marketing sites: 3–5 weeks. Storefronts: 4–6 weeks. Custom apps: 4–10 weeks. Brand identity: 3–4 weeks. CRM + email setup: 2–4 weeks. AI agents: 2–6 weeks. Multi-service engagements run in parallel — they don't stack linearly.
What if scope changes mid-project?
It happens. I write a one-page change order with new scope, timeline, and price. You sign or decline. No drama, no creeping invoices.
Do you use a contract?
Yes — a simple, plain-English MSA with a fixed-fee SOW per project. Half on signing, half on launch. No retainers required, no auto-renewals.
What about confidentiality?
Standard NDA on request. I've worked under NDA with funded startups, public companies, and creators. Your data stays your data.
Can I see work in progress?
Yes. Every project has a live staging URL from week 1, daily commit visibility, and a Friday Loom demo.
What's your refund policy?
If you're unhappy after the discovery + scope phase, you get the deposit back. After build starts, it's pro-rated.