What to do after a buying signal: 5 Account-Based sales plays

A signal can create urgency before the account team knows what changed, who owns the relationship, or whether contact is appropriate. Acting too quickly turns useful evidence into duplicate contact, bad timing, and avoidable sender risk.

This guide shows you how to make the most out of buying signals.

It covers five specific account-based sales plays:

1. a former champion changes jobs;
2. a closed-lost account shows new evidence;
3. a customer approaches a product or capacity expansion point;
4. a target account has relevant news or attends a relevant event; and
5. engagement or intent concentrates inside one account.

The first action after a buying signal should usually be an internal decision, not an external message. Preserve the source, confirm the account and person, check ownership and commercial state, identify the relevant buying role, choose the smallest justified action, and define what will stop it.

This article begins after a signal has appeared. It does not attempt to rank every signal or define signal-based selling as a whole.

The signal-based selling guide owns the broad strategy, and the signal-quality article owns the question of which signals deserve attention.

This page answers the next question: what should the account team do now?

What must be checked before a buying signal becomes an action?

A signal changes what the team knows. It does not, by itself, establish that the account is a fit, that a named person is involved in a purchase, that outreach is permitted, or that a sequence is the right next step.

Before any customer-facing action, the team should preserve and review the following fields:

This is intentionally stricter than "signal detected → sequence started." It lets a team distinguish three valid outcomes:

• Act: the evidence, account state, owner, and recipient justify a specific next action.
• Investigate: the signal is relevant, but identity, relationship, buying role, or commercial state needs clarification.
• Hold or reject: the evidence is stale, ambiguous, excluded, already covered, or commercially irrelevant.

A rejected signal is useful data. It shows which sources, matching rules, or play conditions need improvement.

What should the team do when a former champion changes jobs?

A champion job change is a relationship signal, not automatic proof of demand at the new company.

The prior relationship may create a warm path, but the new account still needs to fit, the person's new role still needs to be relevant, and the history still needs to be safe and accurate to reference.

Amplemarket's current past-customer job-change signal page documents monitoring selected former customer contacts for moves.

The Job Change Signal Tracker describes another procedure: compare a known contact's prior company with current enrichment, research the new company, classify uncertain results, and prepare a reviewable re-engagement path.

The live Skill warns that very recent changes may not yet appear in enrichment, so "unable to determine" is a legitimate result.

What should be verified after a champion changes jobs?

Verify:

• the person's identity, new employer, title, and start date;
• the previous relationship and what the CRM actually records;
• whether the person was a champion, user, evaluator, executive sponsor, or simply associated with the account;
• whether the new company matches the current ICP and territory;
• whether the new company is already a customer, active opportunity, partner, competitor, or excluded account;
• who owns the new account and any current conversation;
• which buying role the person may fill now;
• which past result or relationship detail is approved for external reference.

Do not transfer the old role to the new company by assumption.

• A former administrator who becomes a VP may have more influence
• A former champion who moves into an unrelated function may have less relevance.

The job change is the reason to inspect the account, not a substitute for the inspection.

What is the first action after a champion changes jobs?

The account owner can choose among:

• no action because the new company does not fit;
• an internal relationship brief;
• a private request to the former relationship owner for context;
• a short congratulatory message that does not manufacture a business need;
• a one-to-one reconnection grounded in a real shared history;
• limited research into the new company's relevant buying group before deciding whether to multithread.

If the prior relationship is documented and appropriate to mention, the message can acknowledge it.

If the CRM only proves that the person appeared on an old account or deal, do not call them a champion or imply that they endorsed the product.

What should stop the job-change play?

Stop or hold when:

• the move cannot be verified;
• the new employer is outside the ICP or territory;
• the person joined a competitor or an excluded account;
• the previous relationship is unclear or not approved for use;
• another owner has an active opportunity or conversation;
• the person asks not to be contacted;
• the team would need to reveal private customer information to make the message relevant.

Measure verified moves reviewed, ICP-matched new accounts, owner approvals, identity corrections, replies, meetings, and qualified opportunities separately.

Do not treat every detected move as pipeline.

How should a closed-lost account be reactivated after new evidence appears?

Closed-lost status is historical context. It is not a reason to run a recurring "checking in" sequence.

Reactivation becomes defensible when new evidence changes a condition that mattered to the previous decision.

Examples include:

• a prior contact or decision-maker changes role;
• the account engages again with a relevant property or conversation;
• a previously missing requirement is now supported;
• a budget, planning, contract, or renewal window changes;
• the company announces a material operational change; or
• a new stakeholder appears with a different mandate.

