Thank the prospect for the update and the time they spent evaluating you. Acknowledge their preference without arguing, then ask one optional question or request permission for one specific next step.
Try: “Thanks for letting me know, and for the time you spent evaluating us. If you’re open to sharing, what was the main factor in your decision? I’ll respect your choice either way.”
“Thank you for your consideration” is not inherently wrong. In a competitive conversation, however, it can sound like a final sign-off. The right alternative depends on what the buyer has actually decided. HubSpot’s article on alternatives to “Thank you for your consideration” is editorial sales guidance, not an empirical study proving that a particular phrase or follow-up interval improves conversion.
What to say when a prospect chooses a competitor
Use a simple sequence: acknowledge the decision, ask whether the buyer is willing to share feedback, and make no more than one focused request. Keep the message short and make declining easy.
For optional feedback: “Thanks for letting me know, and for the time you spent evaluating us. If you’re comfortable sharing, what was the main factor in your decision? I’ll respect your choice either way.”
For a clear close: “Thank you for the time you invested in the evaluation. I appreciate the opportunity to be considered.”
For permission to reconnect: “Would it be useful if I checked back around [buyer-agreed date]?”
A buyer’s vendor preference, contract status, and permission for future contact are three separate facts. Verify and record each one independently.
Choose the response that fits the buyer’s situation
Match the message to the status the prospect has stated. Do not use a feedback question or future meeting request to reopen a decision the buyer has clearly closed.
- Clear, final decision: “Thank you for the time you invested in the evaluation. I appreciate the opportunity to be considered.” Close respectfully and do not attach another sales request.
- Feedback is welcome: “If you’re comfortable sharing, which factor mattered most in your decision?” Ask one open question, then listen before probing further.
- Future review may be useful: “Would it be useful if I checked back around [buyer-agreed date]?” Create a reminder only if the buyer agrees.
- Another offer may fit: “We also support [specific need]. Would you like me to send a short overview, or would you prefer to leave it here?” Mention another product or service only when it plausibly addresses the buyer’s need.
Close with appreciation
“Thank you for the time you invested in the evaluation. I appreciate the opportunity to be considered.”
Confirm a date or condition
“Would it be all right if I checked in around [date] to see how the transition is going? If you’d prefer no follow-up, I’ll leave it there.”
Check decision and contract status before trying to win the deal back
“We selected another vendor,” “the agreement is with legal,” and “the contract is signed” describe different states. If you do not know whether the agreement has been signed, record the status as unknown rather than assuming the deal is either recoverable or finished.
Ask a neutral clarification only if the answer changes what you will do: “Has the agreement been signed, or is the decision still going through contracting?” If contracting is incomplete, consult the sales manager before revising price, terms, or scope. Any commercial offer needs pricing authority, a margin check, and a documented approval.
If the contract is signed or the buyer confirms the decision is final, do not reflexively discount. Close respectfully unless the buyer initiates another conversation. A manager-approved offer may be considered when commercial terms are a genuine blocker, but it is not a universally effective tactic.
HubSpot documents closed-won and closed-lost pipeline stages and a deal property called “Closed lost reason.” These fields record CRM state; they do not prove that a recorded reason is complete, accurate, or the cause of a loss. See HubSpot’s documentation on pipeline stages and default deal properties.
Ask for useful feedback without leading the buyer
Start with a low-pressure, open question: “If you’re willing to share, what was the deciding factor?” If the buyer answers and seems willing to continue, ask one neutral follow-up about the relevant dimension: product fit, commercial terms, implementation, timing, risk, or an incumbent relationship.
A question limited to which vendor had the “best technology” can narrow the answer and exclude other reasons that mattered. Asking separately about technology, commercial terms, implementation risk, timing, and the decision process may produce a more useful record than relying on one broad question, but the choice of question should fit the conversation.
Keep the buyer’s explicit words separate from the salesperson’s interpretation. For example, record “Buyer said implementation timing was the deciding factor” as a stated reason. Record “possible concern about our onboarding capacity” as an internal hypothesis, not as a buyer-confirmed fact.
Save the source activity and date with the feedback. HubSpot documents deal properties and reporting on recorded loss reasons, but a report reflects the quality of the data entered. Its sales reporting documentation describes reporting capabilities, not a method for proving why a particular deal was lost.
Do not force one loss reason into every record. Preserve the buyer’s wording, map it to a category only after review, and retain the source activity so another reviewer can distinguish evidence from interpretation.
Agree on future contact instead of prescribing a 12-week check-in
Twelve weeks is an example from sales advice, not a universal interval. Timing should fit the buyer’s stated implementation, review, or contract timeline. Ask permission and capture both the permission and any date or condition the buyer provides.
For example: “Would it be all right if I checked in around [date] to see how the transition is going? If you’d prefer no follow-up, I’ll leave it there.” Do not invent a contract end date or create a follow-up after the buyer declines contact. If the buyer agrees, create one task for the agreed date and assign it to the responsible owner.
HubSpot documents manual task creation, tasks created after logging an activity, and task creation through workflows or sequences. Workflow-created tasks require Professional or Enterprise access according to the cited documentation. Task creation records planned work; it does not establish that a particular interval is optimal. See HubSpot’s task-creation guidance.
A scheduling page can be useful when the buyer has agreed to reconnect. Use a configured page belonging to the intended owner. HubSpot documents sharing scheduling pages, but live availability and automatic booking depend on calendar connection and account settings. Without a connected calendar, a page can operate in offline mode and require manual handling. The source article’s “Insert Meeting Link” is a placeholder, not a ready-made meeting link. See the documentation for sharing scheduling pages and meeting and calendar behavior.
Turn the conversation into a reliable CRM record
A practical record can include decision_status, contract_status, primary_reason, follow_up_permission, follow_up_date, source_activity_id, and reviewed_by. These are proposed field names, not a HubSpot-published schema. HubSpot documents deal properties, notes, record associations, and tasks; the exact workflow below is an implementation pattern.
For a hypothetical conversation in which the prospect says, “We are moving ahead with another provider; legal is reviewing the paperwork,” an optional AI-assisted extraction might draft:
{
"decision_status": "selected_competitor",
"contract_status": "pending_legal",
"stated_reason": null,
"follow_up_permission": "unknown",
"source_activity_id": "activity_789",
"review_status": "pending"
}The values are illustrative. “Legal is reviewing” supports pending legal review, not a signed contract. If the buyer gives no reason or contact preference, preserve those fields as unknown or null rather than filling them by inference.
Deterministic rules are preferable to AI for checking whether a CRM ID exists, whether a date is in the future, whether a buyer has declined contact, and whether an equivalent open task already exists. AI can help draft a summary or suggest a category, but a person should approve consequential CRM changes.
For external processing, separate the conversation event from each extraction attempt. One event row should represent one source conversation. Each model or prompt execution should have its own extraction-run record. Transcript excerpts should be separate citation records, and period-level metrics should be separate aggregate records.
Use a stable event key based on the source system and external conversation ID where available. Give each extraction run a separate ID that includes the event, model version, prompt version, and run identifier. A citation key should identify the extraction run and source segment. An aggregate metric key should identify the account, reporting period, metric definition, and segment definition. Do not use deal_id plus date as a universal key because several calls or runs can share both values.
A lookup-then-create check can race when workers run concurrently. Enforce uniqueness in the integration database or use a transactional upsert. A retry of the same event should update or return the existing event rather than create another note. HubSpot’s note API documentation describes note objects and associations; it does not establish a universal deduplication policy for externally generated notes or tasks.
- Store buyer-stated facts separately from inferred categories and retain source references.
- Use database-enforced uniqueness or a transactional upsert for concurrent retries.
- Require explicit permission before creating a future outreach task.
- Require human approval for stage, contract-status, loss-reason, pricing, and terms changes.
If you are considering an AI-supported conversation workflow, AI agent consulting may be relevant to designing its boundaries and review steps. Convin’s website advertises AI-assisted calls, messages, summaries, tasks, and CRM-related functions. That vendor page does not verify a specific HubSpot integration, field mapping, retention policy, or performance for this use case, so review privacy, access, retention, and vendor requirements separately.
Measure process quality, not just win-backs
Start with measures your team can influence and audit:
- Source coverage: competitive-loss records with a linked source activity divided by all competitive-loss records in the defined period.
- Permission coverage: follow-up tasks with a recorded permission source divided by all follow-up tasks created for competitive losses.
- Duplicate-task rate: duplicate tasks divided by all tasks in the defined cohort, using a consistent definition of “duplicate.”
- Review rate: AI-proposed CRM updates reviewed before commit divided by all AI-proposed updates.
If you measure win-backs, define the cohort, denominator, and observation window. For example, count unique competitive-loss deals that later reopen within a stated period, divided by eligible competitive-loss deals in that cohort. Keep conversation events, extraction runs, deal outcomes, and aggregate metrics at their proper grains. A later sale does not show that a particular phrase caused the result.
Use HubSpot’s closed-lost reason reporting to inspect recorded categories, then review whether those categories are applied consistently. For teams reviewing their CRM setup, HubSpot systems consulting is an optional resource.