Clear Predictable Pricing.

A credit is WPFlow's unit for governed delivery. It is designed to make the scope boundary clear before work starts, and WPFlow explicitly treats credits as delivery units, not hours. Practically, credits attach to the approved outcome for a request, so the commercial conversation stays about what will be delivered and reviewed safely, not about time spent.

WPFlow uses an Architect scoping step before build starts. The Architect scopes the outcome, calls out uncertainty, and estimates an approval cap before work moves into execution. This is why WPFlow can stay predictable: the estimate cap stays attached to the approved outcome rather than drifting inside a long message thread.

One request is one clear outcome that can be scoped, approved, and reviewed safely. If a brief hides multiple goals, multiple templates, or a broader redesign, WPFlow splits it before build starts. Splitting is not bureaucracy, it is how WPFlow keeps the commercial truth clear, so you are not surprised later by a vague request that turns into a much larger piece of work.

WPFlow is built around explicit approvals. You see an estimated credit cost and a cap, and approving moves the item into the queue if capacity allows. Separately, publish remains a client action: the workflow is designed around staging-first delivery and client-approved publish, which keeps both release risk and commercial authority clear.

WPFlow keeps the operating model consistent across plans: Architect scoping before build starts, staging-first implementation, an evidence pack and publish notes, and client-approved publish inside one supported site and one execution lane. That fixed operating model is the point: the plan changes your monthly capacity and priority, it does not change the release discipline.

All lanes share the same governed model, one supported site, one lane, staging-first delivery, and evidence before publish, but they differ in included monthly credits, cost per credit, and priority. Current standard options are: Free: $0/month with no recurring monthly credits, top-ups only after the trial. Core: $730/month with 50 credits included. Pro: $1,400/month with 100 credits included. Scale: $2,335/month with 175 credits included.

You add capacity with top-ups, either because you are on Free, which runs on top-ups, or because you are on a paid plan and have a temporary spike in approved work. Top-ups are worse value than upgrading to the right monthly lane, so they are best used for short bursts rather than as your baseline operating model.

All lanes start with the same public trial: 7 days and 5 trial credits. Importantly, the trial clock starts when staging is ready, not at raw sign-up. Because delivery is governed and staging-backed, payment authority is required before staging is provisioned.

WPFlow positions the service as no long-term commitment: you start with the trial, then choose Free, which runs on top-ups, or a monthly plan, and you can cancel at any time.

WPFlow is designed to work with your current setup, with no hosting or DNS migration required. The model is staging-first: changes are built and reviewed on staging before being pushed live once approved. WPFlow also describes change safety in operational terms, using GitHub for version control and making releases reviewable, with rollback awareness captured in publish notes.