How a Sale Actually Happens: From First Conversation to Customer

S04 • SALES FOUNDATION

A sale does not happen because a salesperson moves a deal through seven boxes in a CRM. A sale happens when a buyer moves from recognising a possible problem to having enough clarity, confidence and organisational agreement to make a commercial commitment - and the seller successfully supports that process.

At beginner level, a sale can be visualised like this:

Someone becomes aware → Shows interest → A conversation begins → The problem is understood → Fit is determined → A solution is discussed → A commercial proposal is made → Questions, risks and objections are addressed → A decision is made → The customer is onboarded

That sequence is useful. But it is not the whole truth.

Real B2B sales rarely proceed in a perfectly straight line.

A buyer may ask for a proposal, then discover a new requirement, then involve finance, then reconsider whether the problem is urgent, then evaluate another supplier, then ask for a pilot, then revise the specification, then return to price.

A salesperson sees pipeline stages. The buyer experiences a decision process.

Understanding the difference is fundamental.

What is a sales process?

A sales process is the repeatable system an organisation uses to identify, understand, qualify and progress potential customers toward commercial decisions.

It typically defines stages, responsibilities, information requirements, activities, decision evidence and handoffs.

Salesforce's current pipeline guidance uses stages such as prospecting, qualification, meeting, proposal, negotiation, contract and post-purchase, while explicitly noting that stages vary by industry and sector.

Source: https://www.salesforce.com/in/sales/pipeline/

The important phrase is: stages vary.

A ₹2,000 consumer product does not require the same sales process as ₹20 lakh consulting, ₹1 crore industrial machinery or a five-year enterprise technology contract.

The sales process should match the buying process.

Has the sales process always been understood this way?

No.

Sales teaching historically used a familiar “seven steps of selling” model: prospecting, pre-approach, approach, presentation, overcoming objections, closing and follow-up.

Moncrief and Marshall reviewed this traditional model and argued that selling had evolved because of factors including technology, more sophisticated buyers, team selling and the expanded strategic role of sales. Importantly, their evolved model was described as less strictly sequential and more customer- and relationship-oriented than the traditional approach.

Source: https://www.sciencedirect.com/science/article/abs/pii/S0019850104000525

That change matters enormously.

The old model is seller-centred: What should the salesperson do next?

A stronger model asks two questions simultaneously:

What does the seller need to do?

and

What does the buyer need to understand or decide?

So is a sale one process or two?

At least two.

There is a selling process and there is a buying process.

A good commercial system connects them.

The seller may have a stage labelled Proposal. But the buyer may still be working on requirements, internal consensus, business case or supplier validation.

If the salesperson assumes “Proposal sent = deal is advanced,” the CRM may show more progress than the customer has actually made.

That is one reason pipelines become misleading.

What does modern B2B research say about the buyer's process?

Gartner describes B2B purchasing as a nonlinear set of buying jobs rather than a clean seller-controlled sequence.

Its framework includes problem identification, solution exploration, requirements building, supplier selection, validation and consensus creation.

Buyers can revisit these tasks repeatedly rather than completing each once in sequence.

Source: https://www.gartner.com/en/sales/insights/b2b-buying-journey

That explains something experienced salespeople already know: a deal can move forward and backward simultaneously.

The customer may love the solution but reopen the business case. They may agree on the problem but disagree internally on requirements. They may select the supplier but then discover implementation risk.

Sales stages remain useful. But they should represent evidence of buyer progress, not merely seller activity.

Where does a sale actually begin?

Potentially before sales knows the buyer exists.

The buyer might notice a problem, read an article, ask a colleague, search Google, use AI, visit a website, attend an exhibition, see an advertisement, talk to an industry peer or encounter a salesperson.

Modern buyers often research independently before speaking with sales.

Gartner's 2026 survey of 645 B2B buyers found respondents used an average of seven information sources in a recent purchase, while substantial numbers preferred digital and self-service experiences even though human sales remained important for validation and decision support.

Source: https://www.gartner.com/en/newsroom/press-releases/2026-05-20-gartner-survey-finds-sixty-nine-percent-of-b-two-b-buyers-turn-to-sales-reps-to-validate-ai-generated-insights

So the sales process often begins after the buying process has already started.

That has an important consequence: the salesperson should not assume the buyer knows nothing.

What is awareness?

Awareness simply means the potential buyer becomes aware of a problem, an opportunity, a category or a possible supplier.

For example:

