Playbooks
Stop staring at dashboards. Just ask.
92 starter prompts backed by required events, properties, and HTTP calls. Each one gives your agent a workflow example to adapt to your app's live signal map.
Featured
Build a composite account-health dashboard
Score every B2B account on usage, revenue, and support load. Publish one URL your CS team checks instead of wrangling data each QBR.
Nightly Routine: draft PRs for low-risk silent bugs
Routine runs at 2am, picks the top silent bug, investigates it, opens a draft PR if the fix is small and contained. Lights-out triage for the next morning's review.
Find your magic activation moment
Discover which first-24h action correlates highest with day-30 retention. Most teams can't answer this. You'll answer it in 90 seconds.
Where exactly do shoppers drop off in checkout?
Build the product-view to purchase funnel with drop-off and time-on-step. The 1-prompt ecommerce funnel that Shopify analytics doesn't ship.
Predict churn 30 days before it happens
Build a behavioral early-warning system that flags at-risk users while there's still time to save them. No ML team required.
Diagnose a customer complaint in 30 seconds
Paste a customer message. The agent pulls their session, finds the error they hit, walks their funnel, and tells you what to reply.
Track crash-free user rate per app version
Distinct users who hit a crash divided by DAU, per app version. The industry-standard mobile health metric — surface version-by-version drops fast.
Find what broke after your last deploy
Diff error fingerprints before and after the latest deploy SHA. Surface regressions in 30 seconds, including a candidate fix.
Rank errors by revenue impact, not raw count
Multiply users-affected by their plan ARR to surface the bugs costing real money. Stop triaging by event volume.
Push notification: sent → opened → action conversion
Joined funnel from push provider's send webhook through open through in-app action. Per-campaign breakdown — what marketing platforms refuse to show you.
Build a signup funnel and find where users drop off
One prompt builds the full funnel from landing → activation, publishes it as a public dashboard, and ranks drop-off steps by severity.
Track trial-to-paid conversion by acquisition source
Build the trial-to-paid funnel split by acquisition source. Surface the channel that converts 8x better than the rest.
Get a weekly digest of what your agent did
Routine that reads the audit log every Friday and Slacks a category breakdown: cases resolved, flags toggled, surveys created. Don't trust — verify in 60s.
debug Stop fires. Find regressions. Catch silent bugs.
-
Diagnose a customer complaint in 30 seconds
30 secondsPaste a customer message. The agent pulls their session, finds the error they hit, walks their funnel, and tells you what to reply.
-
Track crash-free user rate per app version
2 minutesDistinct users who hit a crash divided by DAU, per app version. The industry-standard mobile health metric — surface version-by-version drops fast.
-
Find what broke after your last deploy
30 secondsDiff error fingerprints before and after the latest deploy SHA. Surface regressions in 30 seconds, including a candidate fix.
-
Rank errors by revenue impact, not raw count
2 minutesMultiply users-affected by their plan ARR to surface the bugs costing real money. Stop triaging by event volume.
-
Find slow API routes by customer and plan
5 minutesRank API endpoints by p95 latency, error rate, customer, and plan so engineering can fix performance where it affects revenue.
-
Detect frontend performance regressions
5 minutesCompare page-load and interaction timing by release, browser, and route so frontend regressions are visible beside errors.
-
Find integration setup failures
5 minutesShow where customers fail while connecting integrations so engineering and CS can fix the highest-impact setup blockers.
-
Find queue latency and dead-letter spikes
5 minutesSee which background jobs are backing up, retrying, or landing in dead-letter queues before customers notice stale state.
-
Mobile background-sync failure monitoring
2 minutesBackground sync, refresh, prefetch jobs fail silently and degrade UX. Group failures by task_name and network_type to find the patterns.
-
Find IE/Safari/old-Chrome-only crashes
2 minutesSplit client-side errors by browser and version. Surface fingerprints concentrated in one engine — usually older Safari or a stale Chromium.
grow Funnels. Activation. Churn. Content.
-
Find your magic activation moment
2 minutesDiscover which first-24h action correlates highest with day-30 retention. Most teams can't answer this. You'll answer it in 90 seconds.
-
Where exactly do shoppers drop off in checkout?
2 minutesBuild the product-view to purchase funnel with drop-off and time-on-step. The 1-prompt ecommerce funnel that Shopify analytics doesn't ship.
-
Predict churn 30 days before it happens
10 minutesBuild a behavioral early-warning system that flags at-risk users while there's still time to save them. No ML team required.
-
Push notification: sent → opened → action conversion
5 minutesJoined funnel from push provider's send webhook through open through in-app action. Per-campaign breakdown — what marketing platforms refuse to show you.
-
Build a signup funnel and find where users drop off
2 minutesOne prompt builds the full funnel from landing → activation, publishes it as a public dashboard, and ranks drop-off steps by severity.
-
Track trial-to-paid conversion by acquisition source
3 minutesBuild the trial-to-paid funnel split by acquisition source. Surface the channel that converts 8x better than the rest.
-
Calculate campaign payback by cohort
10 minutesTie acquisition campaigns to paid conversion, revenue, and retention so marketing and finance can see which campaigns pay back.
-
Compare checkout payment methods
5 minutesBreak down checkout completion, failures, and latency by payment method so growth teams know which option hurts revenue.
-
Find docs searches with zero results
3 minutesCapture failed docs searches and connect them to activation, support load, and API adoption so docs work targets real blockers.
-
Track dunning recovery from failed invoices
5 minutesMeasure failed-payment recovery from invoice failure through retry, card update, recovery, or cancellation for subscription revenue.
ops Routines. Webhooks. Alerts. Dashboards.
-
Build a composite account-health dashboard
10 minutesScore every B2B account on usage, revenue, and support load. Publish one URL your CS team checks instead of wrangling data each QBR.
-
Nightly Routine: draft PRs for low-risk silent bugs
1 hour to set upRoutine runs at 2am, picks the top silent bug, investigates it, opens a draft PR if the fix is small and contained. Lights-out triage for the next morning's review.
-
Get a weekly digest of what your agent did
10 minutesRoutine that reads the audit log every Friday and Slacks a category breakdown: cases resolved, flags toggled, surveys created. Don't trust — verify in 60s.
-
Weekly CSM book-of-business digest
10 minutesCreate a weekly account digest for each CSM with risks, expansion signals, product adoption, and customers needing outreach.
-
Track enterprise implementation timeline
7 minutesFollow an enterprise account from kickoff through integration, first data, first value, and blocked steps so solutions teams can unblock launches.
-
Release health scorecard after every deploy
3 minutesSummarize a deploy with new errors, affected users, key metric deltas, and the next engineering action in one chat response.
-
Generate a renewal-risk brief for each account
10 minutesCombine usage decline, errors, seat utilization, and support friction into a renewal-risk brief CS can act on before the renewal date.
-
Audit sourcemap coverage for minified errors
5 minutesFind which production errors cannot be unmangled because sourcemaps are missing, stale, or uploaded under the wrong release.
-
Review stale or dangerous error suppressions
2 minutesFind suppressions that are hiding high-volume, high-impact, or recently regressed errors before noise rules mask real incidents.
-
Rank support load by account
5 minutesCombine errors, complaints, affected users, and plan data to show which accounts are consuming the most support attention.
Try any of these in your own agent.
Send this to Claude Code, Cursor, Codex, or any coding agent. It reads the canonical reference, uses the HTTP API, and sets you up.