You sold the project. The client is excited, your team is ready to handle the strategy and design direction, and your white-label WordPress partner is standing by. There’s just one problem: you have no idea how big this project actually is.
For a non-technical agency owner, scoping a WordPress project can feel like guessing. You know a 5-page brochure site shouldn’t cost the same as a 40-page e-commerce build, but beyond that, the details get murky fast. How many hours does a contact form take? What about a staff directory? Is WooCommerce a weekend project or a month-long build?
The good news: you don’t need to know how to build a WordPress site to scope one accurately. You need a framework for asking the right questions and understanding what drives complexity.
Why scoping matters more than you think
A bad WordPress project estimate doesn’t just hurt your margin. It damages your relationship with the client and with your development partner.
Underestimate, and you’re either eating the cost or going back to the client mid-project asking for more money. Neither one is a good look. Overestimate, and you lose the deal to someone who quoted it tighter.
The root cause is usually the same: the agency treated “build a WordPress website” as one line item instead of breaking it into the components that actually drive time and cost. A scope of work that says “custom WordPress website, 10 pages, responsive” tells your developer almost nothing useful. The difference between a 40-hour build and a 120-hour build often comes down to details that never made it into the brief.
The five questions that determine project size
Before you send anything to your WordPress partner for a quote, get clear answers to these five questions. They cover the factors that account for the vast majority of scope variation in WordPress projects.
1. How many unique page templates does the client need?
This is the single biggest driver of development time. A “page” and a “page template” are different things. If a client has 20 service pages that all use the same layout, that’s one template used 20 times. But if the homepage, about page, services page, team page, and contact page all have different layouts, that’s five unique templates.
Industry data from agencies that specialize in WordPress development suggests that a single page template takes roughly 6-8 hours to build when it includes a few sections, a header, and basic responsive behavior. Complex templates with interactive elements, custom layouts, or data-driven content can take significantly longer.
When you scope a WordPress project, count unique layouts, not pages. A 30-page site with 5 templates is a smaller build than a 10-page site with 10 templates.
2. What functionality does the site need beyond pages and posts?
Standard WordPress gives you pages, blog posts, navigation menus, and basic media management. Everything beyond that adds scope. The most common functionality requests and their general complexity:
Low complexity (a few hours each): Contact forms, basic image galleries, social media icon links, Google Maps embeds, newsletter signup integrations.
Medium complexity (8-20 hours each): Staff or team directory with individual profiles. Event calendar with filtering. Blog with category filtering and custom layouts. Testimonial or portfolio sections with custom post types. Basic search functionality with filtered results.
High complexity (20-80+ hours each): E-commerce with WooCommerce (product catalog, cart, checkout, payment processing). Membership or gated content systems. Learning management (courses, lessons, quizzes). Client portals or dashboards. Custom integrations with CRMs, ERPs, or external APIs. Multilingual support via WPML or similar (4-12 additional hours depending on site size, according to White Label Agency’s project data).
The jump between categories is significant. An agency that quotes a WooCommerce build at the same rate as a brochure site is going to have a problem. E-commerce projects typically involve more unique templates (cart, checkout, account, product pages) and substantially more development and testing time than a standard business site.
3. Is there an existing site, and what’s happening to that content?
Content migration is the hidden time bomb in WordPress projects. If the client has an existing website with 200 blog posts, 50 product listings, or years of content, someone has to move that content into the new site. And it’s rarely as simple as copy-paste.
Migration scope depends on:
Where the content is coming from. Moving from one WordPress site to another is simpler than migrating from Squarespace, Wix, or a custom CMS. Moving from static HTML or PDFs is even more labor-intensive.
How much cleanup is needed. Old content often needs reformatting, broken links fixed, images re-optimized, and outdated information removed. If the client wants to “move everything over exactly as is,” that’s one scope. If they want it cleaned up and reorganized, that’s a bigger one.
SEO considerations. If the existing site has search engine rankings, you need 301 redirects set up for any URLs that change. Missing this step can destroy years of built-up organic traffic. Your WordPress partner should handle the redirect map, but you need to flag it in the scope.
White Label Agency, which has delivered WordPress projects for over 200 agencies, estimates roughly 6 hours per 20 pages for content migration as a general baseline. That’s around 20 minutes per page, but complex pages with lots of media, tables, or custom formatting take longer.
4. Who is providing the content and design?
This seems obvious, but unclear content and design responsibility is the number one cause of project delays and scope creep.
If your agency is providing the design: Your WordPress partner needs complete, finalized design files (Figma, Adobe XD, or similar) before development starts. The more specific the design, the more accurate the estimate. A wireframe gets you a ballpark. A pixel-perfect mockup gets you a real number.
If the client is providing content: Get it before development begins, or scope the project assuming placeholder content with a revision round after real content is loaded. Content that arrives late or in unexpected formats (Word documents with complex tables, PDFs that need to be rebuilt as web pages) can add hours that nobody budgeted for.
If nobody has planned for content or design yet: That’s not a development project. That’s a discovery project. Your white-label partner can’t accurately estimate a build when neither the design nor the content exists yet. The smartest move is to quote discovery and design as a separate phase, then scope the build after those deliverables are locked.
5. What needs to happen after launch?
Post-launch scope is where many agencies leave money on the table or accidentally promise things they haven’t budgeted for.
Clarify upfront:
Training. Does the client need a walkthrough of how to manage their own content in WordPress? Budget 1-3 hours for a basic training session.
Bug fixes and adjustments. Most projects include a post-launch window (typically 2-4 weeks) for fixing bugs and making minor adjustments. Define what “minor” means. Moving a button is minor. Redesigning the homepage is not.
Ongoing maintenance. Updates, security monitoring, backups, and hosting. This is where the recurring revenue conversation from our previous post comes in. Scope it separately and pitch it as a care plan.
How to turn this into a WordPress project estimate
Once you have answers to those five questions, you can build a scope document that actually means something. Here’s a simplified framework:
Small build (40-80 hours): 5-8 unique templates, standard functionality (contact form, blog, basic gallery), no e-commerce, no migration or minimal migration, design provided.
Medium build (80-160 hours): 8-15 unique templates, moderate functionality (custom post types, filtering, staff directory, event calendar), possible content migration from another CMS, design collaboration needed.
Large build (160-300+ hours): 15+ unique templates or WooCommerce, complex functionality (membership, integrations, multilingual), significant content migration, custom design work.
These ranges align with what agencies working with white-label partners typically see. Your actual numbers will vary based on your partner’s pricing, your markup, and regional market rates. But the framework gives you a starting point for a conversation rather than a guess.
The scoping conversation with your client
You don’t need to present any of this technical framework to your client. What you need to do is ask them questions that surface the complexity:
“Walk me through what happens when someone visits your site. What do you want them to do?” This reveals the user flows and key functionality.
“Do you have a site today? What’s on it that needs to come over?” This surfaces migration scope.
“How often will your team need to update the site, and what will they be updating?” This clarifies CMS requirements and post-launch needs.
“Are there any systems this site needs to talk to? CRM, email marketing, payment processing, inventory?” This uncovers integration complexity.
“Do you have a firm launch date? What’s driving that timeline?” This helps you prioritize features and potentially phase the project.
Write down the answers. That document becomes the foundation of your scope of work and the brief you hand to your WordPress partner.
What to include in your scope document
A scope of work that protects both you and your client should include:
What’s included: List every deliverable. Number of unique page templates, specific functionality, content migration details, responsive behavior, browser support, training sessions, post-launch support window.
What’s not included: This is just as important. Explicitly state what falls outside the project: additional pages beyond the agreed count, new functionality not in the original scope, content writing, photography, ongoing maintenance (unless quoted separately), third-party plugin licenses.
How changes are handled: State that any changes to the agreed scope will be assessed and quoted before work begins. This one clause prevents more problems than anything else in the document.
You don’t need to be technical. You need to be thorough.
The agencies that get scoping right aren’t the most technical. They’re the most thorough. They ask enough questions upfront that their development partner can give a real estimate instead of a guess.
Your WordPress partner will appreciate a well-organized brief more than you might expect. A clear scope means they can commit to a timeline, price it accurately, and deliver without the back-and-forth that drains everyone’s time.
And if you’re still not sure whether a project is a 60-hour build or a 150-hour build, that’s exactly the kind of question a good white-label partner can help you answer before you quote the client.
Need help estimating a WordPress project for your client? Send us the brief and we’ll help you scope it before you quote it.