A finance head realises month-end reporting takes fourteen days.

A sales director realises forecasts are consistently unreliable.

A plant manager sees increasing downtime.

A founder discovers that profit is rising but cash is tightening.

Awareness can concern the problem before awareness of any solution exists.

That distinction matters.

Someone who knows “we have a problem” is at a different decision stage from someone who already knows “we need a CRM.”

What happens after awareness?

The buyer starts trying to understand the issue.

This may involve search, internal discussion, vendor research, peer recommendations, consultants, content, comparison or preliminary enquiries.

This is where marketing and sales begin overlapping.

Marketing can help buyers understand the problem. Sales may enter when a particular commercial conversation begins.

What exactly is a lead?

There is no universal definition. Companies use the word differently.

A practical Fiease terminology is:

Contact

A person or organisation whose information exists.

Enquiry

A contact that has expressed some form of interest or request.

Lead

A person or organisation sufficiently relevant to justify further commercial attention.

Prospect

A potential customer broadly fitting the seller's target.

Qualified Opportunity

A potential commercial transaction with enough evidence of problem, fit and buying possibility to justify active sales investment.

These definitions should be adapted to the company. The most important thing is consistency.

Why does terminology matter?

Because management decisions depend on it.

Suppose one salesperson calls anyone who downloads a brochure an “opportunity.” Another creates an opportunity only after discovery. Another waits until budget is confirmed.

The CRM reports 50 opportunities.

But those 50 records do not represent the same thing.

Management then calculates pipeline, win rate, forecast and salesperson performance using inconsistent units.

The mathematical precision becomes misleading.

Definitions are part of data quality.

What should happen when someone shows interest?

The company should establish: Who is this? What prompted the interest? Does the person or company broadly fit? What kind of response is appropriate? Who owns the response? What should happen next?

This sounds obvious. Yet revenue can disappear simply because ownership is unclear.

Marketing thinks sales is calling. Sales thinks the enquiry is unqualified. The regional salesperson thinks inside sales owns it. Nobody contacts the prospect.

The lead existed. The sales process did not.

How important is response speed?

It can matter significantly, particularly for high-intent inbound enquiries.

But Fiease should avoid publishing a universal “respond within X minutes” rule unless evidence and context support it.

A buyer asking for emergency equipment repair is different from someone downloading a six-month planning guide.

The correct standard depends on buying intent, urgency, channel, sales model and customer expectation.

The governing principle is:

Response speed should match commercial intent.

What is the purpose of the first conversation?

Not necessarily to sell.

The first conversation should usually establish enough context to determine what kind of conversation is actually required.

Questions may include: Why did you contact us? What is happening today? What are you trying to achieve? What prompted this now? Who is affected? What have you already tried? What would a sensible next step look like?

Sometimes the right outcome is book deeper discovery. Sometimes send information. Sometimes involve a technical expert. Sometimes disqualify.

The first call does not have one universal objective.

When should salespeople start presenting the solution?

When enough is understood to make the explanation relevant.

A common bad sequence is:

Customer mentions problem.

Salesperson recognises keyword.

Presentation begins.

Twenty slides later, the salesperson knows almost nothing more about the customer.

The presentation may be technically excellent. Commercially it is generic.

A better transition is:

“From what you've described, there seem to be three issues: inconsistent qualification, poor visibility after proposals and weak next-step discipline. If that's accurate, I can show you how our approach addresses those three areas.”

Now the solution is connected to a diagnosis.

What is discovery?

Discovery is the structured process of understanding the customer's situation deeply enough to determine what the problem is, why it matters, what outcome is desired, what constraints exist, who is affected and whether further commercial work is justified.

A good discovery process moves through several layers.

Situation

What happens today?

Problem

What is not working?

Cause

Why is it happening?

Consequence

What does it cost?

Desired state

What should happen instead?

Decision

What would the organisation need to evaluate or approve?

This is not interrogation. It is joint problem definition.

What is qualification?

Qualification is the decision about whether an opportunity deserves additional resources.

Not every relevant prospect should receive a custom proposal, site visit, technical design, senior-management attention, demo or commercial negotiation.

Those activities cost time and money.

Qualification asks whether enough evidence exists to justify the next investment.

What should qualification actually test?

Different businesses need different frameworks. But useful questions include:

Problem

Is there a genuine issue or opportunity?

Importance

Is it important enough to act on?

Fit

Does the customer match the kind of organisation we can serve?

