B2B SALES · SALES OPPORTUNITIES 2026-10-27 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? Four different records connected to one company 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 (https://anivoapp.com/guides/lead-qualification/) to evaluate a prospect and the CRM guide (https://anivoapp.com/guides/what-is-crm/) to organize relationship records. Apply the same entry rule to each reply. Businesses and CRM products use different thresholds. [Salesforce’s training resource](https://trailhead.salesforce.com/content/learn/modules/prospect-tracking-with-salesforce-leads-quick-look/track-prospects-with-salesforce-leads) places conversion criteria within the company’s process. [Microsoft’s guide](https://learn.microsoft.com/en-us/dynamics365/sales/qualify-lead-convert-opportunity-sales) 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. Use separate conditions for early opportunities and revenue forecasts. Track a job that passes your early entry rule. Before including it in a revenue forecast, separately assess the basis for its value and decision timing. Invented amounts and dates entered to satisfy required software fields provide no buyer evidence. Each reply from a company does not create 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. The evidence that changes an opportunity decision 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. Two records are justified by separate buying work 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. Fictional manual record for scenario B 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. Limits of the example entry rule 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. Blank decision record for your own work 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. Company / job reference: [ ] Your entry rule: [ ] Buyer evidence: [ ] Fit and unknowns: [ ] Decision and reason: [ ] Next work: [ ] Review history: [ ] Complete the form manually. It is not an Anivo import format, an automatic evaluation or a win-probability calculation. 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 https://trailhead.salesforce.com/content/learn/modules/prospect-tracking-with-salesforce-leads-quick-look/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 https://learn.microsoft.com/en-us/dynamics365/sales/qualify-lead-convert-opportunity-sales Reviewed qualification and record creation. Dynamics 365 behavior was not transferred into claims about Anivo. HubSpot · Prospecting and Objection Handling https://cdn2.hubspot.net/hubfs/53/Prospecting-Objection-Handling.pdf Reviewed the information-request objection section. Practical guidance on possible meanings, not evidence of your particular buyer’s intent.