Teams

Give engineering, product, and design one shared operating layer for governed AI work.

Teams is the organisational layer above the iteration loop the Blueprint ships. Engineers, product managers, and product designers see the same Readiness Review scores, the same doctrine citations, and the same evidence, so the team governs AI work against one shared standard instead of three siloed ones.

Apply as a Trio Notify me at launch

Key Facts

Base fee: £299 / month
Cross-Functional AI Core: 1 Lead Engineer, 1 Product Manager, 1 Product Designer
Extra seats: +£39 / month
Commercial model: Sales-led / early access

Why Teams is not just more seats

If this layer were priced like a normal seat bundle, teams would treat it like another tool login. Teams is meant to behave like organisational infrastructure: a shared operating standard for AI distribution, validation visibility, and approval boundaries.

Doctrine + MCP make the iteration loop discoverable and runnable inside Claude Code, Cursor, and Codex

Pro is where one practitioner runs the loop privately and recurringly

Teams makes the loop governable across engineering, product, and design: one shared standard, three roles in the room

What the trio sees together

The point is not three parallel views. The point is one shared layer of context and evidence that each role can read through its own lens.

Shared validation visibility instead of isolated private runs

Private overlays for Figma rules, codebase standards, and internal context

Doctrine-aligned review scorecards that can circulate across the product organisation

Governed distribution of the same standard across tools and repositories

The Cross-Functional AI Core

The base package is intentionally structured around the three roles that have to stay aligned if AI work is going to ship safely and coherently.

Teams

Engineer

Owns runtime architecture, MCP implementation, tool boundaries, and operational risk.

Principles for engineers →

Teams

Product Manager

Owns governance, approval boundaries, rollout risk, and the decision logic behind the workflow.

Principles for product managers →

Teams

Product Designer

Owns the visibility contract, what the agent shows, when it shows it, and how feedback is calibrated to the user's level of attention.

Principles for designers →

Weekly run allowance per person

Each Teams member has their own weekly allowance: 100 architect.validate (consensus) and 24 architect.certify a week. Allowances are individual, not shared across the workspace. What Teams adds is the shared view described above.

Per member

100 validate · 24 cert

Your individual weekly allowance. Not pooled or shared with teammates.

Two paths before launch

Some teams want to shape the product early. Others simply want the model, pricing, and package to be clear before general availability. The page should support both.

Apply as a Trio if you want to join the closed beta as a cross-functional team

Notify me at launch if the model is relevant but you prefer to wait for the broader release

Apply as a Trio Notify me at launch

When to stay on Pro vs move to Teams

Stay on Pro when

one practitioner is still validating whether the protected loop creates recurring value

the workflow is still local to one owner

you do not yet need shared oversight or cross-functional visibility

Move to Teams when

engineering, product, and design all need to review the same AI decisions

private overlays and governed distribution matter more than individual critique

the organisation wants a standard, not just one practitioner workspace

Ready to use Teams as the organisational layer?

Apply as a Trio Notify me at launch