WooCommerce agency playbook: Builds, care plans, margins

A WooCommerce agency builds, maintains and improves online stores that run on WooCommerce, the open-source ecommerce plugin for WordPress owned by Automattic. The build is the visible part of the work, but the business is the care plan that follows it, because every Woo store is self-hosted and depends on WordPress core, a theme and a stack of plugins that all need updates, testing and security patches.

This playbook is for agency owners who build on Woo or are thinking about it. It covers how to price builds and care plans, where Woo is the right platform and where it is not, the maintenance problems specific to WooCommerce, and the numbers worth tracking. Prices and margins below are worked examples to plan with, not market benchmarks; check them against your own costs and rates.

Key takeaways

• Sell every build with a care plan. A Woo store without maintenance becomes a security and compatibility problem within months.
• Plugins are where both the flexibility and the risk sit. Patchstack's 2026 report found 91% of new WordPress vulnerabilities in 2025 were in plugins.
• Standardize on one or two managed hosts and a vetted plugin list. Most support hours come from exceptions.
• Woo-specific work (order data on staging, HPOS compatibility, the block Checkout, extension licenses) belongs in your scope and your pricing.
• Recommend Shopify when the client has no one to own WordPress and does not want to pay for ongoing maintenance.

What makes WooCommerce agency work different

A Shopify build ends with a store running on Shopify's infrastructure. A WooCommerce build ends with a store your agency, or someone, has to keep running. That changes the business model in four ways:

1. Hosting is part of the job. Woo runs on whatever server the client pays for. Page speed, uptime, backups and staging all depend on the host.
2. The plugin stack is the product. Payment gateways, shipping, tax, subscriptions, search and marketing integrations are usually separate plugins from separate vendors, each with its own update schedule.
3. Security is continuous. Patchstack's State of WordPress Security in 2026 counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025 (up 42% on 2024), 91% of them in plugins. It also reports that 46% were not fixed by the developer in time for public disclosure.
4. Live stores change every minute. Orders, customers and stock levels are written to the database constantly, which makes "build on staging, push to live" riskier than on a brochure site.

Agencies that do well on Woo treat these four points as billable work, not as favors.

Where WooCommerce wins and where it doesn't

Use this as a qualification filter on every inbound lead. If two or more items in the "Woo fits" column apply, it is a good fit. If two or more in the "consider Shopify" column apply, recommend another platform or offer a migration.

The most reliable single question: "Who will own this site in 12 months?" If the answer is your agency on a care plan, or an in-house WordPress person, Woo works. If the answer is nobody, it will not.

Pricing the build

Price against the full first year, not just the build hours. A build priced at freelancer rates with "we'll make it up on maintenance" usually loses money on launch support alone.

Example build tiers (illustrative; adjust to your rates and region):

Two habits keep build pricing healthy:

• Publish a floor price for your smallest offer so sales never negotiates below what launch support costs you.
• Make a 12-month care plan part of the proposal, not an optional extra. A client who refuses any maintenance is telling you who will be blamed when an update breaks checkout.

To build the numbers line by line, use the project pricing calculator and the scope of work generator.

The care plan is the business

Most of the profit in a Woo practice comes from the monthly care plan: hosting, backups, updates, monitoring, security and a small amount of development each month. In The Admin Bar's State of the WordPress Agency 2026 survey of 622 agency owners and freelancers, 58.3% of those with no recurring revenue (care plans, hosting or retainers) were rarely or never profitable, compared with 9.7% of those earning 25-49% of revenue from recurring work, 4.5% at 50-74% and 6.2% at 75% or more.

Example care plan tiers (illustrative):

Worked example: care plan margin

For example, take a $1,800/month Growth plan with $300/month in hosting and tooling costs and 5 hours of developer time at a loaded cost of $60/hour:

• Delivery cost: $300 + (5 x $60) = $600
• Gross profit: $1,800 - $600 = $1,200
• Gross margin: $1,200 / $1,800 = 67%

If the same client quietly uses 12 hours a month because there is no cap, delivery cost rises to $1,020 and margin drops to 43%. That is why the next rules matter.

Operating rules for care plans

1. Cap development hours each month. Use a monthly allowance with overage billed at your hourly rate. Banked hours that roll over pile up into large, unplanned work at the end of the year.
2. Write security as a response time, not a task list. "We patch critical plugin vulnerabilities within one business day of a fix being released" is clearer to a client than "weekly security scans."
3. Put the WordPress maintenance terms in the contract. Update cadence, what counts as an emergency, what is out of scope. A WordPress maintenance contract template is a good starting point.
4. Offer annual billing. It improves cash flow and gives you a natural renewal date to review scope and price.

Woo-specific maintenance work to scope and price

