Life Sciences and Lab Reagent Selling — 60-Min Training

Stack You'll Run This Training Inside

Every AE in the room operates inside the standard RevOps stack. Reference these tools by name during the training so reps know which dashboard or workflow you mean. Pin the dashboard you'll inspect in Apollo on a shared screen before the meeting starts, queue the most recent recording from Chili Piper as the coaching artifact, and have Zoom open in a second tab for the post-meeting cadence updates. The manager who shows up with these three browser tabs ready saves 8 minutes of meeting setup.

• Apollo at $59/user/month Basic, $99 Pro — data + sequencing combo
• Calendly at $12-$72/user/month — meeting scheduling
• Chili Piper at $22.50/user/month Spicy, $30 Hot — inbound concierge routing
• Slack at $8.75/user/month Pro, $15 Business+ — rep-manager async coaching
• Zoom at $15.99/user/month Pro, $21.99 Business — training delivery + recording
• Salesforce at Sales Cloud Enterprise $165/user/month, Unlimited $330 — CRM + opportunity tracking

Benchmark Context

ScaleVP ("2026 Sales Velocity Benchmark") found that structured weekly training increased deal-stage velocity by 28% for $50K-$500K ACV cycles. Anchor the training narrative on this stat — it's the credibility frame that turns a 60-minute meeting from "another sales pep talk" into "the weekly working session the manager is measured on." Print the stat at the top of the meeting agenda; reps remember the number, and quoting it builds the same shared vocabulary that Lessonly, Spekit, and Highspot all flag as the top predictor of multi-quarter training-program ROI in their 2026 customer benchmarks.

Section 1 — Why the Datasheet Does Not Sell (5 min)

Open with the truth scientists already know on the whiteboard: a reagent spec sheet proves nothing about whether it works in their hands, on their sample, in their assay. Reps who lead with sensitivity numbers and catalog features lose to the rep who understood the customer's protocol well enough to predict where it breaks.

Set the frame:

• The old motion: Recite the datasheet, quote the list price, lose to the incumbent the scientist already validated.
• The new motion: Map the workflow and application, prove technical fit with a sample or trial, align the close to the funding cycle.
• The buying reality: You are selling to the bench scientist (cares about it working on their sample), the PI or lab director (cares about publishable, reproducible results and budget), and procurement or the core-lab manager (cares about price, contracts, and standardization). Technical credibility opens all three doors.

The discipline is consultative technical selling: the scientist trusts the rep who speaks their methodology — the assay format, the sample matrix, the controls — not the rep who reads the brochure. Neil Rackham's "SPIN Selling" supplies the structure — Situation, Problem, Implication, Need-payoff — applied to a protocol, not a budget. Read the line aloud: *"You do not sell the reagent. You make the experiment work."*

---

Section 2 — The Workflow and Application Map (15 min)

This is where credibility is built. The rep diagrams the customer's actual experiment before recommending a product. Walk the room through the verbatim template — have every rep complete it for a live account right now.

Verbatim Workflow Discovery Template (rep completes before recommending a SKU):

> 1. Lab and group: [Institution or company] — [Core lab, academic group, or biotech R&D] — [Field, e.g., immuno-oncology] > 2. The application: [e.g., multiplex cytokine quantification from limited mouse serum] > 3. Current workflow and pain: [What kit/instrument now, where it fails — sensitivity, sample volume, reproducibility, throughput] > 4. What working looks like: [The result that gets a paper published or a program decision made] > 5. The deciders: Bench scientist [name] — PI or lab director [name] — procurement or core manager [name] > 6. Funding and timing: [Grant in hand, grant pending, capital cycle, end-of-fiscal-year spend, instrument capital committee — and the date]

Coach the "map before you pitch" rule. A rep who recommends a SKU without diagramming the workflow is reading a catalog. Mike Bosworth's "Solution Selling" is the discipline — diagnose before you prescribe. If a rep writes "they need a better ELISA kit," push back: *"For what sample matrix, at what sensitivity, with what sample volume, and what is failing in their current protocol?"*

Show the bad example: *"I sent them the catalog and the validation data."* That is not selling, that is mailing. Credibility is knowing their assay better than the last rep did.

