Budget and procurement guide
Budget for the decisions, not just the pages
The number of pages is one small cost variable. Strategy, content, governance, integrations, migration risk, quality assurance, and operational ownership determine whether a redesign is a simple production job or a business platform project.
By Prismo Web Solutions · Published
Three useful planning bands
Use ranges to create an internal investment conversation, not to force an unknown solution into a predetermined number. Scope can move a project above or below these bands.
Illustrative band
$15,000–$30,000
Focused marketing rebuild
A clear audience, limited stakeholder group, modest content set, established brand, standard CMS patterns, few integrations, and client-led content can fit here.
Illustrative band
$30,000–$75,000
Strategic B2B platform
Deeper discovery, custom UX and design, content strategy, multiple templates, CRM or marketing integrations, meaningful migration, analytics, and stakeholder governance often place work here.
Illustrative band
$75,000+
Complex digital ecosystem
Multiple sites, brands, regions, languages, large migrations, custom applications, product data, advanced search, identity, extensive integrations, or formal compliance and procurement can require this level.
What moves the budget
Strategy and stakeholder complexity
A founder and one marketing owner can reach decisions differently from a multi-division organization with executive, legal, IT, sales, HR, and regional reviewers. Interviews, research, workshops, documentation, revision cycles, and governance are real work.
Content condition and ownership
“We will provide the content” lowers cost only when owners, source material, deadlines, review capacity, and migration decisions already exist. Inventory, consolidation, messaging, writing, editing, approvals, entry, media production, and metadata frequently become the critical path.
Design system depth
A small set of flexible patterns costs less than a large component system with multiple states, complex data, motion, personalization, and documentation. Custom visual direction also requires more exploration than adapting an established brand system.
Platform and integrations
CMS workflows, CRM routing, marketing automation, product data, identity, search, payments, maps, job listings, portals, and internal APIs add discovery, implementation, failure handling, security review, and testing—not just connection time.
Migration and search risk
A new company site with no search footprint is different from a ten-year-old domain with thousands of URLs, backlinks, PDFs, campaigns, and business-critical rankings. Inventory, redirect mapping, content preservation, crawling, and monitoring should scale with that risk.
Quality, accessibility, privacy, and security
Browser and device coverage, accessibility review, consent behavior, data minimization, performance work, security controls, recovery planning, and documentation require budget. Treating them as a final plugin or automated scan creates false confidence.
Budget categories proposals often hide
- Internal staff time for interviews, reviews, content, procurement, and approvals.
- Photography, illustration, video, copywriting, translation, or document remediation.
- CMS, font, stock, search, form, analytics, consent, accessibility, and integration licenses.
- Hosting, CDN, email delivery, monitoring, backups, and security services.
- Data cleanup, content entry, redirects, historical files, and third-party migration.
- Training, documentation, launch support, stabilization, maintenance, and optimization.
- Legal, privacy, accessibility, security, or compliance review by qualified specialists.
How to compare two very different proposals
Normalize each proposal into a scope matrix. For every workstream, record deliverables, depth, owner, number of rounds, client dependency, acceptance criteria, exclusions, ongoing cost, and risk assumption.
Comparison questions
- Do both teams define “strategy,” “content,” “SEO,” “accessibility,” and “QA” the same way?
- Who writes, migrates, enters, and approves content?
- Which integrations are implemented and tested, versus merely accommodated?
- Is the redirect map included, and who validates it after launch?
- How many distinct templates and component states are actually designed and built?
- What data, access, people, and decisions must your team supply, and by when?
- What happens when an assumption proves false?
- Who owns defects, stabilization, maintenance, and future changes?
Use contingency for uncertainty, not wish-list features
A planning reserve of roughly 10–20% can be reasonable when legacy systems, content condition, integration behavior, or stakeholder requirements are not fully known. That is a general planning convention, not a mandatory fee. Reduce uncertainty through paid discovery when the unknowns are too large to price responsibly.
Separate build cost from operating cost
The launch budget buys a platform at a point in time. The operating budget keeps it secure, accurate, measurable, accessible, and useful. Model at least three years of hosting, licenses, maintenance, content, SEO, analytics, design-system evolution, and planned improvements.
A simple internal budget worksheet
- Business value: What revenue, cost, risk, or strategic capability could the project affect?
- Required work: Which discovery, content, design, development, integration, migration, and launch workstreams are needed?
- Internal capacity: Which work can your team complete on schedule, and what is the opportunity cost?
- External investment: What range funds the required scope with an appropriate risk reserve?
- Operating model: What annual investment keeps the platform healthy and improving?
- Decision threshold: Which measurable outcomes would justify the investment, and over what period?
Need a scope you can defend?
Share the budget band—and the reasoning behind it.
Prismo can help identify the work, dependencies, and tradeoffs before producing a proposal.