Lifecycle stage definitions sales will actually agree to

Every commercial ops leader in device has sat through the meeting. Marketing reports a rising count of qualified leads. Sales says none of them were real. Both are right, because the stage called “qualified” was defined by one team and measured against the other team’s idea of progress.

The usual fix is a service-level agreement on lead handoff. It rarely holds, because the underlying stages still describe a software sale: one buyer, one decision, a proposal and a close. A device sale through a hospital and a distributor does not move that way, so the stages cannot describe it.

What lifecycle stages work for device and DME channel selling?

Stages that exit on documents rather than scores. A clinical champion named on the account. An evaluation agreement with written criteria. A value analysis committee submission date. A distributor of record. Each is evidence sales creates anyway, so no one has to believe a marketing number to move a record.

The model below runs on two tracks, because a device sale has two. People advance on the clinical side; accounts and opportunities advance on the commercial side. It is designed to sit on top of any CRM’s default fields rather than replace them.

Stage	Record	Entry criteria	Owner	Exit evidence
Inquiry	Contact	An identified person with a recorded role: clinician, provider buyer, distributor rep or end user	Marketing ops	Role classified and contact matched to an account
Clinical interest	Contact	A clinician has engaged: in-service or webinar attended, instructions for use requested, or a rep-logged conversation	Marketing, handing to the clinical specialist	A named clinical champion on the account, with specialty and site
Account fit	Account	Care setting matches the ideal customer profile, incumbent device known, likely contract vehicle known	Commercial ops	Fit fields complete, and sales accepts or rejects with a reason code
Sales accepted	Opportunity	A rep has taken ownership	Sales rep	Discovery logged: economic buyer named, committee process and calendar known
Evaluation	Opportunity	An evaluation or trial is agreed	Sales rep and clinical specialist	Evaluation agreement on file; written success criteria marked met or not met
Committee review	Opportunity	A value analysis or product committee submission is filed	Sales rep, with marketing supplying the dossier	Submission date, meeting date and recorded decision
Contracting	Opportunity	Committee approval, contract vehicle confirmed: direct, GPO, IDN or distributor agreement	Sales and contracts	Pricing agreement or distributor authorisation signed
Channel assigned	Opportunity	The order will flow through a named distributor, or direct	Commercial ops	Distributor of record written to the opportunity
First order	Account	A purchase order is received through any route	Sales ops and finance	Order line in the ERP or the distributor’s sell-through report
Adopted	Account	The account reorders on its expected cadence	Account manager	A second order recorded against the account
Recycled or lost	Any	The record stops moving	The current stage owner	A reason code: no champion, evaluation not met, committee declined, no contract vehicle, channel conflict, timing

What do the CRM defaults actually assume?

A single buyer who decides. Across 3 CRM vendors and 6 default stage models, 4 of 8 device channel requirements had no matching stage anywhere: clinical champion, committee review, evaluation and channel partner. The documentation pages themselves never used the words distributor, committee, champion or clinical.

The defaults are good at what they were built for. HubSpot’s default deal pipeline has seven stages, one of which is “Decision maker bought-in”, weighted at 80%. Salesforce’s master sales process includes “Id. Decision Makers”. Dynamics 365 Sales says to qualify a lead once it “has the appropriate purchasing power”, and its worked example rests on “a budget and a clear decision timeline”.

Those are sound definitions for a sale with one decision maker. A hospital purchase of a new device can be stopped by the clinician who wants it, the committee that reviews it or the buyer who pays. The defaults collapse all three into one stage, so a deal that is stuck at committee looks identical to a deal waiting on a signature.

The word “trial” appeared 6 times across the 8 fetched pages. All 6 were the vendor’s own offer of a free software trial. Nothing in the default documentation describes a customer evaluating a physical product before buying it, which is the step on which many device sales turn.

Why will sales agree to these definitions?

Because no stage asks sales to accept marketing’s judgment. Each exit condition is a document or a date that sales already produces to close the deal: an evaluation agreement, a committee submission, a signed authorisation. Marketing is measured on how many records reach those documents.

The default marketing qualified lead is defined by HubSpot as a record “your marketing team has qualified as ready for the sales team”. That definition is the source of the argument. It gives one team the right to declare readiness and leaves the other to disagree after the fact.

