Cue playbooks and workshops

Cue prompts in your team's own words

Cue does the most for a team that knows what to ask it. Fountain Labs builds Cue playbooks and working-session decks around a team's own roles, stages and locations. Then we walk through real use cases with the team in their own Fountain account, and leave the playbook behind as a prompt library they can keep using.

01 / 05

The problem

Frontline hiring teams do a lot of repetitive work by hand: searching applicants, moving them between stages, chasing paperwork, pulling reports. Cue can take on much of that work. But a blank chat box doesn't tell a recruiter or a hiring manager what to ask, and generic examples only go so far because they aren't written in the team's own language.

02 / 05

What we built

A Cue playbook builder. It drafts a tailored guide with how Cue works, five starter prompts, prompts grouped by the work the team does (reporting, pipeline health, re-engagement, workflow setup, bulk updates, messaging), prompting tips, what to do when an answer looks off, an FAQ and a one-page cheat sheet.
A working-session deck builder that starts from the team's own Fountain activity, shows where repetitive work happens by hand, and matches the biggest manual workflows to prompts the team can paste into Cue.
An honest slide on gaps. Where a team has tried something Cue can't do yet, the deck says so, offers a workaround, and explains how the request reaches the Cue product team.
A library of prompt patterns organized by the work teams do, adapted to each team's vocabulary.
Hands-on Cue workshops and business reviews in the team's own account, with the playbook left behind.

03 / 05

How it works

We start with the team's account: the roles they hire for, their stages and locations, and where repetitive work piles up.
Claude drafts the playbook and the deck in the team's own vocabulary.
We review every draft before it is shared.
Claude Design turns the drafts into a PDF playbook and a slide deck.
We run a working session in the team's own account, built around trying prompts rather than watching a demo.

04 / 05

Where it landed

Used in customer Cue business reviews and hands-on sessions since spring 2026.
Shared with Fountain's customer success team in May 2026.
Requests raised in sessions are shared with the Cue product team.

05 / 05

What we learned

Knowing what to ask is one of the hardest parts of starting with an AI agent. Prompts written with the team's own stage names make the first one easy to try.
Specific beats generic. A team's real roles, stages and locations are what make a prompt worth trying.
Being upfront about what Cue can't do yet keeps the session honest, and gives us clear requests for the product team.
We now put more of our time into each team's most active Cue users, so they can help their teammates get going. That idea is behind CPUC, our Cue Power User Conference.