---

Section 3 — The Credibility-Killing Trap Words (10 min)

Scientists detect a non-technical rep in one sentence. One wrong line and you lose the bench forever. Drill the language.

• Speak the methodology, not the marketing — assay format, sample matrix, limit of detection, controls, reproducibility. The scientist tests you fast.
• Offer to validate, never to "trust the data." A sample, a trial, a side-by-side run beats any datasheet claim.
• Respect the funding reality. Asking about the grant cycle is not rude; it is the only way to time the close.

What to NEVER say to a research scientist (read these aloud, slowly):

• "Our kit is the gold standard" (unverified marketing claim; a scientist wants to validate it on their own sample, not take your word)
• "It works for any application" (no assay works for every matrix; this signals you do not understand the science)
• "Just trust our validation data" (scientists trust data they generate; offer a sample, not a brochure)
• "This is the cheapest option" (price-first signals you missed that reproducibility and a publishable result matter more than unit cost)
• "What is your budget?" (asked cold, it reads as transactional; ask about the grant and the timing instead)
• "Our competitor's reagent has quality issues" (disparagement reads as desperation; let your side-by-side data speak)

Neil Rackham's Implication question, applied to the bench: *"When that assay fails to reproduce, what does it cost you — a repeated experiment, a delayed submission, a blown grant milestone?"* Make the scientist name the cost of the failed result — then you are selling reproducibility, not a SKU.

---

Section 4 — The Sample and Trial Close (10 min)

The sample or trial run exists to let the bench validate technical fit so the data does the selling. Run it from a script. Use the verbatim opening.

Verbatim Sample/Trial Script (rep delivers these exact words):

> Rep: "Before I recommend anything, I want to make sure this works on your sample. You are quantifying cytokines from limited mouse serum and your current kit needs more volume than you have. Is that the core problem?" > > [Bench scientist confirms or corrects the protocol. The rep writes down exactly what THEY say.] > > Rep: "Here is what I propose — not a quote. I send you enough reagent to run your samples side by side against your current method. You generate the data, you decide. If our sensitivity at your sample volume does not beat what you have, you owe me nothing." > > [Rep turns to the PI or lab director.] > > Rep: "Dr. Chen, if this gives you publishable, reproducible data from the sample volume you actually have, what does that do for the immuno-oncology program timeline?" > > [PI connects it to a grant milestone or paper — that is the close.] > > Rep, to the core manager: "And if it standardizes across the core, here is the volume pricing and the consumables plan. When does your grant or capital window open?"

Do NOT:

• Recommend a SKU before the workflow is mapped — a recommendation without a diagnosis is a guess the scientist will catch.
• Skip the validation offer — scientists buy data they generated; a sample run is your strongest close.
• Ignore the funding date — a technically won deal with no grant or capital alignment sits unfunded for two quarters.

---

Section 5 — The Grant-Cycle Math and the Standardization Play (15 min)

This is the part reps misjudge, and why technically won deals stall. Build the operating cadence on the whiteboard.

The math (for a reagent landing into an academic core lab):

• Single bench scientist annual reagent spend: ~$45K — the beachhead
• Core-lab standardization across 6 groups using the same assay: 6 × $45K = ~$270K annual standing reagent revenue
• Reproducibility value to the customer: one failed, non-reproducible experiment costs a postdoc 3 weeks plus sample — the scientist values reliability over a 5 percent price difference
• Instrument pull-through: a $120K bench instrument that consumes your reagents locks in ~$80K per year of consumables for the asset life

Funding controls timing. A federal grant has an award date and a spend window; end-of-fiscal-year produces use-it-or-lose-it spend; capital instruments route through an institutional committee. A rep who does not map the grant or capital cycle misses the window and the deal slips two quarters. Inspect the funding date every 30 days.

Common scientist and procurement objections (rehearse the comebacks):

