Running a WooCommerce agency in 2026 is a different business than running a Shopify Plus agency, even though the deliverable looks similar to a client. Woo is open source, plugin-heavy, hosting-dependent, and dominated by sub-$10M brands. The agencies that thrive on Woo do not compete with Shopify shops on enterprise polish; they compete on flexibility, ongoing maintenance margin, and total cost of ownership. This WooCommerce agency playbook covers how to price builds, structure maintenance retainers, position against Shopify, manage the plugin sprawl problem, and run unit economics that actually compound. If your shop is building Woo sites for $8K and hoping to "make it up on maintenance," this guide is for you.
Key Takeaways:
- Woo builds in 2026 typically land between $12K and $90K; the most profitable agencies push median project size above $30K through productization.
- Maintenance retainers are where Woo agencies earn margin; healthy shops carry 60 to 80 percent of revenue as recurring.
- Plugin-heavy builds carry hidden support cost that must be priced into the retainer, not absorbed.
- Woo wins on bespoke catalog logic, content-commerce overlap, and clients with strict licensing or data-residency requirements.
- The biggest profitability lever is hosting markup plus security retainer, not custom development.
Why WooCommerce Still Pays in 2026
Even after a decade of Shopify expansion, WooCommerce continues to power a meaningful share of online stores and remains the default for brands that already trust WordPress for content. According to recent BuiltWith ecommerce technology data, WooCommerce is consistently among the top three ecommerce platforms by site count globally. For agencies, the math is more interesting than the market-share story. A typical $30K Woo build paired with a $1.5K-per-month care plan can generate $48K of first-year revenue with sticky gross margins above 65 percent, because the same senior developer can support 12 to 20 care-plan clients in parallel. The same client on Shopify rarely returns to the agency once launched.
The trade-off is that Woo agencies live and die by operational discipline. Every plugin, every host, every cron job is a future support ticket, and the unit economics only work if the agency owns the entire delivery and operations stack rather than letting the client choose components piecewise.
Where Woo Actually Wins (and Where It Doesn't)
Use this filter on every inbound RFP. If two or more "Woo wins" apply, lean in. If two or more "Woo loses" apply, route the client elsewhere or productize a migration off Woo onto a SaaS platform.
| Scenario | Woo wins | Woo loses | |---|---|---| | $250K to $5M brand with content-heavy site | Yes | | | Subscription box with custom logic | Yes | | | B2B with complex pricing rules | Yes (with plugins) | | | Strict data residency or open-source mandate | Yes | | | $10M plus with global multi-currency | | Yes | | Brand wanting "set it and forget it" | | Yes | | Internal team has no WordPress experience | | Yes | | Plus headless requirement | | Lean Shopify or BigCommerce |
The single most consistent qualifier is whether the client is willing to pay a real monthly retainer. Woo without a retainer is a hosting incident waiting to happen.
Pricing the Woo Build
Most Woo agencies under-price their builds because they anchor on freelancer rates. The agencies that scale price against total cost of ownership, including the first 12 months of support. A reliable 2026 pricing structure:
| Tier | Project fee | Timeline | Best for | Plugin count | |---|---|---|---|---| | Starter | $12K to $25K | 4 to 8 weeks | $250K to $1M brands | 8 to 14 | | Standard | $25K to $55K | 8 to 14 weeks | $1M to $5M brands | 12 to 20 | | Custom | $55K to $90K plus | 12 to 22 weeks | $5M to $15M brands or complex B2B | 15 to 30 plus custom |
The most common mistake is the $8K build. At that price the agency is losing money on launch support alone. The cleanest fix is to publish a productized "launch sprint" at a single floor price (say, $14K) so the sales team never negotiates against itself. Pair every build with a mandatory 12-month care plan; if the client refuses, that is the strongest possible signal they will not be a profitable account.
For a step-by-step build of the SOW math, see our project pricing calculator and scope of work generator.
The Maintenance Retainer Is the Business
Almost everything profitable about a Woo practice happens in the retainer, not the build. The retainer is where you cover hosting, security, plugin updates, performance monitoring, and small dev requests. A workable three-tier care plan:
| Care plan tier | Monthly fee | Hours / scope | Best for | |---|---|---|---| | Essential | $750 to $1,500 | Hosting, backups, plugin/core updates, security monitoring, 1 to 2 hours dev | $250K to $1M brands | | Growth | $1,500 to $3,500 | Above + 4 to 8 hours dev, monthly performance report, quarterly CRO review | $1M to $5M brands | | Premium | $3,500 to $7,500 | Above + dedicated PM, 10 to 20 hours dev, monthly priority slot | $5M plus brands |
A few critical operating decisions:
- Bill annually wherever possible. Annual billing turns the retainer into deferred revenue and cuts churn 30 to 50 percent.
- Include hosting in the tier. Marking up managed WordPress hosting (Kinsta, WP Engine, Pressable, Pantheon) by 30 to 80 percent is standard and the client usually does not negotiate.
- Cap dev hours, do not bank them. Banked hours create end-of-year cliff scope. Use a "use it or lose it" monthly cap with overage billing.
- Include security as an SLA, not a deliverable. "We will patch critical vulnerabilities within 24 hours" sells better than "we will run weekly security scans."
A single senior developer should be able to support 12 to 20 Essential or Growth retainers in parallel. The margin on a $1,800 retainer with $300 of hosting cost and 5 hours of dev time is typically 65 to 75 percent.
Hosting and Security: The Hidden Profit Center
Hosting is where Woo agencies leak the most invisible money. Most shops let clients buy hosting directly from GoDaddy or a similar low-cost host, and then spend 3 to 6 hours per quarter dealing with downtime, slow pages, and migrations. A profitable Woo agency:
- Standardizes on one or two managed WordPress hosts (Kinsta, WP Engine, Pressable, Cloudways).
- Resells hosting at a 30 to 80 percent margin inside the care plan.
- Owns the DNS, the SSL, the CDN config, and the staging environments.
- Runs weekly automated backups with off-site retention.
- Patches WordPress core, plugins, and themes on a defined cadence with a visual regression check.
This is not glamorous work, but it is the single biggest reason some Woo agencies clear 25 percent EBITDA while others clear 6 percent. According to the Cloudways agency benchmark survey 2025, agencies that bundle hosting into care plans report 40 percent higher retention and 28 percent higher per-client revenue than agencies that do not.
Plugin Sprawl: The Tax on Every Build
Plugins are simultaneously WooCommerce's strength and its biggest cost driver. Every plugin is a potential security incident, a future compatibility break, and a support liability. Three operating rules contain the damage:
- Maintain a vetted plugin shortlist. Forty to sixty plugins your team knows cold. Anything off the list requires senior review and an SOW line item.
- Charge for "plugin discovery" as billable hours. If a client wants a plugin you have never used, scope the integration as a discrete task, not absorbed time.
- Audit the plugin stack at every renewal. Remove anything unused. Replace any unmaintained plugin (no commits in 12 months) before it becomes a vulnerability.
A reliable rule of thumb: every additional plugin beyond 15 adds roughly $80 to $150 of annual support cost per client. Price accordingly.
Woo vs. Shopify: How To Position
The most common Woo agency mistake is competing with Shopify agencies on the same RFPs. The platforms serve different buyers, and a clean positioning statement turns a comparison call into a qualification call.
| Dimension | WooCommerce wins | Shopify wins | |---|---|---| | Up-front cost | Lower | Higher | | Total cost of ownership (3 years) | Comparable | Comparable | | Customization flexibility | High | Medium | | Operational simplicity | Medium | High | | Speed to launch | 8 to 14 weeks | 6 to 12 weeks | | Multi-currency / multi-region | Plugin-dependent | Native (Plus) | | Content + commerce | Excellent | Limited without headless | | Required maintenance | High | Low |
The clearest qualifying question: "Will you have an in-house WordPress champion in 12 months?" If yes, Woo. If no, push them toward Shopify (and consider becoming both a Woo agency and a Shopify migration partner). Pretending Woo is a fit for a client who wants zero ops involvement is how agencies end up firefighting and unprofitable.
Team Structure for a Scaling Woo Practice
A workable 10-person Woo agency:
- 1 partner / commercial lead
- 1 head of delivery / senior PM
- 1 mid-level PM (running 12 to 18 care plans)
- 3 mid-level WordPress / Woo developers
- 1 senior full-stack lead (handles custom dev, plugin builds, integrations)
- 1 designer (theme, PDP, conversion)
- 1 QA / launch ops
- 1 strategy / CRO lead (could be part-time)
This shape supports roughly $1.6M to $2.2M in revenue at 55 to 65 percent gross margin with a retainer-heavy mix. The most common scaling mistake is hiring a fourth developer before hiring a senior PM; the bottleneck on a Woo agency is almost always account management, not code. To get the ratios right, anchor staffing to a team utilization calculator and run quarterly capacity reviews.
Profitability Benchmarks
| Metric | Healthy range | Warning sign | |---|---|---| | Project gross margin | 40 to 55 percent | Below 30 percent | | Care plan gross margin | 60 to 75 percent | Below 45 percent | | Care plan share of revenue | 55 to 75 percent | Below 35 percent | | Average care plan per client | $1,800 to $3,500 per month | Below $1,000 | | Annual revenue per FTE | $150K to $220K | Below $110K | | Care plan churn | Below 12 percent | Above 25 percent | | Hosting markup share of revenue | 8 to 15 percent | 0 percent |
The single most important number on this list is care-plan share of revenue. Below 35 percent and the agency is effectively a project shop with a Woo specialization. Above 55 percent and the business becomes resilient to dry months in new business.
Productized Service Lines That Sell on Woo
Six offerings that consistently sell and run profitably:
- Woo Launch Sprint ($14K to $22K, 4 to 6 weeks): Default theme, vetted plugin stack, basic integration, training.
- Subscription Box Build ($25K to $45K): WooCommerce Subscriptions + custom logic + Klaviyo flows.
- Speed and Core Web Vitals Sprint ($6K to $14K): LCP, INP, CLS focus, image and database optimization.
- Plugin Audit + Rebuild ($8K to $20K): Cull plugin stack, replace unmaintained plugins, document the new stack.
- B2B Configuration ($15K to $30K): Role-based pricing, wholesale registration, quotes.
- WordPress to Shopify Migration ($25K to $70K): Productize this even if you are a Woo shop. The brands that should not be on Woo are easier to make happy on Shopify, and Woo agencies that also offer the off-ramp earn better referrals.
Productizing these offers is the single highest-leverage move for a Woo agency, and it pairs naturally with the productized service software most maturing shops adopt by their fifth year.
Anonymized Scenario: A 6-Person Woo Agency in Austin
A six-person Woo agency we have benchmarked grew from $480K to $1.3M in revenue between 2023 and 2025 by making three operational changes:
- Killed all custom-quoted maintenance plans. Replaced with three published care-plan SKUs at $1,250, $2,500, and $4,500 per month. Within nine months, 78 percent of clients had upgraded into one of the three tiers.
- Standardized on Kinsta with a 60 percent markup baked into the retainer. Added approximately $42K of annual gross profit with zero additional delivery hours.
- Built a vetted shortlist of 47 plugins and refused any build that required more than three off-list plugins without a $4K plugin-vetting SOW addendum.
Their P&L outcome: retainer share moved from 28 percent to 64 percent, EBITDA went from 11 percent to 24 percent, and care-plan churn dropped from 22 percent to 9 percent. The owner reported that the most consequential change was psychological, not financial; the team stopped saying yes to every plugin request.
Tooling and Operations Stack
A workable 2026 stack for a Woo agency:
- Local + staging: Local by Flywheel, WP Engine staging, Pressable previews.
- Deployment: WP Pusher, DeployHQ, or a manual Git-to-staging-to-prod flow with regression testing.
- Monitoring: Better Stack or Pingdom for uptime, New Relic for performance, ManageWP or MainWP for fleet management.
- Security: Wordfence Premium plus a host-level WAF, plus a documented incident-response runbook.
- Agency ops: Time tracking, retainer billing, and capacity planning bound together in an agency management platform so a sales hand-off does not blow utilization. Recurring billing is mandatory the moment you have more than ten care-plan clients.
- Client comms: A shared client portal so requests do not live in email.
The single biggest tooling mistake is running ten clients across five different hosting providers. Standardize.
When To Walk Away from a Woo RFP
A short list of disqualifiers worth printing on the office wall:
- The client wants the cheapest possible build and refuses a maintenance plan.
- The brand needs multi-region, multi-currency, and the client says "let's see if Woo can do it."
- The internal team is two non-technical founders with no WordPress experience.
- The client insists on bringing their own hosting (especially shared hosting).
- The plugin list includes more than five obscure or unmaintained tools.
- The brand is doing $15M plus and wants enterprise polish; this is a Shopify Plus or BigCommerce client.
Saying no to the wrong client is a profit lever, especially in a Woo practice where the per-client margin is lower than on Shopify. Most Woo agencies could lift EBITDA five to seven percentage points by declining the bottom 15 percent of their pipeline.
FAQ
How long should a typical WooCommerce build take?
A standard build for a $1M to $5M brand runs 8 to 14 weeks from kickoff to launch, plus a two-to-three-week stabilization window. Subscription-heavy or custom-B2B builds can extend to 18 to 22 weeks. Anything quoted under six weeks is either a re-skin or a future support nightmare.
What gross margin should a Woo agency target?
A healthy blended gross margin is 55 to 65 percent across projects and retainers. Care plans should clear 65 percent gross margin once hosting markup is included. Project gross margin in the 40 to 50 percent range is normal because of the higher proportion of customization work.
How many care plans can one developer manage?
A senior WordPress developer working alongside a junior pair can typically support 12 to 20 Essential or Growth care plans. Premium retainers above $5K per month are closer to one-to-five because of the dedicated dev hours. The first capacity choke point is usually account management, not engineering.
Should we resell hosting?
Yes. Bundling managed WordPress hosting into the care plan with a 30 to 80 percent markup is standard practice and adds 8 to 15 percent of revenue with minimal operational burden. Just standardize on one or two hosts.
How do we compete with Shopify agencies?
Stop pitching against them on enterprise polish, multi-region, or speed of launch; you will lose. Win on flexibility, content-commerce overlap, total cost of ownership, and bespoke catalog logic. Make sure your pipeline filters for clients who genuinely want WordPress.
Closing
A profitable WooCommerce agency in 2026 is a hosting-and-retainer business that happens to do website builds. Productize the build, standardize the host, vet the plugin stack, and the unit economics take care of themselves. Everything else is operational discipline.
If you want to see how AgencyPro helps Woo agencies manage retainers, hosting markups, and per-client profitability in one place, book a demo and we will walk you through the numbers that move first.