How to build new logo pipeline for scientific instruments sold to core facilities and CROs

Nobody signs, which is the first thing to understand. A core facility director runs a recharge centre inside an institution: they set a rate card, bill labs by the hour or the sample, and cover staff and service out of that income. They are a small business operator who cannot raise prices, cannot choose their customers and does not hold a capital budget.

The money comes from somewhere else. Usually an instrumentation grant, sometimes institutional matching funds, occasionally a department with a surplus at year end. Every one of those routes runs through a faculty principal investigator who has to be willing to put their name on an application, and through a research office that cares about cost share, floor space and whether something similar already exists two buildings away.

So the buying group is four deep: the core director who will operate it and quietly decides, the principal investigator who applies, the research office that approves the match, and the other labs on campus whose letters of support are the evidence that demand exists.

At a contract lab the shape changes and the logic does not. The operations director buys capacity, the commercial lead has to sell the resulting hours, and an instrument nobody can bill against is the same stranded asset it would be in a university basement.

The beliefs in this niche are not resistance. They are the accurate residue of how instrument purchasing has worked for thirty years, and they are the reason a technically superior product from a small company loses to a familiar one from a large company.

What they believe today.

• Instruments arrive when money appears. The core is downstream of funding, so the posture is to wait, keep a wish list, and respond when an opportunity is announced.
• The decision is specification against specification. Sensitivity, resolution, throughput, footprint, side by side in a table, and the best column wins.
• Service and consumables are a tax to be negotiated down, not part of the decision.
• A small vendor is an operational risk. Who fixes it, is there a field engineer within a day's drive, and what happens to us if they are acquired or fold.
• Demand is somebody else's job. Faculty ask for capability, the core provides it, and generating new demand is not something a core director thinks of as their work.

What has to be true before they can buy.

• The purchase is decided at the application, not at the award. The instrument named in the proposal and quoted in the budget is the instrument that gets bought a year later. Arriving after the award means competing against a specification somebody else already wrote.
• Utilization beats specification. An instrument with a modest spec running at seventy percent of capacity funds its own service and its own staff line. A better instrument at twenty percent is a line item the institution regrets, and every core director has seen one.
• Cost of ownership across the funded period is the real comparison, and being explicit about it is an advantage rather than an exposure. The vendor who volunteers the five year number is the one who looks like they have done this before.
• The service risk is answered with evidence, not reassurance. Installed base, response time, uptime, parts availability and three named installs who will take a phone call. Academic buyers ring each other, always, so make that easy rather than hoping it does not happen.
• Demand can be built, and you are better placed to build it than they are. The publication record of their own campus is public, searchable and something you can read by technique. A list of the eight labs whose recent work would have used this instrument is exactly the evidence the application needs and exactly the thing the core director cannot easily assemble.

That last belief is the one that moves the sale. Everything else on this page is timing. The demand map is the reason the core director takes your call in a year when they have no money and no plan to have any.

• Instrumentation award databases. The national funders publish shared instrumentation awards with the institution, the principal investigator, the instrument class and the amount. Read them three ways: who just won and is now standing up a new capability, who bought a competitor's box and will need everything around it, and which institutions apply every year regardless of outcome.
• The application calendar itself. These programs run roughly one cycle a year with a fixed deadline. That is a trigger about the calendar rather than about the account, and it is the spine the whole program hangs on, because your useful window opens about six months before the date and closes weeks before it.
• New research buildings, renovations and core consolidations, visible in institutional announcements and capital plans. Instruments follow space, and a core moving into a new building has a list.
• Core director changes and new core launches. Institutions publish core directories with named staff, and the person who has just taken over a facility is rebuilding its capability map and its rate card in their first year.
• Publications and preprints by technique, filtered to one institution. This is not a trigger about intent, it is the demand map: the labs whose methods sections show they are working around the absence of your instrument.
• Competitor instrument end of support announcements. A core running a platform the manufacturer has just discontinued has a forced replacement, an unhappy user base and a justification that writes itself.
• Contract lab service line and capability announcements, plus their job posts naming a specific platform. A contract lab hiring scientists on a technique is a contract lab that has already sold the work.

The award databases and the publication demand map are the two to build on. One tells you who is in the cycle. The other tells you what to put in the first email that nobody else can.

• Is there a published rate card? Core facilities post them, and a rate card tells you the recharge model, the hourly economics and whether this facility runs like a business or like a cupboard.
• Is there a credible applicant? Somebody on that campus needs the standing and the appetite to put their name on an instrumentation application. No applicant, no purchase, however keen the core is.
• Can the institution meet a cost share where one is required? Doctoral institutions carry matching obligations on some programs, and an institution that has not matched anything recently is telling you something.
• Is there demand you can evidence today? If a scan of that campus produces fewer than five labs whose recent work needs this capability, the application will not survive review and you should spend the week elsewhere.

