A collection of representative B2B lead discovery scenarios, showing how AI identifies qualified sales opportunities from real-world business conversations.
“We're Starting an AI Project” Is Not Enough: What Makes It Worth Following Up?
An illustrative AI document platform scenario showing how AI combines project status, commercial context, and an open technology decision to identify an early, pre-procurement sales signal.
This is an illustrative scenario designed to explain the product’s judgement logic. It is not a real customer case, testimonial, contract, revenue result, or conversion claim.
01Situation
02Signal judgement
03Confidence vs priority
04Human next step
Signals considered
- The team explicitly says it is starting a new AI project
- The project is a business-oriented document processing platform
- The infrastructure stack remains under evaluation
- The architecture and supplier decision window may still be open
This is an illustrative business scenario designed to explain how AI identifies new-project signals. It does not represent a real customer, transaction, or close probability.
Scenario background
An AI infrastructure provider wants to find customers with long-term potential. It is not interested only in teams requesting a quote today. It also wants to notice teams that have just started a project and may gradually need compute, storage, deployment, and compliance support.
In a Telegram discussion about enterprise document workflows, model deployment, and data-storage architecture, one participant says:
We’re starting a new AI document processing platform.
Still evaluating our infrastructure stack.
There is no budget, quote request, supplier list, or Looking for. Yet the combination of a new project and an unresolved technology decision makes this an early signal worth monitoring and engaging carefully.
Original Conversation
09:31 AM
We're starting a new AI document processing platform.
Still evaluating our infrastructure stack.
Why does AI pay attention?
Traditional keyword tools usually search for Buy, Need supplier, or Looking for. None appears here, but the full context describes a new project that may create future purchasing demand.
Signal 1: A project is starting
We're starting is closer to action than learning about a technology or sharing an article. A project start can lead a team to define objectives, owners, architecture, budget, and delivery plans.
Starting does not mean formally approved. The work could still be a concept, internal proposal, or feasibility discussion that needs human verification.
Signal 2: The project type is specific
AI document processing platform names a concrete application. Together with the surrounding enterprise-workflow discussion, it looks more like a business system than an isolated technical topic.
The project label alone cannot prove commercial value. Sales still needs to verify intended users, document volume, data requirements, and the planned deployment model.
Signal 3: The technology decision remains open
Still evaluating our infrastructure stack suggests that architecture and provider decisions may not be final. Potential requirements could include model inference, storage, data residency, security, observability, and scaling.
Compared with We deployed, Still evaluating indicates that a decision window may remain open. It does not prove that the team will buy an external service.
Signal 4: The purchasing window may not have closed
Many sales teams wait until a customer publicly asks for suppliers, when other providers may already be involved. At project initiation, sales may have an earlier opportunity to help define useful evaluation criteria.
Earlier also means less certainty. This type of lead belongs in a monitoring and low-pressure engagement workflow, not a P1 purchasing queue.
How does AI combine the evidence?
TOP Prospect should not send a high-priority alert simply because Project appears. The relevant question is whether the project has commercial context and an unresolved technology or supplier decision.
| Signal | Status |
|---|---|
| New Project | ✅ |
| Commercial Context | ✅ |
| Technology Evaluation | ✅ |
| Supplier Opportunity | Requires verification |
Together, these elements form an Early Buying Signal. It deserves monitoring and nurture, but its maturity remains below scenarios with a stated budget, deadline, or supplier request.
AI Analysis Summary
| Item | Illustrative assessment |
|---|---|
| Scenario Type | New Project Initiation |
| Project Detected | Yes |
| Commercial Context | AI Platform |
| Evaluation Stage | Infrastructure Selection |
| Buying Intent | Medium–High |
| Confidence Score | 89% · illustrative score |
| Recommended Action | P2 · Monitor and Engage |
The 89% is an illustrative score used to explain the product’s reasoning. It is not a calibrated close probability and does not prove that the project is approved, has a budget, or that the sender owns procurement.
Why monitor a new project early?
Procurement rarely happens on the first day of a project. A more common path is:
Project initiation
→ Define requirements and constraints
→ Request or confirm budget
→ Build a supplier shortlist
→ Compare options
→ Purchase and implement
If sales provides a useful evaluation framework during planning, it may establish credibility before the shortlist forms. Engaging too early or pushing repeatedly can have the opposite effect.
Why This Matters
Monitoring only explicit purchasing language limits sales to the later half of the demand lifecycle. A new project creates an earlier observation window: the customer is not ready to buy, but the source of future demand is now visible.
AI should not turn every project into a lead. Its value is in identifying projects with a business setting, concrete use case, and open decision space—and assigning a follow-up cadence different from urgent procurement.
Human Review
AI can identify a project-start pattern, but sales still needs to verify:
- Is the project an idea, feasibility study, approved pilot, or committed product?
- Is it an internal tool, customer delivery, or commercial platform?
- Who owns product, architecture, and provider evaluation?
- Does the team have a budget, existing cloud resources, or incumbent providers?
- What are the document volume, model, latency, storage, security, and data-residency requirements?
- Is the next useful milestone architecture selection, PoC, budget approval, or launch?
The answers determine whether sales should share material now, monitor the next milestone, or exclude a personal experiment or non-target project.
Recommended Sales Action
Do not begin with a product pitch. Offer low-pressure help around project planning:
Saw that your team is evaluating the infrastructure stack for a new AI document processing platform.
A useful way to narrow the options is to map document volume, data residency, model serving, storage and review requirements first. If helpful, I can share a neutral infrastructure evaluation checklist.
This response does not assume that the customer is ready to buy, and it avoids using unverified customer outcomes. It offers a practical tool for the next planning step.
Why doesn’t AI monitor every New Project?
My side project, Weekend hobby project, and coursework can all include Project without a clear commercial objective, team process, or purchasing space.
AI needs to combine project type, business setting, participant roles, discussion depth, and evaluation status. Project initiation is a starting point, not a keyword that should trigger sales action by itself.
Sales Insight
Many teams define a lead as a customer already preparing to buy. Yet earlier access to the project cycle can help sales understand how demand forms and provide useful input at the right milestone.
A new project may create new budget, technology decisions, and supplier opportunities. It may not produce an order immediately, but it can become the beginning of a long-term relationship. The right response is nurture, not an urgent-procurement cadence.
What This Scenario Teaches
Procurement often begins not with a quote request, but with a project start.
AI is not finding today’s order. It is identifying a business process that may gradually create demand. It connects project status, commercial context, and open technology decisions, then gives sales an early opportunity to monitor and engage appropriately.
Related Scenarios
After a project starts, a company may announce: We're opening a new office in Dubai next quarter.
Continue with SCENARIO 008 · Business Expansion. It examines why entering a new market, opening an office, or growing a team can create a sequence of infrastructure, payments, logistics, and local-partner needs.
Frequently asked questions
Does a new project mean procurement has started?
No. It is an early, pre-procurement signal. The team still needs to verify project approval, commercial purpose, technology ownership, and whether an external provider is required.
Is 89% a probability that the opportunity will close?
No. It is an illustrative score showing how project initiation, commercial context, and open technology evaluation can reinforce confidence. It is not a calibrated close probability or a real customer result.
Should sales pitch immediately?
Usually not. A better action is to provide planning or infrastructure-evaluation material, verify the stage and owner, and monitor the project against its next milestone.