Every agency quotes it, every client remembers the discrepancy: the redesign that was “six to eight weeks” and took five months. The gap is not usually laziness or dishonesty — it is that the quoted number covers the agency’s work while the calendar covers the whole project, and most of the elapsed time lives in the gaps between them: the week the feedback sat in an inbox, the content that arrived three weeks late, the approval meeting that kept getting rescheduled. If you are a small business owner about to sign a redesign proposal, you deserve the version of the timeline that includes your part. This article lays out the five phases with realistic durations, shows where delays actually originate, names what you as the client control, and lists the red flags in any quoted schedule. The two decisions that must happen before the timeline starts are covered in our guides to homepage proof points before a redesign and sorting website copy before a redesign — both of which run in parallel with design whether you plan for them or not — and the phase nobody budgets properly is the small business website launch checklist, which is where timelines quietly double.
One honest number up front: for a typical small business site of ten to thirty pages, a well-run redesign takes ten to sixteen weeks from kickoff to launch, and the agency’s labor is less than half of that calendar.



The Five Phases And What Each One Really Takes
A redesign moves through five phases, and each has a realistic duration that proposals rarely state plainly. Discovery and planning — goals, audience, sitemap, the decisions in the proof-points article — takes two to three weeks when the client is responsive, and is the phase most often compressed to a call, which is how redesigns lose their compass. Content work runs in parallel from week two onward: copywriting or copy-refresh for the key pages is the single most underestimated workstream in small business redesigns, and it takes what it takes — usually three to six weeks of elapsed time, less if your copy is mostly sound and only needs restructuring. Design — moodboards, homepage concepts, interior templates — takes three to four weeks including two rounds of feedback; the feedback rounds, not the designing, are what stretch this phase. Development and staging, where the approved designs become a working site on a hidden address, takes four to six weeks for a standard small business build. And launch preparation — content entry, testing, redirects, DNS, the launch checklist — takes one to two weeks that almost nobody reserves, because everyone assumes the project is done when the site looks done. The shapes below compress well only if content and decisions arrive on schedule; they collapse gracefully when you protect the launch window as fiercely as the design phase.
Where The Delays Actually Come From
When a redesign overruns, the post-mortem almost never says “the agency was slow.” It says one of four things, in roughly this order of frequency. Feedback latency: the design sat with the client for eleven business days awaiting comments, and three such pauses add five weeks without a single day of agency delay. This is the dominant cause of overrun by a wide margin, and it is entirely within the client’s control — the fix is a named decision-maker, a forty-eight-hour feedback norm, and consolidated comments in one document instead of scattered email fragments. Content arriving late: the site was ready to build but the new services page copy arrived at week nine, and development either stalls or builds around placeholder text that quietly ships. Scope creep discovered mid-design: the proposal said “redesign,” and at week five the project became “redesign plus a blog plus a booking flow,” and the timeline absorbed a second project without anyone saying so. And third-party dependencies: the photographer, the copywriter, the review-platform integration, each a small external project with its own lead time that the timeline treated as instant. The pattern in all four: elapsed time, not work time. Agencies are rarely the bottleneck; the spaces between the work are.
What You As The Client Control
The uncomfortable truth of redesign timelines is that the client holds most of the schedule levers. Four commitments from your side do more for the deadline than any agency promise. First, name one decision-maker before kickoff: every day a design waits on three people’s opinions is a day the calendar spends idle, and consensus-by-committee is how two weeks of feedback becomes four. Second, commit to the forty-eight-hour feedback norm in writing, with consolidated comments in a single document — scattered reactions across email threads double design rounds because the designer must reconcile contradictions before acting on any of them. Third, deliver content on the dates the schedule assigns it, treating those dates like supplier payments rather than aspirations — and if you cannot write it yourself, book the copywriter at kickoff, not at week six, because good copy has its own lead time. Fourth, freeze scope at approval: every addition after design sign-off is a negotiation, and the honest way to run one is to name its calendar cost explicitly — “yes, and that adds three weeks” — rather than absorbing it silently and discovering the truth at launch. Owners who make these four commitments routinely hit twelve weeks on projects where the same agency quoted sixteen. The levers are yours; agencies are usually just waiting at them.
Red Flags In Any Quoted Timeline
You can learn a great deal about a redesign proposal from reading its timeline closely, and these five patterns should each prompt a question before signing. No content phase: a proposal that jumps from design to development with no content workstream has either assumed your copy is final (is it?) or plans to quietly discover otherwise at week eight. Design before discovery: concepts promised in week one are decorating before the strategy exists, and you will be asked to approve aesthetics for a site whose goals have not been discussed. No launch window: timelines that end at “site complete” without reserved weeks for testing, redirects, and DNS have shipped their risk onto you — the launch checklist deserves named weeks, not a shrug. Vague feedback assumptions: a schedule with one round of “client review” and no stated duration has never met a real client; two named rounds with stated turnaround expectations is what professionalism looks like. And impossibly short totals: a ten-page site quoted at three weeks total is quoting a template swap while selling a redesign — official guidance such as Google Search Central is blunt that a quality site needs substance, and substance has a calendar cost. You will either get the template or the overrun, possibly both. None of these are automatic deal-breakers — small projects genuinely can be fast — but each is a question worth asking at proposal stage, where answers are cheap, rather than at week ten, where they are not.
A Worked Example: The Twelve-Week Redesign That Held
Watch the framework hold under real conditions. The site: a fourteen-page site for a small bakery-cafe business, redesign goals are modernizing an eight-year-old design, adding online ordering, and moving to a current CMS. Week one: kickoff, goals, sitemap, and the proof-points decisions from the parallel guide — done in three working days because the owner had done the homework. Weeks two to four: design concepts, homepage and two interior templates, with feedback returned inside forty-eight hours by the one named decision-maker; two rounds, no drift. Content: the owner rewrites six key pages with a booked copywriter’s light editing, delivered end of week five — on schedule because it was assigned at kickoff. Weeks five to nine: development on staging, ordering integration tested with real menu items, placeholder text never allowed to linger more than a day. Weeks ten to eleven: the launch checklist — content entry final pass, forms tested with real submissions, old-to-new URL redirects mapped and spot-checked, DNS cutover planned for a quiet Tuesday morning with the old site left runnable for a week as rollback. Week twelve: launched, monitored, old site retired. Total elapsed: twelve weeks, of which agency labor was about half, and the difference was the four client commitments doing their quiet work. The same project without them is the five-month version you have already lived through once.
Before signing the next proposal, ask for the phase durations in writing, check the five red flags, and commit to the four client-side levers — the timeline is yours more than you think.