One plan, and a month of shipping

We repriced Pagerox, and the honest version of the story is that the old pricing described a product we no longer build. Per-employee salaries made sense when an employee was a heavy, singular thing. Then we made hiring take five minutes, gave every role starter scaffolds, and let one org brain feed the whole roster, and the per-seat math started punishing exactly the behavior the product rewards: hiring a small team.

So: one plan. $20 a month for the workspace, up to 10 agents, $15 a month of model usage included across all of them. Usage beyond that bills at metered cost plus 40%, and, more importantly, you can cap it: per agent and for the whole workspace. At your cap, agents pause until next month. The included usage is never blocked, a $0 cap simply means never bill me beyond the plan, and there is no premium-model surcharge anywhere: usage is usage, whichever model served it. Free stays what it was: one agent on your own model key, forever.

The month of shipping that made the old pricing obsolete:

Hiring is one stepper now. Pick a role card that answers the three questions you actually have (what it does, what it needs connected, what a first week looks like), name your hire, and walk the tool, knowledge, and Slack steps. Everything after the name is skippable, and every skip stays visible on the profile as a to-do. Skipping Slack is a real finish: the employee answers in web chat until you connect it.

Knowledge packs. A curated library of scaffolds (support playbooks, policy skeletons, runbook shapes, escalation etiquette) that installs as editable copies into your org brain. No upstream link, deliberately: once installed, the copies are yours, your edits can never be clobbered, and uninstalling keeps anything you touched.

Deep code investigations. Ask a support employee why the product actually behaves some way and it can read your real codebase: a sandboxed deep investigation whose answer comes back in plain language, with every command it ran kept in the flight recorder. Your model keys never enter the sandbox; it holds only a scoped, budget-capped token and dies minutes later. Support answers stop being the wiki's best guess.

Self-tuning, under version control. Tell an employee 'from now on, lead with the fix' and it becomes standing guidance: versioned, visible on the profile, governed by a dial you set from propose-only to apply-and-notify, revertible in one click. The same rule that has always governed learning here applies to self-improvement: no silent changes, anywhere.

The through-line, including in the pricing: you should be able to see what it will cost, what it learned, and what it did, and undo any of the three. Caps you set, ledgers you can read, versions you can revert. The $20 is the least interesting part; the ceiling being yours is the point.