Date: 2026-07-31
Role: Marketing / Content
Backlog task: US-GTM-01-05
Status: Content/MKT readiness complete; real pilot completion remains blocked until signed scope, payment and delivery evidence exist.
Purpose
This pack turns the AI Coding Workspace Setup offer into a sales-and-delivery operating kit for the first 3-5 paid pilots. It does not claim pilots have been sold. It defines the evidence required before any pilot can be counted.
Pilot Qualification Gate
A lead can move to "paid pilot candidate" only when all are true:
- ICP fit: software agency, product team or dev team using AI coding tools already.
- Clear painful workflow: review burden, inconsistent AI output, context drift, sandbox gap or slow delivery.
- One repo/task family can be used safely.
- Buyer can name an owner and reviewer.
- Data boundary is explicit: no production secrets, credentials or sensitive client data in AI tools.
- Timeline is 7-14 days.
- Budget expectation fits the pilot range.
Paid Pilot Count Gate
Do not count a pilot as won unless there is:
- signed or written scope approval;
- payment status recorded;
- pilot start date;
- one named client owner;
- baseline metrics agreed before delivery;
- delivery artifacts saved;
- win/loss and testimonial consent tracked separately.
Proposal Template
Title
AI Coding Workspace Setup – 7-14 Day Paid Pilot
Context
Your team is already using AI coding tools, but usage is inconsistent across developers. The pilot standardizes one workflow for one repo/task family so the team can decide whether to scale, adjust or stop AI-assisted development practices.
Scope
- One team or squad.
- One repository.
- One repeated task family.
- One approved set of AI coding tools.
- One sandbox/test path.
- One review checklist.
Deliverables
- Repo context pack.
- AI tool routing map.
- Prompt/context rules.
- Sandbox/test workflow.
- Review checklist for AI-generated changes.
- Pilot demo task.
- Measurement memo with scale/adjust/stop recommendation.
Timeline
- Day 1: workflow audit and repo boundary.
- Day 2: context pack and tool routing.
- Day 3: sandbox/test path.
- Day 4: pilot task run.
- Day 5: review checklist and handoff.
- Day 6-10: optional second task and tuning.
- Day 11-14: measurement memo and next-step decision.
Pricing Anchor
- Setup Sprint: USD 1,500-3,000.
- Team Pilot: USD 3,000-7,500.
- Retainer option: USD 1,500-5,000/month after pilot, only if baseline supports continuation.
Success Metrics
- Cycle time for selected task family.
- Review effort.
- Rework rate.
- Bug leakage or failed checks.
- Prompt/context reuse.
- Developer adoption feedback.
Exclusions
- No enterprise-wide rollout.
- No unlimited repo migration.
- No security/procurement implementation.
- No guarantee of productivity lift before baseline.
- No use of production secrets or restricted customer data.
Delivery Checklist
Before Kickoff
- Confirm buyer, owner and reviewer.
- Confirm repo/task boundary.
- Confirm data boundary.
- Confirm current AI tools in use.
- Capture baseline workflow and timing.
- Confirm payment/scope status.
During Pilot
- Build context pack.
- Configure tool routing.
- Run one bounded task.
- Test in sandbox.
- Apply review checklist.
- Record failure modes.
- Capture before/after observations.
After Pilot
- Deliver measurement memo.
- Recommend scale, adjust or stop.
- Record delivery effort.
- Estimate gross margin.
- Ask for testimonial/case-study consent separately.
- Log win/loss reason.
Evidence Table
| Evidence | Required before status | Storage note |
|---|---|---|
| Scope approved | Paid pilot won | Store proposal/scope doc reference only. |
| Payment status | Paid pilot won | Record paid/pending/failed, not payment details. |
| Baseline metrics | Pilot start | Record task family, cycle time, review effort and rework baseline. |
| Delivery artifacts | Pilot delivered | Store memo/checklist/context-pack references. |
| Client feedback | Pilot delivered | Keep consent separate from internal notes. |
| Testimonial consent | Case-study eligible | Explicit opt-in only. |
Outreach-to-Pilot Funnel
1. Target account selected.
2. Touch 1 sent.
3. Touch 2 sent.
4. Touch 3 sent.
5. Reply.
6. Discovery call.
7. Qualified opportunity.
8. Proposal sent.
9. Scope/payment accepted.
10. Pilot delivered.
11. Win/loss learned.
Follow-Up Copy After Discovery
Subject: Proposed AI coding workflow pilot for {{company}}
Thanks for the call. Based on what you shared, the safest pilot is one repo, one repeated task family and one reviewer-owned workflow.
The pilot would produce:
- repo context pack;
- AI tool routing and prompt/context rules;
- sandbox/test workflow;
- review checklist;
- one demo task;
- measurement memo with scale/adjust/stop recommendation.
I would not count this as a success unless the baseline shows lower review friction, better repeatability or a clear reason to stop.
Decision Rules
- Proceed if the buyer has urgency, reviewer availability and one safe repo/task.
- Nurture if interest exists but no owner or timing.
- Disqualify if the team wants vague "AI transformation", requires enterprise procurement first or cannot define data boundaries.
- Do not discount below delivery cost; reduce scope instead.