Tidal Service Playbook Deck
A service playbook that runs on the rhythm of tides — intake, deep work, delivery, review.
Turns your AI into a service-playbook writer — builds a client-facing deck that runs your service on the rhythm of tides: intake, deep work, delivery, and review, with the cadence, handoffs, and checklists each phase needs.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Tidal Service Playbook Deck
When to use
- You run a service business — agency, studio, consultancy, maintenance crew, care team — and every engagement currently runs on memory and improvisation
- New hires keep asking how a job is supposed to go, and every senior person gives a different answer
- Clients keep asking "what happens next?" because the process was never shown to them
- Your work already has a natural cycle (intake → work → delivery → review) but nothing written down holds it to that rhythm
- You need a deck you can send to a client before kickoff that sets expectations without reading like a legal contract
Workflow
- Name the four phases (input: how engagements actually run → output: phase map)
Write down the four phases of your service in tidal terms: High Tide / Intake (everything flows in — brief, assets, access, expectations), Ebb / Deep Work (the team goes quiet and does the work), Low Tide / Delivery (the work comes back to the client, exposed and reviewable), and Flood / Review (feedback flows back in and the next cycle is set). For each phase, write one sentence saying what the client experiences — not what your team does internally. If a phase has no client-visible moment, it is not a phase yet; it is a task list waiting for a delivery point. Keep the four names consistent everywhere from now on — the deck's whole power is that one shared vocabulary replaces four different explanations. - Set the cadence (input: phase map → output: rhythm table)
For each phase, set how long it lasts and how often it repeats: intake takes two days at the start of an engagement and a half-day at the start of each cycle, deep work runs in one-week blocks, delivery happens every Friday, review closes within two working days. A playbook without times is a poster — the cadence is what turns it into a schedule a client can plan around. Write the cadence as a table (phase, duration, repeats, who is involved) and sanity-check it against your last three engagements: if the real work never fit the stated rhythm, the rhythm is aspirational fiction and the deck will be ignored on first contact with reality.
Template preview
Tidal Service Playbook Deck — Build Template
One service = one deck (8 pages). Fill this in before laying out any slides.
Service
Service name: {name} Audience: {who receives this deck — clients / new hires / both} Single point of contact: {name + role} Single feedback channel: {e.g. shared channel / shared doc — one only}
Phase map (one client-facing sentence per phase)
Rhythm table
Reality check: [ ] Rhythm checked against the last 3 engagements — it fits real work
Handoffs (per boundary: what, format, sender → receiver, confirmation)
Checklists (5–8 items per phase, clear done-states, one stop rule each)
Intake checklist:
