Scope comes first
We discuss the problem, your approved tools and the workflow worth building. Features, delivery timing, support and price belong in the written agreement.
Operating systems
A workspace built around a seller’s accounts, methodology and voice, with repeatable support for research, meeting preparation and follow-up.
Inquiry-only. Scope, availability and price are agreed individually. A paid session is the fastest way to scope one.
Illustrative example
This interactive example uses fictional deal and account data. It shows possible workflows, not a live client record, a promised result or an included feature list for every engagement.
1 · Company snapshot
Regional health system: 11 hospitals, 60+ outpatient sites, $2.1B revenue, 14,000 employees, HQ Columbus. Two years post-merger and still running as two companies under one logo.
2 · Market signals & strategic triggers
3 · Relationship & engagement history
| Name | Title | Strength | Notes |
|---|---|---|---|
| Tom Okafor | VP, Revenue Cycle | Warm | Met at HIMSS 2024. Asked for the ROI model, never got it. |
| Dana Reeves | Dir., IT Ops | Dormant | Your 2024 pilot contact. Left the company in March. |
4 · Business model & revenue strategy
Payer mix shifting to value-based contracts; ambulatory expansion is the growth engine. Margin pressure is the board conversation.
5 · Strategic initiatives
Systems consolidation (annual report), revenue-cycle modernization (four open job postings), ambulatory build-out (earnings call).
6 · Technology landscape
| Layer | Stack | Friction |
|---|---|---|
| ERP | Three instances post-merger | The consolidation target |
| EHR | Single vendor, stable | Not the play |
| Rev cycle | Legacy + manual workqueues | 4 open reqs say it's breaking |
7 · White space & use cases
8 · Industry landscape
Peer systems are 12-18 months ahead on consolidation. The cost of inaction is a board slide her competitors already show.
9 · Why we might be a fit: the POV
Lead with: "You told the street efficiency. Consolidation is how that becomes a number." Illustrative peer story: a two-state system that cut $3.1M in year one. This number is fictional demo data, not a HUMN Minds result.
10 · Quick reference
10-K · investor deck · earnings transcript · your 2024 pilot notes, all linked.
11 · Account team
You (owner) · SE support at demo stage · partner intro available via the northeast alliance.
| Who | Role in decision | Messaging angle |
|---|---|---|
| CFO (new) | Economic buyer | The efficiency mandate she announced. Board-visible win in year one. |
| Tom Okafor, VP Rev Cycle | Likely champion | He asked you for the ROI model in 2024. Open by delivering it. |
| CIO | Gatekeeper | Risk framing: consolidation without a rip-and-replace. |
Engagement plan: Phase 1 exec touch via Okafor → Phase 2 IT validation → Phase 3 functional rollout sponsors.
Eleven times
You said "efficiency" eleven times on Friday's call. That usually means the board asked for a number, and the systems side hasn't produced one yet.
Illustrative proof example: a two-state health system cut $3.1M in year one without a rip-and-replace, and its CFO presented the result to the board in month four. This is fictional demo data.
I wrote up how the math would look on your footprint. Worth a look?
Best, Alex
Meeting context
She replied to the "eleven times" email in 4 hours, copied her chief of staff, and asked for "the math you mentioned." Expectation set: numbers, not a pitch.
Stakeholder profile
Second CFO seat, promoted from a system twice this size. Public style: direct, numbers-first, allergic to vendor theater. She will interrupt the deck. Let her.
Meeting intent
Primary: earn the working session with her chief of staff and Okafor in the room. Discovery focus: which of the three ERPs is politically hardest to retire.
Suggested openers
Objective
Leave with the working session booked and the denials data request in writing.
Customer priorities
Board-visible efficiency number by Q2 · consolidation without operational risk · keep the nurses out of it.
Pain points identified
Our positioning
Phase 1 = revenue-cycle consolidation, the smallest politically-safe wedge with the biggest number attached. The phrase that landed: "your first board win."
Key milestones
| Milestone | Date | Owner |
|---|---|---|
| Working session (CoS + Okafor) | Next Thursday | You |
| Denials data delivered | Friday | Her chief of staff |
| Phase 1 proposal | In 3 weeks | You |
Risks & considerations
CIO not yet in the loop (mitigation: Okafor intro before the working session) · budget cycle closes in 9 weeks.
Next steps
Three follow-ups, all drafted and waiting.
The number, and Thursday
Marissa, appreciated the directness today. Here is the math I promised, built on the denials volumes your chief of staff is pulling.
Thursday we pressure-test it with your people in the room. If the number doesn't hold, I'll tell you before you have to.
Best, Alex
Team, quick all-up on Meridian Health. New CFO with a public efficiency mandate. Rev-cycle consolidation is the wedge, and she engaged in 4 hours. Data starts flowing Friday.
What I need from you: an SE for Thursday's working session, and the two-state case study numbers verified by Wednesday. My read is this one moves fast.
What this is: Phase 1 revenue-cycle consolidation across the three legacy systems. Why now: the efficiency mandate has a Q2 board date. What you get: the denials backlog cut, one workqueue, a board-ready number in month four. Investment & ROI: one recovered denials month pays for the phase.
Two things. You're selling ROI to the CFO, but the CIO is graded on risk, and he still hasn't heard your name: get the Okafor intro done before the working session, not after. And watch yourself in the room. In 2024, and at your last two CFO meetings, you over-explained the moment someone pushed on the number. Give her the number, then hold the silence.
One deal, one conversation. Your strategic thinking partner and your execution engine, in the same thread.
Before a build
We discuss the problem, your approved tools and the workflow worth building. Features, delivery timing, support and price belong in the written agreement.
You own your data and the delivered workspace copy as set out in your agreement. Third-party tools and any licenses are identified before work begins.
Only share material you are allowed to use. We agree on data access and handling, and keep each client’s work separate. Read our privacy and security information.
Start a conversation
An inquiry establishes the next conversation. It does not reserve a build or require payment. If your question needs a focused working session first, the paid hour with Nick Labo and Daniel Borodyansky is a separate service.
Already a customer? Get support for your existing order. Your accepted terms and access remain in place.