Amplemarket's current Signals page documents closed-lost reactivation and Custom CRM Signals. A Custom CRM Signal can start from a CRM report and include mapped context for the subsequent play.

The presence of a closed-lost record alone should not qualify the account; the new evidence is the reason for review.

What should the owner compare with the previous loss?

Review:

• the opportunity, account, and contact records;
• the documented loss reason and date;
• the last substantive buyer conversation;
• commitments, objections, and conditions recorded at the time;
• current account ownership and any new opportunity;
• whether the same people still hold the relevant roles;
• the new evidence and why it could change the decision; and
• whether the old context is accurate and appropriate to reference.

The key question is: what is different now?‍

If the answer is only "six months passed," the team has a schedule, not a buying signal.

What is the first action for a closed-lost account?

The owner can prepare a short brief comparing the old condition with the new evidence, then decide whether to:

• keep the account closed because the loss reason remains unchanged;
• ask a known contact whether the changed condition matters;
• route the account to a new owner or segment;
• reopen discovery around one specific question;
• create a small, reviewed sequence for the relevant people.

Clara's customer story describes a HubSpot-grounded reactivation motion in which the team pulled closed-lost opportunities, used prior-conversation context in AI-assisted drafts, and received replies that reopened old conversations.

That is evidence of one customer's procedure, not proof that every closed-lost record should be contacted or that reactivation caused Clara's broader reported results.

What should stop the closed-lost play?

Stop or hold when the new evidence does not address the loss reason, the account explicitly declined future contact, the prior decision involved a legal or policy restriction, another opportunity is already active, ownership is unclear, the contact has moved and cannot be resolved, or the message would expose private notes.

Measure records reviewed, records with genuinely new evidence, owner acceptance, reopened conversations, qualified reopened opportunities, and progression after reopening.

Keep "record reactivated" separate from "opportunity reopened."

What should happen when product usage or capacity points to expansion?

A product or capacity signal belongs to a customer relationship. The first destination should be the account owner or customer team, not an automated cross-sell sequence.

Product usage, capacity, license utilization, renewal timing, support state, account health, and contract data should come from the systems that authoritatively store them.

Amplemarket can receive permitted first-party conditions through Custom CRM Signals or Custom API Signals, then use mapped context in an approved sales process. Amplemarket is not the source of truth for a customer's contract, usage ledger, support history, or health model.

What must the account owner validate?

Validate:

• what changed in product use or capacity, according to which system and date;
• whether the change represents healthy adoption, a temporary fluctuation, a technical issue, or a data error;
• the customer's current contract, renewal, support, and relationship state;
• active expansion, renewal, or service conversations;
• the adjacent use case or capacity need that may create customer value;
• the existing champion, account owner, customer-success owner, and commercial owner;
• the safest relationship path to the relevant team;
• which product or customer details may be referenced externally.

High usage can support an expansion hypothesis. It can also precede an operational problem. Low usage can indicate whitespace, poor adoption, implementation friction, or churn risk.

Neither should be interpreted without the customer context the account team owns.

What is the first action for a potential expansion?

The first action may be:

• an internal account review;
• a customer-success or account-owner task;
• a usage or capacity check with the existing champion;
• a request for a warm introduction to an adjacent team;
• a small account map for a validated use case;
• a reviewed expansion sequence after the owner confirms the timing and relationship path.

The Wasabi customer story provides a concrete example. Wasabi used custom CRM reports to identify existing customers approaching storage limits and ran monthly add-on plays through Amplemarket.

The story reports that those plays were producing pipeline and closing business. This supports the mechanism for that customer; it does not establish a universal expansion threshold, typical result, or automatic attribution rule.

What should stop the expansion play?

Stop or hold when customer health or support context makes commercial outreach inappropriate, an active renewal or opportunity already owns the conversation, the adjacent use case is not validated, account ownership is disputed, the data is stale, the relationship path is unclear, or private usage and contract facts would need to appear in the message.

Measure hypotheses reviewed, customer-owner approvals, corrections, introductions, qualified expansion conversations, opportunities, and revenue under the company's attribution policy.

This section is limited to the immediate response to a product or capacity trigger; customer-whitespace strategy, relationship mapping, and full expansion-program design require a separate account-expansion guide.

How should sales respond to relevant account news or an event?

Company news and event participation can reveal a change in priorities or create a timely context for research.

Neither proves that the account is buying.

The source may be:

• an official company announcement;
• a regulatory filing or other authoritative record;
• a named conference or webinar attendee record obtained and used lawfully;
• an Amplemarket company-news or event signal;
• an approved partner or first-party event system;
• public-web research performed by an AI client or another connected web tool.

