When does an AI agent use this pattern?

When the trigger described above matches the situation the agent is handling. The agent queries FusedFrames at runtime, this pattern is returned and the agent follows the recorded reasoning and steps to reach the recorded outcome.

How were the steps captured?

By the desktop app on the machine of someone who actually does this work. It records clicks, keystrokes, copy and paste, drag and drop, selected text and screen regions across HubSpot and Gong, then groups them into the meaningful steps shown above.

Where does the reasoning come from?

From the operator. When the desktop app sees a decision the action alone cannot explain, it asks why in the moment. The operator's answer is recorded and becomes the reasoning attached to the pattern, so the AI agent gets the thinking and not just the steps.

What if my team handles this differently?

Capture how your team actually does it. The desktop app records what your operator does on your tools and the web app distills that into a pattern shaped by your team. Each team's library reflects their own approach rather than the example shown here.

What if a case looks like this pattern but does not quite fit?

The pattern is linked to 1 alternative. The agent can follow the connections shown on this page to a related pattern that matches the case more closely.

How does my AI agent actually call this pattern?

Through the read-only REST API or the npm CLI. Create an API key in the dashboard, choose whether it accesses all libraries or specific ones and have your agent query at runtime. The response is structured JSON ready for tool use.

Is the data shown on this page from a live customer?

No. Example libraries on this site are illustrative. Patterns in your own account are built from your team's captured actions and stay private to your workspace.

How do I build a pattern like this for my team?

Install the desktop app on the machine of the person who already does this work, ask them to handle a real case end to end, then distill the captured action into a pattern in the web app. The pattern you end up with mirrors how your team actually operates.

Logging an expansion opportunity in HubSpot

When a Gong call captures the customer raising new requirements, the CSM clips the moment and creates a Renewals-pipeline deal in HubSpot at Expansion-Discovery. The deal carries the Gong moment URL, the 'expansion-within-renewal' tag and an @mention to the assigned AE.

Tags

expansionhubspotgongrenewaldeal

Lets your agent filter to the right pattern

Categories and tags scope the retrieval set, so your agent receives only the patterns relevant to the task instead of scanning the full library.

What and why

The observed behaviour and the reasoning behind it.

Behaviour

When a Gong call moment captures the customer raising new requirements (additional users, extra modules, multi-year extension), the customer success manager clips the moment, opens the customer’s company record in HubSpot, creates a new deal in the Renewals pipeline at stage ‘Expansion-Discovery’ with the deal name in the format ‘[Account] · Expansion · [thing]’, pastes the Gong moment URL into the deal description, tags the deal ‘expansion-within-renewal’ and @mentions the assigned AE in the deal note thread.

Reasoning

Expansion signals surface in calls long before customers turn them into formal asks. Capturing them as deal records (not internal notes) means the expansion enters the leader’s forecast and the assigned AE picks it up via their normal pipeline view, rather than living as a CSM mental note that disappears at the next handoff. The Gong moment URL is mandatory because the AE will need the customer’s exact words and tone when they respond. Tagging as ‘expansion-within-renewal’ rather than ‘new business’ is intentional. The renewal cycle is already negotiating value, so bundling expansion into the renewal converts more reliably than separating it as a standalone deal that bypasses the renewal context.

Gives your agent an operator's reasoning

Behaviour records the action; reasoning records the rationale. Your agent applies both to handle cases that diverge from the captured examples.

Cause and effect

What initiates this pattern and what it produces.

Trigger

A Gong call (any call, not just a QBR) contains a moment where the customer raises additional users, extra modules, multi-year interest or anything that does not fit on the current contract.

Outcome

A new HubSpot deal exists in the Renewals pipeline at the Expansion-Discovery stage, tagged ‘expansion-within-renewal’, with the Gong moment URL pasted in the description and the assigned AE notified in the note thread.

Tells your agent when to act and what to verify

Your agent stays within the scope set by the trigger and outcome, so it doesn't extend beyond the work or finish before the outcome is met.

Standard operating procedure

Step-by-step instructions to reproduce this pattern.

Gong

Find the moment on the call where the customer raised the expansion signal.

Common phrases that indicate expansion: ‘we’re hiring’, ‘the other teams want to use this’, ‘what would it cost to add’, ‘could we get [feature] as well’, ‘we’re thinking about a 2-year’. Discard hypothetical-sounding moments (‘eventually we might’). Only present-tense interest counts as a signal worth logging.

Expected: You have a single Gong moment that contains a present-tense expansion signal worth routing to the assigned AE.

Gong

Click ‘Save to Library’ and choose the ‘Expansion signals’ shared folder.

