AI-Assisted Delivery Pilot
Own a governed AI delivery path, proven on one real issue.
Within five business days after readiness, your team owns a repository-native path from a qualified issue to a verified draft pull request, with existing CI and human approval intact.
$1,500 fixed founding price · 5 business days after readiness · async-first
One team. One repository. One real backlog item.
The fit call is optional. Intake collects no payment.
Outcome
A customer-owned path—not a demonstration.
Within five business days after the readiness gate passes, your team owns a repository-native AI delivery path proven on one approved issue. A customer engineer can run the documented path without Collin and explain which decisions remain human-controlled.
The operating path
Installed assets
These are the core delivery—not add-on bonuses. The customer owns the adapted files after handoff.
- Structured issue intake and readiness checklist
- Repository-specific AGENTS.md
- Protected-path and human-only policy
- One configured coding-agent adapter
- Existing CI and verification hook
- Version-controlled model configuration
- Normalized model-usage evidence
- Five smoke cases and a customer-owned handoff guide
Readiness gate
The five-day clock starts only when the environment is ready.
- Written scope names one approved low-risk issue, its non-goals, protected areas, and acceptance checks.
- Least-privilege repository and issue access is available; production credentials are not required or accepted.
- The agreed existing verification baseline passes before installation begins.
- One issue system and coding-agent adapter are selected, authenticated, and permitted on the customer network.
- The existing CI, draft-PR path, and branch protection are available.
- A named technical owner and reviewer can answer questions and review the pilot change by business day four.
- The $500 first installment is paid and the start date is confirmed.
Customer-caused access or review delays pause the clock. A changed issue or expanded scope requires a new written scope.
Five business days
Map, install, prove, and hand off.
- Day 1Map the repository and confirm the seven customer-specific decisions.
- Day 2Install the repository contract, issue intake, protected paths, and verification hook.
- Day 3Configure the agent, model, and usage evidence; pass the five smoke cases.
- Day 4Run the approved issue to a verified draft pull request for customer review.
- Day 5Correct in-scope findings, run the working handoff, and evaluate acceptance.
Acceptance criteria
Acceptance is observable and agreed before payment.
- The customer repository contains the agreed issue intake, repository instructions, protected-path policy, coding-agent adapter, model configuration, verification hook, usage evidence, and handoff guide.
- The existing verification path and five smoke cases pass, and protected paths fail closed before changed code executes.
- One approved backlog item reaches a verified draft pull request with schema-valid usage evidence.
- Human approval remains required before merge and normal deployment; the agent cannot access production credentials or approve its own work.
- A customer engineer runs the documented non-production path without Collin driving and can explain which decisions remain human-controlled.
Payment and risk reversal
$500 to start. $1,000 only after acceptance.
Payment
$500 after written scope acceptance · $1,000 after acceptance. The written scope fixes the issue, boundaries, readiness gate, and acceptance criteria before the first installment.
If acceptance misses day five
If the ready environment does not meet the written acceptance criteria by the end of business day five, the $1,000 final installment is not due. I continue correcting the agreed in-scope installation at no additional charge until those criteria pass. Customer access or review delays pause the clock; scope changes and pre-existing failures are re-scoped.
The $1,500 fixed founding price is available to the first three clients whose written scope is accepted and $500 first installment is paid. Accepted pilots keep the agreed price; pricing is reviewed after that cohort.
Public proof preview
The installable package stays private. This preview explains the control model without distributing runnable client assets.
Private package tree
AGENTS.md .ai-sdlc/ protected-paths.txt models.yml verify.local.sh adapters/codex/
Synthetic issue
Example only: add validation to a sample invoice parser while leaving authentication, payments, and production infrastructure untouched.
Redacted usage summary
Model: configured adapter · tokens: unavailable · cost: unavailable · verification: passed.
| Agent may | Human retains |
|---|---|
| Draft changes on an agent-owned branch | Scope, protected paths, approval, and merge |
| Run existing checks after path review | Credentials, production, payments, destructive migrations |
AGENTS.md excerpt: “Do not touch protected paths. Run repository verification. Stop for human review before merge.”Best fit—and not fit
Best fit
Small engineering teams already using AI coding tools, with one low-risk backlog item, a working repository and CI baseline, and a named technical owner and reviewer.
Not fit
Greenfield platform builds, autonomous production access, replacement CI, multi-agent platforms, an issue that requires protected production-sensitive paths, or financial-services work.
Qualified proof
Outcomes from full-time engineering roles, not consulting clients.
- Ford work associated with approximately $5M in annual savings across systems supporting 450K+ vehicles.
- Platforms handling 600K+ events/day and integrations serving 23+ enterprise recordkeepers.
- Approximately 90% less processing volume/time plus a 35% throughput/latency improvement.
- Led a broader AI-adoption and delivery-hardening initiative associated with 42% fewer defects and approximately 20% shorter cycle time.
Working model and confidentiality
One required 60-minute working handoff; the free 30-minute fit call is optional. There is no standing kickoff or status meeting. Work is async-first inside the customer’s repository and existing checks.
Customer code, credentials, and installable assets remain private. Production credentials are not accepted. Calls are recorded for notes by default; clients can opt out before the session.
Next steps
Three decisions move the pilot from scope review to an accepted delivery path.