Solution

Can we plausibly address the requirement?

Economics

Could the expected value justify the investment?

Stakeholders

Who is involved?

Decision path

How will a decision actually be made?

Timing

Is there a credible reason for action within a meaningful period?

Next step

Is the customer willing to do something that demonstrates continued progress?

The purpose is not certainty. It is enough evidence to justify deeper pursuit.

Does qualification have to happen once?

No.

Qualification should continue throughout the opportunity.

A deal that looked excellent two months ago may become weak because budget disappeared, management changed, requirements changed, the problem became less urgent, a competitor gained advantage or implementation capacity vanished.

Good salespeople continually requalify.

Otherwise CRM pipelines fill with historical optimism.

What is the difference between qualification and discovery?

Discovery asks: “What is happening?”

Qualification asks: “Should we continue investing in this?”

They overlap heavily.

Discovery produces information. Qualification uses information to make resource-allocation decisions.

When does something become an opportunity?

When the organisation has enough evidence that a plausible transaction exists and decides to actively pursue it.

Fiease should avoid defining an opportunity simply as someone asked for price, someone took a meeting or someone said they were interested.

Interest is useful. Opportunity status should require stronger evidence.

A possible minimum might be real problem identified, reasonable fit, customer engagement and credible next action.

For more complex B2B sales, additional evidence may be required.

What is a pipeline?

A sales pipeline is the set of active commercial opportunities organised according to their progress through the sales process.

Salesforce describes the pipeline as stages through which prospects move toward a sale, including qualification, meetings, proposal, negotiation and post-purchase activity.

A pipeline answers: What opportunities exist? Where are they? What is their potential value? What is blocking them? What might happen next?

It is a management system. Not simply a CRM report.

What is the difference between a sales funnel and a pipeline?

They are related but different concepts.

A funnel usually examines conversion across groups.

For example: 1,000 enquiries → 500 contacted → 200 qualified → 100 opportunities → 50 proposals → 20 customers.

It is useful for understanding stage-to-stage leakage.

A pipeline examines active individual opportunities.

For example:

ABC Ltd - ₹20 lakh - proposal.

XYZ Ltd - ₹50 lakh - discovery.

LMN Ltd - ₹12 lakh - negotiation.

The funnel asks: Where do we lose volume?

The pipeline asks: What is happening in our active deals?

Management needs both.

What should a sales stage represent?

Preferably a meaningful change in buyer progress.

Weak stage: Presentation sent. That describes seller activity.

Stronger stage: Customer confirmed requirements and agreed solution review. That represents buying progress.

Weak stage: Follow-up. Almost anything can be called follow-up.

Stronger stage: Commercial proposal under stakeholder evaluation.

The better the stage reflects evidence, the more useful the pipeline becomes.

Why do stage definitions matter?

Because stages influence forecasting, resource allocation, coaching and reporting.

If “qualified” means something different to every salesperson, the pipeline cannot reliably answer how much opportunity exists, which deals are likely to move, where conversion fails or which salesperson needs support.

Stage definition is therefore management infrastructure.

What is a stage gate?

A stage gate is evidence that should exist before an opportunity moves into the next stage.

For example:

Discovery → Qualified Opportunity

Possible exit evidence: problem confirmed, basic fit established, stakeholder identified, next action agreed.

Qualified Opportunity → Solution Alignment

Possible exit evidence: requirements understood, technical fit plausible, key stakeholders engaged.

Solution Alignment → Proposal

Possible exit evidence: scope sufficiently defined, commercial basis understood, buyer expects formal proposal.

Proposal → Decision

Possible exit evidence: proposal reviewed, decision criteria known, outstanding concerns explicit, decision process visible.

The exact gates should reflect the company's sales model.

Why is seller activity a poor substitute for stage evidence?

Because sellers can be very busy without the buyer moving at all.

Activities: five calls, three emails, one proposal, two presentations.

Buyer progress: none.

A pipeline based primarily on seller activity can therefore reward effort without distinguishing movement.

Sales management should care about activity. But activity must eventually create decision progress.

The Fiease Sales Stage-Gate Model

