30 days. Real work. A practice that sticks.
Every exercise produces a real artefact โ not a training simulation.
The problem
The problem isn't the tool. It's the entry point.
Asked it to write an email, got something close but not quite right, edited it for 15 minutes, concluded it wasn't much faster than doing it themselves.
Went through a course, practised on hypothetical scenarios, then sat down on Monday with a real project and didn't know where to start.
Uses it when they remember. Doesn't use it when they're busy. The habit never formed because the starting point was never clear enough.
One PM uses it constantly. Another doesn't bother. The difference isn't skill โ it's whether someone gave them a working entry point.
The difference
The habit forms because the practice is the work โ not a simulation of it.
The one rule: use your real project data. Not a hypothetical. Not a worked example. Your actual brief, your actual Slack thread, your actual task list.
The 30-day arc
Each week builds on the last. By Day 30 you won't just have a habit โ you'll have a documented AI working practice you can apply to any project.
Requirements, inputs, and structure. Bounded tasks with clear inputs and expected outputs. Build the muscle of using AI on real work.
Making sense of project data. Meeting transcripts, risk registers, change logs, health assessments, lessons learned.
Drafting for real stakeholders. Executive briefings, escalations, scope change emails, stakeholder updates. The biggest time savings.
Building your personal prompt library. Custom status report prompt, QA checklist, and your 30-day AI Workflow Blueprint.
What's included
30-day money-back guarantee
Week 1 โ Free
Days 1โ7 plus the Week 1 Playbook. Everything you need to see whether the stack works on your real project before you commit to the full 30 days.
Who it's for
You spent an afternoon with it, got outputs that were close but needed editing, and went back to your inbox. The problem was the entry point โ not the tool.
You know AI could save you time but you're not sure where to begin. The Habit Stack gives you one concrete task per day, starting with the highest-value, easiest-to-evaluate outputs.
Some people produce great outputs. Others don't bother. The gap isn't capability โ it's whether they have a working entry point and a clear standard for what good looks like.
Building the habit early โ before manual processes are entrenched โ is the fastest path to a working AI practice. The Habit Stack gives you 30 days of structured starting points.
FAQ
No โ that's a suggestion, not a rule. Some people run two or three in a session when they have project material that fits. What matters is that you use real project data each time, and that you work through the weeks in order. Don't skip ahead to Week 4 before you've done Weeks 1 and 2 โ the arc is designed to build.
Yes. The prompts work with Claude, ChatGPT, Gemini, and any other major AI assistant. You don't need a specific tool or subscription level. If a prompt references a format that differs in your tool, adjust the output format instruction โ the prompts are designed to be adaptable.
Use recent project material. If Day 8 (action register from a meeting transcript) falls on a week where you haven't had meetings, use a transcript from last week or last month. The habit still forms โ and you'll know exactly what to do the next time that scenario comes up.
30 days. If you work through the stack on real project data and it doesn't save you time, get a full refund. No questions asked.