Product →Examples →FAQ →All solutions →About →
Business problemsHow it worksRolesOrganizations
Scopeout for teams

Runs on its own. Checks in with your team.

Operators do the running. Your team approves plans, picks variants, reviews PRs and comments on findings, on the same canvas, with each hand-off carrying its context.

Hypothesis H1 · comments
P
priya Go with B, but keep the express-pay guardrail. @tejas can you review the PR?
T
tejas Reviewed. Merging behind the flag.
Approvalsplan · priya variant · sam PR · tejas

Autonomy with people in the loop

Every step is a switch and every approval is a role. Turn autonomy up as trust grows, per team, per step.

Approve in place

A plan, a hypothesis, a variant or a rollout is approved on the block itself, with the evidence attached.

Waiting for a person · 3
🔒
Merge PR #482tejas · tests passed, preview ready
Review
🔒
Roll variant B to 100%priya · guardrails holding 3 / 3
Approve
🔒
Start interviews · 12 userssam · guide attached
Approve

Hand-offs that carry context

The PM approves, the designer picks, the engineer merges, leadership reads, all on one block with comments and mentions.

Hand-off · H1 → variant → PR
P
priya Approved the plan. Evidence attached.
S
sam Picked B, sized to content.
T
tejas Merged behind the flag.
Approvalseach step, same block

Digest to where the team lives

The weekly review lands in Slack with links back to every block, so nobody has to open a dashboard.

#product · where the team lives
4 runs shipped
3 won · +6.9%
Every line links back to its block
Waiting on you2 decisions
Open the canvas

Built for the whole team

Who directs each step
Researchruns · asks priya
Analyzeruns
Designsam picks
Buildtejas reviews
Testruns · bar 95%
Publishpriya approves
Change any of theseper team, per step

Roles per step

Decide who directs research, design, build, test and publish.

Finding · comments and mentions
P
priya @sam can we try the header entry point?
S
sam On it. Variant in an hour.
Approvalsdiscussion stays on the block

Comments and mentions

Discussion happens on the finding, the variant or the result, not in a separate thread.

Autonomy per step
Research
runs, then asks
Design
proposes
Build
opens PRs
Publish
waits for a person
Spend ceiling$500 per loop

Nothing ships without a person

Build opens PRs, Test proposes promotions, Publish waits for an approver.

Connected · read in place, cited
GA4MixpanelZendeskIntercomFigmaStorybookGitHubGitLabNotionSlackBrowser agent
Not connected yet?the browser agent gathers evidence from any URL

Your tools, connected

Slack, GitHub, Figma, Notion. The canvas is the shared context, not another inbox.

Start from a prompt.

Review

“What shipped this week, and did it work?”

Run this when my batch opens →
Ask

“What is waiting on my approval?”

Run this when my batch opens →
Plan

“Propose three tests for onboarding ranked by expected lift and assign owners.”

Run this when my batch opens →

Questions, answered.

Can the AI act without approval?

Only where you allow it. Each step has an autonomy dial from ask-every-time to fully automatic.

How do non-technical teammates join?

The canvas is the interface. They read findings, comment and approve; no tool to learn.

Does it replace our project tracker?

No. It links to tickets and PRs; the record stays on the canvas.

Stop running the business. Start directing it.

Join the waitlist

Private beta. We onboard teams in small batches. Or contact us.