Playbooks

A playbook is a standard setup packed with the five or so questions it needs: a follow-up call for every new contact, a weekly report to a team, a school’s admissions funnel. You answer the questions, and you get the whole setup as drafts that land switched off: segments, forms, templates, follow-ups with tasks for your team, reports and dashboards.

Nothing sends until you have looked at it, added people to the teams, and switched it on.

How to use one

Today, a playbook page is a recipe: build each draft it lists in the dashboard, with the answers to its questions, and leave everything switched off until you’ve tested it. Every object on the page maps to one screen (Segments, Forms, Templates, Follow-ups, Reports, Dashboards, and Settings → Collaborators → Teams).

Coming next: install in one step

One-step install isn’t live yet. When it ships, you’ll ask the copilot in your own words (“follow up every new enquiry with a call”) or name the playbook. It will read your workspace first, so it reuses forms and segments you already have, ask the playbook’s questions, show the plan as a table, create everything as drafts switched off, and end with what you need to do. MCP clients such as Claude and ChatGPT will get the same through list_playbooks and plan_playbook, which turn a playbook and your answers into a changeset you review before it’s applied. The spec files are already published for that.

The library

Pack	Playbook	Built from	Needs a developer?	Installs
Base: every workspace	Birthday or anniversary	A real engagement (2026-10-22)	No	5 drafts
	Feedback form with follow-up	Synthesized	No	5 drafts
	First-contact follow-up with call tasks	A real engagement (2026-10-31)	No	9 drafts
	Renewal or payment reminder	Synthesized	No	10 drafts
	Weekly report to a team	A real engagement (2026-10-31)	No	7 drafts
	Welcome and onboarding	A real engagement (2026-10-31)	Yes: events from your app	6 drafts
	Win-back	Synthesized	No	5 drafts
Church	First-timer to member	A real engagement (2026-10-31)	No	41 drafts
	Giving thank-you	Synthesized	No	8 drafts
	House fellowship routing	A real engagement (2026-10-31)	No	6 drafts
Schools	Fee reminders	Synthesized	No	10 drafts
	School tour to enrolment	Synthesized	No	30 drafts
Edtech	Admissions funnel	A real engagement (2026-10-25)	Yes: events from your app	18 drafts
	Cohort onboarding	Synthesized	No	25 drafts
	Keep learners going and celebrate completion	Synthesized	No	14 drafts
Retail and e-commerce	Abandoned cart	Synthesized	Yes: events from your app	3 drafts
	After the sale	Synthesized	No	17 drafts
	Back in stock	Synthesized	No	4 drafts
Lending and cooperatives	Cooperative contributions	Synthesized	No	16 drafts
	KYC nudge	Synthesized	Yes: events from your app	5 drafts
	Loan application follow-up	Synthesized	No	17 drafts
	Repayment reminders	Synthesized	No	12 drafts
Fintech	First transaction activation	Synthesized	No	13 drafts
	Failed transaction support	Synthesized	Yes: events from your app	13 drafts
SaaS	Trial to paid	Synthesized	Yes: events from your app	6 drafts
Salons, barbers and spas	Booking reminders for salons and studios	Synthesized	No	15 drafts
	Thank-yous, rebooking nudges and win-back for salons	Synthesized	No	13 drafts
Restaurants and caterers	Catering and event enquiries	Synthesized	No	12 drafts
	Table feedback and bring-them-back texts	Synthesized	No	8 drafts
Gyms and studios	Membership renewal reminders	Synthesized	No	17 drafts
	Trial class to member	Synthesized	No	19 drafts
Real estate and lettings	Property enquiry to viewing	Synthesized	No	18 drafts
	Rent and lease reminders	Synthesized	No	16 drafts
Hotels and short-lets	Post-stay review and come-back message	Synthesized	No	9 drafts
	Pre-arrival messages for guests	Synthesized	No	10 drafts
Insurance agents	Policy renewal reminders	Synthesized	No	15 drafts
Insurtech	Claims status updates	Synthesized	No	27 drafts
	Quote to policy	Synthesized	No	17 drafts
Mechanics and car services	Service reminders for garages and workshops	Synthesized	No	15 drafts
Professional services	Document collection before a deadline	Synthesized	No	8 drafts
	Enquiry to consultation	Synthesized	No	18 drafts
Nonprofits	Donor thank-you and yearly follow-up	Synthesized	No	20 drafts
	Volunteer onboarding	Synthesized	No	26 drafts
Events	Event registration and reminders	Synthesized	No	23 drafts
Communities and associations	Membership dues renewals	Synthesized	No	15 drafts
	New member welcome	Synthesized	No	20 drafts
Residential estates	New residents and maintenance requests	Synthesized	No	17 drafts
	Service charge reminders	Synthesized	No	16 drafts
Government services	Application status updates	Synthesized	No	30 drafts
	Renewal deadline reminders	Synthesized	No	17 drafts
Logistics and delivery	Delivery updates and failed-delivery recovery	Synthesized	No	23 drafts
	Merchant onboarding and first shipment	Synthesized	No	16 drafts

Most of them need no developer: their data comes in through forms, booking forms, forms your staff fill in, or a spreadsheet you already keep. Patterns for small businesses explains how. The table says which ones need events from an app.

Base playbooks fit any workspace and use neutral words: people, contacts, teams. Sector packs use your sector’s words and add setups only that sector needs. You can use any playbook from any pack.

“Built from a real engagement” means the structure was copied from a setup we built with a customer, with every name, number and identifier removed. “Synthesized” means it was written from the base patterns for a sector we haven’t built with yet. Both are reviewed before they are added. Adding a playbook explains how new ones get in.

No people data

Playbooks hold structure and questions only. No playbook contains a name, phone number, email address or anything copied from a customer’s people. They’re filled in from your answers, never from your contacts.

Reading a playbook page

Every page has the same parts, all rendered from the playbook’s spec file:

• When to use it, and where the data comes from: a form, a booking form, a staff form, a synced sheet, or your app.
• What it sets up: each draft, what it does, and how it lands.
• The questions it asks, with defaults, and the other settings it assumes.
• Timings: delays, due times, reminders and schedules.
• Channels: which ones it uses and what each needs before it can send. Email needs a verified sender; SMS needs a provider, or Origamy managed SMS after business verification.
• What you need to do before switching it on.
• Copilot eval: the request we test the copilot with, so you can see how to ask for it.

The spec itself is linked at the top of each page. Its format is in Playbook spec format.