Two days.
Your codebase is agent-ready.
Most teams have Claude or Copilot switched on and are still getting slop out of it. That is not a model problem. It is that nobody told the agent how this codebase works. I spend two days with your team and we fix that against your actual repository. You keep everything we build.
Your agents are guessing
An agent pointed at an undocumented codebase does what a new hire would do without onboarding: it invents conventions, ignores your invariants, and writes code your reviewers send back.
The fix is not a better prompt. It is the same thing that makes human onboarding work: written conventions, real tooling access, and clear limits on what can be touched.
That setup takes a specialist about two days. Most teams never get around to it, so they conclude the tools do not work.
Fixed deliverables
Everything below is built during the two days, against your repository, with your engineers doing the work.
Repo audit
Where agents will and will not work in this codebase, and exactly why.
Written conventions
A CLAUDE.md for each repo in scope, tuned to how your team actually writes code, not to a template.
A custom MCP server
Wired to one internal system your team uses every day: your ticket tracker, your staging database, your internal docs, your design system. Yours to keep and extend.
Three working agent workflows
Built live against your real backlog. Not demos.
A code-review skill
Your team's actual review standards, encoded so the agent applies them before a human sees the PR.
Guardrails
What agents may never touch, how secrets are handled, how changes get gated before merge.
A 30-day adoption plan
One page, plus a checkpoint call at day 30.
Recordings
For anyone who could not be in the room.
Format: on site or remote, up to 8 developers, 20% theory and 80% hands-on.
The two days, half-day by half-day
You may already be paying for this
Under the Loi favorisant le développement et la reconnaissance des compétences de la main-d'œuvre (the “loi du 1%”), Quebec employers with a payroll above $2M must spend at least 1% of payroll on eligible training. Whatever you do not spend, you pay to the Fonds de développement et de reconnaissance des compétences de la main-d'œuvre instead.
The rules were loosened in April 2026, and more training now qualifies than most employers realise.
If you are over the threshold, the budget for this already exists. I am happy to walk your finance contact through it.
Eligibility depends on your specific situation. Confirm with your finance team or Revenu Québec.
Four rungs, one path
Agent Readiness Review
25 minutes on a call, plus a one-page written finding: where your codebase blocks agents, what it is costing you, and the three fixes worth doing first. No obligation, and useful whether or not you book anything.
Executive session
Half a day with your CTO, VP Engineering, and team leads. What agents change about how software gets built, where the real risk sits, and what to fund next quarter.
Groundwork
Two days, up to 8 developers, all eight deliverables above, against your real code.
30-day support
Async access plus a checkpoint call while the team builds the habit.
Prices in CAD. Delivered in English or French.
What I bring to the room
I have shipped 38 projects across AI, data, healthcare, hardware, and developer tooling, and won four hackathons doing it. I have built production MCP servers, multi-agent orchestration, and agent workflows against real systems, and I know precisely where they break, because I have broken them.
Day to day I am a senior developer working on enterprise integrations. Groundwork is what I have learned about making these tools survive contact with a real codebase.
Start with the free review
Twenty-five minutes. You get a written one-pager either way.
Book the 25-minute readiness review