Step 01 · Discover · 3–5 days
Understand the problem before designing the solution.
Every project starts with a short, focused discovery phase. We learn your business, your users, and what a win looks like — so every design and engineering decision afterwards is made for a reason, not a guess.
Inside the discover phase
- Kickoff conversation — A working session with the senior team who will design and build your project — not a sales handoff.
- Business and user goals — We map who your users are, what they need to do, and how the project should move your business forward.
- Content and structure — We review your existing site or product, content, and competitors, and shape them into a clear structure.
- Technical context — We look at the systems, integrations, and constraints the project has to work with, so there are no surprises in the build.
What you walk away with
- Project brief — A shared summary of goals, audience, and requirements that both sides sign off on.
- Sitemap & scope — The pages, features, and integrations in scope — and just as importantly, what isn’t.
- Success metrics — The measurable outcomes we’ll use to judge whether the project worked.
What we need from you
- Time with the people who know your business and customers best.
- Access to any existing site, brand guidelines, content, and analytics.
- Honest input on goals, constraints, budget, and deadlines.
Common questions about discover
Why not skip straight to design?
A few days of discovery prevents weeks of rework. Agreeing on goals and scope first means design and build move faster and deliver what you actually need.
How long does discovery take?
Typically 3–5 days, depending on the size of the project and how quickly we can speak with the right people on your side.
What if our requirements change later?
That happens. Changes after scope is agreed go through a simple change request, so you always know the effect on timeline and cost before anything moves.