By the time a multi-site practice group or DSO issues a formal RFP for practice management software, the shortlist is usually already three vendors long. The RFP looks like an open competition. It rarely is one.
Procurement teams don't start their research the day the document goes out. They start months earlier, quietly, with a Google search and a scroll through whatever a vendor has published. By the time the RFP lands in your inbox, most of the evaluation has already happened without you in the room.
The evaluation nobody tells you about
Ask any founder who's won an enterprise health tech deal how the process actually started, and the RFP is rarely the true beginning. Someone on the buying committee, usually the ops lead tasked with vetting vendors, had already read your blog, checked your case studies, and formed an opinion weeks before legal drafted the first document.
This is the part of the sales cycle that content strategy for complex sales has to account for, and most health tech companies don't. They treat content as something that supports an active deal. It should be doing that work before the deal exists.
A practice group evaluating scheduling software for 40 locations isn't starting from zero. Someone on staff has probably already Googled "best patient scheduling software for multi-site practices" and read whatever came up. If your company wasn't in those results, or was there but said nothing specific, you didn't make the list of people they call.
What the pre-RFP research phase actually looks for
Four things show up again and again when you talk to the people who run vendor evaluations for practice groups and DSOs.
Proof you understand their operating model. A 15-location group and a solo practice buy software differently. Content that talks about "practices" in the abstract signals you've never sold past location three. Content that names the specific friction of multi-site scheduling, cross-location patient records, or centralized billing tells them you've been inside this problem before.
A track record they can verify without calling you. Case studies, named clients where possible, specific numbers where you have them. If your published content leans on vague claims like "trusted by leading practices," that's a red flag to anyone who's evaluated software before. They've learned to read past it.
Evidence you'll still be relevant in three years. Multi-site software decisions come with long implementation timelines and real switching costs. Buyers are quietly asking whether your company will still exist, and still be good, three years from now. A steady publishing history says more about staying power than a funding announcement does.
Something specific enough to remember. The vendors procurement teams shortlist without prompting are the ones who said one memorable, specific thing, not the ones who covered every feature evenly. A sharp point of view on how DSO consolidation changes vendor requirements does more than a generic "why choose us" page ever will.
Why reactive content always arrives too late
The instinct, once an RFP shows up, is to scramble. Pull together a case study. Write a comparison page. Get a testimonial from your best client. All reasonable moves, and all too late to do the job that mattered.
Content written after a deal opens reads as sales collateral, because it is sales collateral. It's built to answer this buyer's questions, not to demonstrate a standing point of view. Buyers can tell the difference. A case study written specifically for one prospect, dated the week the RFP dropped, doesn't carry the same weight as one that's been sitting on your site for a year, already indexed, already read by other buyers before this one.
The content that actually wins the deal was written when there was no deal to win. It was written for the version of the buyer who was still just quietly researching, months before anyone on their side had opened a spreadsheet to compare vendors.
What "written a year early" looks like in practice
It's about publishing the specific things a procurement committee will be looking for before they know they're looking for them.
Write for the operational reality of your buyer's next stage of growth, not just their current one. If Scaling Sarah's company sells to 5 to 20 location groups today but wants to move upmarket to 50-plus location DSOs, content aimed at that operating model should already exist before the first DSO evaluation shows up. Waiting until a DSO opens an RFP means starting the trust-building process from a standing start, against competitors who've been publishing for that buyer for a year.
Name the specific failure modes your buyer has lived through. A piece on why centralized scheduling rollouts stall at location 12, with the real operational reason (not a generic "change management is hard"), reads as insider knowledge. That's the kind of thing a procurement lead forwards to a colleague without being asked.
Publish steadily enough that a buyer researching you six months from now finds a body of work, not three posts from last spring. Consistency is itself a signal. A content archive with real gaps in it quietly tells a buyer that content, and by extension marketing, isn't something this company takes seriously. That reads as risk to a procurement team weighing a multi-year contract.
Where DSOs and practice groups actually go looking
The research phase usually plays out as three or four separate checks, spread across a few weeks, done by two or three different people on the buying side.
The ops lead searches for operational proof: has this vendor written anything about multi-site rollouts specifically, or does everything on their blog read like it was written for a single-location practice? The finance lead, if there is one this early, is quietly checking pricing pages and case studies for anything that hints at total cost of ownership across a large footprint. Someone, often more junior, is checking G2 and Capterra reviews and cross-referencing them against whatever the vendor has said publicly, looking for gaps.
None of these people talk to your sales team during this phase. That's the point. They're forming an opinion in private, and the only input you have into that opinion is what you've already published.
A short audit before your next content sprint
Before planning the next quarter of articles, run your own site through the questions a procurement committee is quietly asking.
Search your own blog for content written specifically for a buyer three sizes bigger than your current average client. If there's nothing there, that's the gap a competitor's content is currently filling instead of yours.
Check whether your last 5 published pieces contain a number, a named client, or a specific operational detail a competitor couldn't have written without direct experience. Generic content doesn't get remembered. Specific content does.
Look at your publishing cadence over the last 12 months. A gap of 2 or 3 months reads as a company that deprioritized content the moment things got busy, which is exactly the kind of inconsistency a buyer weighing a multi-year contract quietly notices.
Ask your sales team for the last 3 deals that stalled after an RFP was issued. In each case, find out what content existed on your site at that point that could have answered the buyer's underlying concern before they ever wrote the requirement into the document. If nothing existed, that's this quarter's content brief.
The budget conversation this changes
Sarah's harder conversation with her VP is about why a channel with no direct attribution deserves a line item next to paid acquisition, which shows a cost-per-lead number every week.
The RFP timeline gives her a sharper argument than "SEO." Paid spend stops producing the moment the budget stops. A piece written today about multi-site scheduling failure modes is still sitting there, still ranking, still doing the pre-RFP research work, when a DSO opens an evaluation 14 months from now. It's a pipeline-timing argument, one a VP weighing budget against a 6 to 12 month enterprise sales cycle can actually use.
It also reframes what "content ROI" should be measured against. A blog post that never gets a single form fill can still be the reason a company made a shortlist. Most attribution models can't see that. The procurement lead who read it 8 months ago and forwarded it to her boss never fills out a contact form. She just remembers the name when the RFP goes out.
Building a habit of writing for the deal you don't have yet
Practically, this means treating your content calendar as partly built around the buyer you want in 12 months, not just the one you're actively selling to now.
Keep a running list of the operational questions that came up in the last 10 lost or stalled deals, especially the ones that came from bigger, more complex buyers than your current average client. Those questions are a preview of what next year's procurement committees will be quietly researching. Write for them now, while there's no deal on the line and no pressure to make the piece sound like a pitch.
Talk to your sales team about which pieces of content actually come up in conversation, unprompted, from prospects who found them on their own. That's the closest signal you'll get to what a procurement committee is actually reading before they ever talk to you.
What the RFP actually confirms
By the time the document arrives with a submission deadline and a scoring rubric, most of the real evaluation is already behind you, whether you did the work to influence it or not. An RFP formalizes a decision that mostly already happened, weeks or months earlier, in a browser tab nobody on your team ever saw.
Treat the year before the RFP as the part of the sales cycle worth investing in. That's where the shortlist gets written, long before anyone types up a document asking you to prove you belong on it.