Playbooks
A set of tasks, installed together.
Connect the apps they share, read a preview on your own work, and approve.
Quotes priced. Tomorrow's customers get a note.
Six tasks. Plumbers, electricians, HVAC, roofers and landscapers, where the owner is the person answering the company mailbox.
The Home Buyers PlaybookSellers get a reply overnight.
Five tasks. Cash home buyers and small buying shops, where the seller who writes in goes to whoever answers first.
The Agency PlaybookNew leads in the pipeline. The weekly update drafted.
Five tasks. Marketing, SEO and creative agency owners, and the consultants who owe a client the same weekly update.
The Manager PlaybookMeeting notes become tasks on the list.
Four tasks. People who run a team, and spend the week in meetings about work other people are doing.
The Email PlaybookInbox sorted. Replies already drafted.
Four tasks. Anyone whose day starts in the inbox and ends with replies still owed.
The Support PlaybookQuestions answered. Customers told when it is fixed.
Five tasks. People who answer support, file the bugs, and still owe the customer a note when the bug is fixed.
Why a set
Connect the shared apps once.
You describe nothing. Each task in a playbook is already written, and setup asks only for what it needs from you.
You connect a mailbox, a calendar or a tracker once for the whole set, not once per task.
Every task runs a preview on your own work first, with the actions held back for you to read.
Any task you do not want comes out before anything is installed.
Pick a playbook.
Choose the closest set, connect what they share, read the preview.