Predictable
Pricing.

WPFlow uses plans and credits. Every plan follows the same governed model: one supported site, one governed lane, staging-first delivery, scoped requests, and client-approved live release.

Plans mainly change monthly capacity and value per credit. Current examples are Free at $0/month with 50 welcome credits, Core at $25/month with 50 welcome credits and 25 monthly credits, Pro at $99/month with 50 welcome credits and 100 monthly credits, Custom by quote. The Pricing page may show values in your selected currency.

Free, Core, and Pro include 50 welcome credits that expire after 30 days. PAYG credits are $1.25 each with a 10-credit checkout minimum.

A credit is WPFlow's unit for approved delivery capacity.

Credits are tied to the scoped outcome, risk, validation, and delivery work involved in a request. They are not developer hours, and they are not internal AI or supplier costs.

Before work starts, WPFlow scopes the request and shows an estimated credit cost and approval cap, so you know the commercial boundary before the item enters the queue.

No. Credits are outcome-based delivery units, not hours.

This keeps the conversation focused on what will be delivered and reviewed, rather than how long someone spent on it. Two requests that sound similar can have different credit estimates if one is simple content work and the other touches checkout, accounts, live data, plugin behaviour, or harder-to-prove release surfaces.

One request is one clear outcome that can be scoped, approved, built, checked, and reviewed safely as a single item.

Related micro-edits can stay together when they support the same outcome. A homepage hero copy and spacing update might be one request. A homepage redesign, checkout fix, navigation restructure, and pricing rewrite should be split or planned as a larger piece of work.

That keeps your estimate, approval cap, staging review, and release record clear.

WPFlow estimates credits during the scoping step before build work starts.

Architect looks at the requested outcome, the surfaces involved, complexity, uncertainty, proof needs, site context, and risk. Sensitive areas such as checkout, payments, accounts, customer data, plugins, schema, migrations, security, or live publish risk are handled more carefully.

You see the customer-facing result: a clear scoped outcome, an estimated credit cost, and an approval cap. Internal supplier costs, token costs, and margin are not public pricing details.

An approval cap is the maximum number of credits you have approved for a request unless you later approve a revised scope or revised cap.

When you approve work, credits may be reserved while the item is in progress. Final settlement should stay at or below the approved cap unless you approve a change. Automatic top-up, where enabled, can add capacity within your budget, but it does not approve work, publish live, change your plan, or override role permissions.

Every plan includes the same governed WPFlow operating model: one supported site, one execution lane, Architect scoping, upfront estimates, staging-first build, checks and evidence where relevant, staging review, revisions before acceptance, and client-approved live release.

Higher plans increase monthly credit capacity and value per credit, but they do not remove the safety and approval discipline. That consistency is part of the product promise.

All plans use the same governed workflow. The main differences are monthly included credits, value per credit, and whether the plan is self-serve or custom.

Current examples are Free at $0/month with 50 welcome credits, Core at $25/month with 50 welcome credits and 25 monthly credits, Pro at $99/month with 50 welcome credits and 100 monthly credits, Custom by quote.

Free is best for starting without a card or occasional pay-as-you-go use. Core and Pro are designed for regular one-site WordPress change demand. Custom is for multi-site, agency, SLA, SSO, invoicing, or other needs that should not be forced into self-serve tiers.

PAYG credit purchases add extra credits when you need capacity without starting a subscription.

New paid credits are quantity-based whole-credit purchases with a 10-credit checkout minimum: $1.25 per credit. The same PAYG unit price applies whether you are on Free, Core, or Pro.

Manual purchases and automatic top-up both buy whole PAYG credits. Automatic top-up starts from the 10-credit top-up minimum and can only spend within the monthly budget you set; it does not approve work, publish live, change your plan, or create surprise overage.

Free and Core do not include an operator recovery entitlement. That does not remove delivery safety recovery for current staged work where WPFlow has a safe prepared recovery path.

Pro includes same-day operator recovery during UK business hours for supported in-scope platform delivery failures. Same-day means an operator recovery response within the same UK business day when the operator paging trigger fires by 14:00 UK time. Triggers after 14:00 receive next-business-day response unless handled earlier.

Custom / Enterprise agreements can include premium support with a 2-hour SLA during UK business hours where that is included in the custom agreement.

Operator recovery still follows the same scoped, staging-first process, so you review staging and approve anything before it goes live. It does not turn WPFlow into unlimited or out-of-scope work: unsupported site states, unsafe production changes, new scope, payment-truth blockers, or impossible requests still need re-scoping or a custom route.

Yes. WPFlow is positioned with no long-term commitment.

Free customers can stay on Free, buy PAYG credits, or choose Core, Pro, or Custom. Core and Pro customers can cancel from the billing area. For the V4 launch model, plan changes are handled through the checkout or support route shown in Billing and billing currency stays locked at signup.

WPFlow does not automatically upgrade you without consent.