Stage	Main question	Minimum evidence
1. Potential Lead	Is this worth attention?	Basic relevance
2. Meaningful Contact	Have we established two-way interaction?	Customer engagement
3. Discovery	Is there a real problem or opportunity?	Situation and problem understood
4. Qualified Opportunity	Should both sides continue?	Problem, fit, importance and next step
5. Solution Alignment	Can our approach credibly fit?	Requirements and approach sufficiently aligned
6. Commercial Proposal	Is there a defined offer against a defined requirement?	Scope, economics and proposal
7. Decision	What remains before commitment?	Risks, stakeholders and decision process explicit
8. Closed Won/Lost	What did the customer decide?	Formal outcome
9. Handoff	Can delivery fulfil the promise?	Commercial and operating context transferred

This is a Fiease operating framework. It is not intended as a universal academic sales standard.

Some businesses need fewer stages. Some need more. The purpose is disciplined meaning.

Should the CRM automatically determine the sales process?

No.

This is one of the most important concepts in the article.

CRM is not the sales process.

CRM is the system that helps record, organise and share commercial information.

Salesforce defines CRM as a system for managing interactions with current and potential customers, including sales calls, marketing interactions and service activity.

Source: https://www.salesforce.com/in/crm/what-is-crm/

A CRM can store customer, owner, stage, deal value, activities, expected close date, next action, contacts, documents and notes.

But software cannot decide what your company means by qualified, proposal, commitment or lost.

Management must define those things. Then CRM should support them.

What happens when CRM comes before process design?

The company digitises ambiguity.

Suppose management configures these stages:

Lead. Qualified. Proposal. Negotiation. Won.

Looks sensible.

Then ask five salespeople: “What must happen before a deal enters Qualified?”

Salesperson A: “They responded.”

Salesperson B: “They need the product.”

Salesperson C: “They asked for a quotation.”

Salesperson D: “They have budget.”

Salesperson E: “I think they'll buy.”

Same CRM. Five processes.

The software has not standardised anything. It has merely given inconsistency a dashboard.

When should a proposal be sent?

When enough has been understood that the proposal can represent a serious commercial recommendation.

Not simply because the customer says: “Send your price.”

Sometimes price should be provided quickly. In transactional selling, delaying price can frustrate buyers.

But in complex B2B situations, a full proposal sent before discovery can create several problems: wrong scope, irrelevant features, bad assumptions, commodity comparison and wasted proposal effort.

The correct timing depends on complexity.

What should a proposal actually accomplish?

A strong proposal should help answer:

What problem are we solving? What are we proposing? Why this approach? What is included? What is excluded? What must the customer contribute? What will implementation look like? What does it cost? What assumptions matter? What are the commercial terms? What decision is required?

A proposal is therefore a decision document.

Not a company brochure with a price on the final page.

Why do companies send too many proposals?

Because “proposal sent” feels like progress.

Management asks: “How many quotes did we send?” Salespeople respond by sending quotes.

But a high number of proposals can mean strong opportunity flow or poor qualification.

Suppose 100 proposals create 10 orders. Is that good? Maybe.

But if 60 proposals never had a genuine buying process, the company is wasting selling capacity.

Proposal volume should therefore be interpreted alongside qualification, conversion and economic value.

What happens after the proposal?

The buyer evaluates.

But evaluation is not one thing.

Different people may examine technical fit, commercial terms, financial value, security, implementation, delivery, contract and organisational risk.

This is often where a deal appears to “stall.”

In reality, multiple buyer tasks may still be incomplete.

Gartner's buying framework specifically includes validation and consensus creation among the jobs buyers must complete.

That means the seller should ask: “What still needs to be resolved?” not merely: “Any update?”

What is an objection in the process?

An objection is information about something preventing progress.

It may reveal risk, weak value, misfit, timing, priority, competition or internal disagreement.

For example: “Your price is too high.”

Possible underlying issues: budget, comparison, unclear value, scope or negotiation.

The seller should diagnose before responding.

Where does negotiation begin?

Negotiation can happen throughout the sale.

But formal commercial negotiation usually begins when both sides agree there is enough potential fit to discuss terms.

Negotiable variables can include price, scope, quantity, payment, delivery, support, warranty, implementation, contract period, service levels, risk allocation and exclusivity.

Negotiation is therefore not synonymous with discounting.

Why does finance need to be involved before the sale closes?

Because terms affect economics.

Example:

Price = ₹50 lakh.

Gross margin before concession = 30%.

Gross profit = ₹15 lakh.

Suppose sales offers a 10% discount:

New revenue = ₹45 lakh.

If underlying cost remains ₹35 lakh:

New gross profit = ₹10 lakh.

Revenue fell 10%.

