Rung 00 · The Req Read

Your ninety-day plan, written from your own req.

You posted a req for the person who will run your practice-management conversion. Before anyone pitches you, here is the ninety-day project plan that posting already describes — every workstream quoted back to the line of yours that implies it.

Fee noneBuilt in ~40 minutesAsked of you nothing

Free artifact · short path or full dossier · same-day when a live req URL is provided

Send the req URL →Book twenty minutes → One open req URL · the read comes back the same day

Rodgers Intelligence Group is an independent firm and is not affiliated with any practice-management, imaging or conversion vendor. Product names are used nominatively to identify the systems discussed.

Req lines resolving into a ninety-day cutover sequence — RIG dossier visual

Req lines resolving into a ninety-day cutover sequence — RIG dossier visual

01

Why this one asks for nothing

What normally arrives

A document that asks for something is a pitch with a document attached, and everybody already deletes those. The ask is the reason it does not get read.

What this is instead

One page, deliberately worth more forwarded than answered. If it is useful, the person who forwards it inside your group is the person who spotted the risk.

The window it is useful in

Between posting the role and filling it. That role takes months to fill and the migration queue does not pause while you look.

Why that matters

Whoever you hire inherits the backlog that exists on their first day, not the one that exists now. The first ninety days of it can be cleared during the search.

02

What you get

Deliverable 01

Every workstream your posting implies

Each one carries the verbatim line from your req that implies it, how that surface tends to fail during a multi-system consolidation, and the specific check that settles it before cutover.

  • Quoted from your posting, not from a template
  • Source URL, publication date and retrieval timestamp printed on the page
Deliverable 02

A dated ninety-day sequence

Ordered so that everything depending on a comparison against the outgoing system happens while that system is still the system of record — the ordering is the part that is hard to redo later.

  • Four windows, each naming what it clears
  • Sequenced against the retirement of the source system
Deliverable 03

An explicit omissions log

What was left out and why, including every figure that could not be sourced. On a page with no figures on it, that log is the honest part.

  • No estimate of your revenue, volumes or location count
  • No claim about systems nobody has seen
03

What is included, and what is not

Included
  • One page, self-contained, yours to forward
  • Every workstream the posting implies, with the req line that fired it
  • A dated ninety-day sequence
  • The omissions log
Explicitly not included
  • No access to any system, and no request for one
  • No patient data anywhere in the process
  • No ROI, savings or revenue figure — there are no figures at all
  • No claim about your size, your volumes or your location count
  • No follow-up implied and no reply expected
04

What is true, and how you can check it

ClaimHow to verify it
Built only from your own public postingThe source URL, publication date and retrieval timestamp are printed on the page.
Every quoted line is verbatimOpen the source link and search for the line.
No figures are inventedThere are no figures on the page, and that omission is stated on it.
The page requests nothingThere is no form, scheduler, price or reply address anywhere on it.
The page makes no network callsSave it and open it offline; it renders identically.
A dead or blocked source cannot be read as a live onebin/req_read.py --selftest plants twelve fetch defects — a 403 body that exits 0, a parked-domain bounce, a bot wall answering 200, an empty body — and each is caught. Verified 2026-07-31, exit 0.

Anything Rodgers Intelligence Group cannot demonstrate today is not claimed here. There are no client references, no case studies and no results figures, because there are none to cite yet. Every command named above was run and passed on 2026-07-31.

05

Before you ask

“What is the catch?”
There is not one, and that is the point of the design rather than a generosity claim. Nothing is asked, so nothing has to be approved by anyone. If the read is wrong you have lost the four minutes it takes to notice.
“This is an audit with a friendly cover.”
It is not an audit and the page says so in those words. Nobody has seen your systems, your ledgers or your data. Every failure mode described is how that workstream behaves in a multi-system consolidation generally — never a finding about you. Where the two differ, you are right and the document is wrong.
“Who have you done this for?”
Rodgers Intelligence Group has no delivered clients in this category, no case studies and no reference customers, and will not invent any. The read is the sample.
06

Who this is for

This is for

Anyone running a multi-site consolidation who has a req open for the person meant to run it.

This is not for

Groups with no conversion in flight — there is no posting to read, and a read built from a press release instead of a req is a guess with a citation attached.

The Req Read

It costs you one link and four minutes to find out if it is any good.

Send the URL of one open req. The read comes back the same day, with the source and the retrieval timestamp printed on it. There is no next step attached to it.

Send the req URL →

One open req URL · the read comes back the same day

Use the free resources now. If you would like help applying them, send Mike a brief through the contact page. Nothing is submitted from this section; calculator results stay on this page.

Browse free resources · Contact RIG