July 11, 2026 · Faith Forge Labs Editorial Team
Website Redesign Cost and Timeline for a Small Business
A small-business redesign is priced by much more than page count. Content decisions, migrations, integrations, approvals, and launch risk usually determine the schedule.
A redesign can mean new colors on five existing pages or a complete rebuild of how a business presents services and receives leads. Those projects should not have the same budget or timeline. The quickest way to get a misleading quote is to ask for “a new website” without agreeing on what the current one is failing to do.
Before comparing proposals, define the job. Is the site hard to use on a phone? Does the business no longer match the copy? Are search pages missing? Do leads fail to reach anyone? Design should solve those problems, not simply make the screenshots look newer.
Inventory what has to move
List public pages, articles, forms, files, analytics, domains, email dependencies, booking tools, accessibility needs, and search-performing URLs. Decide what stays, what is rewritten, and what can retire. Content review often takes longer than expected because it requires business decisions, not typing.
Preserve valuable URLs where possible and plan redirects for the rest. A launch that breaks years of trusted links has created a new problem.
Understand the major cost drivers
Custom visual direction, original photography or illustration, content strategy, copywriting, a content management system, complex forms, integrations, multilingual pages, and migrations all add real work. Template customization may be appropriate when the business does not need a unique interaction or system.
Ask whether hosting, maintenance, premium licenses, analytics, and post-launch support are included or recurring. Compare the whole first year rather than one build figure.
Build an approval schedule
A project can stall for weeks while waiting on a logo, service description, legal review, or one decision-maker. Name who approves structure, design, copy, and launch. Put review windows on the calendar and decide what happens when feedback conflicts.
Allow time for revision after people see real responsive pages. A flat image cannot reveal every content wrap, form behavior, or mobile tradeoff.
Treat launch as work
Before release, crawl the new site, test forms and notifications, verify analytics, review mobile layouts, rehearse redirects, back up the existing property, and confirm domain access. Choose a launch window when someone can respond if an integration fails.
After release, check real submissions, indexing signals, errors, and performance. The first few days are part of the project, not an optional maintenance contract.
Choose clarity over a rushed date
A focused small site can move quickly when content and decisions are ready. A larger redesign may need staged releases. If a fixed event or season matters, reduce scope rather than quietly removing testing from the schedule.
A good proposal makes the relationship between price, timeline, responsibilities, and deliverables easy to see. If those remain vague, the final design is not the biggest risk.