Use it when answering from email, Slack, WhatsApp or Teams messages.
7 rolesRead moreThe team already knows how the job is done.
124 playbooks, among them how to ship a launch nobody has to rescue, shape a post for where it will be read, run experiments instead of opinions and read an ad account without double-counting. Each one is written around how the work usually goes wrong, and the team picks the right one for the task.
Written by people who do the job.
Each playbook captures the steps and the traps, not just the task name.
Picked for the task.
Ask Iris why signups dropped and Iris uses the analytics playbooks. You don't have to choose.
Every one is listed below.
Browse all 124, grouped by the kind of work.
SHOWING 1–11 OF 11
Use it when answering from Notion, Drive, Docs, Sheets or a wiki.
7 rolesRead moreUse it when answering an invoice, receivables or ledger question.
4 rolesRead moreUse it when answering from a store or payments connector.
4 rolesRead moreUse it when answering from a calendar, Zoom, Meet or meeting notes.
3 rolesRead moreUse it when answering from product or web analytics.
3 rolesRead moreUse it when answering from a tracker — what is done, late, or blocked.
3 rolesRead moreUse it when computing ROAS/CAC, or any number mixing two connectors.
2 rolesRead moreUse it when answering a pipeline, deal or forecast question from a CRM.
2 rolesRead moreUse it when answering from a social connector.
2 rolesRead moreUse it when answering from an ad account — spend, conversions, ROAS.
2 rolesRead moreQuoting a message as company fact — "we agreed 20% discount" — when it is only evidence that one person typed it. Mailboxes are tier `memory` (lib/connectors/ingest-policy.ts), so this is the family that writes company truth.
Reading a strategy doc written eighteen months ago as the current strategy. Documents carry no expiry and search ranks by relevance, not recency.
Answering "how many invoices are pending and for how much" by summing `total` across whatever statuses looked pending. Zoho Books has no status called pending, the amount owed is `balance`, and a partially paid invoice contributes its remainder — three judgement calls that were all the model's guess.
Saying "revenue" when the number is gross orders including tax, shipping, cancellations and not-yet-settled refunds — four different numbers that all get called revenue.
Reporting that a decision was made because a meeting called "Pricing decision" appeared on the calendar. A meeting existing is evidence it was scheduled, nothing more.
Reporting sessions as users, or users as customers. Three de-duplication rules produce three different denominators and every one of them is defensible on its own.
Reporting "8 of 10 done" from status fields as delivery progress. The status field is a claim by its owner, updated when they remember, and "In Review" is where work goes to be forgotten.
Silent division — ad spend over store revenue, presented as ROAS, with two different attribution windows underneath it.
Calling the generic list-objects tool on a toolkit with 100+ read tools, then reasoning over metadata instead of the pipeline.
Placing reach or follower growth next to revenue in a report, which invites the reader to treat them as the same kind of number. Composio's own Instagram guidance also warns that an empty insights payload is a successful call, not an error.
Repeating a platform-reported conversion count as the business result. The platform both runs the ads and decides which sales they caused; its attribution window is its own.
Stop launching into silence.
Start free with your website, or tell us about your product and we’ll set the team up with you.