How long a product design engagement actually takes

Timelines are one of the few things we publish directly on every practice page, because vague answers here cost trust for no reason. Foundation — strategy, positioning, identity — typically runs four to eight weeks. Interface — product and UX design — four to ten. Build — engineering, from Webflow through headless Next.js — four to twelve, depending on scope. Systems, for full applications and platforms, eight to twenty. Loop, the post-launch practice, isn't a fixed engagement at all — it's a monthly retainer with a six-month minimum, because iteration doesn't have a natural finish line.

Those ranges are wide on purpose, and the width isn't padding — it's mostly explained by three things that have nothing to do with how fast the studio works. The first is decision-making structure: a single, empowered decision-maker moves a project through review in days; nine stakeholders who each want a say move it through review in weeks, for identical work. The second is content and asset readiness — a design phase can't finish waiting on copy, photography, or data that was supposed to arrive in week two and arrives in week six. The third is feedback latency: a round that takes a client three days to review costs three days, every round, compounding across a project with several rounds built in.

What actually shortens a timeline, in order: naming one final decision-maker before the project starts, delivering content and assets on the schedule agreed at kickoff instead of the schedule that felt possible at the time, and turning feedback rounds around in under 48 hours. None of those cost anything. All three, together, are usually the difference between the low end of a range and the high end of it.

The honest answer to "why did our project run long" is almost never "the studio was slow." It's almost always one of the three things above, quietly compounding, unnoticed until the project is already three weeks past where everyone expected it to be.