01
1) Discovery: define the job
Before anyone opens a design tool, we nail the job: who it’s for, what success looks like, must-haves vs later, and which tier fits (business site, tool, or full product). Vague briefs create expensive rebuilds. Clear discovery creates a quote you can trust.
02
2) Scope and estimate
You get a fixed-range estimate and a milestone plan — not an open-ended retainer. Scope includes pages/features, integrations, timeline, and what’s explicitly out. If something later expands the job, we re-scope as a new milestone instead of silently burning hours.
03
3) Design direction
We shape hierarchy, messaging, and visual direction around conversion — not decoration. You’ll see direction early enough to course-correct before engineering is deep. Taste matters; so does a clear primary action on every key page.
04
4) Build in milestones
Work ships in chapters you can review: structure first, then depth. You get shared previews, feedback windows, and progress you can see. That’s how larger products stay honest — and how smaller sites stay on a 1–2 week track.
05
5) Launch and handoff
Launch isn’t “files in a zip.” It’s live hosting (or handoff), basics like forms and analytics, and clarity on who owns what next. You leave with the codebase and a path for hosting/care if you want it.
FAQs
Quick answers
How long does discovery take?
Usually a short call plus any follow-up notes. Enough to quote honestly — not a multi-week workshop.
Do you use agile sprints?
We use milestone delivery with clear outcomes. You always know what’s shipping next and what it costs.
What if requirements change mid-build?
We pause, re-scope the change, and quote the new milestone. No surprise invoices for “just one more thing.”