Gross profit fell from ₹15 lakh to ₹10 lakh - a 33.3% reduction.

That is why “only 10% discount” can be economically misleading.

Sales concessions should be understood through contribution, not merely invoice value.

Why does operations need to be involved?

Because sales may negotiate variables operations must deliver.

For example: two-week installation, custom packaging, special production batch, rush delivery, extended support or unusual specification.

An order is not valuable if fulfilment destroys the economics or customer relationship.

Sales therefore cannot optimise deals in isolation.

What is a buying committee?

In complex B2B purchases, several stakeholders may influence the decision.

Examples: user, technical evaluator, finance, procurement, business sponsor, executive decision-maker, IT, legal, operations.

Different stakeholders perform different buying jobs.

A strong salesperson maps: Who needs what? Who believes what? Who remains unconvinced? Who has authority? Who bears risk?

One enthusiastic champion is useful. It is not the same as organisational commitment.

What is a champion?

A champion is an internal stakeholder who actively supports the proposed change and can help the seller understand or navigate the organisation.

But “friendly contact” and “champion” are different.

A genuine champion may share internal context, bring other stakeholders into the process, help build consensus, explain decision criteria and advocate internally.

A person who enjoys the salesperson's calls but has little influence may not be a champion.

What is the role of the next step?

A credible opportunity should have a credible next action.

Weak next action: “Follow up next week.”

Strong next action: “Finance review with CFO on 14 September to validate payback assumptions.”

Weak: “Waiting for client.”

Strong: “Customer engineering team to provide machine-layout dimensions before technical proposal revision.”

A next action should represent a real piece of the decision process.

Why are close dates often unreliable?

Because sellers frequently use close dates as hopes rather than evidence.

A salesperson may enter 30 September because that is quarter-end, their manager wants a date or the customer said “maybe next month.”

A useful close date should be connected to a known decision process such as board approval, procurement meeting, contract expiry, project launch or installation requirement.

Forecasting quality depends on decision evidence.

Is a large pipeline always good?

No.

Pipeline value can be inflated by poor qualification, stale deals, duplicate opportunities, unrealistic values and repeatedly moved close dates.

₹10 crore of genuine opportunities is better than ₹30 crore of CRM hope.

Pipeline quality matters alongside pipeline quantity.

What is pipeline hygiene?

Pipeline hygiene means maintaining records so that they reflect current commercial reality.

This can include removing dead opportunities, updating stages, maintaining realistic values, recording next actions, updating close dates and documenting loss reasons.

The objective is not administrative cleanliness for its own sake. It is decision quality.

Management allocates attention, resources and forecasts using pipeline data. Bad data creates bad decisions.

When should an opportunity be closed lost?

When there is sufficient evidence that the current transaction is no longer active.

Examples: customer chose competitor, project cancelled, budget withdrawn, solution does not fit, customer explicitly declined or timing moved outside the active opportunity horizon.

Closed lost does not necessarily mean never speak again. The company may nurture the relationship.

But an inactive situation should not remain in active pipeline merely because a salesperson dislikes closing it.

Should no decision be a loss reason?

Yes, if that accurately describes the outcome.

But management should ideally understand why no decision happened.

Possible reasons: problem not important enough, budget not approved, internal consensus failed, implementation impossible, status quo preferred or decision indefinitely postponed.

No decision can be commercially diagnostic.

What does closed won actually mean?

The company needs one explicit definition.

Possible definitions: signed contract, confirmed purchase order, payment received or another agreed commercial event.

The exact trigger depends on the business. But everyone must use the same trigger.

Otherwise one salesperson marks a deal won at verbal approval while another waits for the purchase order. Reporting becomes inconsistent.

Is the sale finished at closed won?

Commercial acquisition may be complete. Customer value is not.

The next step is handoff.

A weak handoff sounds like: “Here's the new customer. Please take over.”

A strong handoff transfers customer objectives, scope, agreed deliverables, timelines, commercial terms, stakeholders, risks, expectations and commitments made during sales.

This is the point at which sales becomes operations.

Why is handoff part of the sales process?

Because poor handoff can destroy the value of a successful close.

Possible consequences: wrong implementation, scope disputes, missed deadlines, customer frustration, delayed invoices, payment disputes or early churn.

The salesperson cannot promise one experience and hand the customer into another.

The customer bought one company.

What happens after onboarding?

The relationship enters post-sale management.

Depending on the business, account management, customer success, service, operations or the original salesperson may remain involved.

