Project Timeline
Business & StrategyHow long a website project takes from kickoff to launch, broken into discovery, design, build, and QA phases — usually eight to sixteen weeks for serious…
Discovery Phase | Project Discovery | Discovery Call
The Discovery Process is the early phase of a project — also called the discovery phase or project discovery — where the team and the client define goals, audience, scope, and constraints before design or development begins. It typically includes stakeholder interviews, brand audits, competitive research, content inventory, and a written brief. The output is a shared understanding of what is being built, for whom, and why.
Strategy before design. Pretty pages without a plan are expensive decoration. Most website projects that go off the rails went off in the first two weeks, when the team skipped discovery to start the part that feels productive — the visuals. By the time the design is in review, the goals are vague, the audience is undefined, and every stakeholder is rewriting from their own playbook. A real discovery process surfaces the hard questions early, when changing direction costs a Figma file instead of a rebuild. It is the cheapest leverage on the whole project, and the part teams cut first under time pressure.
A discovery typically runs one to three weeks. It opens with a discovery call that maps the business, the audience, the buying motion, and the goals. From there, the team interviews stakeholders, audits the current site, reviews analytics, surveys customers if relevant, and benchmarks competitors. Content is inventoried — what exists, what is missing, what gets rewritten. The output is a written brief covering positioning, sitemap, content strategy, technical requirements, and success metrics. Both sides sign off before design begins. Done well, the brief becomes the reference that resolves every design and scope debate downstream — instead of a sales document nobody reads again.
How long a website project takes from kickoff to launch, broken into discovery, design, build, and QA phases — usually eight to sixteen weeks for serious…
A full visual and structural overhaul of an existing site — new design system, new content model, often a new platform — done because the old one no longer…
The strategic work of deciding what types of content your business publishes, what fields each type has, and how they relate to each other — done before any…
A low-fidelity sketch of a webpage that shows structure, layout, and content priorities — without color, type, or polish — so the team can argue about the plan…
A semi-fictional profile of the person you are trying to sell to — role, goals, pain points, tools they already use — built so the team can write and design…
The plan for how a company will reach customers, position the product, set pricing, choose channels, and book revenue — turning a thing that exists into a…
The smallest version of a product you can ship to real users to learn whether the idea actually works, instead of guessing in a room for a year and launching…