Check the plan before you pay for another build
We review what went wrong last time, map your integrations and write a brief any vendor can quote against, so the next build starts with fewer unknowns.
Plan Your Next BuildFind our content helpful? (?)
Add as a Preferred source on Google
Before you sign another $20K to $100K WordPress proposal, see what a WordPress consultant covers, a self-test for whether you need one, and a brief you can hand to any vendor.
| Short answer: Do you need a WordPress consultant before your next build?
● Book one if any of these apply: your last build failed, the site connects to more than three other systems, or you’re thinking about changing platforms. ● What you get: an audit of what you have, an architecture plan, and a vendor brief every agency quotes against. At US agency rates, that’s roughly $1,000 to $9,000. ● Skip it if: the build is under $20K on a standard theme, or the team that built your current site is doing the work and your scope is already written. |
Your last build cost $40,000 and took five months. It launched late, and checkout still breaks every time the shipping plugin updates.
Your team fixes failed orders. You spend evenings chasing a developer who now takes a week to reply.
When the business was smaller, a freelancer or part-time developer held the site together. A theme, a handful of plugins and a few quick fixes were enough.
Growth changed that. Every new offer (a membership tier, a product bundle, a second course) makes the system more fragile, and some launches break it outright.
You’re now too big for a theme and a few plugins to cope, and too small to hire an engineering team. That’s what makes deciding on the next build so hard.
A $60,000 proposal from a new agency is on your desk, and it reads a lot like the first one. You’re not a developer, so you can’t tell if it misses what broke last time.
Before you sign, ask one question: has anyone who isn’t building the site checked the plan?
We’ve seen this across many rebuilds at this size. The second build usually fails for the same reasons as the first: nobody wrote down what broke, which systems connect, or what “done” means.
A short consulting engagement settles those three things before the money goes out. It’s where many of our WordPress development projects start.
This guide covers what a WordPress consultant does before a build, a self-test for whether you need one, what it costs against your build budget, and a brief you can hand to any vendor.
What a WordPress consultant covers before a $20K to $100K build
| In short:
A pre-build consulting engagement produces three documents you own: an audit, an architecture plan and a vendor brief. ● The audit shows what works, what broke last time and what’s worth keeping. ● The architecture plan decides which plugins, which custom code and how each integration connects. ● The vendor brief turns both into one scope that every agency quotes against. |
At $200K to $1M+, most of your revenue passes through the site: checkout, course access, subscriptions, member logins and the sync to your CRM or warehouse.
A wrong architecture call shows up months later as a slow checkout, a run of failed renewals or a second rebuild. By then the money is spent and the vendor has moved on.
A WordPress consultant’s job is to make those calls before anyone writes code, and to write them down so you’re no longer the only person who knows how the site fits together.
| Part | What the consultant does | What you get | Typical time |
| Audit | Reviews your code, plugins, hosting, data and the last build’s scope and handover | A written list of what to keep, fix or replace | 1 to 2 weeks |
| Architecture | Decides plugins versus custom code, how each integration connects, hosting, and which system owns which data | An architecture plan and an integration map | 1 to 2 weeks |
| Vendor brief | Turns the audit and plan into scope, must-haves, exclusions and acceptance criteria | A brief three vendors can quote against | 2 to 5 days |
Consulting doesn’t include writing production code, designing pages or running the site after launch. Some consultants also build, which is fine as long as the audit, plan and brief are written down and yours to take to any vendor. Ask for that in writing before you start.
If you need technical decisions every month after the build, a fractional CTO may fit better. Our post on whether to choose a fractional CTO or another developer covers when each makes sense.
What the engagement needs from you
Consulting still takes your time. Expect to spend 3 to 5 hours a week while it runs:
● Hand over logins for hosting, code, domain, payment gateway and every connected tool.
● Bring in the person who handles workarounds today, such as your ops manager or course admin. They know where the site breaks.
● Share the last contract, proposal and any messages about missed deadlines.
If you can’t find the logins or the last contract, that becomes the audit’s first finding.
Here’s what the three parts look like for a business whose first build went wrong.
| Example: the $450K course business whose first LMS build failed
The situation: You sell online courses on WordPress at about $450K a year. You paid a freelancer $35,000 to move from a hosted course platform to LearnDash: ● Launch slipped from 8 weeks to 5 months. ● Your CRM, payment gateway and live-class tool are connected, but enrollments sync only some of the time. ● About 2,000 students were migrated, and some lost their course progress. ● The freelancer has moved on, and nobody has the full admin and hosting logins. ● Support tickets about lost progress keep coming, some students have asked for refunds, and your next course launch has slipped a quarter. The fix: A three-week consulting engagement before hiring the next team. ● Audit: recover all accounts, then list which pages, courses and plugins to keep and which to rebuild. ● Architecture: pick one system as the source of truth for enrollments, and replace the custom sync with a supported integration. ● Vendor brief: define “done” as enrollments syncing within 5 minutes and every student’s progress carried over. The outcome: Three agencies quote against the same brief. You keep most of the existing course content, the rebuild has a fixed scope, and you know which problems were the platform and which were the build. |
| Section recap
● Pre-build consulting gives you an audit, an architecture plan and a vendor brief. ● At your size, the architecture calls protect checkout, enrollments and integrations that carry revenue. Next steps ● Collect every login for hosting, code, domain and plugins before you talk to any vendor. ● Write down what broke in your last build, even as a rough list. |
You now know what you’d be paying for. The next question is whether your build needs it at all.
Should you skip it? A self-test before your next build
| In short:
Three signs say don’t skip consulting. A small, well-defined build with a team that already knows your site usually can. ● A failed last build: the new vendor inherits code and data nobody has checked. ● More than three integrations: each connection is a place orders, students or stock can go missing. ● A platform change: traffic, customer accounts and subscriptions all have to move safely. |
Sign 1: your last build failed
At your size, a failed build costs far more than the invoice:
● Sales lost while checkout or enrollment was broken.
● Staff hours spent fixing orders, syncs and student records by hand.
● Ad spend sent to pages that didn’t convert.
● Your own time, pulled away from growth for months.
Trust takes a hit too. After one bad agency, every new proposal looks either too cheap to be real or too expensive to justify. The next vendor will also inherit the first one’s code, and without an audit their quote has to guess. Some pad the estimate, and others propose a full rewrite you may not need.
Take extra care with: who owns the code, hosting and domain accounts; what the last contract promised against what was delivered; and the state of your customer and order data.
Sign 2: more than three integrations
A store or course business in this band often runs WordPress alongside a CRM, email platform, payment gateway, ERP or accounting tool, warehouse, or live-class software.
In the rebuilds we’ve seen, the site usually broke at a connection between two systems. You’ve likely hit this point if someone on your team re-enters data between systems every week, or if updating one plugin breaks a sync somewhere else.
Take extra care with: which system is the source of truth for customers, orders and stock; how often data syncs; and what happens when one system goes down.
Sign 3: a replatform is on the table
Moving from Shopify to WooCommerce, from a hosted course platform to LearnDash, or from a custom build to WordPress changes more than the theme. Search traffic, customer accounts, subscriptions and order history all have to move.
For a subscription or membership business, the risk is concentrated: one migration mistake can mean hundreds of failed renewals in the first billing cycle and a week of angry support emails. If the platform choice is wrong, you pay for the move twice.
If you’re not sure WordPress itself is the limit, our post on signs your website has outgrown standard WordPress walks through them.
Take extra care with: URL redirects, saved payment methods and active subscriptions, and whether the new platform can handle your next two years of growth.
Timing matters as much as the decision
Avoid starting a rebuild eight weeks before Black Friday or a big course launch. Run consulting while the old site still works, so the build starts with a plan and goes live in a quieter month. If your peak is less than three months away, stabilize the current site first and plan the rebuild for after it.
When you can skip it
● The build is under $20K on a standard theme and well-known plugins.
● The team that built your current site is doing the work, and it has gone well.
● Your scope is already written, with measurable acceptance criteria.
● The problem is urgent, such as a security issue or outage. Fix that first and plan later.
The self-test
Answer each question for your next build:
| Question | If yes |
| Did your last build miss its deadline, budget or scope? | Book consulting first |
| Will the site connect to more than three other systems? | Book consulting first |
| Are you considering a platform change? | Book consulting first |
| Are quotes for the same project more than twice apart? | Your scope is unclear, so start with a brief |
| Are you missing admin access to hosting, code or domain? | Start with an audit |
| Is it a build under $20K on a standard theme? | You can likely skip consulting |
A yes to any of the first three questions is enough reason to book consulting. Here’s how the integration sign plays out for a store that got very different quotes.
| Example: the $800K store with quotes from $30K to $95K
The situation: You run a WooCommerce store at about $800K a year and want a rebuild. The site connects to: ● An ERP for stock and invoices, a 3PL for shipping, a subscription plugin and an email platform. ● Three agencies quoted $30K, $58K and $95K for “the same” project. ● The lowest quote didn’t mention the ERP, and the highest assumed a full custom build. ● You’ve spent two months collecting quotes, and peak season is four months away. The fix: A consulting engagement to map the integrations before asking for new quotes. ● Integration map: the ERP owns stock, WooCommerce owns orders, and the 3PL only receives orders and returns tracking. ● Plugins versus custom code: supported connectors for the 3PL and email, with custom work limited to the ERP sync. ● Phasing: checkout and subscriptions in phase 1, reporting in phase 2. The outcome: New quotes on the same brief land within about $10K of each other, and you choose on fit and track record. The cheapest quote is no longer a guess. |
| Section recap
● A failed build, more than three integrations or a platform change are each a reason to book consulting. ● Small, well-scoped builds with a proven team can usually skip it. Next steps ● Answer the self-test for your next build. ● List every system your site connects to and which one owns each type of data. |
If the self-test says you need it, the next question is what it costs and whether it pays back.
Plan your next WordPress build before you commission it
We audit what you have, map your integrations and set the architecture, so the build that follows has a clear scope and fewer surprises.
What WordPress consulting services cost, and how to judge the return
| In short:
At US agency rates, pre-build consulting usually costs a few thousand dollars. Judge it against the build budget and the cost of building twice. ● Rates: US WordPress agencies charge about $100 to $149 an hour. ● Share of the build: about 4% to 9% on a $100K build, and up to 15% on a $20K one. ● Return: narrower quotes, salvaged work and no second rebuild. |
US WordPress development companies charge about $100 to $149 an hour, according to Clutch. Most pre-build consulting takes 10 to 60 hours. Here’s what that means for your build:
| Your next build | What to buy | Budget for consulting | Share of the build |
| $20K with a simple scope | A plan review, or skip it | $1,000 to $3,000 | 5% to 15% |
| $50K with several integrations | Architecture plan and vendor brief | $2,500 to $6,000 | 5% to 12% |
| $100K after a failed build or before a platform change | Audit, architecture and replatform plan | $4,000 to $9,000 | 4% to 9% |
What this tells you: the bigger and riskier the build, the smaller consulting is as a share of it. On a $100K build, under 10% of the budget buys a plan every vendor quotes against. On a simple $20K build, the same money is a big slice, so skip it unless one of the three signs applies.
These figures are our estimates from published hourly rates. Fixed prices vary by consultant and scope.
How to judge the return
The return comes from three places:
● Narrower quotes: vendors price a written scope, so you compare like for like.
● Salvaged work: an audit often shows which parts of the old build can stay.
● Avoided rework: shortcuts in a rushed build compound over time. Our post on how technical debt compounds on a $1M+ site shows how.
When consulting doesn’t help
Consulting can waste money too. Watch for these:
● No build experience at your scale: the plan reads well, but vendors can’t price it.
● Endless documents: weeks of reports with no decision about platform or architecture.
● Over-specified briefs: so much detail that good vendors can’t suggest a better approach.
● A plan steered toward the consultant’s own build: the brief quietly fits one vendor.
Take extra care when buying consulting: agree a fixed price for named deliverables, confirm you own every document, ask the consultant to say upfront whether they’ll bid on the build, and ask for a sample of a past brief or architecture plan.
| Section recap
● Pre-build consulting costs about $1,000 to $9,000 at US agency rates, depending on scope. ● It’s easiest to justify on builds of $40K and up, after a failed build, or before a platform change. Next steps ● Work out what 5% to 10% of your build budget would be. ● Ask any consultant for fixed deliverables, a fixed price and a sample. |
Whether you hire a consultant or write it yourself, the brief is the document every vendor will quote against. Here’s a template.
A vendor brief template you can hand to any vendor
| In short:
A good brief makes every vendor quote the same project, so you can compare price, approach and fit. ● Eight sections: context, what went wrong, stack, integrations, must-haves, exclusions, acceptance criteria, and budget and ownership. ● Measurable “done”: each must-have gets a test you can check at handover. ● Same brief, three vendors: ask each to quote line by line and say what they’d change. |
Fill in each section below. If a consultant writes it for you, check that every section is complete before it goes out.
| Section | What to write | Example line |
| 1. Business context | Revenue, sales channels, team size and why you’re building now | “$600K a year, WooCommerce and Amazon, two-person team” |
| 2. What went wrong last time | Missed dates, broken features and handover gaps | “Subscriptions failed to renew after the last update” |
| 3. Current stack | Platform, theme, key plugins, hosting and versions | “WooCommerce 10.x, custom theme, managed host” |
| 4. Integrations | Each system, which way data moves, how often and which system owns it | “ERP owns stock and syncs to WooCommerce every 15 minutes” |
| 5. Must-haves | Features tied to revenue, in priority order | “Subscriptions, one-page checkout, wholesale pricing” |
| 6. Out of scope | What this project won’t include | “No redesign of blog pages in phase 1” |
| 7. Acceptance criteria | How you’ll test “done” | “Checkout loads in under 3 seconds on mobile” |
| 8. Budget, timeline and ownership | Budget range, launch date, and who owns code, accounts and documentation | “$50K to $70K, live by March, all code in our repository” |
How to use it with vendors:
● Send the same brief to three vendors.
● Ask each to quote line by line against the must-haves and acceptance criteria.
● Ask what they’d change in the brief. A vendor who pushes back on a section has usually read it closely.
● Compare quotes on scope coverage first and price second.
Here’s what a finished brief changed for one store planning a platform move.
| Example: the $600K supplements store moving to WooCommerce
The situation: You sell supplements at about $600K a year, mostly on subscription, and want to move from Shopify to WooCommerce: ● About 1,800 active subscribers with saved cards, making up most of your monthly revenue. ● Most of your traffic comes from search, with product pages ranking for years. ● Your first agency’s proposal didn’t mention subscriptions or redirects. ● One bad migration could mean hundreds of declined renewals in the first billing cycle. The fix: Write the brief before asking anyone else to quote. ● Must-haves: active subscriptions and saved payment methods moved without asking customers to re-subscribe. ● Acceptance criteria: every old product URL redirects, and search traffic is tracked weekly for 8 weeks after launch. ● Ownership: all code in your own repository, with written handover notes. The outcome: Two of three vendors quote the subscription migration as a separate line, which shows you where the risk sits. You choose the vendor that planned for it and keep your subscriber base through the move. |
| Section recap
● A brief with eight sections lets three vendors quote the same project. ● Measurable acceptance criteria make the handover something you can check. Next steps ● Fill in sections 1 to 4 yourself this week. ● Send the finished brief to three vendors and compare line by line. |
A brief sets up the build. Someone still has to keep the site healthy after launch, or it slowly drifts back to where it started.
Keep your new build running the way it launched
We handle updates, monitoring and fixes for revenue-critical WordPress sites, so integrations and checkout keep working after the build team moves on.
Conclusion: check the plan before you pay for the build
After a failed build, it’s tempting to sign the next proposal fast to get it over with, or to put the rebuild off for another year. Neither fixes what went wrong the first time.
If your last build failed, your site connects to more than three systems, or you’re changing platforms, a few weeks of consulting costs a small share of the build and answers the questions that sank the last one.
If your next build is small, simple and in the hands of a team that already knows your site, skip it and put the money into the build.
Either way, write the brief. It’s the cheapest way to get comparable quotes and a handover you can check. If you’d like a second opinion on your plan, our WordPress development team can review it with you.
WordPress consultant FAQs
What does a WordPress consultant do?
A WordPress consultant reviews your current site, decides how the next build should be put together, and writes a scope vendors can quote against. They focus on plugins versus custom code, integrations, hosting and data. Some also build, but the consulting work itself produces documents and decisions.
How much do WordPress consulting services cost?
US WordPress agencies charge about $100 to $149 an hour, according to Clutch. A pre-build engagement of 10 to 60 hours costs roughly $1,000 to $9,000, depending on whether you need a plan review, an architecture and brief, or a full audit and replatform plan.
What’s the difference between a WordPress consultant and a developer?
A consultant decides what should be built and how. A developer builds it. On a $20K to $100K project with several integrations, separating the two lets someone check the plan before the code is written.
Should the consultant also build the site?
It can work well, since they already know the plan. Make sure you own the audit, architecture plan and brief, and that you could take them to another vendor. Ask the consultant upfront whether they’ll bid on the build.
| Further reading
● Headless WordPress Development: Signs Your Website Has Outgrown Standard WordPress: how to tell when standard WordPress is the limit before you plan a replatform. ● Fractional CTO or Another Developer? Know When to Choose: when you need ongoing technical direction and when another developer is enough. ● How Technical Debt Compounds on a $1M+ Site: how shortcuts in a rushed build turn into ongoing costs. |
