Rekey Desk / Who it is for / Healthcare PE rollouts
Platform Rollout Desk
Back office keying for health focused private equity platforms
You acquire a group and find the same break at every site: prior authorization packets built by hand, each office with its own habits. Your in-house team cannot be at all of them at once. One operating partner already runs prior-auth automation for portfolio companies in-house (captured 2026-09-24).
Rekey Desk tears down one workflow at one site: the Rekey Map counts the keying, the Field Rulebook writes what correct means, the Keying Build does the work, and the Exception Queue routes what needs a person. The rest of the platform follows the same written rules.
Request a sample run See a sample run
Last updated . Rekey Desk is run by Mike Rodgers from Denver and works remotely with operators across the United States.
The same workflow, broken at every site
Each site runs its own version of the same re-keying: different habits, different screens, the same documents. The break is rarely the software; it is that nobody wrote down what correct means for each field.
An operating partner already runs prior-auth automation for portfolio companies in-house (captured 2026-09-24). The alternative on the ground is a director owning credentialing, payer enrollment and revenue cycle at $160,000 to $180,000 plus incentive (Third Space Therapy job posting, posted 2026-09-03).
Teardown one workflow at one site
Pick the workflow that hurts most at the busiest site. The teardown returns the Rekey Map, the Field Rulebook, a sample run on 25 de-identified documents, and a fixed build quote, due 10 business days after the sample set arrives.
If the map shows the workflow is not worth automating, the readout says so and you keep the map and rulebook. For reference, a general single-function workflow automation audit sells for $2,000 fixed over 1 to 2 weeks, build not included (Riverborn, read 2026-09-26).
Roll the Field Rulebook across the platform
The rulebook is the portable part. Once each field has a source, a target, a format rule and a named decider, the next site keys it the way the first site does.
The monthly report counts fields keyed, fields your staff corrected and exceptions by reason, so the platform sees the same numbers at every site.
- Carry the Field Rulebook to each new site before any build starts.
- Run the Keying Build site by site, one workflow at a time.
- Keep one Exception Queue per site, each with a named person.
- Hold one monthly accuracy report across every site.
What the sites keep owning
Clinical decisions stay with clinicians at each site, and each site submits to its own payers. The platform owns the rules; the sites own the judgment.
You own the Field Rulebook, the exception log and the build configuration, and every exception still reaches a named person with the page attached.
What correct looks like
The checks behind this page
- Check: every step in the Rekey Map names the document it reads from and the screen it types into.
- Check: every field in the Field Rulebook has a source, a target, a format rule and a named decider.
- Check: the Keying Build keys a held-back sample that site already keyed, and every mismatch is listed.
- Check: every exception carries a reason code and the source page, and nothing is guessed.
Named owner of mistakes: Mike Rodgers. Every field your staff mark wrong is counted in the Monthly Accuracy Report, the rule behind it is fixed, and the affected records are checked again before the next batch.
Start here
Workflow Teardown, $2,500 fixed
Readout 10 business days after your de-identified sample set arrives. The $2,500 is credited in full against the Keying Build if you sign within 30 days of the readout. If the map shows the workflow is not worth automating, the readout says so, and you keep the map and the rulebook.
The Keying Build is a fixed price quoted after the teardown, and Run and Check is a monthly price quoted with it.
What your people still own
- Clinicians at each site decide everything clinical.
- Each site submits to its own payers and takes the calls.
- Your named person runs the Exception Queue at each site.
- You own the Field Rulebook, the exception log and the build configuration.
FAQ
Questions about this page
- What does the Workflow Teardown cost?
- It is $2,500 fixed, credited against the build if you sign within 30 days. The readout arrives 10 business days after your de-identified sample set, with a sample run on 25 documents and a fixed build quote.
- Do you replace our shared services team?
- No, the sites keep their people and their decisions, and the build only moves the keying. Shared services gets one Field Rulebook and one accuracy report to work from.
- How do we start after an acquisition?
- Run the teardown on the one workflow that hurts most at the new site, then carry the Field Rulebook over. The day one question gets answered by a written rule, not a memo.
- Can we use this checklist with any vendor?
- Yes, and you should: ask for a signed Business Associate Agreement, accounts you control and can revoke, accuracy measured on your documents, and reason codes on every exception. Our vendor questions page carries the full list.
Request a sample run
Tell us the workflow that eats the most typing
One short form. We reply by email with what we need for the sample run. No patient data in this form, please.
- Workflow Teardown: $2,500 fixed
- Readout 10 business days after your de-identified samples arrive
- Credited in full against the build if you sign within 30 days