This is where customer experience influences renewal, repeat sales, referrals and reputation.

Modern sales-process thinking has increasingly moved beyond treating the close as the absolute end. Salesforce's current guidance, for example, includes post-purchase stages within pipeline thinking.

How do you design a sales process for an SME?

Start with reality. Do not copy a software template.

Take ten recently won deals and ten lost deals.

Map: How did they begin? Who was involved? What information mattered? What steps occurred? Where did deals stall? What evidence existed before proposals? What caused loss? What happened after agreement?

Look for recurring patterns.

Then design stages around meaningful changes in the decision.

How many stages should a process have?

Enough to create management visibility. Not so many that salespeople spend their lives changing statuses.

A simple transactional process may need Lead → Qualified → Proposal → Won/Lost.

A complex industrial sale may require Lead → Discovery → Technical Qualification → Commercial Qualification → Solution Design → Proposal → Technical Approval → Commercial Negotiation → Contract → Won/Lost.

The right number is contextual.

What information should be mandatory?

Only information that materially improves sales execution, management, forecasting, handoff or learning.

Examples: source, problem, opportunity value, stakeholders, stage, next action, expected decision date, loss reason.

Avoid collecting information nobody uses.

A CRM full of mandatory fields can reduce selling productivity without improving decisions.

How should management review the pipeline?

Do not ask only: “Will this close?”

Ask: What changed since last review? What evidence supports the current stage? What is the buyer doing? What uncertainty remains? Who is missing? What is the next customer action? What could make us lose? Should this still be active?

Those questions improve diagnosis.

What metrics reveal whether the process works?

Possible metrics include:

Top of funnel

Enquiries. Source quality. Contact rate.

Qualification

Lead-to-opportunity conversion.

Progress

Stage-to-stage conversion. Stage ageing.

Commercialisation

Opportunity-to-proposal. Proposal-to-win.

Speed

Sales-cycle duration. Time in stage.

Economics

Average selling price. Discount. Margin.

Forecast

Forecast versus actual outcome.

Handoff

Onboarding delays. Scope disputes. Early payment issues.

There is no universal ideal conversion benchmark.

Compare historical performance, segments, sources, salespeople, deal sizes and product types. Use external benchmarks cautiously.

What does a worked sales process look like?

HYPOTHETICAL EXAMPLE

A manufacturer sells automated packaging equipment.

Typical project value: ₹40-80 lakh.

Stage 1 - Awareness

A food manufacturer sees the equipment at an industry exhibition.

No sales opportunity exists yet.

Stage 2 - Interest

The plant manager asks whether automation could reduce manual packaging labour.

Sales captures the contact.

Stage 3 - Initial conversation

The salesperson learns a new production line is being planned, manual packaging currently constrains peak throughput and expansion is expected within nine months.

The conversation is relevant.

Stage 4 - Discovery

Sales and engineering investigate current throughput, pack size, floor space, labour, shift structure, future volume, integration and required commissioning date.

Stage 5 - Qualification

Evidence suggests a real project, credible budget range, appropriate technical fit, decision expected within four months, engineering and finance involved.

Opportunity created: ₹60 lakh.

Stage 6 - Solution alignment

Engineering proposes a configuration. The customer's operations team reviews layout. The solution fits technically.

Stage 7 - Business case

Customer wants to understand labour economics.

Current packaging labour:

12 workers per shift.

2 shifts.

Loaded labour cost: ₹32,000 per worker per month.

Annual labour cost represented:

12 × 2 × ₹32,000 × 12 = ₹92.16 lakh.

The proposed machine does not eliminate all labour.

Assume the customer estimates net reduction equivalent to 6 workers across the operating model.

Annual labour-capacity equivalent:

6 × ₹32,000 × 12 = ₹23.04 lakh.

That is one input into the investment decision. It is not the entire ROI. Maintenance, energy, downtime, financing and throughput effects still matter.

Stage 8 - Proposal

Supplier sends technical scope, layout, installation, training, warranty, commercial terms and implementation schedule.

Stage 9 - Validation

Customer visits an existing installation. Engineering validates performance. Finance tests economics.

Stage 10 - Negotiation

Customer requests 5% lower price, revised payment schedule and longer warranty.

Supplier evaluates margin and risk.

Stage 11 - Decision

Purchase order issued.

Stage 12 - Handoff

Sales transfers approved layout, specifications, commercial commitments, timing, decision stakeholders and installation expectations to operations/project delivery.

