Pricing and the Gwen Work Budget

Most software charges you per seat per month whether you use it or not, and whether it produces anything or not. That model made sense for tools people operate. It makes less sense for an intelligence that does the work itself.

Gwen is priced around outcomes. You fund a Work Budget, and that budget is consumed as Gwen actually performs work you have approved. A quiet week costs little; a heavy build week draws more. You are paying for results, not for the right to log in.

Work Budget is prepaid credit that powers Gwen. You add budget to your workspace, and Gwen draws against it as approved work completes — building, researching, generating content, running tools, and the rest.

It is workspace-level, so an entire team draws from the same budget rather than buying a seat each. And because it is prepaid, you always know your exposure: Gwen cannot run up a surprise bill beyond the budget and the top-up rules you have set.

Work Budget stays available while your workspace remains active. Unused credit expires after 12 months of workspace inactivity.

This fits how real businesses work: a burst of building, a quiet stretch, then another campaign. You are not forced to spend within a monthly subscription window, but inactive balances do not sit open forever.

A new workspace can get a free first pass on an eligible scoped job — most visibly, a full website preview you can open and judge.

The point is to let you see real Gwen output before paying anything. Continuing past that first pass — further edits, publishing, exports, connected tools, longer runtime, and paid missions — is what a Work Budget funds.

Spending tracks the work performed. Heavier jobs — a large build, a long research run, a runtime-intensive task — draw more budget than a quick draft or a short answer.

Your balance and activity are visible to you, so you can see what work cost what. You are never charged for seats, idle time, or capacity you did not use; you are charged for the work Gwen did on your behalf.

Different jobs have very different weights: a light content or research task is inexpensive, while a complex build, a runtime-heavy job, or a governance-heavy enterprise workflow needs more headroom.

Gwen can estimate the weight of a request while scoping it and recommend a budget that fits, so you are not guessing. For current tiers and amounts, see the pricing page — Work Budget scales from individual use up to dedicated enterprise capacity.

Auto top-up keeps work flowing by refilling your budget when it runs low. Checkout includes a clear authorization checkbox so you can approve it before payment, and you can uncheck it if you want to start paused.

You adjust or pause it from Billing whenever you want. This keeps you in deliberate control of spend while making continuous work the normal path.

Everything about your spend lives in your Gwen dashboard, not in a third-party portal. You can see your current balance, your order and top-up history, and your receipts in one place.

Billing, upgrades, and budget management all happen inside Gwen so the money side of the product feels like part of the product — not a detour to someone else's billing page.

Work Budget is prepaid credit for work, and it is non-refundable once added. Gwen performs real, costly computation on your behalf the moment work runs, so credit funds capacity that gets consumed.

The protections that matter are the ones that prevent waste before it happens: the free first pass to prove quality, scoping before execution, approvals before external actions, explicit auto top-up authorization, and a visible balance. You decide what work runs; the budget funds exactly that.

If a job would exceed your available budget, Gwen does not silently stop mid-work or quietly overspend. It tells you, so you can top up and continue or adjust the scope.

With auto top-up on, eligible work can continue without interruption under the rules you set. With it off, you stay fully in the loop on every addition. Either way, there are no surprises.