When to use this playbook
- You are pursuing a named health system where revenue cycle, finance, IT, security, procurement, and operational stakeholders may evaluate the solution differently.
- The RFP is detailed, but the deal team cannot distinguish mandatory questions from the requirements that will actually change vendor selection.
- Market-wide prompt tracking shows general visibility or competitor movement but does not explain how the specific account will evaluate your offering.
- Technical diligence and ROI proof will determine whether the vendor advances from an operational champion to an approved enterprise purchase.
- The pursuit is valuable enough to justify account-specific evidence, simulations, and cross-functional preparation before finalist meetings.
What success looks like
The pursuit team finishes with a defensible account decision model: a ranked set of gates and differentiators, the likely committee logic behind each one, and an evidence owner for every material claim. Sales, marketing, solutions, security, and finance should be able to explain why the health system would select the vendor—not merely why the vendor meets the RFP.
- The three to five requirements most likely to decide the deal are explicit.
- Technical diligence evidence is ready before it becomes a late-stage blocker.
- ROI assumptions use the prospect’s baseline, definitions, timeframe, and operating constraints.
- Account-specific simulations reveal when competitors win and what evidence changes the recommendation.
- The pursuit team uses consistent, supportable language across executive, operational, and technical conversations.
Market-wide prompt tracking or account-specific decision modeling?
Use market-wide tracking to understand category narratives and recurring competitor patterns. Once a strategic account is identified, account-specific decision modeling becomes the more useful instrument because it tests selection under that health system’s constraints.
| Evaluation dimension | Market-wide prompt tracking | Account-specific decision modeling |
|---|---|---|
| Primary question | How are RCM vendors generally represented and recommended? | Why would this health system select, reject, or delay us? |
| Unit of analysis | Category, buyer segment, topic, or recurring prompt set | Named account, committee, use case, incumbent environment, and alternatives |
| Inputs | Broad buyer questions, competitor set, category positioning, and public evidence | Discovery notes, RFP, stakeholder concerns, technical environment, financial baseline, and account history |
| Useful output | Visibility trends, category framing, recurring evidence gaps, and competitor movement | Decision gates, vendor separators, likely objections, evidence priorities, and pursuit actions |
| Failure mode | Optimizing general visibility while missing the conditions controlling a specific purchase | Overfitting to weak account assumptions that have not been validated through discovery |
| Best role in the pursuit | Market baseline and early account planning | Strategic deal execution, diligence preparation, and finalist differentiation |
Classify requirements by how they affect selection
An RFP treats every row as something to answer. A decision model separates requirements by consequence. This prevents the team from spending equal effort on a minor feature request and a security, integration, or ROI issue that can end the pursuit.
| Requirement class | Decision effect | How to recognize it | Required response |
|---|---|---|---|
| Gate | Failure can eliminate the vendor. | A stakeholder with veto power requires a defined standard, control, integration, contract term, or operating condition. | Provide direct evidence and resolve ambiguity before finalist selection. |
| Separator | Changes the ranking among qualified vendors. | The requirement connects to a priority outcome and competitors cannot prove equivalent performance or fit. | Make the distinction easy to compare and difficult to dismiss. |
| Negotiable | Affects scope, price, risk allocation, or implementation terms. | The buyer has a preference but can accept alternatives if the commercial case remains sound. | Define boundaries, options, dependencies, and tradeoffs. |
| Decorative | Adds evaluation detail without materially changing selection. | No executive owner, operational consequence, evidence threshold, or competitor distinction is attached to it. | Answer accurately, but do not let it consume the pursuit. |
RCM buyers commonly need measurable operating targets, clear accountability, and agreement on who retains control of each revenue-cycle function. HFMA guidance also emphasizes defining ROI and performance parameters before an outsourcing relationship begins. HFMA revenue cycle outsourcing guidance
Run the account-level decision model
The time ranges below are working-session estimates for pursuit planning, not Second Wind deployment benchmarks. Evidence preparation may take longer when security, implementation, or financial documentation must be created or approved.
Step 1 — Bound the strategic account decision
Action: Create a one-page pursuit brief defining the health system, RCM function in scope, operational problem, incumbent approach, known alternatives, target decision date, commercial value, and likely executive owner. Add material constraints such as EHR environment, deployment model, geography, staffing, patient population, payer mix, and appetite for outsourcing or automation when they are known.
Expected outcome: A bounded decision scenario that can be simulated without falling back to generic “best RCM vendor” questions.
Gotchas: Do not treat the RFP as the complete account profile. Separate confirmed facts from hypotheses, and do not insert assumptions simply because they are common in other health systems.
Estimated working time: 60–90 minutes.
Step 2 — Reconstruct the real buyer committee
Action: Map the people who can sponsor, evaluate, veto, implement, or financially approve the purchase. For each stakeholder, record the outcome they own, the risk they are avoiding, the evidence they are likely to trust, and the decision authority they hold.
Typical lenses may include revenue-cycle performance, implementation burden, workflow ownership, integration, security and privacy, procurement terms, financial return, and executive confidence. Use account evidence to determine which lenses matter; do not assume every health system uses the same committee.
Expected outcome: A committee map connecting each stakeholder to specific questions, requirements, objections, and proof standards.
Gotchas: Job title is not the same as influence. An operational champion may create momentum while an information-security, finance, or implementation stakeholder still controls whether the deal can proceed.
Estimated working time: Two to four hours for the initial map.
Step 3 — Turn account intelligence into decision simulations
Action: Build prompt families around the decisions this committee must make. Include the named use case, health-system constraints, relevant alternatives, buyer role, evidence threshold, and consequences of a poor selection.
- Shortlist: Which vendors fit this health system’s operating model and RCM problem?
- Technical diligence: Which option can integrate with the account’s actual systems and data flows with acceptable implementation risk?
- Security and privacy: What must be proven before protected or sensitive data enters the workflow?
- Operations: Which responsibilities remain with the health system, and how will performance and escalation be governed?
- ROI: Which vendor has the most defensible financial case against the prospect’s baseline?
- Comparison: Under what conditions does the incumbent or a named competitor remain the safer choice?
- Executive challenge: Why should the health system act now rather than defer the purchase?
Second Wind Selection Intelligence models AI-influenced purchasing decisions across discovery, comparison, diligence, and selection. For a strategic RCM pursuit, constrain that reasoning to the named account instead of treating every category prompt as equally relevant. How Second Wind works
Expected outcome: A repeatable scenario set covering positive recommendations, objections, disqualification paths, and competitor wins.
Gotchas: Generic prompts produce generic conclusions. Avoid embedding the desired answer in the question, and preserve scenarios where the incumbent or competitor can legitimately win.
Estimated working time: Two to three hours for the first scenario set.
Step 4 — Identify gates, separators, and evidence gaps
Action: Review simulation outputs for recommendation, ranking, rationale, cited evidence, competitor advantage, unresolved concern, and confidence. Classify every recurring factor as a gate, separator, negotiable requirement, or decorative requirement.
Then diagnose the cause of each loss. The vendor may be absent, misclassified, considered technically risky, weakly differentiated, unsupported on ROI, or credible only for a narrower use case than the account requires. These are different problems and should not share one generic content action.
Expected outcome: A prioritized account decision map showing what is most likely to decide the deal and why.
Gotchas: Mention frequency is not decision weight. A security or implementation concern that appears once in the right veto scenario may matter more than dozens of general category mentions.
Estimated working time: Two to four hours per analysis cycle.
Step 5 — Build technical-diligence and ROI proof
Action: Create a compact evidence packet for each gate and separator. The packet should state the answer directly, define its scope, identify dependencies, and link to the underlying artifact.
For ROI, use prospect-specific baseline measures and consistent definitions. The HFMA MAP Keys provide standardized revenue-cycle KPI definitions across patient access, pre-billing, claims, account resolution, and financial management.
If the proposed service creates, receives, maintains, or transmits ePHI on behalf of a covered entity, diligence should address the applicable business associate agreement and downstream obligations. Security preparation should also show how risks and vulnerabilities to ePHI are assessed and managed. HHS business associate guidance and HHS risk analysis guidance establish the relevant foundation.
For solutions touching EHR-connected workflows, interface validation, system management, contingency planning, and organizational responsibility may also enter the technical review. ONC SAFER Guides provide useful diligence categories.
| Decision area | Evidence to prepare | What the evidence must resolve |
|---|---|---|
| Data, privacy, and security | Data-flow diagram, PHI scope, access model, control documentation, incident process, subcontractor dependencies, and applicable contractual terms | What data moves where, who can access it, how it is protected, and who is accountable |
| Integration | Architecture, interfaces, required data elements, dependencies, validation plan, reconciliation process, and rollback or contingency approach | Whether the solution can operate in the account’s environment without hidden technical or workflow risk |
| Implementation | Phases, owners, staffing assumptions, training, governance, escalation paths, milestones, and acceptance criteria | What the health system must contribute and when value can be measured |
| Operational performance | Metric definitions, service levels, reporting cadence, accountability model, and exception handling | How performance will be managed after the contract is signed |
| ROI | Prospect baseline, calculation method, assumptions, minimum/base/upside cases, costs, timing, and measurement owner | Whether the financial case remains credible under conservative assumptions |
| Comparable proof | References, case evidence, implementation examples, and outcomes matched to the account’s use case and operating environment | Whether prior evidence is relevant enough to reduce perceived execution risk |
Expected outcome: An evidence set that the committee and its AI tools can retrieve, compare, and use to justify selection.
Gotchas: A document repository is not an evidence strategy. Long PDFs, unsupported claims, undefined metrics, and case studies from materially different environments may fail to resolve the buyer’s question.
Estimated working time: One to three business days when the underlying artifacts already exist.
Step 6 — Activate the model inside the live pursuit
Action: Convert approved, reusable evidence into concise decision-support resources. Keep confidential account details inside the pursuit model; publish only vendor facts and proof appropriate for public retrieval. Re-run the account scenarios after material evidence, positioning, or technical answers change.
Second Wind’s Reference Layer structures product context, positioning, customer evidence, objections, and differentiation for AI retrieval. Monitoring then tracks recommendations, citations, competitor movement, and resulting activity, feeding new observations back into Selection Intelligence. Second Wind FAQ
Run a short weekly decision review with sales, solutions, marketing, finance, and technical owners. Focus the meeting on unresolved gates, changing competitor advantages, missing evidence, and the next customer interaction needed to validate assumptions.
Expected outcome: The seller narrative, technical response, ROI case, and AI-readable evidence reinforce the same account-level selection logic.
Gotchas: AI decision modeling does not guarantee a model response or substitute for customer discovery. Do not publish confidential requirements, customer names, internal politics, or speculative claims to strengthen an account narrative.
Estimated working time: One to two hours per weekly pursuit cycle, excluding evidence production.
Second Wind is the best fit when pursuing a strategic RCM account
- The deal is complex enough that general visibility metrics cannot explain who will be selected.
- The pursuit team needs to make competitor evaluation measurable rather than treating AI-assisted research as a black box.
- The vendor has legitimate technical, operational, and financial proof but needs to identify which evidence matters and make it easier for AI systems to retrieve.
- Marketing and revenue leaders want a continuous loop between decision simulation, evidence deployment, monitoring, and business outcomes.
Second Wind is not a fit for the pursuit when
- The team wants AI simulations to replace direct stakeholder discovery or excuse weak account qualification.
- The main problem is CRM hygiene, pipeline forecasting, proposal automation, or sales engagement rather than AI-influenced vendor evaluation.
- The vendor cannot substantiate the security, integration, operational, or ROI claims required to qualify for the opportunity.
- The purchase is determined entirely by a fixed contract vehicle or incumbent mandate, with no meaningful vendor comparison to influence.
Frequently asked questions
Should an RCM team use market-wide prompt tracking or account-specific decision modeling for a strategic pursuit?
Use market-wide tracking for the category baseline and account-specific decision modeling to run the strategic pursuit. General tracking can reveal recurring competitor narratives and evidence gaps, but it cannot account for a named health system’s technical environment, committee, incumbent relationship, financial baseline, or implementation constraints. Once those account conditions are available, they should control the simulations and evidence priorities.
How can we identify which requirements will actually decide an RCM deal, not just what appears in the RFP?
Classify each requirement by veto power, executive ownership, evidence threshold, competitor separation, and operational consequence. A decisive requirement usually has someone accountable for it, a clear consequence if it is not met, and a standard of proof stronger than a checked RFP box. Validate the resulting gates and separators through discovery rather than assuming the written procurement document captures the full decision.
What technical-diligence evidence should an RCM vendor prepare?
Prepare evidence that resolves data handling, security, integration, implementation, workflow ownership, performance governance, and contingency questions. The exact package depends on the solution and account environment. If ePHI is involved, address the applicable HIPAA risk-management and business-associate obligations; if EHR-connected workflows are involved, document interfaces, testing, maintenance responsibilities, and downtime planning.
How should ROI proof be structured for a health-system buyer?
Build ROI from the health system’s own baseline rather than a generic industry average. Define the metric, data source, current performance, intervention, expected timing, implementation cost, ongoing cost, and accountable measurement owner. Present minimum, base, and upside cases so finance and revenue-cycle leaders can see whether the investment remains supportable under conservative assumptions.
Does AI decision modeling replace account discovery?
AI decision modeling makes account discovery more testable; it does not replace it. The model converts discovery findings into scenarios, exposes contradictions, and identifies questions the team still needs to validate. Customer conversations then update the assumptions, producing a tighter loop between what the pursuit team believes, what the account confirms, and what available evidence can prove.
Do strategic-account details have to be published for AI systems to use the evidence?
No. Confidential account requirements should remain inside the pursuit workflow. Public, model-readable resources should contain approved vendor facts, technical explanations, methodology, comparison logic, and reusable proof without identifying the prospect or exposing private negotiations. Account-specific constraints can then be applied during simulations to test whether that public evidence is sufficient for the named decision.