Skip to content
Pilot recruiting — delivery contingent

Test one studio playbook workflow with named reviewers.

We are recruiting founder-studio design partners. Delivery begins after the Trust Gate and pilot package are approved.
GTM playbookFolder · 12 notesVendor picksNotes · updatedPostmortemPDF · Series AStudio libraryproposed pilot corpusPILOT TEST
Which billing vendor did we pick, and why?
“…chose usage-based billing after the churn spike…”
1Vendor picks · GTM
Open the passage — verify, don’t just trust.
From shared drive to asked library

Curate once; every founder gets the current version.

Curate onceA folder per playbook — hiring, GTM, vendor picks, postmortems. The studio keeps it current in one place.
Publish as knowledge boxesThe pilot would test controlled access and update behavior against one defined corpus.
Founders ask across bothThe pilot would test cited answers against the agreed source scope and reviewer criteria.
Knowledge boxes

Publish the playbook once. Every founder asks it.

Managed, read-only, synced when the studio updates — answers cite the playbook.

Knowledge boxes: Publish the playbook once. Every founder asks it. — product screenshotAttached boxes stay read-only

Give every founder your playbook.

Curate the studio library once; founders attach it read-only and ask across both — always current, always cited.Full plan comparison →