The pilot is CodexDominion's only paid offer and the page every growth campaign will send people to. It still says "3 slots — Q3 2026" and "3 slots available for Q3 2026", and Q3 ended on September 30. Its own success criteria promise "Anyone on your team can clone the repo", and the footer links to GitHub, but the GitHub organization has zero public repositories. A compliance or security lead, exactly the buyer the page targets, checks these details first. A stale date and an empty repository read as "nobody is home".
First action
Replace the Q3 badge today.
How to measure it
Pilot applications
- Now
- –
- Target
- 6 a month
- By
- 60 days
Steps
Fix the date
Rolling cohort badge on the homepage and pilot page.
Founder & CEO 1 hour
Decide on GitHub
Publish a small public repo or remove the link.
Founder & CEO 1 day
Publish proof
Runbook, smoke-test list and a sample export.
Contract Developer 3 days
Add booking
Calendar link for the 20-minute call.
Founder & CEO 1 hour
Add timeline
What happens after you apply, week by week.
Growth Marketer 2 hours
Track
Visits, applications and calls booked.
Growth Marketer weekly
Review monthly
Update the cohort date and slots.
Founder & CEO monthly
Why it works
Change the badge to a rolling cohort ("Next cohort starts [date]: 2 of 3 slots open") and update it monthly. Either publish a small public repository (the runbook, a sample audit export, and the smoke-test list) or remove the GitHub link until there is something to show. Add a "what happens after you apply" timeline and a calendar link for the 20-minute call so a buyer can book without waiting a day. Once a growth hire starts sending traffic, track visits to applications to booked calls from this page.
Fixing the proof on the one page that converts costs a few hours and protects every visitor the new growth work buys. Real scarcity with a current date also helps the decision-in-one-conversation buyer the page targets.
Ready to use
ChecklistPilot page proof check
[ ] Cohort date is in the future [ ] Slot count matches reality [ ] Every link (GitHub, demo, contact) leads to something real [ ] Sample audit export downloadable [ ] Calendar link for the qualification call [ ] "After the pilot" pricing stated [ ] One quote or result from a completed pilot
Risks and how to handle them
Publishing code exposes too much
Publish only the runbook, docs and a sample export, not the product source.
Evidence
- Your websitePilot page: headline badge "3 slots — Q3 2026" and "3 slots available for Q3 2026"; "$7,500 flat fee", a 4-week engagement "Billed upfront. No retainer, no recurring fees", with deployment, up to 3 workspaces, audit evidence for at least 10 tasks, a runbook and a written production gap assessment. The fit list includes teams that "Can make a decision in one conversation", and success criteria say "Anyone on your team can clone the repo and stand it up from the runbook". Applicants get "a 20-minute qualification call" within one business day. There is no price or plan for after the pilot.Source
- GitHubThe GitHub link in the site footer goes to The-Merritt-Method organization, created August 24, 2026, with 0 public repositories and 1 follower; its bio says "governed AI, compliance, financial, healthcare, and federal mission software".Source
- Your websiteHomepage (checked November 4, 2026): "Your team is using AI. Who's governing it?" Approval gates for medium- and high-risk tasks (a "keyword-based risk classifier"), four roles enforced at the API layer, and a "7-event audit chain" exported as JSON and Markdown with a SHA-256 hash; badges "Live demo available", "17-test smoke suite passing", "OpenAI + Claude + Stub providers", "3 pilot slots available". An honest "What it isn't (yet)" list: no SOC 2 or HIPAA certification, "Not production-hardened auth (bcrypt, MFA, SSO not yet built)", single-tenant pilots, 5-second polling instead of real-time updates.Source