How long does it take to design a web app?
A focused web application design engagement typically runs 8–16 weeks. The range depends on complexity: how many user types, how many core flows, and whether the engagement includes a design system or just the screens. Research and definition take the first 3–4 weeks. Design and iteration take the rest.
What affects the timeline
Complexity is the main driver. A web app with one user type, three core flows, and a well-defined brief can be designed in 8 weeks. An app with multiple user types, complex permissions, and admin interfaces alongside user-facing screens needs 12–16 weeks.
Research depth also matters. If you have clear user research and a validated problem definition, we can move faster. If we need to do discovery work to define the problem before designing the solution, that adds 2–3 weeks.
How the time breaks down
Weeks 1–3: discovery and definition. User research, stakeholder alignment, problem framing, and information architecture. Weeks 4–8: interaction design. Flows, wireframes, and prototypes before visual design is applied. Weeks 8–14: visual design. Finished screens, states, and edge cases. Final 2 weeks: design system and handoff documentation.
What slows things down
Unclear ownership on the client side. When multiple stakeholders need to approve each review, cycles lengthen significantly. Scope changes mid-engagement. Feedback that contradicts earlier decisions. We build review processes that minimize these risks, but the biggest factor is having a clear decision-maker on your team.
How we approach it
Discovery
2–3 weeks. Research, problem definition, and architecture.
Interaction design
3–4 weeks. Flows, wireframes, and prototypes.
Visual design
4–6 weeks. Finished screens, states, and system.
Handoff
1–2 weeks. Figma files, specs, and documentation.
Common questions
Ready to start?
Tell us what you're building and when you need it. We'll scope what's realistic and what it takes to get there.
Start a project