Build an expansion campaign from product usage and customer success notes
Use usage signals, renewal context, and CS notes to find expansion opportunities and create segmented customer campaigns with relevant messaging.
What you will have
A customer expansion campaign with segments, message angles, email copy, CSM notes, and performance tracking.
Setup time
3-5 hours
Time saved
6-10 hours per expansion campaign
Estimated cost
$0 to $400 per month
Tools used
5 tools
Why this works
Expansion campaigns fail when they treat customers like prospects. Existing customers have product history, adoption gaps, success moments, and account context. This workflow uses those signals to create relevant expansion plays while keeping CSM review in the loop.
Step-by-step workflow
Preview the workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
1
Assemble the customer signal dataset
1-1.5 hours
1-1.5 hours
In HubSpot, export one row per customer account with company ID, company name, current plan, contract value, renewal date, account owner, lifecycle status, and previous expansion history. Add product-usage fields for active users, licensed users, feature adoption, usage trend, team or workspace count, and the most recent meaningful activity date. Add customer-context fields for account health, open support issues, escalation status, CSM notes, champion activity, executive sponsor coverage, and active commercial conversations. Load the export into a Google Sheets workbook with separate Raw Export, Working Dataset, Suppression Review, and Data Dictionary tabs, and keep the Raw Export tab unchanged for auditability. Create explicit suppression columns for unresolved support issues, churn risk, payment problems, legal restrictions, active renewal negotiation, existing expansion opportunity, opt-out status, and any CSM-requested hold. Deduplicate by stable HubSpot company ID, reconcile the final row count to the source export, and flag missing renewal dates, owners, or usage timestamps before segmentation begins. Save the cleaned and suppressed population in the Working Dataset tab, with a QA note showing export date, source filters, total accounts, excluded accounts, and unresolved data gaps.
Output
A reconciled customer signal workbook with raw data, normalized fields, suppression flags, and documented data-quality exceptions.
HubSpotGoogle Sheets
Pro tip
Keep the raw CRM export immutable and make every correction in a separate working tab. This lets RevOps or a CSM trace any surprising campaign decision back to the original account record.
2
Create expansion segments
60-75 min
60-75 min
Start in the Google Sheets Working Dataset and calculate the basic signals needed for segmentation, including seat utilization, usage trend, feature breadth, multi-team adoption, renewal proximity, champion activity, and account-health status. Define hard eligibility rules first so accounts with suppressions, stale data, or unresolved customer issues cannot enter a marketing segment regardless of their usage score. Open Claude, start a new chat for the expansion campaign, and paste the prompt below into the main chat composer. Include the cleaned customer dataset, field definitions, product or package expansion options, customer-health rules, suppression policy, and any minimum account-value thresholds as source inputs. Ask Claude to propose four to seven mutually understandable segments, with exact entry criteria, expansion hypothesis, recommended offer, message angle, confidence level, required CSM review, and exclusion logic for each segment. Copy the proposed segment table into a new Segment Map tab in Google Sheets and save the Claude output alongside the workbook for auditability. QA the segment map by testing at least five accounts per segment, confirming that every account satisfies the written criteria and that no suppressed account appears in an eligible segment.
Output
A tested expansion segment map with explicit criteria, confidence, offer fit, review requirements, and suppression rules.
ClaudeGoogle Sheets
Pro tip
Require every segment to explain why expansion is useful to the customer now. A segment based only on account value or renewal timing is a sales priority list, not a customer-relevant campaign.
Prompt template
Create a customer expansion segmentation model from the supplied account dataset.
Source inputs:
- Cleaned customer signal dataset: {{customer_signal_dataset}}
- Field definitions and calculation notes: {{field_definitions}}
- Product or package expansion options: {{expansion_options}}
- Customer-health rules: {{customer_health_rules}}
- Suppression and exclusion policy: {{suppression_policy}}
- Minimum account-value or fit thresholds: {{commercial_thresholds}}
Build 4-7 segments. For each segment, return:
1. Segment name
2. Exact entry criteria using available fields
3. Customer-centered expansion hypothesis
4. Recommended offer or next-best action
5. Primary message angle
6. Confidence level and why
7. Required CSM review
8. Suppression or exclusion criteria
9. Three example account patterns that belong
10. One example that looks similar but must be excluded
Make the segments distinct enough for routing and messaging. Do not use unsupported assumptions, and do not allow commercial value to override customer-health or suppression rules.
Pro workflow preview
Previewing 2 of 7 steps
Pro membership
Unlock the full workflow
Get the remaining 5 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and weekly new workflows.