Most budget conversations about website rebuilds start in the wrong place.
Founders ask: "How much does a website cost?" The real question is: "What are we actually trying to build, and what will it cost us not to build it right?"
I've rebuilt sites for government agencies, B2B SaaS companies, e-commerce brands, and early-stage startups. Projects ranging from $5K to $75K+. Here's what I've learned about where money goes, where timelines die, and what I'd do differently.
The Tiers Are Real. The Ranges Are Deceptive.
Before we get into the nuance, here's the honest breakdown:
Template refresh — $3K to $8K New design on an existing platform (Webflow, WordPress theme, Squarespace). 5 to 15 pages. Better copy, better structure, no custom logic. Ships in 3 to 5 weeks.
Custom design and build — $15K to $40K Custom design system, built on Webflow or Next.js. 10 to 30 pages. Includes strategy, CMS setup, SEO foundation, and maybe a CRM or analytics integration. 8 to 12 weeks.
Platform rebuild — $40K to $100K+ Ground-up rebuild with custom application logic. Customer portals, partner ecosystems, multi-language support, migrating off a legacy CMS no one on the team fully understands. 3 to 6 months.
These tiers look clean on paper. The real question is what moves you from the low end to the high end within each tier. That's where most scoping conversations go sideways.
The Cost Drivers Nobody Talks About Clearly
1. Custom Logic Compounds Fast
A static 10-page marketing site is a fundamentally different engineering problem than a site with role-based access, dynamic pricing, or third-party API integrations.
A concrete example: a "simple" booking form integration might take one day. A custom partner dashboard with role-based access and a synced data model takes weeks, including edge cases, error states, and the inevitable "wait, can external users see this field?" conversation on week three.
If you're a technical founder, you already know scope creep lives in the logic layer. The same is true here.
2. Content Is Always the Bottleneck
A 10-page site costs less than a 50-page site. Obviously. But what actually kills timelines isn't the page count. It's the content pipeline.
Most clients say they'll have content ready. Most don't.
What actually delays projects: copy that needs writing, case studies that need creating, product screenshots that can only be taken after the new UI ships, existing documentation that needs restructuring.
Treat content delivery like a hard dependency in your project plan. Gate development milestones on content sign-off, not the other way around.
3. SEO Migration Is an Iceberg
If your site has any search equity, even modest rankings, a rebuild without a migration plan can wipe years of accumulated value overnight.
What this actually involves: redirect mapping for every changed URL, preserving backlink equity, auditing canonical tags, maintaining hreflang attributes across language variants.
I recently scoped a migration for a site with 1,700+ URLs. That work alone was a meaningful piece of the engagement. Not glamorous, but the kind of thing that quietly costs companies thousands in lost organic traffic when it gets skipped.
Rule of thumb: if the site has been live for more than two years and gets any organic traffic, budget for a dedicated SEO migration plan. It's not optional.
4. Skipping Strategy Is the Most Expensive Decision You Can Make
The most expensive mistake in a rebuild is spending $40K rebuilding the wrong thing.
A proper strategy phase, covering analytics audits, user research, competitor analysis, and conversion funnel mapping, costs $2,500 to $10,000 and regularly prevents six-figure mistakes.
A real example: an audit I did revealed a company's primary conversion page had been broken for over four years. It was returning raw code instead of a form. Every lead that landed on that page during that window was lost.
If a vendor quotes only "design and development," ask explicitly: who is doing the strategy, and when? If the answer is "we'll figure it out during kickoff," that's a yellow flag.
Platform Choice: Follow the Strategy, Not Familiarity
The failure mode I see most often: companies choose a platform based on familiarity, then spend years fighting its limitations.
The second most common: companies go fully custom Next.js when Webflow would have shipped twice as fast at half the cost, because someone wanted maximum control over a site that just needs to look good and convert visitors.
The question to ask before picking anything: What does this site need to do in 12 months that it can't do today? Work backward from that, not from what your team already knows.
Here's how I think about the main options:
Webflow is the right call for most marketing sites and CMS-driven content, especially if non-technical teammates need to make edits without filing a ticket. The hard limit is custom logic. If you need a real backend, user authentication, or anything resembling a web app, you'll hit that ceiling fast.
Next.js and React make sense for custom apps, portals, dashboards, and performance-critical builds. The tradeoff: every content change requires a developer unless you wire up a headless CMS on top of it. More power, more maintenance surface.
WordPress still works well for content-heavy sites and teams already deep in that ecosystem. But go in with eyes open. Performance out of the box is rough, plugin bloat is real, and security is an ongoing maintenance burden, not a one-time setup.
Shopify is the obvious choice for e-commerce: product catalogs, checkout optimization, inventory management. Outside that lane, it gets painful quickly.
The platform should follow the strategy. Pick what fits what you need to build, not what someone on the team already knows.
What Actually Brings the Cost Down
Ship content before development starts. This is the single highest-leverage thing a client can do. Final copy, brand assets, and images delivered before the build begins can eliminate 20 to 30 percent of a project timeline.
Scope the MVP tightly. Launch with 15 essential pages instead of 40. Add the rest in phase two, after you have real user data. The best sites are built iteratively. A 15-page launch that ships in 8 weeks usually outperforms a 50-page launch that ships in 6 months.
Work with a small team or senior freelancer. A large agency has overhead: account execs, project managers, sales teams, office space. A senior freelancer or boutique team delivers comparable quality without the markup. You're paying for the work, not the org chart.
The Hidden Cost: Doing Nothing
Here's the math that doesn't show up in vendor proposals.
If your site is underperforming, that cost is paid every day. Not as a line item, but as leads that bounce, search rankings that slip, and credibility that quietly erodes.
A real example: one audit found a B2B company ranking on page four of Google for their primary product keyword. Their site was built on a bloated platform generating pages twice the recommended size, with navigation that had 60+ items when top competitors had 11.
That wasn't a design problem. It was compound technical debt masquerading as a marketing problem.
A rebuild is a one-time cost. An underperforming site is a recurring one.
How to Actually Budget for This
1. Start with an audit, not a redesign. A $3K to $7K audit tells you exactly what needs to change and often surfaces quick wins you can ship before touching the core build.
2. Budget for strategy, design, and development as a unit. These aren't separable phases. A pretty site that doesn't convert is just expensive art.
3. Plan for post-launch optimization. Budget $1K to $3K per month for the first three months after go-live. Real user data surfaces things no amount of pre-launch testing catches.
4. Compare total cost, not hourly rate. A $150/hr senior developer who ships in 8 weeks costs less than a $75/hr junior who takes 6 months and needs three rounds of revisions.
What I'd Do Differently
Gate every project on a written content plan before design begins. No exceptions.
Build SEO migration into default scope for any site older than two years. It's always needed and almost always underbid.
Push back harder on scope creep in the logic layer. That's where timelines go to die.
Start smaller and ship faster. The version that gets real data beats the version that tries to anticipate everything.
For those who've been through a rebuild, as the client or the one doing the work: where did the scope surprise you most?
Was it the content pipeline? The SEO migration? Platform limitations? Something else entirely?
And if you're currently scoping one, what's the decision you're stuck on? Happy to think it through in the comments.
Top comments (0)