Lead with their campus, not your instrument. The core director receives specification sheets continuously and reads none of them, because a specification is an answer to a question they have not been asked to consider.

What they have never received is a list of their own colleagues who need the capability they do not have. Send that.

All three give something before asking for anything, and none of them mentions a demonstration. The demonstration is your ask. The demand map is theirs.

• A specification sheet as the first touch. It answers a comparison the buyer is not yet running and it invites them to run it against a larger competitor.
• The word solution anywhere near a scientist. This audience reads it as a signal that the sender does not understand the technique, and the judgement is instant and permanent.
• A fiscal year end discount as the angle. It works occasionally on small consumable orders and it teaches the buyer that your price is soft, which is expensive later when you are negotiating a multi year service contract.
• Anything sent to a faculty principal investigator over the head of the core director. Campuses are small, the note gets forwarded, and you have just told the person who decides that you tried to go around them.
• Claims about being the only one. Somebody on that campus has read the competing literature more carefully than you have, and being corrected in the first exchange is difficult to recover from.

We have no budget for this. Almost always true and almost never relevant, which is why the standard reply of asking about next year fails. The money for an instrument does not sit in a budget waiting to be spent, it is created by an application. Move the conversation from money to the document, offer the demand map and the quote structure, and the objection dissolves because you are no longer asking them to spend anything.

We already have something that does that. Ask two questions instead of arguing: what is the current wait time for users, and what percentage of capacity is booked. A core with a six week queue has a demand case already written. A core with an idle instrument has just told you the campus does not need a second one, which is worth knowing in week one rather than month nine.

You are a small company. What happens when it breaks. The most legitimate objection in this niche and the one most often answered with warmth instead of numbers. Give the installed base, the median response time, whether parts ship from stock, what the firmware situation would be if you were acquired, and the names of three cores who will take the call. Then stop talking. Reassurance reads as evasion here.

Our users will not change methods. Correct, and this is where instrument sales quietly die after the purchase order. Bring the method transfer plan into the sales conversation rather than the installation conversation: which assays move first, who validates them, how long the parallel running period is. A core director who can see that plan can promise their users something, and a core director who cannot will keep the old instrument running beside yours.

• Capital: commonly $80K to $500K for a benchtop or mid range system, and into seven figures for high end platforms funded through the larger instrumentation programs.
• Service contract: typically eight to twelve percent of capital annually, and the number that decides whether you are still installed in year five. Fund year one inside the capital request wherever the program allows it.
• Consumables, reagents and validated kits: the recurring line, and often the difference between a break even placement and a good one. Price it visibly rather than hiding it, because reviewers look for it.
• Evaluation placement: two to eight weeks, conditional on the core supplying samples and a named operator. Produces the preliminary data that goes into the application.
• Signer: the institution's procurement office signs, the core director decides, the principal investigator applies, and the research office can veto on space or cost share. Cycle: twelve to twenty four months from first contact to purchase order, structured entirely around one annual deadline.

One consequence of that cycle is worth stating plainly. Your pipeline is not a funnel, it is a calendar, and the accounts you fail to reach before this year's deadline are not lost, they are next year's, provided you keep them warm without pestering them.

• Quarterly, pull the instrumentation award databases and update three lists: new awards in adjacent techniques, competitor placements, and institutions that apply every cycle.
• Monthly, run a publication scan by technique for the next tranche of target institutions and build the demand map before you write to anyone there.
• Six months before the annual deadline, open the accounts you intend to be in. Three months before, the conversation is about the budget justification. Three weeks before, it is too late and you should say so kindly and diarise the next cycle.
• Continuously, watch core director changes and new core launches, which arrive on no schedule and are the best cold entry point this niche offers.
• Ten to fifteen institutions a week is a full program. Each one needs a demand map before the first email, which is real work, and it is the work that makes the difference.
• Three touches, then leave them until the next cycle. This universe is a few hundred institutions and a few thousand cores, and it has a long memory in both directions.

The instrument is not the product. The justification is the product, and the company that helps write it is the company named in the budget line twelve months later.

Everything above is about who and what. This is about how, and it is where most outbound in this niche quietly dies. Seven rules. None of them are optional.

None of this is specific to your niche. All of it is specific to whether anyone ever reads the angle you spent an hour getting right.

That is what we do. ExpertLayer runs this exact loop for firms with proprietary technology: the award database pull, the per institution publication scan that produces the demand map, the core directory and staff changes, the timing against the annual deadline, the sending across warmed mailboxes, and the reply reading. You take the scientific conversations, which is the part that cannot be delegated.

The first step is free and it is the same research described above. Send us your website and we will come back with 10 companies that hit these triggers right now, with the award, the publication evidence or the staff change, the contact, and the opening line for each.