• *"We already validated the incumbent reagent."* — Then a side-by-side costs you one afternoon. If ours does not beat it on your sample, keep what you have. Let the data decide.
• *"The grant has not been awarded yet."* — Understood. Let me get you a sample now so you are ready to order the day the funds land, and we lock the volume pricing in advance.
• *"Procurement says go with the cheapest qualified vendor."* — Cheapest qualified means it has to work on our samples first. Here is the side-by-side; a reagent that fails reproducibility is not qualified at any price.

Have each rep identify the funding date on their top deal before they leave the room. No exit without a grant or capital window mapped.

---

Section 6 — Commitments and Close (5 min)

Each rep leaves with three written commitments, pinned to their CRM:

• My top three accounts have a mapped workflow — application, current method, and failure point — by end of month.
• One deal moves to a side-by-side sample run this quarter, with a result tied to a publishable or program outcome.
• Every active opportunity has a dated funding window — grant award, fiscal-year spend, or capital cycle — documented in the account plan.

Close by reading the technical-selling truth aloud: *"The scientist does not buy your spec sheet. They buy the experiment working on their bench, the result they can publish, and a vendor who understood the assay. Be that rep."*

Then pin the application-fit checklist in the team channel and have every rep tag their top opportunity for a workflow review.

---

FAQ

Q1: I am not a scientist — how do I build technical credibility fast? A: You do not need a PhD; you need to map their workflow accurately and ask precise questions about sample matrix, sensitivity, and reproducibility. Bring your field applications scientist for depth, but you must speak the methodology well enough to diagnose, not just describe.

Q2: The scientist already validated a competitor — is the deal lost? A: No. Offer a side-by-side sample run on their actual sample. Scientists trust data they generate. If your reagent wins on their critical endpoint at their sample volume, validation is reversible; if it does not, you learned cheaply.

Q3: How do I handle the funding timing? A: Map it explicitly — grant in hand, grant pending with an award date, fiscal-year spend window, or capital committee cycle. Send samples while funds are pending so the scientist is ready to order the day money lands. Funding controls the close date, not your pipeline.

Q4: When do I bring in the field applications scientist? A: After the workflow is mapped and a sample run is on the table, to ensure technical success and answer deep methodology questions. The FAS proves fit; you own the relationship, the commercial terms, and the funding timing.

Q5: How do I grow a single bench win into core-lab standardization? A: Land one group, generate published or reproducible results, then reference-sell to the other groups running the same assay. Core-lab standardization turns a $45K beachhead into a standing reagent agreement across the facility.

Q6: How is reagent selling different from selling lab instruments? A: Reagents are recurring, high-frequency, application-fit-driven consumables; instruments are a larger capital purchase routed through a committee and funding cycle. The smart play sells the instrument to lock in years of reagent and consumable pull-through.

---

Related on PULSE

• [Active Listening Lab: Paraphrasing and Clarification Exercise Template](/knowledge/st0717)
• [Life Insurance Needs Analysis — 60-Min Training](/knowledge/st0011)
• [The Sandler Selling System: Ready-to-Run Mini-Training for New Hires](/knowledge/st0794)
• [Selling with Stories: Narrative Structure Template for a 45-Minute Sales Workshop](/knowledge/st0792)
• [Leveraging Social Selling: Hands-On Activity Template for a Remote Team Session](/knowledge/st0787)
• [The Consultative Selling Blueprint: Facilitator’s Guide for a 45-Minute Workshop](/knowledge/st0778)

Sources

1. Neil Rackham, *SPIN Selling*, McGraw-Hill, 1988.
2. Michael Bosworth, *Solution Selling: Creating Buyers in Difficult Selling Markets*, McGraw-Hill, 1994.
3. John McMahon, *The Qualified Sales Leader*, McMahon Group, 2021.
4. Keith M. Eades, *The New Solution Selling*, McGraw-Hill, 2003.
5. Matthew Dixon and Brent Adamson, *The Challenger Sale*, Portfolio/Penguin, 2011.
6. Society for Laboratory Automation and Screening (SLAS), *laboratory workflow and core-lab practice resources*, slas.org.
7. Association of Biomolecular Resource Facilities (ABRF), *core-laboratory standards and benchmarking*, abrf.org.
8. Mike Weinberg, *New Sales. Simplified.*, AMACOM, 2012.