Notice what happened.

The deal did not progress because salesperson presented → customer bought.

It progressed because multiple buyer questions were resolved.

That is what a sale actually looks like.

What are the most common process failures?

Mistaking interest for opportunity

Interest does not prove fit or buying intention.

Proposing before diagnosing

Quotes become generic and price-driven.

Allowing stages to mean different things

CRM analytics become unreliable.

Tracking seller action rather than buyer progress

Busy deals appear healthier than they are.

Never disqualifying

Pipeline becomes bloated.

Using arbitrary close dates

Forecasts become wishes.

Treating objections as one stage

Risk and disagreement occur throughout buying.

Negotiating only on price

Other commercial variables are ignored.

Closing without operational review

Sales promises become delivery problems.

Treating CRM as process

Technology automates inconsistency.

What should the Fiease philosophy be?

A sale should be understood as:

A sequence of evidence-backed decisions.

At each point, ask:

What do we know?

What does the buyer know?

What remains uncertain?

What evidence justifies progression?

Who needs to be involved?

What is the next decision?

That approach produces a very different CRM, a very different pipeline review and ultimately a much more reliable revenue system.

What is the final answer: how does a sale actually happen?

A sale begins when a potential buyer starts recognising a problem or opportunity.

It develops as the buyer understands the issue, explores possible solutions, defines requirements, evaluates suppliers, tests evidence, aligns stakeholders and decides whether change is worth the cost and risk.

The seller supports that journey by making contact, discovering the problem, qualifying fit, developing a relevant solution, building the commercial case, addressing uncertainty, negotiating workable terms and creating a clean handoff.

The CRM records that process. It does not create it.

The pipeline represents that process. It is not the process itself.

And a sales stage is useful only when it reflects something meaningful about the buyer's progress.

That is how Fiease should teach sales: not as a series of tricks leading to a close, but as a disciplined system that helps a customer move from possible problem → understood problem → credible solution → commercial decision → successful delivery.

Frequently asked questions

What is the first stage of a sale?

It depends on the business. The buying process may begin with problem awareness before the seller knows the customer exists. The company's own sales process may begin with prospecting or enquiry capture.

What is the difference between a lead and an opportunity?

A lead is a potentially relevant contact or organisation. An opportunity is a sufficiently qualified potential transaction that justifies active sales investment.

Does every sale follow the same stages?

No. Sales processes vary by product, market, complexity, deal value and buying structure.

Is the B2B buying process linear?

Generally no. Gartner's research describes buyers as repeatedly moving across buying jobs such as problem identification, solution exploration, requirements, supplier selection, validation and consensus.

What is discovery?

Discovery is the process of understanding the customer's situation, problem, consequence, desired outcome, constraints and decision environment.

What is qualification?

Qualification determines whether there is enough evidence to justify continued sales investment.

When should a proposal be sent?

When the seller understands enough of the requirement to create a relevant commercial offer. In simple transactional selling, pricing may appropriately be much earlier.

What is a sales pipeline?

A pipeline is the set of active opportunities organised according to meaningful stages of progression.

What is CRM?

CRM is a system for managing and recording interactions with prospects and customers. It supports the sales process but does not replace process design.

Is closed won the end of sales?

It is the end of customer acquisition for that transaction, but the promise still needs to be handed into delivery, onboarding and ongoing account management.

What is the simplest Fiease sales-process model?

Awareness → Interest → Conversation → Discovery → Qualification → Solution → Proposal → Decision → Handoff.

Use it as a conceptual foundation, then adapt stages to the actual business.

Research foundation

This article draws on Moncrief and Marshall's examination of how the traditional seven-step selling model evolved toward a less sequential, more relationship-oriented view; contemporary Salesforce definitions of CRM and pipeline stages; Gartner's research on nonlinear B2B buying jobs and current multi-source buyer behaviour; and research examining how sales processes adapt to buyers and buyer-seller relationships.

Sources:

https://www.sciencedirect.com/science/article/abs/pii/S0019850104000525

https://www.salesforce.com/in/sales/pipeline/

https://www.salesforce.com/in/crm/what-is-crm/

https://www.gartner.com/en/sales/insights/b2b-buying-journey

https://www.gartner.com/en/newsroom/press-releases/2026-05-20-gartner-survey-finds-sixty-nine-percent-of-b-two-b-buyers-turn-to-sales-reps-to-validate-ai-generated-insights