In this model the handoff moves. Marketing owns Inquiry and Clinical interest, and its output is a named champion. Commercial ops owns Account fit, which is a set of facts about the account. Sales accepts or rejects with a reason code, and the rejection reasons become the feedback loop that marketing’s targeting runs on.

The committee stage is where marketing earns its place later in the funnel. A value analysis committee reads a dossier, and assembling that dossier is marketing work: the evidence summary, the product comparison, the cost and workflow case. Recording the submission date makes that contribution visible. Carmine’s review of who generates device clinical evidence is a guide to what a category can put in one.

How does it fit into HubSpot, Salesforce or Dynamics?

Keep the vendor’s lifecycle property for the coarse picture and build the commercial track as an opportunity pipeline. Add the clinical champion as a contact role on the account, the distributor of record as a field on the opportunity, and reason codes as a required picklist on every backward move.

Check two details in the defaults before building. HubSpot’s automatic updates will “only move the stage forward”, so a failed evaluation cannot send a record back without a workflow or a manual change. Build the Recycled path deliberately, or the stage history will overstate progress.

Salesforce’s default Lead Status values describe contact attempts, such as “Open - Not Contacted”, rather than buying progress. Leave them alone and use them for what they describe. Putting clinical progress into a contact attempt field makes both meanings unreadable.

The Channel assigned stage writes exactly the field that Carmine’s lead-source schema for distributor channels calls transaction_partner. The two are designed to run together: one records who created the demand, the other records who books the order. Together they let marketing-sourced pipeline survive the distributor handoff, which is the subject of the P1 pillar.

Where does this model break?

Four places. Low-cost disposables bought without committee review, where the committee stage is empty. Direct-to-patient DME, where the prescriber and the patient replace the hospital. Distributors who run their own evaluations. And any team that uses the Recycled stage as a parking lot instead of recording why.

No committee. Many consumables and replacement parts never see a value analysis committee. Skip the stage for those product lines rather than forcing a date into it. An empty stage is honest.

Prescriber-led DME. When a clinician prescribes and a supplier fulfils to a patient at home, the account track is thin and the clinical track carries most of the weight. The model still works, but Account fit becomes a question about the supplier network rather than the facility.

Distributor-run evaluations. Some distributors run product trials without the manufacturer present. The evaluation evidence then lives in someone else’s system, and the stage can only record that an evaluation was reported.

Reason-code decay. The loop depends on reason codes being chosen honestly. If “timing” becomes the default, the model has stopped producing information. Watch its share every month.

How was the teardown run?

The teardown fetched 8 public documentation pages from HubSpot’s Knowledge Base, Salesforce Trailhead and Microsoft Learn for Dynamics 365 Sales. It transcribed 39 default stage labels across 6 models and kept a label only if it appeared verbatim in the fetched text. 34 were verified; 5 were not and are marked so.

Each default model was then tested against 8 requirements of device and DME channel selling. A requirement counted as covered if one of its keywords appeared in a verified stage label of that model. The keyword lists, the fetched page text and the per-model results are recorded in the teardown file.

Salesforce’s help site renders articles in the browser and returned no article text to a plain fetch, so the Salesforce defaults were read from Trailhead units. The run date was 2026-09-30, and every page cited here was snapshotted the same day.

What can this teardown not tell you?

It describes defaults. Every one of these CRMs documents how to customise stages, and most live installations are customised. The teardown shows what a new implementation inherits, which may differ from what any device company runs today. It also cannot show that this model shortens a sales cycle.

The coverage test is lexical and deliberately generous. It counted Salesforce’s “Value Proposition” as a proposal stage and HubSpot’s “Contract sent” as evidence of a contract vehicle, which is a charitable reading of both. The four requirements with no coverage are the reliable finding; the covered ones may be weaker than the file suggests.

Nor does the teardown establish how often device sales involve a committee, an evaluation or a distributor. Those vary by product and setting, and no public dataset in this analysis measures them. The model assumes they matter because the defaults give them nowhere to go. No rate was measured.

What is the smallest first step?

Add the four missing facts before changing any stage names: a clinical champion contact role, an evaluation agreement date, a committee submission date and a distributor of record. Make each one required to reach the stage it gates. That takes a day of configuration and changes the next pipeline review.

Then run a quarter with the new fields alongside the old stages. The conversation at the end of it will be about which deals have a champion and which have a committee date. That is a conversation sales can agree with, because the evidence came from sales. More on building this kind of operating discipline is in the P5 pillar.