SheetP-03
FieldPILOT
StatusCURRENT
Version03
One engagement to start with.
Everything after the pilot is scoped from what the pilot finds, which is the only honest way to price work nobody has measured yet.
Four weeks, fixed scope and fixed fee. What follows is the schedule, what it asks of your team, and the three points where you decide whether to continue.
P-03 · S00What the pilot needs from you
Before you read the schedule
~6 hoursLeadership time across the four weeks.
2–4 peopleWilling to have their work watched and to run it afterwards.
Existing systemsAccess to where the work already lives.
No new toolingNo platform purchase is required to run the pilot.
$45,000–$85,000Set by the number of departments in scope and the state of the underlying information. Fixed before we start.
Commission document
FOUR-WEEK PILOT
ObjectiveFind where AI actually helps, and prove it before you spend on it.
Engagement typePILOT
Week 01
OBSERVE
- Leadership and department interviews
- Baseline of how AI is used today
- Workflow observation and information mapping
Week 02
STRUCTURE
- Acceptable use and classifications
- Knowledge and workspace architecture
- First workflows built
Week 03
DEPLOY
- Workflows put into live use
- Training by role, plus office hours
- Refinement against real work
Week 04
MEASURE
- Before and after on the tasks we touched
- Executive readout
- 90-day roadmap
What you keep
- Governance and classification framework
- Knowledge architecture
- Tested workflows and their instructions
- Measured before and after
- 90-day roadmap
InvestmentFixed scope and fixed fee, set before week one and unchanged after scope lock.
If it is the wrong moveI will say so on the call. That is a reasonable outcome.
Nate Heilman
P-03 · S02Three decision points
All three are yours
End of week one — scope lock
You choose which two or three workflows the engagement builds. Everything after this is fixed
against that list, so nothing expands quietly.
End of week two — governance sign-off
You approve where the line sits on what AI may reach, and who owns each part of it. Nothing is
deployed against information you have not cleared.
End of week four — readout
You decide what scales, what is retired, and whether there is a second engagement. If the measured
difference does not hold up, the recommendation is to stop.
P-03 · S03After the pilot
Scoped from what the four weeks find
Direction 01
Implementation
The same structure extended into departments the pilot did not reach.
Direction 02
Advisory
Retained support so governance and workflows keep pace with the platforms. Fixed terms, renewed against a quarterly review.
Direction 03
Integration
Direct connections to systems of record, once a workflow has earned it manually.
P-03 · S04Not a fit
Said early, on purpose
Under roughly $25M in revenue. The institutional knowledge is not deep enough yet to be worth structuring.
No one internally who can own a workflow after I leave. Without an owner it decays inside a quarter.
Looking for someone to run AI permanently. This builds capability and hands it over.
Wanting a tool selected first. If the platform decision is already made, the useful work is mostly done or mostly wrong.
P-03 · S05Working together
Contracting and data
EntityHeilman Operations LLC, Massachusetts. W-9 and COI on request.
InsuranceProfessional liability and cyber liability carried. Certificates before kickoff.
PaperMy MSA or yours. NDA signed before discovery begins, not after.
Your dataData Sovereignty Contract. All data extractions operate strictly within your existing corporate network tenancy. Zero external data sharing occurs. No data is exported to external servers, and zero corporate records are utilized for public model or foundational training loops.
The pilot is the front door.
Thirty minutes is usually enough to tell whether it fits.
Contact
nate@heilmanops.com
Hopkinton, Massachusetts