Hammer Labs HL-PIL-001 1 SHEET
REV AUG 31, 2026
PILOT

A six-week pilot, with the scope written down.

A private world is six weeks, hand-authored with you, fixed scope, $20k. It ends with a corpus your agents can call, the refusals written down, and the vintages preserved. Paid tiers on the plan start the same way: tell us the job.

SCOPE
One code family, up to three payers, one market, two dated vintages.
DURATION
Six weeks, hand-authored with you, fixed scope.
PRICE
$20k, credited against year one on production conversion.
YOUR DATA
None required. No PHI.
AFTER
We operate the queries and keep the vintages preserved.
01

The eight questions, answered here

Every one of these has been asked on a call that could have been an email. They are answered on the page so a buyer can decide before spending an hour, and so procurement has something to read that is not a deck.

Which corpus does it run against?
Ours, yours, or both, named before kickoff. The public corpus is preserved payer and CMS material with dated vintages. A private world is the case where the answer has to rest on something we do not hold yet.
How many codes and payers?
One code family, up to three payers, one market, two dated vintages. Wider than that is a production scope, not a pilot, and pricing it as one helps nobody.
Does our data enter it?
None required. No PHI. Public record, plus your own published assumptions if you choose to share them. If a pilot does need your data, it is named in the scope and covered in writing before anything moves.
What do we get?
Preserved source artifacts with their vintages; the policy and rate deltas across the two vintages; three repeatable queries wired to your workflow; the in-scope refusal classes published; and a reproducibility package a reviewer can re-run.
What do you operate afterwards?
After week six we operate the queries and keep preserving the vintages. The thing you bought does not stop working when the engagement ends.
What proves it worked?
Success criteria are agreed in writing before kickoff, in your terms, not ours. A pilot with no written criterion is a demonstration, and we would rather not run one.
What becomes the annual contract?
Production deployment is priced separately, and the pilot fee is credited against year one. So the pilot is not a sunk cost if it converts.
Who owns the artifacts?
You own your outputs. We retain the right to publish an anonymised case study; a named case study is at your option and is written into the agreement rather than asked for afterwards.

Evaluating somebody else's savings claim is a different scope with a different deliverable, and it has its own page. The rate and coverage job is described on reimbursement evidence.

02

Tell us the job

Four questions. They are the ones that decide whether we can help, and answering them badly is better than answering none: we would rather read a rough note than schedule a call to find out you need adjudicated claims, which no world here holds.

The recurring job, not the technology. "Establish the payer-published rate and coverage policy for a code, a market and an effective date, every week."

What the answer has to rest on. Ours, yours, or both. If it is yours, say roughly what it is and who publishes it.

How long after the work is done does somebody adversarial read it. A month, a year, seven years.

Hosted, your VPC, air-gapped, a procurement rule, a data residency line. Say the one that would end the conversation.

Where the reply goes. We answer from a person, not a sequence.

Or write to hello@hammer.ai.

What we keep and how to have it deleted is on the privacy page. Nothing here is shared with anybody outside Hammer Labs.

← Hammer Labs Reimbursement evidence → Docs →