FelagarBeta
EN
ENEnglishNLNederlandsDEDeutschHRHrvatskiESEspañol
Get started

Features

FelagarAgency Knowledge & decisions

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

Get started with Felagar

In practice

Agency Knowledge & decisions

Agency Knowledge holds studio SOPs, pricing rules, proposal templates, and onboarding notes for the whole tenant, deliberately separate from company vault pins. The assistant can search that library alongside a Client Vault without mixing the two. Decisions from approvals and design 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 and Decisions keep those scopes honest so AI 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 the assistant without blurring scopes.

  1. 01

    Add Knowledge items in Settings for SOPs, pricing rules, and proposal 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

    Approve work as usual; Decisions capture who decided what and when across cards and design reviews.

  4. 04

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

Related features

These sit in the same room of the product. Open one when the workflow continues next door.

All features →

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.

Get startedSelf-hostComing soon