These are the jobs that catch agencies out because they do not exist, or are much smaller, on SaaS platforms.

Staging and live order data

On a Woo store, orders, customers and stock are stored in the WordPress database. If you copy a staging database over production after a redesign, you overwrite every order placed since the staging copy was made. Decide the deployment method before the build starts: push code and files only, or use a host or tool that supports selective database merges, and schedule a short code freeze for risky changes.

HPOS compatibility

High-Performance Order Storage (HPOS) moves orders out of the WordPress posts tables into dedicated order tables. According to the WooCommerce developer docs, it has been enabled by default for new stores since WooCommerce 8.2 (October 2023), and the HPOS setting is disabled if an active plugin is not compatible. Older stores you inherit may still be on legacy storage. Check plugin compatibility before you switch, and treat the migration as a scoped project, not a routine update.

Block-based cart and checkout

Since WooCommerce 8.3 (November 2023), new stores get the block-based Cart and Checkout by default. Some extensions that add checkout fields or payment options do not support the blocks yet; WooCommerce shows a warning and lets you switch back to the classic checkout (WooCommerce docs). Test the full checkout after every plugin update, with each payment method the store accepts.

Extension licenses and renewals

Paid extensions from the Woo Marketplace are sold as annual or biennial subscriptions that cover updates and support (WooCommerce.com). Third-party plugins work the same way. Decide up front who owns each license (agency or client), who pays for renewals, and how renewal costs are passed through. An expired license usually means no updates, which means unpatched vulnerabilities.

Scheduled tasks

Subscriptions renewals, scheduled sales and many plugin jobs run through WordPress scheduled tasks, which by default fire when someone visits the site. On low-traffic stores, set up a real server cron job so renewals and emails run on time.

Hosting and security

Hosting decisions drive a large share of support time. A care-plan agency should:

• Standardize on one or two managed WordPress hosts (for example Kinsta, WP Engine, Pressable, Pantheon or Cloudways) so the team knows the tooling.
• Decide whether to resell hosting inside the care plan or have the client pay the host directly. Reselling gives you control and margin; client-paid hosting reduces your liability if the host fails. Either way, require hosting you have approved.
• Own DNS, SSL, CDN configuration and staging environments, or document exactly who does.
• Keep daily backups with off-site copies, and test a restore at least once a quarter.
• Update WordPress core, the theme and plugins on a fixed schedule, with a visual check of key templates and a test order after each update.

Patchstack's report also found that heavily targeted vulnerabilities reached mass exploitation in a median of about five hours. A monthly update cycle is fine for routine updates, but your contract should allow emergency patching outside it.

Plugin sprawl: the hidden cost of every build

Plugins are why Woo can do almost anything, and why it is expensive to maintain. Three rules contain the cost:

1. Keep a vetted plugin list. A short list of plugins your team knows well for payments, shipping, tax, SEO, forms, caching and security. Anything off the list needs senior review and its own line in the SOW.
2. Bill plugin evaluation as work. If a client wants a plugin you have never used, scope the research and integration as a task.
3. Audit the stack at every renewal. Remove anything unused and replace plugins that have not been updated in the last year or that have open, unpatched vulnerabilities.

Positioning against Shopify agencies

Woo and Shopify serve different buyers, so do not pitch against Shopify on its strengths. Position on what Woo does well:

Offer both directions. A Woo agency that also runs WooCommerce-to-Shopify migrations for clients who should not be on Woo earns trust and referrals rather than losing those clients to another agency. For the other side of the market, see our Shopify Plus agency guide.

Team structure for a growing Woo practice

An example shape for a 10-person Woo agency:

• 1 owner or commercial lead
• 1 head of delivery or senior project manager
• 1 account or project manager running the care-plan clients
• 3 WordPress and WooCommerce developers
• 1 senior full-stack developer for custom plugins and integrations
• 1 designer (theme, product pages, conversion)
• 1 QA and launch specialist
• 1 strategy or conversion lead (can be part-time)

A common scaling mistake is hiring another developer before a project manager. On a care-plan-heavy agency, the first bottleneck is usually client communication and scheduling, not code. Track it with the utilization rate calculator and a quarterly capacity review.

Numbers to track

Set your own targets and review them monthly. The ranges below are planning examples, not published industry benchmarks:

Care-plan share of revenue is the number that tells you whether you run a recurring business or a project shop with a WooCommerce specialty. Tracking profitability per client tells you which care plans are underpriced.

Productized services that sell on Woo

Fixed-scope offers are easier to sell and deliver than custom quotes. Examples (prices illustrative):