The folder is shared with the AEs and the CS Lead. Saving here triggers the daily 5pm digest to the AE team so they see new expansion clips even when no HubSpot deal has been created yet, which is the safety net for the half of expansion signals the CSM does not have time to formalise the same day.

Expected: The clip is saved in the shared library folder and the AE team will see it in the daily digest.

Gong

Click ‘Share’ on the moment, tick ‘Start at current time’ and copy the URL.

Without the timestamp the link drops the AE on the call’s first second. They will not scrub through 60 minutes to find the moment, and the deal will sit untouched until the next CSM update.

Expected: A Gong URL ending with the moment timestamp is on the clipboard, ready to paste into HubSpot.

HubSpot

Open the customer’s company record and click ‘New deal’ from the company’s Deals panel.

Always create the deal under the company record, not from the deals list, so the company association is automatic. Forgetting the association causes the deal to fall out of the renewal forecast view, which filters by company. The leader will see a phantom expansion deal that does not appear on the account’s rollup.

Expected: The New Deal dialog opens with the customer’s company pre-filled in the company association field.

HubSpot

Set Pipeline = Renewals (not New Business), Stage = Expansion-Discovery, Deal name = ‘[Account] · Expansion · [thing]’.

Examples: ‘Monarch Foods · Expansion · 30 add’l seats’, ‘Cascadia Bank · Expansion · 2yr commit’. The naming format powers the AE’s saved pipeline filter. The New Business pipeline is wrong because the deal is tied to the renewal. Putting it on New Business pipelines makes the expansion invisible to the renewal forecast and double-counts the customer for the AE.

Expected: The deal sits on the Renewals pipeline at Expansion-Discovery with a name the AE filter will pick up.

HubSpot

Paste the Gong moment URL into the deal description and tag the deal ‘expansion-within-renewal’.

The tag is what the leader’s expansion report filters on. Without the tag the deal still exists but does not show up in the weekly expansion review, so the leader cannot prioritise it for AE coaching or pull it into the renewal pricing conversation.

Expected: The deal description carries the Gong link and the deal carries the tag that makes it visible to the leader’s expansion report.

HubSpot

@mention the assigned AE in the deal’s note thread with the deal value estimate.

The estimate is the CSM’s best guess and is not a commitment. The AE will refine it. Format: ‘@[AE name] · expansion signal from [date] · est. $[ARR] · listen: [Gong URL]’. Including the date matters because the AE may not pick up the deal for 24 to 48 hours and needs the call freshness anchor to know whether to call the same week or wait.

Expected: The assigned AE has a HubSpot notification with everything they need to respond to the customer in the same week the signal surfaced.

Hands your agent your team's exact steps

Your agent executes the documented procedure in order, against the applications named at each step, producing consistent output across human and agent runs.

Book a demo

Related patterns

How this pattern connects to other patterns in the library.

Alternative to

Creating a Risk CTA after a health drop

Often previous

Mining Gong for QBR talking points Updating Gainsight from a QBR recording Logging the QBR outcome in HubSpot

Lets your agent confirm the match and its scope

Alternative patterns let your agent compare candidates and select the closest match. Previous and next patterns define position in the workflow, so the agent operates within the scope of this one.

Supporting actions

Actions that provide evidence for this pattern.

Created HubSpot deal ‘Apex Marine · Expansion · 25 add’l seats’ tagged expansion-within-renewal

Saved 3 expansion clips to Expansion signals folder from Northwind Logistics QBR

@mentioned @priya.raman on Helios Energy 2yr commit deal with Gong moment URL

Routed Beacon Hospitality SSO add-on signal to AE @ae.jordan via deal note

Shows your agent the evidence behind the pattern

Each pattern is derived from captured action sequences. Your agent can reference the source actions to verify any field, so nothing it acts on is authored by hand or hallucinated.

Metadata

Timestamps and identifiers.

Evidence	Observed 16 times across 4 connections
Applications	HubSpot, Gong
First seen	16 Feb 2026, 11:08
Last seen	6 May 2026, 16:42

Helps your agent rank patterns by confidence

Action count and last-seen timestamp weight each pattern by frequency and recency, so your agent selects the highest-scoring match rather than the first returned.

Questions

Frequently asked questions

Book a demo View all examples

Speak to the founder

Get a demo. Watch a live capture, then an AI agent query the result.

Ask anything. Pricing, security or integrating with your stack.

No purchase obligation

Book a call

Start capturing

Record in minutes. Install once and work as normal.

Plug AI agents in. One API call from any AI agent stack.

Refund on unused credits if you cancel