The Automation Stack We Deploy on Every Client Build
WordPress automation for agencies stops being a nice-to-have the moment you manage more than ten client sites. At that scale, manual follow-up on form leads, one-off welcome emails, and ad hoc user role assignments cost you roughly 8 to 12 hours a month in unbillable labour. We standardise the same core automation stack on every client build using Krom Automation, export each workflow as JSON, and import it on the next site in under two minutes.
This is not a list of ideas. It is the actual stack we deploy, the workflows that pay for themselves, and an honest account of where automation creates risk as well as reward. If you are evaluating whether to standardise a tool across your agency or sell automation as a care-plan add-on, read this first.
For a broader look at the automation landscape, the WordPress Automation Glossary is worth bookmarking before you get into tool comparisons.
Browse the full Krom Automation feature listWhy the Tool Choice Matters More for Agencies Than for Single Sites
A single-site owner picks the tool that solves their immediate problem. An agency picks a tool that survives 50 client environments, stays maintainable when a developer leaves, and produces no per-execution billing surprises at month end. Those are fundamentally different criteria.
External platforms like Zapier and Make are good tools. They become expensive and fragile at agency scale for three reasons: billing multiplies per client account, workflow data lives outside the client’s WordPress installation, and you own the integration glue rather than the client.
If you offboard, the automations break. We have seen agencies inherit sites where the automation layer depended on a personal Zapier account that was cancelled two years earlier.
If your automation layer breaks the moment someone cancels a subscription they forgot they owned, you did not build a system. You built a liability.
A self-hosted, WordPress-native tool means the workflow data, execution logs and API credentials stay in the client’s own database. The client owns their automation history.
You can hand off the site without unravelling a web of external accounts. That is the argument for native tooling, and it is a straightforward one to make to a client who has been burned before.
The Six Workflows We Deploy on Every Build
These are the automations that appear in every client proposal. They are ordered by impact. Work through them in this sequence because the first three eliminate the most manual labour, and skipping ahead to number five before number two is configured wastes time on a client site that still has unaddressed gaps.
1. New User Welcome Sequence
Every site that accepts registrations needs a welcome email. Without automation, this either does not happen or it happens via a plugin that sends a generic WordPress default. A proper welcome sequence, triggered on User Registered, sends a branded email with the user’s name injected via merge tags and optionally assigns a role or tags the user in a CRM like FluentCRM or ActiveCampaign.
This is the first workflow we build on every site because it is also the demonstration workflow we show clients. The first workflow walkthrough in the documentation covers the exact setup steps.
2. Form Lead Routing and Follow-Up
Forms generate leads. Leads sit in an inbox. Nothing happens.
This is the most common failure mode we see on inherited sites, and it is entirely preventable. A form submission trigger connects to an email action, a CRM contact creation, and optionally a Slack notification so the account manager knows within 30 seconds that a lead arrived.
The specific setup depends on which form plugin the client uses. We have documented this for Gravity Forms, Contact Form 7, WPForms, and Fluent Forms.
The automation shape is identical across all four. Only the trigger node changes.
3. Post-Purchase Email and CRM Sync
For WooCommerce clients, the Order Completed trigger fires a confirmation email, tags the customer in the email marketing platform, and optionally enrols them in a post-purchase sequence. Without this, the client’s marketing list and their actual customer list drift apart inside three months. The Mailchimp integration and FluentCRM integration both handle the subscriber sync side of this.
4. Content Distribution on Publish
Post Published fires when a new article goes live. The workflow posts a summary to the client’s LinkedIn page, sends the URL to a Google Sheet for the content team’s tracking spreadsheet, and triggers a notification in a Slack channel.
The client stops manually announcing their own content. The social media integration documentation covers the exact node configuration.
5. Internal Alert on Failed Payments or Subscription Changes
For membership and subscription clients, a lapsed payment is a churn event. Without an alert, it stays invisible until someone checks the dashboard.
A subscription status trigger fires a Slack or email notification to the account manager, giving the client a window to act before the customer churns. The WooCommerce Subscriptions integration and MemberPress integration both support status change triggers.
6. Client-Facing Report Generation
This one is less about the WordPress site and more about your care plan. A scheduled trigger running on the first of each month can pull execution data from Krom Automation’s analytics dashboard and push a summary to a Google Sheet, which becomes the basis for a monthly report. We have written about this pattern in more detail in automated WordPress reports without logging in daily.
What the Standard Stack Costs to Run
Cost at agency scale is almost never what the pricing page shows. It is what the pricing page shows multiplied by client count, plus the maintenance overhead nobody quotes you.
| Scenario | External platform (per client account) | Krom Automation Pro (self-hosted) |
|---|---|---|
| 10 client sites | $490 to $990/year across accounts | $369/year, unlimited sites (Enterprise plan) |
| 30 client sites | $1,470 to $2,970/year | $369/year, same plan |
| 50 client sites | $2,450 to $4,950/year | $369/year, same plan |
| Per-execution billing risk | Yes, spikes on high-traffic months | None, no run caps at any tier |
| Workflow data ownership | External platform, not client’s server | Client’s own database |
| Offboarding risk | Automations break if account closes | Zero, plugin stays active on site |
The external platform estimates above are conservative. They assume basic task volumes. Any client site with a WooCommerce store running a promotion or a membership site onboarding a cohort will push those figures higher in the same month.
Krom Automation Pro’s Enterprise licence is $369 per year or $799 as a lifetime purchase for unlimited sites. There is no per-task billing at any tier. The free version, available on the WordPress.org plugin directory, includes 16 triggers, 21 actions and 20 ready-made workflow templates with no run caps and no expiry.
At 30 client sites, a self-hosted automation tool running at $369 per year costs less than one month of a mid-tier external platform subscription. The maths is not close.
JSON Export and Repeatable Deployment
The feature that makes Krom Automation practical for agencies is workflow import and export as portable JSON. You build the welcome email workflow once on one client site, export it, and import it on the next site in under two minutes.
The workflow structure transfers completely. You adjust the sender name and any client-specific field values, then activate.
This matters because the alternative is rebuilding the same workflow from scratch on every new site, which takes 20 to 45 minutes per workflow depending on complexity. Across six standard workflows and 20 new client builds per year, that is 40 to 90 hours of setup time that disappears with an import workflow. At a $120 hourly rate, that is $4,800 to $10,800 recovered per year, or billed as setup fees rather than absorbed as overhead.
The workflow settings documentation covers the exact import and export process, including how to handle merge tags that reference client-specific values.
Building Your Agency Workflow Library
We maintain a folder of exported JSON files, one per workflow template. The folder is organised by site type: WooCommerce, membership, LMS, lead generation. When a new build starts, we import the relevant set and spend the first session on client-specific configuration rather than structural setup.
- WooCommerce set: order confirmation, post-purchase CRM sync, failed payment alert, cart recovery follow-up
- Membership set: registration welcome, subscription renewal reminder, lapsed payment alert, role change notification
- LMS set: course enrolment confirmation, completion certificate trigger, quiz failure follow-up
- Lead generation set: form submission routing, follow-up sequence, CRM contact creation, internal Slack alert
Each set is a ZIP of four to six JSON files. Import takes less time than explaining to a client what automation is.
Automation as a Billable Service
There are two ways to recover the cost of your automation infrastructure. The first is treating it as overhead that makes your team faster. The second is charging for it directly.
The second model is more durable. Automation setup and ongoing management is a service clients understand because they can see what it does.
A client who receives a monthly report showing 340 automated executions and a 98.2% success rate in the past 30 days has evidence that their care plan is working. That is a retention argument and an upsell argument in the same number.
| Service tier | What is included | Suggested price range | Krom Automation cost per site |
|---|---|---|---|
| Basic care plan | 6 standard workflows, monthly report | $150 to $250/month | $0.62/month (Enterprise annual) |
| Growth care plan | 12 workflows including integrations, quarterly review | $350 to $600/month | $0.62/month |
| Automation setup fee | Initial build, configuration, testing | $500 to $1,500 one-time | 30 to 90 minutes of time |
| Custom workflow build | Bespoke automation outside the standard set | $200 to $500 per workflow | 1 to 3 hours of time |
The Krom Automation cost per site figure above assumes the Enterprise annual licence ($369/year, unlimited sites) divided across 50 active client sites. At 30 sites the per-site cost is $1.03/month.
At 10 sites it is $3.08/month. Even at 10 sites, a basic care plan priced at $150/month covers the tool cost inside three days of the billing cycle.
What the Analytics Dashboard Tells You (and Why It Matters for Clients)
Krom Automation’s analytics dashboard shows total executions, active workflow count, estimated time saved, failed execution count and an execution trend chart. The reports page adds date range filtering, per-workflow success rate and CSV export.
That last one is the client-facing deliverable. Export the month’s execution data, drop it into a report template, and you have a concrete answer to the question every client eventually asks: “What am I actually paying for?” A 98% success rate across 400 executions is a better answer than “we handle your maintenance.”
Failures matter as much as successes. A workflow failing 15% of the time looks identical to a working one from the outside until you check the execution log. Per-step audit trails mean you can identify whether a failure happened at the trigger, a conditional branch, or a specific action node, and fix it without guessing.
Most competing tools put per-step logging behind a paid tier. In Krom Automation it is included in the free version.
A monthly report showing 400 automated executions at 98% success is a better retention argument than any care plan pitch deck you will ever write.
Where Automation Creates Risk and How to Manage It
Honest account of the failure modes, because every tool has them and you will encounter all of these if you manage 50 sites.
Delay Reliability on Low-Traffic Sites
Delays in Krom Automation run via Action Scheduler, which piggybacks on WordPress Cron. On sites with very low traffic, WP-Cron fires late if nothing visits the site for hours.
A delay set to 30 minutes can become a delay of 4 hours on a low-traffic client site. The fix is configuring a real server cron job on those sites, which takes under five minutes but needs to be part of your setup checklist.
Auto-Update Risk on Complex Sites
Plugin auto-updates and automation are not the same risk category, but they intersect. If a client site has a complex WooCommerce setup and you trigger a workflow on Order Completed, a plugin update that changes the order object structure can break downstream actions.
We stage every update on a test environment before pushing to production on sites with active automation. This is not an automation-specific risk, but automation makes the consequences of a breaking update more visible and more immediate.
AI Actions Require API Key Management
Krom Automation’s AI actions (text generation, content moderation, auto-tagging) require the user to supply their own API key. wpRigel does not charge per AI call and does not mark up tokens.
The client pays their AI provider directly. For agencies, this means managing API keys per client rather than centrally, which is the right ownership model but adds a setup step to the onboarding checklist.
The Incoming Webhook Dependency
Pro’s incoming webhook receiver gives each workflow a unique secret URL with HMAC-SHA256 signature validation. This makes it possible to receive data from external services, payment processors, booking platforms, anything that can send a POST request.
The risk is that if you rotate the secret or change the workflow, you need to update the sending service. Document these connections explicitly in the client handoff notes.
The Workflows We Do Not Standardise
Not everything belongs in the standard stack. These are the categories we handle as custom builds rather than templates, because they require client-specific logic that cannot be generalised cleanly.
- Billing and churn alerts tied to external payment data: anything that pulls from a payment processor API rather than WooCommerce or MemberPress needs bespoke configuration per client
- Multi-step lead scoring: assigning points based on behaviour across multiple triggers is workflow logic that differs by industry and sales process
- LMS completion and certificate workflows: LearnDash and TutorLMS both support completion triggers, but the actions after completion, grade thresholds, group assignments, certificate delivery, vary enough that templating produces workflows that need heavy editing anyway
- Affiliate program automation: AffiliateWP triggers on registration, referral and payout events, but commission structures differ too much to standardise the action side
Comparing Tool Categories, Not Just Tools
The question we get most from other agency owners is whether to use a WordPress-native automation plugin or an external platform. Here is the honest comparison by decision factor, not by feature count.
| Decision factor | WordPress-native (Krom Automation) | External platform (Zapier/Make) |
|---|---|---|
| Data ownership | Client’s database, always | External servers, third-party terms |
| Billing model | Annual or lifetime per licence | Monthly, per task or per connection |
| Cost at 50 sites | $369/year flat | $2,450 to $4,950+/year |
| Works without internet | Yes, runs inside WordPress | No, requires external service availability |
| WordPress event depth | Deep, 16+ native triggers free, 80+ Pro | Shallow, depends on plugin’s Zapier integration |
| Client handoff | Clean, plugin stays with site | Requires account migration or rebuild |
| External service connections | 24 Pro integrations, webhook receiver | Thousands of app connectors |
External platforms win on breadth of third-party connectors. If the automation you need connects two external services with no WordPress involvement, a native plugin is not the right tool. But if the trigger or the action touches WordPress, a self-hosted tool is faster to configure, cheaper to run across multiple sites, and safer to hand off.
For the six standard workflows above, every trigger and every action involves WordPress. The choice is straightforward.
For a detailed comparison of the available options in this category, the agency-focused automation tool roundup covers the full landscape.
Also from wpRigel
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the dashboard to search posts, manage WooCommerce orders, switch plugins, or jump to any settings screen without clicking through menus. It is the only command palette with real WooCommerce order, product and customer commands built in, which makes it worth deploying on any client site where the owner manages their own store.
Pollify is a Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as native blocks, so there are no shortcodes to paste and no separate interface to switch to. If you manage content-heavy client sites or community sites, it is a straightforward add to the standard plugin set.
Our Verdict: Who Should Build This Stack and Who Should Not
If you manage more than ten client sites and you are still handling welcome emails, lead routing and post-publish distribution manually or with a patchwork of single-purpose plugins, the stack described here will recover that time within the first billing month. The JSON export and import workflow alone saves 40 to 90 hours per year on new client builds. The Enterprise licence at $369/year costs less than one billable hour at most agency rates.
If you manage fewer than five sites and your clients have simple, low-volume needs, the free version on the WordPress.org plugin directory covers the six standard workflows with no cost and no time limit. Start there.
Who should not build this stack: agencies whose automation needs are primarily between external services with no WordPress involvement. If the client’s critical automations run Salesforce to Slack to HubSpot with no WordPress trigger or action, a WordPress-native tool is the wrong layer. Use the right tool for the job.
For everyone else, standardise the stack, build the JSON library, and start charging for it. The margin is there.
See full pricing details for Krom AutomationFrequently Asked Questions
Can I use one Krom Automation Pro licence across all my client sites?
Yes. The Enterprise plan covers unlimited sites at $369 per year or $799 as a lifetime purchase.
Every Pro feature is included at every plan level. The only difference between plans is the number of site activations.
Does Krom Automation work without a WooCommerce installation?
Yes. WooCommerce is optional.
The WooCommerce-specific triggers and actions only appear if WooCommerce is active. The core triggers covering users, posts, comments and media work on any WordPress site running version 6.2 or higher.
What happens to client automations if I offboard?
Nothing breaks. The plugin and all workflow data live on the client’s server. Automations continue running as long as the plugin is active, with no dependency on your account or any external service you control.
Can I automate client onboarding, from contract signing to site setup?
Partially, using the incoming webhook receiver in Pro. When a contract is signed in a platform that can send a webhook, Krom Automation receives that payload and can trigger user creation, role assignment, and welcome email sequences on the WordPress side. The steps outside WordPress, such as project management task creation or invoice generation, require the external platform to fire additional webhooks to those services separately.
Is the workflow simulator safe to use on live client sites?
Yes. The simulator runs a dry-run pass through the entire workflow with zero side effects.
No emails are sent, no posts are created, no CRM contacts are modified. It is specifically designed for testing on production environments where a full test execution would have real consequences.