The Methodology · $99
I’ve consulted on AI projects from $5K to $2 Million.They all start here.
Old code. New code. Greenfield. Mature. It doesn’t matter. Before we write a single feature, draft a single scope, or have a single architecture conversation, we install this. It is the foundation under every AI project that actually ships.
Less than 1% of developers walk into a project with this foundation in place. After 25 years of consulting, I’ve put it in writing — every prompt, every script, every template — so your team can install it themselves.
THE METHODOLOGY
The AI Foundation Framework
PUSHBUTTON AI · 2026
Diagnosis
Your AI projects are failing for one reason. It isn’t what you think.
Six months in, the project is “almost there.” Three months after that, it’s still “almost there.” The team is shipping code, but the same kinds of bugs keep coming back. The AI agents are doing roughly what was asked — but every output drifts a little, and the drift accumulates. New developers spend their first three weeks re-explaining the project to the AI from scratch. Decisions get made, then quietly relitigated next month. Velocity feels good in week one and terrible by month four.
Most CEOs are told this is a model problem. “We’re waiting on the next generation of agents.” Or a skill problem. “We need someone better at prompting.” Or a tooling problem. “We’re switching frameworks.”
It is none of those things. It is a foundation problem.
When the foundation isn’t there, you get drift. Hallucinations. Errors that compound. Agents that confidently produce code that has to be torn out and rewritten. You get the horror stories.
When the foundation is there, you get builds and scopes that move at lightning speed, and the AI gets better at your project the longer you work on it.
Why nobody talks about this
Less than 1% of developers know about this.
I’m not exaggerating. In 25 years of consulting, I’ve worked with hundreds of developers — junior and senior, in-house and contractor, brilliant and competent. The number who walk into a project with this foundation already in place is fewer than one in a hundred.
Your team isn’t behind. The methodology I’m describing is genuinely new — formalized in academic research published this year out of the University of Edinburgh — and the practitioner adaptation that makes it work for production codebases hasn’t been written down anywhere as a complete system.
Your developers aren’t lazy. They aren’t bad. They aren’t behind the curve.
Until now.
This is why you keep hearing the horror stories. AI projects that ate $200K and shipped nothing. Agents that confidently produced code that had to be torn out and rewritten. Three-person teams that should have shipped in two months and are now eight months in with no end in sight.
Every one of those projects had the same root cause. The foundation wasn’t there. Nobody knew to put it there. Nobody knew it existed.
What this actually is
Four things it is not.
I’m being deliberately vague about the mechanism on this page. Inside the playbook, I name it, document it, and hand you the exact prompts and scripts to install it. Here’s what I will tell you:
Nothing to install. No dependencies. No vendor lock-in. Works in any language, on any stack, with any AI coding agent — Claude Code, Cursor, Copilot, your custom build.
It’s a structural protocol — a way of organizing what your AI agents read, see, and remember. Implemented correctly, it transforms how every AI session your team runs.
You install it once per project. Roughly an hour of senior developer time. After that, the foundation is in place permanently and every AI session compounds against it.
your team can do before scoping, building, or hiring for any AI work. That’s how I run my own company. Hundreds of codebases, all running on this foundation.
The paradox
This is designed to slow you down.
While the rest of your industry is racing to ship features as fast as possible, this playbook is going to make you stop for an hour and set up a foundation before you build anything else. That feels wrong. That feels like the opposite of what you should be doing in a market where speed matters.
It is exactly what you should be doing.
Skip the foundation
Every AI session your team runs starts from zero. Pasted context, drifting output, accumulating debt. Eventually someone proposes a tech debt sprint to clean it up. Three weeks later, you’re back to shipping features and the cycle repeats.
With the foundation
Every AI session starts with the agent reading the project’s foundational files in under five seconds. It already knows what the project is, what conventions apply, what mistakes have been avoided, what’s being worked on right now. The session goes straight to productive work.
A few hours of foundation work prevents months of accumulating debt — and unlocks lightning-speed execution forever after.
The teams that install this in early 2026 will have a permanent structural advantage over teams that install it in late 2027. The advantage compounds quietly, in the form of code that fits, decisions that stay decided, and AI tooling that gets better at your projects over time instead of worse.
What you get
33 files. Two tracks. Ten minutes to install.
I built this the way I run my own portfolio. One track for the person signing the checks, one for the person writing the code. Both are short, dense, and designed to be read in a single sitting.
The Orientation PDF
The first thing you open. How to use the bundle, in what order, with what rules.
The CEO Track
Why this matters at the business level. The methodology in plain English. The five diagnostic questions to ask your developers — and what their answers tell you.
The Coder Track
Full methodology. Audit phase. Apply phase. The session protocol that keeps the foundation current, and the hub-and-spoke pattern I use to scale across hundreds of codebases.
The Prompts
Copy-paste ready. Phase 1 audit scans any project. Phase 2 apply installs the foundation. Session starter + checkpoint commands keep it current.
The Scripts
A session wrapper that logs every AI session for later debugging or audit. Agent-agnostic.
The Templates
Every new feature, decision, and gotcha gets shaped the same way every time, so the foundation grows consistently across every project.
Total: 33 files. About 10 minutes to install on your most active project. Cost: $99.
Run the math
What this costs to not have.
Run the math against your last AI project.
- How many hours did your senior engineers spend re-explaining the project to AI agents?
- How many bugs got reintroduced because the AI didn’t know they’d already been fixed?
- How much code review time went to pattern drift instead of real review?
- How many decisions got relitigated three months after they were settled?
- How long did it take to onboard the last new developer?
- How much did your last contractor handoff actually cost in synchronous walkthrough time?
Add it up. The answer is in five or six figures, not three.
This playbook is $99. It pays back on the second AI session you run after installing the foundation.
Two tracks
Who this is for.
The bundle has two tracks. One for the person signing the checks. One for the person writing the code. Whichever side of the project you sit on, this is built for you.
The CEO Track
For CEOs, owners, presidents.
- You manage a software team that uses AI coding tools — Claude Code, Cursor, Copilot, anything similar.
- You are about to start, or are in the middle of, an AI-driven product or feature initiative.
- You have hired or are about to hire a contractor or vendor to build something with AI.
- You manage more than one project and want consistency across them.
- You sit on the board of a company building AI products and aren’t sure whether the foundation is in place.
- You have ever heard yourself or your team say: “the AI is being weird,” “the agent forgot what we decided,” or “we keep re-introducing the same bug.”
The Coder Track
For coders, developers, AI agents.
- You use Claude Code, Cursor, Copilot, Aider, or any AI coding agent every day.
- You’re tired of re-explaining the project to the AI on every session.
- You’ve felt the drift — bugs reintroduced, decisions relitigated, context lost between sessions.
- You’ve tried rules files or agents.md and want a complete system instead of half-measures.
- You manage multiple repos and want a consistent foundation across all of them.
- You want a session protocol your team will actually follow — not another doc in /docs.
After you buy
You see the difference within the first hour.
- First 10 minYou read the orientation PDF and decide which track applies to you.
- Next 30 minYou read your track end-to-end. CEO or Coder. Both are written to be read in a single sitting.
- Within the hourYou pick the project you want to migrate first. You run the Phase 1 audit. You review the report.
- Same afternoonYou run the Phase 2 apply. You commit to Git. You start your next AI session through the new protocol. You see the difference within the first hour.
- TomorrowYou apply it across your portfolio. You stop having the conversations that have been quietly costing your team a quarter of its productive time for the last year.
By the end of today, you’ll have a working foundation, a session protocol, and the start of a quiet but compounding advantage.
The pricing
Why I’m selling this for $99.
Because the alternative is that I write a 30-page proposal, schedule three discovery calls, charge you $15,000 to come implement it personally, and we both feel like we’ve done something serious.
I’ve done that engagement many, many times. The work is the same every time. The result is the same every time. The only thing that varies is which client is paying for the same hour of foundation work.
You don’t need me to do it for you. You need to know it exists, understand why it matters, and have the prompts and scripts ready to run it yourself.
That’s what this playbook is.
If you’d rather hire me directly to come install this in your organization personally, I’m available. The rate is $15,000. The result is the same. The choice is yours.
Frequently asked
Questions.
Will this work with my AI tool?
Yes. The methodology is filesystem-based and tool-agnostic. The bundle uses Claude Code in its examples, but every prompt and pattern adapts cleanly to Cursor, Aider, Continue, Copilot, or any custom agent that can read files in a repository.
How long does the actual setup take?
About twenty minutes per project.
Do I need to be technical to use this?
The CEO track is written for non-technical readers. You can read and understand the entire methodology without writing code. The hands-on setup is done by your developers using the prompts in the bundle.
Why won’t you tell me what the methodology actually is on this page?
Because the value of having this foundation is partly that your competitors don’t have it. I’m not going to broadcast the playbook for free on a public page. Inside the bundle, I name it, document it completely, and hand you the working prompts. The price of admission is $99.
What if my team pushes back on it?
Common. The Coder track addresses every objection developers typically raise. The most effective response is to ask them to run the Phase 1 audit on a single project. The audit is read-only and takes five minutes. The report itself usually changes their minds.
Can I share this with my team?
The bundle is licensed for use within your organization. The prompts, scripts, and templates are yours to use, modify, and adapt for any commercial purpose. Redistribution of the playbook itself is not permitted.
What’s the refund policy?
If you read the orientation PDF and the first file of either track and don’t think this is worth $99, email me and I’ll refund you. I’d rather you not buy something you won’t use than have you sitting on a playbook that isn’t right for you.
Buy the playbook. Open the PDF. See the difference within the hour.
The teams who install this in 2026 will be eating the lunch of the teams who don’t, for as long as AI matters in software development.
Instant download.