Launch Review Agent

Check how a new capability is being talked about on live calls thirty days after launch, including who raises it, what buyers compare it to, and whether it changes the conversation.

Trigger: thirty days after a capability launches
AI steps: report how the capability is landing on buyer calls
Output: a launch report and three buyer quotes emailed to product and marketing

See Agent Template

Copied

Launch Review Agent: thirty days after a capability launches; report how the capability is landing on buyer calls; a launch report and three buyer quotes emailed to product and marketing

How it works

Agent breakdown

A blueprint to adapt, not a fixed recipe. Set the trigger, thresholds, and methodology that fit your team, and each step builds on the last, using the conversation and CRM context you already capture.

Wait thirty days after the launch

Trigger

Schedule-Triggered · Thirty days after a launch

Pull the calls that mention the capability

Action

Get/Lookup · Recording · Calls: where it was mentioned

Report how the capability is landing

Action

AI Step · Output: how it is landing

Send the report with the buyer quotes

Output

Send Internal Email · Recipients: product and marketing

TriggerStep 1 of 6

Wait thirty days after the launch

The agent waits thirty days after the capability launches before starting the review. This gives the initial launch noise time to settle, while leaving product and marketing time to change the messaging before it hardens.

Trigger: A capability launches
Timing: Thirty days after the launch

ActionStep 2 of 6

Pull the calls that mention the capability

Next, the agent pulls the calls from the last thirty days where the capability was actually mentioned. It leaves out internal enablement sessions, so the review reflects how buyers talk about it rather than how the team presents it internally.

Window: The last thirty days
Excludes: Internal sessions

ActionStep 3 of 6

Report how the capability is landing

Using those calls, the agent reports who raises the capability, what buyers compare it to, and whether it changes the conversation. It includes three direct buyer quotes instead of turning the response into a sentiment score.

Prompt

You are reviewing how a newly launched capability is being talked about on live calls thirty days after launch.

Input: calls from the last thirty days where the capability was mentioned, excluding internal sessions.

Report:

Who raises the capability in the conversation.
What buyers compare it to.
Whether it changes the conversation, and how.
Three direct quotes from buyers that show how the capability is landing.

Rules: use only the calls provided. Quote buyers rather than our own team. Do not summarize sentiment as a score.

Return a short report with the sections: who raises it, what buyers compare it to, how it changes the conversation, and three buyer quotes.

Copy

OutputStep 4 of 6

Send the report with the buyer quotes

Finally, the agent emails the report and its supporting quotes to product and marketing. They get the buyers' own words rather than a rating, which makes it easier to see why the capability is landing well or badly.

Includes: The quotes behind the report
Excludes: Internal sessions
When: Thirty days after launch

Output

A launch report with three buyer quotes in the inboxes of product and marketing

See who brings up the capability, what buyers compare it to, and whether it changes the conversation. The report arrives thirty days after launch with three buyer quotes, so product and marketing can adjust the messaging while it is still taking shape.