The actor distinction matters.

Amplemarket's current Signals page lists company news and events among supported signal categories.

In an MCP-based workflow, public-web browsing comes from ChatGPT, Claude, or another connected web tool—not from a generic Amplemarket MCP signal-search tool.

How can the team decide whether the event matters?

Ask:

• Is the source original, current, and specific?
• What actually changed at the company?
• Which operational consequence is plausible for the problem we solve?
• What evidence would disprove that consequence?
• Which department and decision roles would own the change?
• Is there an existing relationship, opportunity, customer motion, or event follow-up owner?
• Is direct outreach appropriate, or should the team research first?
• Would mentioning the event be useful to the recipient, or merely prove that the seller saw it?

"The company announced a new region" is evidence. "The CRO now needs our platform" is an inference.

Preserve that distinction in the internal brief and the message.

What is the first action after relevant account news?

• For weak or early evidence, assign research.
• For a clear event with a known owner and relevant person, prepare one role-specific message or task.
• For a strategic account, review buying-group coverage and coordinate the event follow-up across the team.

Do not enroll several executives in the same news-based sequence.

What should stop the news or event play?

• Stop or hold when the source is stale, syndicated without confirmation, unrelated to the use case, based on a sensitive event such as layoffs or a crisis, already covered by an event owner, or too broad to resolve to a credible buying role.
• Stop external action after a reply, meeting, opt-out, source correction, or owner decision changes the account state.

Measure source-verification rate, owner acceptance, time from event to review, research-only decisions, replies, meetings, and opportunity progression.

What should sales do when engagement or intent concentrates in one account?

Concentrated activity can justify an account review when several relevant events occur in a defined window.

Examples include multiple known people replying or meeting, repeated first-party activity from legitimately resolved contacts, a known contact returning after a quiet period, or several distinct sources pointing to the same account.

The evidence must remain at its real level:

• an anonymous website visit is anonymous;
• company-level intent identifies a company, not a buyer;
• an email open can be affected by privacy protection or automated scanning;
• a click does not prove a purchase project;
• a reply or meeting is stronger relationship evidence, but its meaning still depends on content and owner context;
• activity from several people may indicate a buying group, unrelated individual research, or an existing motion already in progress.

How should the account team review concentrated activity?

The owner should:

1. list each event, source, person resolution, and time;
2. separate known people from anonymous or account-level activity;
3. inspect current sequences, replies, meetings, opportunities, and customer state;
4. map the active people to plausible buying roles without presenting inference as fact;
5. pause duplicate or unrelated outreach while the pattern is reviewed;
6. identify the one missing question or stakeholder that matters next;
7. choose one coordinated follow-up.

As of May 2026 Amplemarket allows filtering Contacts by a specific Duo signal and action date, routing Workflows by CRM ownership, and filtering Accounts by custom CRM ownership fields.

These controls can help an operator inspect a defined signal cohort and route it to the accountable owner. They do not determine whether the pattern represents a purchase.

What is the first action after concentrated account engagement?

When a substantive conversation already exists, the owner should take control and pause unrelated automation.

When the evidence is concentrated but anonymous, research the account rather than claiming to know who acted.

When several verified roles engage, prepare a shared account brief and coordinate role-specific follow-up around one account thesis.

What should stop the concentrated-activity play?

Stop or hold when the pattern consists only of opens, bots, duplicated events, anonymous traffic, stale activity, or actions already explained by a current opportunity or campaign.

Pause unrelated sequences after an interested reply, meeting, opportunity creation, owner takeover, opt-out, or identity correction.

Measure signal-to-review time, duplicate-touch prevention, verified engaged-role coverage, owner acceptance, relevant replies, meetings, opportunity creation, and stage progression.

Raw event volume should remain a diagnostic input.

What can Amplemarket do after a signal appears?

Amplemarket can support the path from evidence to reviewed action, but different product surfaces do different jobs:

• Signals, Custom CRM Signals, and Custom API Signals can surface supported public, first-party, CRM, and external events with mapped context. The team defines what qualifies and how long it remains relevant.
• Accounts, Searcher, enrichment, and connected CRM context can help resolve the company, people, ownership, available opportunities, custom fields, and engagement state. CRM context must be connected, available, and authorized for the user.
• Duo can research the account and prepare signal-aware messaging or sequences according to configured settings. The output still needs the account-specific checks described in this guide.
• Workflows is Amplemarket's configured automation surface. It supports triggers, conditions and branches, actions, delays, run settings, CRM updates, list and sequence actions, tasks, enrichment, and exclusions. A Workflow applies the rules the team configures; it does not decide the commercial strategy.
• Amplemarket MCP gives an authenticated ChatGPT or Claude user permission-scoped tools for people and company search, enrichment, accounts, contacts, exclusions, lists, supported draft-sequence work, sequence leads, Unibox, outbox, and analytics.
• MCP sequence tools can create an empty draft, add or update supported linear email, phone, and LinkedIn stages, and enroll or manage leads. A newly created sequence still requires review and launch in the Amplemarket dashboard; sequence-step deletion also remains in the dashboard.
• Analytics can answer documented engagement questions and provide supporting numbers. CRM opportunity and revenue state remains dependent on the connected, authorized record and the company's attribution rules.

