Skip to main content
Use this flow to get a first payback-aware action queue running.
1

Create a workspace

Create a FloKit workspace for one app, one legal entity, and one growth team. Keep staging and production workspaces separate if you test with synthetic data.
2

Connect acquisition channels

Add the paid and organic channels you want FloKit to observe or operate. Start read-only until the team agrees on spend guardrails and approval rules.
3

Connect product and revenue events

Send activation, subscription, trial, renewal, cancellation, refund, and attribution events. FloKit uses these signals to compare acquisition quality across cohorts.
4

Set guardrails

Define budget caps, excluded campaigns, minimum payback thresholds, approval requirements, and actions FloKit can prepare but not execute.
5

Review the action queue

Approve, reject, or modify recommended actions. Each action should explain the signal behind it, the expected payback impact, and the rollback path.

​
Local docs workflow

Run the docs locally from the repository root: 
npm install
npm run dev
Validate the docs before pushing: 
npm run validate
npm run broken-links