Selected work & evidence
Relevant experience, with the evidence boundary stated.
TKO's public record combines healthcare operating experience, an inspectable live operating environment, and supporting method evidence. These are not interchangeable claims. Each case states what Todd did, what can be supported, what cannot be claimed, and why it matters to a prior-authorization buyer.
Healthcare experience
Prior authorization, utilization management, interoperability, and enterprise transformation establish domain and operating context. They are not presented as quantified TKO client outcomes.
Live operating proof
RachelOS shows that Todd can design, build, govern, and audit a working operating environment. It is not a healthcare product or proof of prior-authorization performance.
Method portability
Supporting work shows that the method for making expert knowledge, exceptions, and decisions explicit can travel. Domain logic and outcome claims do not transfer automatically.
Evidence record
Start with the case closest to the operating question.
Healthcare cases establish relevant operating experience. RachelOS establishes direct implementation capability. Method-portability evidence answers a narrower objection about whether the underlying approach can travel.
RachelOS: A Live Operating Environment
Follow-up, prioritization, and context reconstruction depended on the operator being available.
Evidence boundary: RachelOS is one founder-operated, non-healthcare environment. It does not establish enterprise scale, healthcare compliance, prior-authorization performance, or causal financial outcomes.
Review the evidencePrior Authorization Workflow Design Experience
Administrative work and exceptions were being discussed as an automation problem before the review tiers and escalation paths were explicit.
Evidence boundary: The experience is anonymized and employment-based. Client identity, workflow artifacts, baselines, and post-implementation measures are not publishable.
Review the evidenceEnterprise Program Recovery
Local workstream status did not explain where enterprise delivery risk was accumulating.
Evidence boundary: This is employment-period enterprise experience, not a named TKO client case. Public artifacts and quantified outcomes are unavailable.
Review the evidenceHealthcare Interoperability Modernization
Regulatory and interoperability requirements had to become working platform behavior rather than remain policy or documentation.
Evidence boundary: Employer and client endorsement is not implied. Confidential program artifacts and outcome measures are not published.
Review the evidenceCRE Intelligence Model
Knowledge left with the analyst and could not be reused consistently across subsequent questions or decisions.
Evidence boundary: This is supporting method evidence. It should not be read as equivalent to verified client outcomes or healthcare implementation proof.
Review the evidenceDoes the method apply here?
The method transfers only at the operating-mechanism level.
Prior authorization and the supporting proof environments share a structural problem: work crosses systems and roles, exceptions depend on experienced staff, and leadership needs reliable evidence before changing the workflow. TKO does not claim that real-estate software, financial-services logic, or one enterprise program proves a healthcare result. The transferable capability is the disciplined work of tracing the workflow, clarifying evidence and authority, designing controls, and measuring the change.
Diagnostic fit call
Use the evidence to decide whether the Diagnostic fits.
If prior-authorization performance is under pressure and leadership needs a defensible operating baseline before another investment, start with the 15-business-day Diagnostic.