This division of work prevents a common product claim error.

If ChatGPT searches the web for recent account news and then uses Amplemarket MCP to inspect the account and prepare a sequence draft, the web research came from the AI client or its web tool. MCP supplied the authorized Amplemarket context and actions.

If an Amplemarket Workflow routes the record after a configured event, the Workflow—not MCP—performed that automation.

Amplemarket's practical advantage for this use case is continuity across supported data, account context, signals, multichannel engagement, delivery controls, and workflow actions.

That continuity reduces handoffs, but it does not remove the CRM, the accountable seller, or a company's customer, legal, and data-governance systems.

When should a team use a modular stack instead?

A modular stack can be the better fit when a company:

• wants a standalone signal or data feed and has no need for native engagement;
• already has reliable identity resolution, CRM routing, exclusions, sequence orchestration, deliverability controls, and analytics across its existing tools;
• has GTM Engineering capacity to maintain connectors, field mappings, retries, permissions, audit paths, and vendor changes;
• needs a specialist system whose depth outweighs the integration cost;
• uses a CRM, customer system, or regional process that the proposed Amplemarket configuration does not support;
• deliberately keeps detection and execution separate for security, procurement, or operating-model reasons.

The tradeoff is operational ownership.

A modular stack can be flexible, but the team must preserve the signal source, account and person identity, CRM owner, exclusions, message context, engagement state, and stop behavior across several systems.

When is Amplemarket not the right fit for this motion?

Amplemarket is not the right answer when the team only needs occasional contact lookup, does not run repeatable outbound or account plays, lacks a clean ownership model, cannot define its allowed actions and exclusions, or expects software to infer customer health, contract truth, or buying authority without authoritative sources.

It is also a poor fit when the buyer expects:

• the MCP connection to expose every signal through a generic signal feed;
• MCP to create or launch Amplemarket Workflows;
• a new MCP-built sequence to launch without dashboard review;
• public-web research to come from Amplemarket MCP alone;
• every CRM field or private system to be available regardless of connection and user permission;
• signals to prove purchase intent; or
• activity metrics to replace opportunity and revenue evidence.

Those are product and operating boundaries, not missing adjectives. A credible evaluation should test the exact signal sources, CRM objects, ownership rules, exclusions, channels, review points, and outcomes the team intends to use.

How should signal-driven account plays be measured?

Measure the quality of the decision path as well as the commercial result:

Keep denominators visible. "Eight meetings" means little without the number of signals reviewed, accounts approved, people contacted, and opportunities qualified.

Compare plays by source, account segment, owner, evidence age, action, and outcome.

Use a cohort design where practical:

1. choose a fixed signal source and date range;
2. record every eligible, held, and rejected account;
3. preserve the owner's decision and reason;
4. connect approved actions to engagement and CRM outcomes;
5. review false positives, collisions, and stop behavior;
6. change one rule at a time.

This makes the process learnable. It also prevents an impressive customer story or one successful account from becoming an assumed benchmark.

How was this guide researched?

This guide was checked against public sources available on July 28, 2026:

• the current Amplemarket Signals page and past-customer job-change page;
• current descriptions of Custom CRM Signals, Custom API Signals, and Amplemarket Workflows;
• the May 2026 product update for CRM-owner routing, signal filters, and MCP sequence creation;
• current Amplemarket MCP documentation and the MCP sequence-building guide;
• the live Job Change Signal Tracker; and
• the published Clara, Wasabi, and SpendLab customer stories.

The customer examples are individual, customer-reported results. They explain how a motion worked for that customer; they are not controlled comparisons, typical results, or guarantees.

Research and disclosure

Sources: Official product documentation and product pages checked for this article. Public customer, pricing, and review evidence is used only when the named source is linked.

Check date: July 28, 2026.

Disclosure: Amplemarket publishes this article and competes in the sales technology categories discussed.

Not verified (NV): A capability or claim is marked NV when it could not be confirmed in a current public source. NV does not mean the capability is absent and is not scored as zero.