/FIXED-PRICE PILOT BUILD
ONE SCOPE.
FOUR MILESTONES.
A pilot build is not an hourly bucket. It is a written agreement on the smallest useful product, the payment checkpoints, the acceptance criteria, and the handoff package.
/PAYMENT STRUCTURE
/01
25%
SIGNING
Kickoff, access, technical setup, final scope lock, and project plan.
/02
25%
WORKFLOW
Primary user flow works end-to-end on staging with real test data.
/03
25%
OUTPUT
Reports, exports, admin QA, and acceptance-critical outputs are approved.
/04
25%
PILOT
Hardening, handoff, docs, deployment notes, and pilot acceptance.
/SCOPE LOCKS
- One primary user workflow
- One admin workflow
- One reporting/export package
- Two rounds of report/template revision
- Known integrations only
- Acceptance criteria written before kickoff
/OWNERSHIP
- GitHub repository under your organization
- Cloud and vendor accounts under your billing
- Environment variables and deployment config documented
- Data and exports under your retention policy
- No code hostage situation at handoff
- Studio retains only generic pre-existing know-how
NEED A WRITTEN PILOT SCOPE?
Bring the workflow, the pilot audience, the must-have output, and the target date. We will tell you what belongs in the pilot and what should wait.