These prompts are designed for current Breeze Assistant behavior in HubSpot. They perform best when they include a clear task, defined context, specific data sources such as CRM records or files, and a structured output format. Breeze is particularly effective at synthesizing relationship data, identifying patterns, preparing teams for interactions, and helping structure follow-up actions and workflows.
Fintech is not a single industry but a convergence of financial services, software, infrastructure, and user experience. That creates unique operational challenges: rapid product iteration, onboarding friction, regulatory considerations, technical integrations, and a constant need to balance growth with risk. Sales cycles often involve technical stakeholders, compliance reviews, and product evaluation—not just commercial conversations.
Because of this, the most effective use of Breeze in fintech environments is around onboarding visibility, activation tracking, product adoption signals, integration progress, support trends, and cross-functional coordination. These prompts are designed to reflect those realities and help teams identify friction, accelerate revenue, and improve customer experience.
Use your portal’s exact pipeline names, stages, product lines, onboarding statuses, segments, and property names in the brackets below. That will improve output quality and make the results more actionable.
10 Breeze-optimized prompts for FinTech
1) Customer onboarding and activation briefing
Best for account managers, onboarding teams, and customer success preparing for activation calls.
Prepare me for my meeting with [CONTACT NAME] at [COMPANY NAME]. Use the contact, company, associated deals, notes, emails, calls, meetings, tickets, and onboarding activity from the last [TIMEFRAME]. Give me: 1. a 1-paragraph relationship summary, 2. current onboarding or activation status, 3. any blockers, delays, or technical issues, 4. key milestones completed and what remains, 5. 5 smart questions I should ask to move activation forward, 6. a concise follow-up email draft. Write this for a fintech onboarding or customer success professional.
2) Activation and onboarding risk scan
Useful for identifying customers that are unlikely to go live or fully adopt the product.
Review accounts and deals in pipeline [PIPELINE NAME] where onboarding or activation is in progress. Identify the top 20 accounts that appear at risk based on: - long stage duration, - missing onboarding steps, - incomplete integration or API setup, - overdue tasks, - low engagement, - notes indicating confusion or dependency on engineering or compliance teams. For each account, provide: - why it appears at risk, - current onboarding stage, - what is blocking progress, - recommended next best action, - a short internal or external follow-up message. Output as a prioritized list from highest to lowest risk.
3) Product adoption and usage signal analysis
Strong fit for product, growth, and customer success teams looking to identify expansion or churn signals.
Analyze CRM activity, notes, tickets, and engagement data for customers using [PRODUCT OR FEATURE]. Identify patterns that suggest: - strong adoption, - partial adoption, - declining usage or disengagement, - opportunities for expansion. For each segment, provide: - defining characteristics, - key signals, - risks or opportunities, - recommended actions for the team, - a sample outreach message. Keep the output practical for a fintech growth or customer success team.
4) Integration and technical blocker identification
Useful for surfacing where deals or accounts are stuck due to technical dependencies.
Analyze open deals and active accounts involving [INTEGRATION, API, OR PLATFORM]. Identify where progress is blocked based on: - notes mentioning technical issues, - long delays between activities, - unresolved support tickets, - unclear ownership between teams, - missing technical requirements or documentation. For each flagged account or deal, provide: - the likely blocker, - which teams are involved, - what is unclear or missing, - recommended next step, - a suggested internal summary for alignment. Focus on improving coordination between sales, product, and engineering.
5) Fintech deal complexity and slippage review
Strong fit for sales teams managing multi-stakeholder and technically complex deals.
Analyze open deals in pipeline [PIPELINE NAME] with expected close dates in [DATE RANGE]. Flag which deals are most likely to slip based on: - stage duration, - last activity date, - missing stakeholder engagement, - unresolved technical or compliance questions, - overdue tasks, - notes indicating uncertainty or delays. For each at-risk deal, show: - current stage, - why it appears at risk, - what is missing, - the best next move, - a suggested owner action for this week. Start with an executive summary, then provide the deal-by-deal breakdown.
6) Support and issue trend clustering
Helpful for identifying systemic product or operational issues.
Analyze tickets, support conversations, and notes from the last [90/180] days for [PRODUCT OR SEGMENT]. Cluster the top issues into categories such as: - integration errors, - onboarding confusion, - API failures, - reporting discrepancies, - transaction issues, - user experience friction. For each category, provide: - issue summary, - likely root cause, - representative examples, - whether this is a product, process, or support gap, - recommended action. Keep the output actionable for product and operations teams.
7) Expansion and upsell opportunity scan
Useful for identifying customers ready to adopt additional features or products.
Review existing customers using [CURRENT PRODUCT] but not [TARGET PRODUCT OR FEATURE]. Use CRM history, notes, tickets, and engagement activity to identify the top 15 expansion candidates. For each candidate, provide: - why they are a fit, - signals supporting the recommendation, - likely angle for the conversation, - any risks to address first, - a personalized outreach draft. Focus on product usage and relationship signals.
8) Lost deal pattern analysis
Useful for identifying why fintech deals are lost and how to improve win rates.
Review all closed-lost deals in pipeline [PIPELINE NAME] from the last [6/12] months. Group the losses by: - segment, - product type, - objection themes, - competitor mentions, - stage where the deal was lost, - common missing capabilities or integrations. Then tell me: 1. the top 5 loss patterns, 2. what we should change in our sales process, 3. what product or enablement gaps may exist, 4. 3 actions we should take this quarter to improve win rate.
9) Ideal customer profile generation
Helpful for refining targeting based on real customer data.
Analyze our closed-won deals and strongest customer relationships from the last [12/24] months for [PRODUCT OR PLATFORM]. Create an ideal customer profile using: - company types, - size indicators, - geography, - contact roles, - engagement patterns, - sales cycle signals, - common use cases from notes and calls, - objections that were successfully overcome. Then provide: 1. the profile summary, 2. key stakeholders to target, 3. top messaging angles, 4. early warning signs of poor-fit prospects, 5. the top 20 current open deals or companies that match this profile.
10) Workflow builder for onboarding and support escalation
A strong operational use case for aligning teams across growth, onboarding, and support.
Build a workflow for [PIPELINE NAME OR TICKET PIPELINE NAME]. Goal: identify accounts that are stalled, at risk, or experiencing onboarding or support issues. Criteria: - onboarding stage has been active for more than [X] days, - no activity in [Y] days, - ticket priority is [HIGH] with no response in [X] hours, - repeated support tickets within [TIMEFRAME], - notes indicating confusion, delays, or technical blockers. Create a workflow with: - enrollment triggers, - if/then branches, - internal notifications, - task creation, - internal notes summarizing issues, - optional customer follow-up drafts, - exit criteria, - suppression logic. Show the workflow in a clear step-by-step structure.
Two practical notes
Sensitive data note
Fintech teams should avoid entering highly sensitive information into prompts. This includes authentication credentials, financial account details, transaction-level data, compliance-sensitive information, or anything subject to regulatory protection. Breeze should be used to interpret patterns and coordinate actions based on CRM activity, not to process or expose sensitive data directly.
How to get the most out of Breeze Assistant
For best results, use exact pipeline names, onboarding stages, product lines, and segments in your prompts. Be explicit about what output you want—such as a prioritized list, summary, or outreach draft. The closer the prompt matches how your fintech team actually operates across onboarding, product, and support, the more actionable the output will be.
