Last updated: July 14, 2026
The gap between a WordPress quote and the final invoice is almost never dishonesty — it is discovered scope: the 400 extra pages, the CRM nobody mentioned, the “small” calculator embedded in a page since 2019. Scoping is the work of discovering those before they are change orders.
What belongs in a WordPress project scope?
- Content inventory — a crawl-based count of pages, posts, and files, flagged keep / improve / retire. Counts, not impressions: when we migrated Lando & Anastasi to WordPress, the inventory was 576+ pages — a number that shapes budget honestly before anyone designs anything.
- Template list — the distinct page designs the build actually requires. Twelve templates and forty templates are different projects.
- Content model — the structured types beyond pages/posts (team, case studies, products, locations) and the fields editors need.
- Integration list — every system the site touches: CRM, marketing automation, analytics, search, gated content, embeds. Named, with an owner for credentials on each.
- Migration plan — what moves, how (scripted vs. manual), and who does editorial cleanup.
- Environments & workflow — local/staging/production, version control, and how changes deploy.
- Performance, accessibility & SEO targets — Core Web Vitals expectations, WCAG level, full redirect map ownership.
- QA & launch plan — device/browser coverage, form testing against real destinations, analytics verification, rollback plan.
Which scope items blow up budgets most often?
Integrations and migration volume, in that order. An integration list that says “HubSpot” when reality is HubSpot forms + lifecycle tracking + a legacy Salesforce sync is a five-figure surprise waiting for a status call. Migration surprises are quieter but relentless — every uncounted page is cost somebody eats later. Third place: the unowned redirect map, which is how sites lose SEO in an otherwise good rebuild.
What should you prepare before asking for quotes?
You don’t need a specification — you need honest inputs: a site crawl (or ask each vendor to run one and cite counts), your integration list with owners, examples of sites whose function you want (not just looks), your team’s editing reality, and a real budget range. Vendors scope to the information they get; vague inputs produce padded-or-lowballed guesses, and you cannot tell which is which.
How do you compare quotes once they arrive?
Normalize them against your scope document: does each quote cite the same page counts, template counts, and integrations? Does it name what is excluded? Does it separate build cost from post-launch support? A materially lower number usually means an assumption difference — find it before you sign, not after. The vendor-vetting questions in our guide to choosing a web partner pair well with this exercise; pricing clarity under scrutiny is one of the strongest signals a partner sends. For where budgets typically land and why, see our custom WordPress cost guide.
What are the red flags in a scope document?
Read scopes for what they refuse to commit to. Warning signs: no page or template counts anywhere (“full site redesign” is a sentence, not a scope); “content migration included” with no volume attached; integrations listed as product names without pattern or ownership; QA described as “thorough testing” with no device or browser matrix; no redirect plan; and hosting or post-launch support waved at rather than priced. Any one of these is where the extra invoice lives. The same instincts apply to the relationship itself — the vendor warning signs in Red Flags in a Web Vendor Relationship usually show up first in the paperwork.
How should change orders work?
A change order is not a failure — discovered scope is normal. What separates healthy projects is process: the change is written down with its cost and schedule impact before the work happens, you approve or defer it explicitly, and a running scope ledger keeps the current total visible. The failure mode is the drip — small unpriced accommodations that surface as one large number at the end. If a vendor’s answer to “how do changes get priced?” is “we’ll work it out,” you have found the future dispute.
What does a well-scoped project feel like?
Boring, in the best way: discovery confirms the inventory instead of exploding it, integrations are proven on staging early, content migrates on schedule because someone counted, and launch week is a checklist rather than a scramble. That is the experience our WordPress development team scopes for — and it starts before the quote, not after the contract.
