What is a sales opportunity? Decide what the buyer’s reply starts.
Decide what a reply actually starts. Compare four requests from the same fictional company, keep quote revisions together and record the reason for your decision.
1,000 credits + 7 days full accessOn first app sign-in · Once per device · No card required
A sales opportunity is a specific possible purchase being discussed with a company. Our early-stage entry rule asks for a buyer-confirmed job, delivery fit and an agreed next action. A request for information alone does not meet that rule. Opening an opportunity does not establish approved budget or a future sale.
Name the work being discussed.
“We spoke with North Equipment” describes a company relationship. “North Equipment is evaluating technical content for two product families” identifies a particular job. An opportunity record should answer that second question: what work is this company considering buying from you?
| Record | What it represents | What it cannot establish alone |
|---|---|---|
| Lead / prospect | A company or person that may fit your service. | An active buying project. |
| Activity / interaction | An event that happened, such as an email or meeting. | That the buyer wants your service. |
| Sales opportunity | A possible purchase of particular work under discussion. | Approved budget or a completed sale. |
| Task | An action someone plans to complete. | That the buyer agreed to it; the task might be your own reminder. |
This page covers opening an opportunity, avoiding duplicate jobs and revising the decision when evidence changes. Use the lead qualification guide to evaluate a prospect and the CRM guide to organize relationship records.
Apply the same entry rule to each reply.
Businesses and CRM products use different thresholds. Salesforce’s training resource places conversion criteria within the company’s process. Microsoft’s guide explains qualification and related record creation. A software operation cannot verify missing buyer information.
Our proposed early opportunity rule: a specific buyer-confirmed job, the ability to deliver it and an agreed next action about that job. This is a working suggestion for small B2B service projects. It is not a universal standard or a validated performance model.
- Confirm the job. Which product, process or scope did the buyer say they want to evaluate? Retain the dated message and relevant passage.
- Check delivery fit. Can you actually provide the requested work? A positive reply can still concern a service you cannot supply.
- Separate the next action. What did both sides accept? Your calendar reminder differs from a scope review accepted by the buyer.
- Keep unknowns visible. Record missing budget, final approval, amount and decision timing. Do not turn a meeting date into a closing date.
Not every reply from a company creates a new deal.
Entirely fictional example: Ada writes English technical content for industrial products. North Equipment and its contact Deniz are invented. These replies are four alternative scenarios from the same starting point, rather than successive events. They represent no customer conversation or Anivo result.
| Alternative reply | Known / unknown | Decision under this rule | Next work |
|---|---|---|---|
| A · “Send your service information.” | Information is requested. A particular content project and evaluation step are unknown. | Keep an information request; do not open a new opportunity. | Provide the requested information. If useful, ask which product family interests them. |
| B · “We want to update the English technical pages for two pump series. Let’s review the scope together on 26 October.” | A specific job and accepted scope discussion exist. Budget and final approval remain unknown. | Open an early opportunity; leave it outside the revenue forecast. | Record the 26 October scope review; ask for a sample page and approval route. |
| C · “Please correct a typo on the page you delivered last month.” | A correction to delivered work is requested. No separate paid scope is being discussed. | Record delivery / support work. | Check the earlier scope and track the correction. Do not assume a new sale. |
| D · “Please update your quote for the same two series to include translation review.” | The open job’s scope changes. A separate purchase is unconfirmed. | Update the existing opportunity. | Keep the revised quote and changed scope under the same job. |
Scenario A does not prove rejection or lack of interest either. Keeping uncertainty visible differs from disqualifying the company.
Check the buying decision before counting another job.
Counterexample: the same company also asks to evaluate a separate paid writing workshop for its maintenance team. Check the distinct purpose and approval route. An independent purchase may justify a second opportunity. A new person, email or quote version alone does not establish that distinction.
| Change | What to check | Recording decision |
|---|---|---|
| Another reviewer joins the content discussion. | Does the reviewer contribute to the same purchase? | Retain the job reference and add the person’s role. |
| Translation review is added to the content quote. | Is this a revised scope for the same buyer decision? | Retain the job reference and quotation versions. |
| A paid workshop has its own purpose and approval. | Can the workshop be accepted or declined independently? | If confirmed, use a separate job reference linked to the same company. |
In this manual example, two quote versions for F-01 still represent one job. If the separate workshop is confirmed under F-02, the company has two possible purchases. Keep each source attached so another reviewer can reproduce the distinction.
Reconstruct the decision from what was known that day.
| Field | Record as of 23 October 2026 |
|---|---|
| Company / job reference | K-021 / F-01. North Equipment; English technical pages for two pump series. |
| Evidence and source | Fictional buyer email dated 23 October; the scope and discussion request in scenario B. |
| Delivery fit | Ada supplies this technical content service. Page count and the technical reviewer remain to be clarified. |
| Decision / current stage | Open an early opportunity; scope discussion pending. Exclude from the revenue forecast. |
| Agreed work / owner | Ada and Deniz will review scope on 26 October. Ada will prepare the sample page. |
| Amount / budget / decision date | Unknown / not approved / unknown. The 26 October date is only a meeting date. |
| Evidence that would change the decision | Cancellation, work outside the service scope or a buyer-stated project deferral. |
Fictional continuation: on 26 October, Deniz says the project has stopped with no new review date. Append that event. With no agreed next action, remove the job from the active opportunity list and mark it “on hold, no new action.” Retain the valid decision from 23 October; the evidence available then was different.
Define “on hold” and “lost” within your process. If the buyer explicitly selects another supplier, base the loss reason on that statement. Silence cannot tell you that a competitor won or the project was cancelled.
Choose a threshold that fits the purchase.
| Situation | More suitable approach | Distinction to preserve |
|---|---|---|
| Formal tender or mandatory procurement gates | Follow the tender conditions and your organization’s approval requirements. | An early conversation does not establish eligibility or budget approval. |
| Low-value direct order without a sales discussion | Tracking the order and actual transaction may be sufficient. | Avoid adding unnecessary opportunity stages. |
| Long evaluation with complex approvals | Separate early discovery from opportunities eligible for forecasting. | A relevant contact does not establish final purchase authority. |
| Separate paid project for an existing customer | Define the new scope and its relationship to existing work. | One company can buy another job; each message is not another job. |
Keep an existing entry rule if it already works for your team. Write it down and apply it to several past examples. Check whether different people reach different decisions from the same evidence.
Keep the opening and update reasons together.
| Field | Information to complete |
|---|---|
| Company / job reference | Company, possible job and relationship to an existing opportunity. |
| Your entry rule | Separate conditions for early opportunity entry and forecast entry. |
| Buyer evidence | Source, date and confirmed request; keep seller interpretation separate. |
| Fit and unknowns | Scope you can deliver; missing budget, amount, authority and timing. |
| Decision and reason | Open / update existing job / clarify / route to support / remove from active list. |
| Next work | Agreed action or your own planned check; owner and date. |
| Review history | Event changing the decision, new source and previous decision date. |
An independent TXT file containing four alternative replies, the completed B record and blank decision fields. No account required.
Complete the form manually. It is not an Anivo import format, an automatic evaluation or a win-probability calculation.
Connect company research with the conversation note.
Research relevant businesses.
Describe your service and target market to the Agent. Review and approve the research plan. Treat results as candidates for evaluation.
Add the reason to a company note.
Move a suitable company into the CRM. Record the buyer request, source, date and unknowns. Do not infer a purchase decision from a research score.
Track the next work as a task.
Add the agreed action as a task. Review the note and current work when a new reply arrives. Keep the detailed opportunity decision in your independent working form.
This method uses Anivo’s company research, CRM notes and tasks. The job references and entry rule are not applied automatically in Anivo. This guide promises no separate opportunity objects, multiple-project management or automatic revenue forecast.
Review the B2B sales workflow, user guide and pricing. Anivo runs on Windows for one user and one local workspace.
Questions about sales opportunities
Distinguish a reply, a project, a quotation and a won deal.
What is a sales opportunity?
A specific possible purchase being discussed with a company. This guide’s early entry rule requires a buyer-confirmed job, delivery fit and an agreed next action. Businesses may use different thresholds.
Does “send me information” create an opportunity?
That reply alone does not confirm a particular buying project or evaluation step. Record the information request. Clarify the relevant job if useful, and avoid treating the reply as automatic rejection.
Can you open an opportunity without a confirmed budget?
You can if your written early-stage rule permits it. Keep budget marked unknown. Do not present the early opportunity as approved spending or a revenue forecast; apply your forecast conditions separately.
Is a revised quotation a new opportunity?
Update the existing opportunity when the same purchase changes in scope or price. Separate paid work with an independent purpose and approval process may justify another opportunity. The number of documents alone cannot decide this.
Can an existing customer have a new sales opportunity?
Yes, a separate purchase may be under evaluation. Distinguish corrections and support for earlier delivery from new paid scope. The customer relationship alone does not establish a new sale.
Should I mark an opportunity lost after no response?
Silence does not explain the loss. Without a current action, remove it from the active list or place it on hold under your rule. Retain the last actual event and avoid inventing cancellation or a competitor decision.
Does Anivo apply this decision form automatically?
No. The TXT file is an independent manual working record. Anivo’s company research, notes and tasks support the follow-up work. This guide offers no automatic opportunity creation or revenue forecast.
Sources and method limits
Checked on 27 October 2026. These are publishers’ training and usage resources, not independent sales-performance studies. The four scenarios, entry rule and form are our own fictional working examples.
- Salesforce Trailhead · Track Prospects with Salesforce Leads
Reviewed the “Convert Leads to Opportunities” section. Supports company-specific criteria rather than a universal opening threshold.
- Microsoft Learn · Qualify and convert a lead to opportunity
Reviewed qualification and record creation. Dynamics 365 behavior was not transferred into claims about Anivo.
- HubSpot · Prospecting and Objection Handling
Reviewed the information-request objection section. Practical guidance on possible meanings, not evidence of your particular buyer’s intent.
