Hunt · searching for Capital

Founder for home health revenue cycle

Home health revenue cycle is a documentation problem wearing a billing costume. The founder we want has already been personally responsible for a denial rate and has built something to fix it, even if the something was a spreadsheet.

Native Alpha™ sought. Somebody who reads denials as a data source rather than as a queue to be worked down.

Who fits and who doesn't

What would qualify them

Owned a denial rate or a days in accounts receivable number
Built or specified a tool that changed it
Can explain a payer's behavior without moralizing about it

What would rule them out

Only sold into revenue cycle, never operated it
Treats the answer as more staff

Signals we watch

Reasons to look closer, none of them proof

Detailed public writing about specific denial reason codes
Open source or public templates for appeals
Speaking at home health operations meetings rather than general health IT ones

How far this search has run

These figures are illustrative, like the candidate packet below. They show the shape of a hunt at this stage rather than counts from a search we are running today.

Surfaced: 21
Reviewed: 9
In conversation: 3
Experiments: 1

What a candidate looks like

This is the written answer you would get for each candidate: why they surfaced, what backs it, what we don't know, and what to do next. The person below is a composite, not a real individual.

Evidence packet · illustrative

Illustrative candidate: an agency revenue cycle director

Director of revenue cycle, multi state home health agency

Surfaced for: Founder for home health revenue cycle
Why surfaced: Published a public breakdown of the six denial reasons that accounted for most of their volume, with the documentation change that closed each one.
Current signals: Long form post with reason code level detail
Answers operational questions in a practitioner forum, consistently and without selling
Built an internal appeals template later adopted by two other agencies
Possible Native Alpha™: Turns payer behavior into a documentation specification, which is exactly the product thesis we want to fund.
Why it might matter: The fund needs a founder who already knows which denials are worth automating and which are noise. That knowledge is not purchasable.
Evidence: Published the denial breakdown with reason codesSource: Public post
Template adopted by peer agenciesSource: Practitioner forum thread
Known relationship: Warm. They commented on a Press article about authorization turnaround in 2025.
Unknowns: Whether they want to found rather than lead operations
Whether the template result survives outside their own agency
Suggested next action: Invite to a paid two week diagnostic on one agency's denial file, as an experiment before any founder conversation.
Confidence and status: High confidence · In conversation

What this search has taught us so far

The most useful signal was specificity. Anyone who wrote about reason codes by number was worth reading. Everyone who wrote about revenue cycle in general was not.