Features

FelagarAgency Knowledge & decisions

Keep studio SOPs and contract templates in one place, keep client vaults client-bound, and show decisions where clients expect them.

In practice

Agency Knowledge & decisions

Agency Knowledge holds studio SOPs, pricing rules, proposal and contract templates, and onboarding notes for the whole tenant, deliberately separate from company vault pins. Generate contract documents from Knowledge with company and project details merged in during client onboarding. Rad and MCP-connected agents can search that library alongside a Client Vault without mixing the two. Decisions from approvals and deliverable reviews stay first-class records with who, what, when, and source. Clients get a portal Decisions view of their own outcomes without internal-only fields.

Studios need two kinds of memory: how we work as a studio, and what we decided with this client. Knowledge, contract generation, and Decisions keep those scopes honest so Rad and portals never blur them.

Highlights

What stands out when this becomes part of how you run client work.

How it works

Knowledge is agency-wide. Decisions are relationship history. Both feed Rad without blurring scopes.

  1. 01

    Add Knowledge items in Settings for SOPs, pricing rules, proposal templates, and contract templates your whole studio should share.

  2. 02

    Keep client-specific brief and tone in the Client Vault so company context stays intentional.

  3. 03

    During onboarding, generate a contract document from Knowledge with merged company and project details.

  4. 04

    Clients open portal Decisions for their outcomes. Rad can search Knowledge and vault pins without mixing scopes.

We run the platform. You run the studio.

Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.

Beta

Request beta access

We will only use this email for beta updates and your invite.