Native Alpha™
Most good ideas in health and adjacent systems die unproven and unowned
Native Alpha™ is the method that stops that. Find what people are working around, test it against real data before spending money, give one person the decision and a date, then reuse everything the decision produces.
This matters to anyone considering our patents, capital, or companies, because it is the reason the register is short and the claims hold up. Nothing gets filed, funded, or built until it has already been attacked with real provider, device, trials, insurance, or marketplace data.
The alpha is native because it comes from the work itself. Nobody here invents hospital discharge software from a whiteboard. The ideas come from having been in the building: in a health system's IT shop, a device maker's regulatory review, a research organization's trial operations, an insurer's records and evidence workflow, and noticing what nobody had fixed.
Find is also where our position on AI does its work. The easy question is whether a tool makes today's job faster or lets a department run with fewer people. We aim Find at the harder one: which entirely new forms of work become possible? An existing job done in less time is a feature, and we price it like one. A function nobody could staff before, such as reading every denial a plan issues, or keeping a device submission's evidence current while the product runs, is worth proving, filing, and building around.
The stages run in order because each one is expensive to skip. Without Prove we would be buying opinions. Without Decide we would be filling a library nobody opens. Without Compound we would start over every January.
Stage 1
Find
What is somebody working around every day?
Good inventions rarely announce themselves. They show up as a workaround: the nurse who keeps a paper list because the discharge screen is too slow, the records clerk with a spreadsheet that catches the access requests the system misses, the trial coordinator who keeps a paper binder because the study system will not show the current protocol version. We log the workaround, who does it, and how often, before anybody argues about what it means.
- Write down the workaround before writing down the theory.
- Attach the actual artifact: the spreadsheet, the log file, the denial letter.
- Say who does the workaround and how many hours a week it costs them.
Stage 2
Prove
What would show this does not work?
Before money moves, we write down what would kill the idea. A prior-authorization idea gets tested against a payer's real denial history. A device idea gets shown to the regulatory people who would have to file it, early, when the answer is still cheap. A state modernization idea gets checked against what procurement can actually buy. Ideas that fail get written up too, because knowing in six weeks beats knowing in two years.
- Name the kill condition in writing before spending.
- Test against production data or a live operating environment.
- Ask the person who has to sign the FDA submission or the state contract, up front.
Stage 3
Decide
Who acts on it, and by when?
An idea that survives goes to one person who can do something about it: file the application, publish the disclosure, size a position, charter a company, or stop. That person writes the date and the reason. Without a named owner and a date, a good finding goes into a deck, circulates for a quarter, and quietly dies of committee. We have watched it happen elsewhere and we do not allow it here.
- One named owner carries the decision.
- A date on every decision, including the decision to wait.
- The reason written down while the evidence is still fresh.
Stage 4
Compound
What does the next one inherit?
Claim language drafted for a hospital interoperability filing gets reused for the trials version. A test harness built for device telemetry gets pointed at metric queues. The people who have lived through a large system replacement know exactly which month an integration will slip and why. All of that accumulates, which is why the fourth filing in a family costs a fraction of the first.
- Every artifact goes back into the shared record.
- Reuse claim language, test harnesses, and diligence checklists across markets.
- Track how long a cycle takes, and what it produced.
What we turn down
We pass on work we cannot defend to a skeptical customer: savings estimates that assume a hospital changes its staffing model, device software that nobody has run past a regulatory reviewer, insurance analytics that only work on a cleaned extract, and proposals that require a procurement path the buyer does not have. We also pass on secrecy for its own sake. Trade secrets stay closed where secrecy is genuinely the asset; everything else gets published.
A method only counts when it changes what actually gets filed, funded, published, or built. If a stage never once stopped us from spending money, it was decoration.