Quick Prompts: Business Meeting
Real-time AI assistance for professional meetings, team discussions, and collaborative work sessions.
Business Meeting quick prompts are designed for professional settings where you're collaborating with colleagues, clients, or stakeholders. Whether you're in a strategy session, project update, team sync, or client call, these prompts help you stay engaged, contribute meaningfully, and lead effectively.
Each goal category addresses a different aspect of meeting participation. You might use "Help Understand" prompts during a technical discussion where you're less familiar with the subject matter, then switch to "Contribute Ideas" when brainstorming solutions.
Goal: Help Understand
When this applies: You're in a meeting where complex information is being shared—perhaps a technical review, financial presentation, or strategy discussion—and you need help processing what's being said. This is especially useful when you've joined a meeting late, are less familiar with the topic, or when speakers are using specialized terminology.
Ideal meeting types: Technical reviews, financial updates, cross-departmental meetings, onboarding sessions, client briefings where you're new to the account.
💡Summarize last 5 minutes
What it does: Provides a concise recap of the key points, decisions, and topics covered in the last 5 minutes of discussion.
When to use it:
You briefly stepped away (grabbed coffee, answered an urgent message) and need to catch up
Your attention drifted during a complex explanation and you want to ensure you didn't miss anything critical
The conversation moved quickly through several topics and you want to consolidate your understanding
You're multitasking in a lower-priority meeting but need to stay informed
Example scenario: You're in a quarterly planning meeting and had to step out for 3 minutes to handle an urgent Slack message from a direct report. When you return, the team has moved from discussing Q3 results to Q4 priorities. Use this prompt to quickly understand what was covered while you were away, including any decisions made or action items assigned.
What to expect: A brief, bullet-point style summary focusing on main topics discussed, any conclusions reached, and names mentioned in connection with specific items.
💡Translate what was said
What it does: Restates the recent discussion in your preferred language, maintaining the meaning and context of the original conversation.
When to use it:
You're in a multilingual meeting and someone spoke in a language you're less fluent in
Technical jargon was used that you understand better in your native language
You want to ensure you correctly understood nuanced points made in a second language
You're preparing to respond and want to formulate your thoughts in your preferred language first
Example scenario: You're on a global team call where colleagues switch between English and German. A German colleague just made an important point about a regulatory requirement, speaking quickly in German. You understood the gist but want to make sure you caught the specifics before the team moves on.
What to expect: A clear restatement of the recent discussion translated into the language Hedy has identified as your preference (or the meeting's primary language if no preference is set).
💡Explain it like I'm 5
What it does: Breaks down complex concepts, technical terms, or intricate processes into simple, accessible language using the "ELI5" method—clear explanations without jargon.
When to use it:
A technical team is discussing implementation details that are outside your expertise
Financial or legal terminology is being used that you're not familiar with
You need to understand something well enough to explain it to others later
You're feeling lost but don't want to interrupt the flow by asking basic questions
Example scenario: You're in a product roadmap meeting where the engineering lead is explaining a proposed microservices architecture migration. Terms like "containerization," "Kubernetes orchestration," and "service mesh" are flying around. You need to understand the business implications to provide input, but the technical details are over your head.
What to expect: A straightforward explanation that strips away jargon, uses analogies where helpful, and focuses on the practical meaning and implications rather than technical specifics. Written for an intelligent adult, not literally a child.
💡Request concept clarification
What it does: Identifies a specific confusing point from the recent discussion and helps you formulate a targeted, professional question that shows you've been paying attention while seeking clarity.
When to use it:
Something specific was unclear but you're not sure how to ask about it without seeming unprepared
You want to ask a clarifying question but need help phrasing it diplomatically
Multiple concepts were discussed and you're confused about how they connect
You sense others might also be confused and a well-phrased question would help everyone
Example scenario: During a budget review, the CFO mentioned something about "capitalizing development costs" versus "expensing them" and how this affects the P&L timing. You know this is important for your project's perception by leadership, but you don't fully understand the distinction or its implications.
What to expect: A suggested question that addresses the specific point of confusion, phrased in a way that sounds informed rather than lost. The prompt will also explain what was likely meant, so you can decide whether you still need to ask or if the explanation was sufficient.
Goal: Lead the Meeting
When this applies: You're facilitating, chairing, or playing a leadership role in guiding the discussion. This could be as the formal meeting organizer or simply someone who wants to help move the conversation forward productively. These prompts help you keep discussions on track, ensure important topics are covered, and drive toward outcomes.
Ideal meeting types: Team meetings you're running, project standups, strategy sessions, problem-solving discussions, any meeting where you feel responsible for ensuring productive outcomes.
💡Outline next steps
What it does: Distills the current discussion into 3 clear, actionable next steps that align with what's been discussed.
When to use it:
A topic has been thoroughly discussed and it's time to move toward action
The conversation is going in circles and you want to crystallize what should happen next
You're wrapping up the meeting and want to ensure everyone leaves with clarity
You sense the team agrees on a direction but hasn't explicitly stated what that means in practice
Example scenario: Your team has spent 20 minutes discussing a customer complaint about slow response times. Various causes and solutions have been proposed—more staff, better tooling, process changes. As the discussion winds down, you want to capture specific actions rather than letting it end with vague agreement that "something should be done."
What to expect: A numbered list of 3 concrete next steps, each specific enough to be actionable. Steps will be based on what's been discussed, not generic suggestions. When possible, they'll indicate who might be responsible.
💡Identify blindspots
What it does: Analyzes the discussion so far and highlights 1-2 critical topics, perspectives, or considerations that haven't been addressed but should be.
When to use it:
Before concluding a topic, you want to make sure nothing important was missed
The team seems to be converging on a decision quickly—perhaps too quickly
You're making a significant decision and want a sanity check on your discussion coverage
You have a nagging feeling something's being overlooked but can't pinpoint what
Example scenario: Your team is excitedly planning a product launch, discussing marketing channels, pricing, and the launch date. Everyone's enthusiastic and ready to commit. Before you finalize, you want to check if the group has considered risks or dependencies that enthusiasm might be masking.
What to expect: One or two specific blindspots relevant to the current discussion—not generic concerns, but issues specifically missing from what's been said. Each will include a brief explanation of why it might matter.
💡Challenge idea constructively
What it does: Provides a way to play devil's advocate on the main idea being discussed, framed as questions or considerations that strengthen rather than dismiss the idea.
When to use it:
Groupthink seems to be setting in and you want to stress-test the emerging consensus
You have concerns but want to raise them diplomatically
An idea sounds good but you want to make sure it's been properly vetted
You're the designated "red team" or devil's advocate in the discussion
Example scenario: A colleague has proposed changing your CRM system to a new platform. Several team members are enthusiastically agreeing, citing various frustrations with the current system. You want to make sure the team has considered migration costs, learning curves, and integration challenges before committing.
What to expect: A constructive critique framed as questions or considerations rather than objections. The tone will be collaborative ("Have we considered...?" or "One thing worth exploring...") rather than dismissive.
💡Resolve disagreements
What it does: Identifies any tensions or conflicting viewpoints in the discussion and suggests diplomatic language to address them constructively.
When to use it:
Two or more participants have expressed opposing views and the conversation is becoming tense
A disagreement is being avoided rather than addressed, causing awkwardness
You sense underlying conflict that needs to be surfaced and resolved
You're mediating between parties with different priorities
Example scenario: In a resource allocation meeting, the sales team is pushing for more marketing budget while operations is advocating for infrastructure investment. The discussion is becoming heated, with each side dismissing the other's priorities. As the meeting leader, you need to acknowledge both perspectives and find common ground.
What to expect: If conflicts exist, specific language to acknowledge different viewpoints and redirect toward resolution. If no significant disagreements are apparent, the prompt will say so and keep the response brief.
💡Recap decisions and actions
What it does: Summarizes the key decisions made during the meeting and lists action items with owners and deadlines where mentioned.
When to use it:
Before ending the meeting, you want to confirm what was decided
Multiple discussions happened and you need to consolidate the outcomes
You want to prepare content for meeting notes or a follow-up email
You're concerned that not everyone has the same understanding of what was agreed
Example scenario: You've had a 45-minute project review meeting covering timeline changes, budget adjustments, and resource reallocation. Multiple decisions were made throughout. Before ending, you want to recap everything clearly so everyone leaves aligned.
What to expect: A structured summary with two sections: (1) Decisions made—what the team agreed to, and (2) Action items—who is doing what, with deadlines if mentioned. If no clear decisions or actions were captured, the prompt will note that as well.
Goal: Contribute Ideas
When this applies: You want to actively participate and add value to the discussion, whether by answering questions, sharing insights, or proposing solutions. These prompts help you contribute meaningfully even when you're not the subject matter expert or when you're having trouble finding an opening.
Ideal meeting types: Brainstorming sessions, problem-solving discussions, strategy meetings, client presentations, any meeting where your input is expected or valued.
💡Say something smart
What it does: Suggests a single, impactful statement relevant to the recent discussion that demonstrates insight and could leave a lasting impression.
When to use it:
You want to make a memorable contribution but aren't sure what to say
The discussion is on a topic where you have less expertise but still want to add value
You're in a meeting with senior stakeholders and want to demonstrate your thinking
There's a pause in conversation and you want to contribute meaningfully
Example scenario: You're in a leadership meeting discussing market expansion. More senior colleagues are debating specific markets. You have thoughts but don't want to just restate what others have said. You want to contribute something that shows strategic thinking and gets remembered.
What to expect: A single, polished statement (1-2 sentences) that's relevant to the recent discussion, demonstrates insight, and could realistically be delivered by you. It will be memorable and substantive, not generic.
💡Answer the last question
What it does: Identifies the most recent question asked by a participant and provides a thoughtful answer you can use or adapt.
When to use it:
Someone asked a question and you want help formulating a good response
You know the answer but want help articulating it clearly
A question was asked to the group and you want to step up
You weren't sure if something was a rhetorical question or one that needed an answer
Example scenario: The marketing director asks, "How are our competitors handling this privacy regulation change?" There's a pause. You have some knowledge about this but want to make sure you answer comprehensively and accurately.
What to expect: The response will first state what question was identified (to confirm it caught the right one), then provide a substantive answer based on the meeting context. If no clear question was asked recently, it will say so.
💡Share a strategic insight
What it does: Provides a concise, strategic observation that demonstrates deep understanding of the topic and its business implications.
When to use it:
You want to elevate the discussion beyond tactical details to strategic thinking
The team is focused on implementation but should consider bigger-picture implications
You want to demonstrate business acumen in front of senior colleagues
You sense a strategic angle that hasn't been articulated yet
Example scenario: Your team is discussing the specifics of a new customer onboarding process—workflow steps, documentation, tooling. You want to contribute a strategic perspective about how this connects to customer lifetime value or competitive differentiation.
What to expect: A single, strategic observation that connects the current discussion to broader business implications. It will avoid repeating what's already been said and focus on demonstrating strategic thinking.
💡Propose creative solution
What it does: Suggests an innovative, out-of-the-box approach to the main challenge being discussed—something that might not have been considered yet.
When to use it:
Traditional solutions have been proposed but none seem quite right
The team is stuck in conventional thinking and could use a fresh perspective
You're in a brainstorming session where creativity is valued
You want to be seen as an innovative thinker
Example scenario: Your team is discussing how to reduce customer churn. The usual ideas have been mentioned—better support, loyalty programs, exit surveys. You want to propose something creative that could differentiate your approach.
What to expect: A creative solution relevant to the specific challenge being discussed, not a generic innovation. It will be practical enough to be considered seriously while being distinctive enough to spark new thinking.
💡Combine and enhance ideas
What it does: Synthesizes multiple ideas that have been shared into a stronger, unified concept that builds on each contribution.
When to use it:
Several good ideas have been proposed and you see how they could work together
You want to build bridges between different participants' contributions
The team is debating between options that might not be mutually exclusive
You want to demonstrate collaborative thinking and add value without dismissing others' ideas
Example scenario: During a product feature discussion, one colleague suggested adding AI recommendations, another proposed better filtering, and a third mentioned personalization. You see how these could be combined into a comprehensive approach.
What to expect: A synthesized concept that explicitly references and combines the ideas that were shared, explaining how they enhance each other. This demonstrates you were listening and can think integratively.
💡Ask thought-provoking question
What it does: Provides a thought-provoking, open-ended question designed to deepen the discussion and challenge the team to think more critically.
When to use it:
The discussion feels surface-level and could benefit from deeper exploration
You want to contribute by facilitating better thinking rather than providing answers
The team is rushing toward a decision and should consider implications more carefully
You want to demonstrate intellectual engagement without claiming expertise you don't have
Example scenario: Your team is quickly agreeing on a new pricing strategy. Rather than objecting or proposing alternatives, you want to ask a question that helps everyone think more carefully about assumptions and implications.
What to expect: A single, well-crafted question that's relevant to the current topic, challenges assumptions, and stimulates deeper discussion. It will be phrased in a way that's easy to remember and deliver naturally.
Goal: Make Decisions
When this applies: The meeting is focused on evaluating options and making choices. These prompts help you analyze alternatives, assess risks, and build alignment around decisions.
Ideal meeting types: Decision-making meetings, vendor selection discussions, strategy reviews, project prioritization sessions, any meeting where you need to choose between options.
💡Analyze pros and cons
What it does: Evaluates the advantages and disadvantages of each option being considered in the current discussion.
When to use it:
Multiple options are on the table and you need a balanced view
The discussion seems biased toward one option and you want a more objective assessment
You need to present a summary to others who weren't in the meeting
You're struggling to weigh competing considerations
Example scenario: Your team is debating whether to build a feature in-house or use a third-party solution. Strong opinions exist on both sides. You want to step back and get a clear, unbiased comparison of the trade-offs.
What to expect: A structured analysis of each option mentioned, with specific pros and cons drawn from the discussion. The analysis will be balanced, presenting both sides fairly.
💡Clarify decision criteria
What it does: Helps define and articulate the key objectives and criteria that should guide the decision being made.
When to use it:
The team is debating options without agreeing on what matters most
Different stakeholders seem to be using different criteria to evaluate options
You want to establish shared evaluation standards before getting too deep into comparison
The discussion is going in circles because there's no clear framework
Example scenario: Your team is evaluating three vendors for a new software tool. Different people are championing different options based on price, features, integration ease, and vendor reputation—but there's no agreement on which factors matter most.
What to expect: A summary of the key objectives and criteria that appear most relevant to the decision at hand, organized in a way that could help the team align on priorities.
💡Compare options on key factors
What it does: Creates a brief comparison of the main options being considered, showing how each performs against the key decision criteria.
When to use it:
You want a structured side-by-side comparison of alternatives
The team has discussed criteria and needs to apply them to the options
You're preparing to make a recommendation and want data to support it
Complex trade-offs are making it hard to compare options mentally
Example scenario: After 30 minutes of discussion about three potential marketing agencies, you want to summarize how each compares on the factors the team has discussed: cost, industry experience, creative capabilities, and turnaround time.
What to expect: A concise comparison matrix or summary showing how each option performs on the key factors discussed. May include a simple scoring system if appropriate.
💡Evaluate risks and mitigations
What it does: Identifies the top risks or potential unintended consequences of the preferred option, along with possible strategies to address them.
When to use it:
The team is converging on a choice and you want to ensure risks have been considered
You're about to commit resources and want to understand what could go wrong
Stakeholders need assurance that risks have been evaluated
You want to be prepared with mitigation strategies for likely objections
Example scenario: The team has agreed to proceed with an aggressive product launch timeline. Before finalizing, you want to articulate the key risks (scope creep, quality issues, team burnout) and have mitigation strategies ready.
What to expect: Two to three key risks specific to the decision being made, each with a brief explanation of why it matters and a suggested mitigation approach.
💡Build team alignment
What it does: Suggests an approach to bring stakeholders together around the emerging decision, addressing concerns and highlighting shared benefits.
When to use it:
Some team members seem hesitant about the direction being taken
You need buy-in from people with different priorities
The decision requires collective commitment to succeed
You want to move from tentative agreement to genuine alignment
Example scenario: The team is leaning toward a significant process change, but the operations lead seems reluctant and the sales team has expressed concerns about disruption. You need to build genuine alignment before proceeding.
What to expect: Specific points that address the concerns of different stakeholders while emphasizing shared benefits. May include suggested language for acknowledging reservations and building commitment.
Goal: Demonstrate EQ
When this applies: You want to strengthen relationships, improve team dynamics, or navigate the interpersonal aspects of the meeting. These prompts help you build rapport, diffuse tension, and show emotional intelligence.
Ideal meeting types: Team building sessions, one-on-ones, tense discussions, cross-functional meetings with new colleagues, any meeting where relationship dynamics matter as much as content.
💡Say something funny
What it does: Suggests something lighthearted or humorous that could help you appear more approachable and strengthen relationships with others in the meeting.
When to use it:
The meeting has been intense and could use some levity
You want to build rapport with colleagues you don't know well
You want to be seen as personable, not just professional
There's a natural opening for humor that you don't want to miss
Example scenario: You're in a planning meeting that's been running long and everyone looks tired. You want to lighten the mood before diving into the next topic, making yourself more relatable in the process.
What to expect: A contextually appropriate humorous comment or observation that's safe for professional settings. The humor will be gentle and inclusive, not sarcastic or at anyone's expense.
💡Tell a dad joke
What it does: Provides a classic "dad joke"—the kind of corny, harmless humor that makes people groan and smile at the same time.
When to use it:
You want guaranteed-safe humor that can't possibly offend
The team knows you for your cheesy jokes and you want to maintain that reputation
You want to break the ice with something universally inoffensive
A groan-worthy pun seems appropriate for the moment
Example scenario: You've just finished a productive but intense quarterly review. Before ending the meeting, you want to leave everyone with a smile—something light and memorable, even if it makes them roll their eyes.
What to expect: A classic dad joke, ideally connected to something recently discussed if possible. Expect eye-rolls accompanied by reluctant smiles.
💡Identify common ground
What it does: Identifies shared interests, goals, or experiences that you might have with other meeting participants, based on the discussion.
When to use it:
You're meeting with people you don't know well and want to build connection
The meeting has stakeholders with different priorities that need bridging
You sense an opportunity to strengthen a relationship
You want to transition from transactional to more personal interaction
Example scenario: You're in a cross-functional meeting with someone from another department you'll need to collaborate with. You want to find something you have in common to build rapport beyond this project.
What to expect: Specific shared interests or goals identified from the conversation, along with natural language to articulate them without seeming forced.
💡Reduce conversation tension
What it does: Suggests diplomatic language to de-escalate tension or negative emotions in the current discussion, redirecting toward constructive dialogue.
When to use it:
The discussion has become heated or confrontational
Someone seems upset or defensive
You can feel tension building and want to prevent escalation
An important relationship is at risk because of the current dynamic
Example scenario: A colleague just criticized another team's work quite harshly, and you can see the other team lead's face tightening. The conversation is about to go sideways unless someone intervenes diplomatically.
What to expect: A specific statement you can use to acknowledge the tension, validate concerns, and redirect the conversation constructively. The language will be calming without dismissing legitimate issues.
💡Address potential biases
What it does: Identifies cognitive biases that might be influencing the current discussion and suggests a tactful way to bring attention to them.
When to use it:
You notice the group seems to be falling into groupthink or confirmation bias
Recent events might be disproportionately influencing the discussion (recency bias)
The team seems anchored on the first idea proposed
You want to improve decision quality by surfacing hidden assumptions
Example scenario: After a recent customer complaint went viral, your team is proposing dramatic changes to customer service. You sense this is an overreaction driven by a single visible incident rather than systematic data.
What to expect: Identification of a specific bias that appears to be at play, along with diplomatic language to raise awareness without making others feel criticized.
💡Make discussion more inclusive
What it does: Suggests ways to ensure all voices are heard, particularly from those who may not have had a chance to contribute.
When to use it:
Certain people have dominated the conversation while others haven't spoken
You notice someone trying to speak but getting talked over
Important perspectives might be missing from the discussion
You want to model inclusive leadership behavior
Example scenario: During a product roadmap discussion, the most senior and extroverted team members have been driving the conversation. The UX designer and junior developer haven't said anything, but their perspectives are valuable.
What to expect: A specific approach to invite quieter participants into the discussion naturally, without putting them on the spot or making the situation awkward.
💡Acknowledge team progress
What it does: Helps you recognize and celebrate the team's efforts and accomplishments, even when goals haven't been fully achieved.
When to use it:
The team has been working hard and deserves recognition
Morale seems low despite meaningful progress being made
You want to end the meeting on a positive, motivating note
Specific contributions should be highlighted
Example scenario: Your project is behind schedule, and the mood is discouraged. But the team has actually overcome significant obstacles and made real progress. You want to acknowledge this without seeming to minimize the remaining challenges.
What to expect: Specific accomplishments from the discussion to highlight, with language that genuinely celebrates progress while remaining honest about where things stand.
Goal: Drive Sales
When this applies: You're in a conversation with prospects, clients, or partners where the goal is to advance a business relationship or close a deal. These prompts help you uncover needs, handle objections, and move toward commitment.
Ideal meeting types: Sales calls, client presentations, discovery meetings, negotiation sessions, partnership discussions, account reviews.
💡Uncover client's pain points
What it does: Identifies the key challenges, frustrations, or unmet needs the client has mentioned or implied, and suggests how to acknowledge and address them.
When to use it:
You want to make sure you've fully understood what's driving the client's interest
The client has mentioned problems that you can address but hasn't fully articulated them
You need to transition from listening to proposing solutions
You want to demonstrate that you've been paying attention and understand their situation
Example scenario: You're 20 minutes into a discovery call with a potential client. They've mentioned several frustrations with their current vendor—response times, reporting quality, integration issues. You want to summarize these effectively before presenting your solution.
What to expect: A summary of the key pain points identified from the conversation, organized by importance, with suggested language to acknowledge them empathetically.
💡Emphasize relevant benefits
What it does: Identifies the product or service benefits most relevant to what the client cares about, based on the conversation so far.
When to use it:
You're about to present your solution and want to lead with the most compelling benefits
The client has expressed specific needs that map to your strengths
You want to avoid generic pitching and personalize your value proposition
You're not sure which of your many features to emphasize
Example scenario: The prospect has emphasized speed of implementation and ease of use. Your product has many features, but you want to focus your pitch on what matters most to them rather than running through everything.
What to expect: One or two key benefits specifically matched to the client's expressed needs, with suggested language that connects your capabilities to their priorities.
💡Showcase my expertise
What it does: Identifies an opportunity to demonstrate your deep knowledge and position yourself as a strategic partner rather than just a vendor.
When to use it:
You want to differentiate yourself from competitors through expertise
The conversation offers an opening to share valuable insights
You want to build credibility before discussing your solution
The client seems to be evaluating multiple options and you need to stand out
Example scenario: The client is asking about industry trends and best practices. This is your opportunity to demonstrate thought leadership before they've even heard your pitch.
What to expect: An insight or perspective relevant to the client's business that demonstrates your expertise without being preachy, along with how to naturally share it.
💡Elevate to strategic discussion
What it does: Suggests how to move the conversation beyond product features to strategic business value, positioning you as a partner rather than a vendor.
When to use it:
The discussion is getting bogged down in feature comparisons
You want to reframe the conversation around business outcomes
The client seems focused on price and you need to shift to value
You're trying to reach higher-level decision makers
Example scenario: The procurement team is focused on line-item pricing. You want to shift the conversation to total cost of ownership, business impact, and strategic alignment—factors where you can differentiate more effectively.
What to expect: A question or statement that reframes the discussion around strategic concerns, tailored to the context of the current conversation.
💡Address client's objection
What it does: Identifies objections or hesitations the client has expressed and suggests tactful ways to address them without being defensive.
When to use it:
The client has raised a concern that could derail the deal
You sense hesitation but aren't sure exactly what's causing it
A competitor has been mentioned favorably
Price or timing objections have come up
Example scenario: The client just said, "This sounds great, but we tried something similar last year and it didn't work out." You need to acknowledge their concern while differentiating your approach.
What to expect: The specific objection identified, along with an approach to acknowledge it, address the underlying concern, and redirect to your value—without being dismissive or defensive.
💡Strengthen client relationship
What it does: Identifies opportunities to build rapport and trust beyond the transactional elements of the conversation.
When to use it:
You want to build a relationship that goes beyond this single deal
The client has shared something personal you can connect with
Trust-building is as important as feature-selling at this stage
You're playing the long game on an important account
Example scenario: During the call, the client mentioned they're dealing with organizational changes and uncertainty. You want to acknowledge this empathetically and position yourself as a supportive partner.
What to expect: Specific connection points from the conversation that could strengthen the relationship, with natural language to build on them.
💡Propose next action steps
What it does: Suggests appropriate next steps to move the sales process forward based on the current stage and the client's engagement level.
When to use it:
The conversation is wrapping up and you need to secure commitment to a next step
You want to maintain momentum without being pushy
You're not sure what the appropriate ask is at this stage
The client seems interested but hasn't committed to anything specific
Example scenario: You've had a productive discovery call and the client seems interested. You want to propose clear next steps—perhaps a demo, a proposal, or a meeting with additional stakeholders.
What to expect: An appropriate next step matched to the conversation's progress, with specific language to propose it confidently while giving the client an easy way to commit.