Launching Cue with customers

01 / 05

The problem

Frontline hiring teams do a lot of repetitive work: pulling reports, chasing stuck candidates, and updating openings and stages. An AI system can take on that work only if it fits how recruiters really work and earns their trust. We wanted real customer teams using Cue on their own hiring data before it reached everyone.

02 / 05

What we built

• A hands-on beta. From March 16 to April 14, 2026, a small group of customer teams used Cue in their own Fountain accounts.
• Live kickoffs inside each team's own account. The goal was for someone on the customer's team to run a prompt themselves before the call ended.
• Check-ins about every two weeks to go over what Cue got right, where it fell short, and what to try next.
• Starter prompts, like finding where candidates get stuck or summarizing applicants by stage, so new users had an easy place to begin.
• One place for feedback from calls, in-product ratings and support requests, tagged for the team best placed to act on it.
• Launch rehearsals: full dry runs to activate an account, open Cue, ask a question, get an answer, and check everything was tracked.

03 / 05

How it works

1. Invite: a small group of customer teams gets early access to Cue.
2. Kick off: a live session in the customer's own account, where someone on their team runs a prompt.
3. Learn: regular check-ins, with all feedback collected in one place.
4. Fix: a daily review of where Cue fell short, with each issue sent to the team that owns it.
5. Launch: full dry runs, then public launch on April 14, 2026.

04 / 05

Where it landed

• Customer teams used Cue in their own Fountain accounts for four weeks before launch.
• Cue launched publicly on April 14, 2026, with a live launch keynote.
• Bug reports, requests and pain points from beta teams reached the product teams that own them before launch.
• After launch, we reused the same in-account kickoffs and check-ins for guided customer rollouts.

05 / 05

What we learned

• Start with questions, then actions. Lead with reports and pipeline questions before handing Cue bulk changes.
• Hands-on beats watching. Someone should run a prompt themselves on the first call.
• Wins spread person to person. Use grew when one person found a real win and showed their teammates.
• Prompting is a skill, so starter prompts and onboarding matter.
• Say the limits out loud, and ask people to review Cue's work before high-impact changes.