1. Woo launch sprint ($14,000 to $22,000, 4-6 weeks): theme, vetted plugin stack, payments, shipping, training.
2. Subscription store build ($25,000 to $45,000): WooCommerce Subscriptions, renewal emails, customer account flows, email platform integration.
3. Speed and Core Web Vitals sprint ($6,000 to $14,000): LCP, INP and CLS work, image and database optimization, caching.
4. Plugin audit and cleanup ($8,000 to $20,000): remove and replace plugins, document the stack, fix compatibility issues.
5. HPOS and block checkout upgrade (scoped per store): compatibility audit, plugin replacements, migration and checkout testing.
6. B2B configuration ($15,000 to $30,000): role-based pricing, wholesale registration, quotes.
7. WooCommerce to Shopify migration (scoped per store): for clients who should not be on Woo.

Software for selling fixed packages is covered in our roundup of productized service software.

The Woo agency programs worth knowing

Automattic runs an agency program covering WooCommerce and its other WordPress products. The Woo + Automattic for Agencies page lists special agency pricing, a referral program, partner directory listings across Automattic brands, a dashboard to manage client sites, and priority support; it does not publish discount or referral percentages. Separately, the Woo Agency Partners directory lists agencies that WooCommerce has vetted. Both are worth applying to once you have a portfolio of live Woo stores.

Tooling for a Woo agency

• Local and staging: Local (by WP Engine), plus your host's staging environments.
• Deployment: Git-based deploys (for example DeployHQ or WP Pusher), with a rule that the production database is never overwritten.
• Fleet management and monitoring: ManageWP or MainWP for updates across sites, an uptime monitor such as Better Stack or Pingdom, and performance monitoring such as New Relic where the host supports it.
• Security: a security plugin such as Wordfence, a host-level firewall, and a written incident-response runbook.
• Agency operations: a system for care-plan requests, time tracking against each plan, recurring invoices and client communication, so requests do not live in email. See our guide to agency management software.

When to walk away from a Woo project

• The client wants the cheapest possible build and refuses any maintenance plan.
• The store must sell in many countries and currencies at launch, and the client asks "can Woo do it?"
• No one on the client side, and no budget for your agency, will own the site after launch.
• The client insists on their own budget shared hosting.
• The requirements depend on several obscure or unmaintained plugins.

Turning down the wrong client protects your margin. On a care-plan business, one badly qualified client can absorb the support hours of three good ones.

Running a Woo care-plan business in AgencyPro

AgencyPro handles the client-facing and billing side of a care-plan practice: a branded client portal where clients submit requests and see status, project management, file sharing, messaging and invoicing on every plan. The Pro plan adds time tracking against each client, hourly and credit-based services for monthly dev allowances, tickets, SLA tracking for response-time commitments, and recurring requests that create monthly maintenance tasks on schedule. The Plus plan adds profitability reports by client.

Pricing is per plan plus seats. A 10-person team on Pro pays $79 + 9 x $20 = $259 per month; on Plus, $149 + 9 x $30 = $419 per month. Clients are unlimited on every plan. See pricing.

AgencyPro is not a WordPress management tool. It does not run plugin updates, backups or uptime checks on client sites, so you still need ManageWP, MainWP or your host's tools for that. If your care plans are mostly automated updates with very few client requests, a fleet tool plus your accounting software may be enough.

FAQ

How long does a WooCommerce build take?

As a planning range, a standard store with a custom design and a few integrations takes 8-14 weeks from kickoff to launch, plus two to three weeks of post-launch stabilization. Subscription-heavy or custom B2B builds can run 18-22 weeks. A quote under six weeks is usually a reskin of an existing store or a theme-based launch.

What should a WooCommerce care plan include?

At minimum: hosting (resold or approved), daily backups with off-site copies, scheduled core, theme and plugin updates with a test order afterwards, uptime and security monitoring, an emergency patching commitment and a capped number of development hours with overage billing.

Should a Woo agency resell hosting?

It depends on how much control you want. Reselling managed WordPress hosting inside the care plan lets you standardize, control staging and backups, and add margin. Having the client pay the host directly reduces your exposure if the host has an outage. Either way, only support hosts you have approved.

How many care plans can one developer support?

It depends on how many dev hours each plan includes and how standardized your stack is. Work it out from hours: if a developer has about 120 billable hours a month and your Growth plan averages 6 hours of dev work, that is roughly 15-20 plans after time for updates, emergencies and internal work. Premium plans with 10-20 hours each need far fewer per developer.

Is WooCommerce or Shopify better for agency clients?

Neither is better for every client. WooCommerce suits clients who need custom logic, want to own their code and data, or already run on WordPress, and who will pay for maintenance. Shopify suits clients who want the platform to handle hosting, updates and security and are fine working within its app ecosystem.

If you want to see how a care-plan agency runs requests, time and invoices in one client portal, book a demo.