AI did not make you a better leader. A framework might.
Nearly everyone now has the same models on the same screen. The gap is no longer access — it is knowing what to ask, in what order, with what context attached.
Three reasons AI quietly disappoints people.
A blank box gives you back exactly what you put in.
Type “write a marketing plan” and you get a marketing plan for nobody — no industry, no stage, no constraint, no customer. It reads fine and is useless, which is the worst combination, because it takes a week to notice.
The model is not guessing badly. It is guessing, because you did not tell it anything worth using.
Everyone on the team prompts differently.
One person writes a paragraph, another writes five words, a third pastes a whole document. Three answers come back in three shapes, and none of them can be compared, reviewed or reused.
Without a shared structure, AI makes a team faster at producing work that does not add up.
What worked last year stops working.
Prompting technique moves faster than print. A book of prompts written today is partly wrong within a year, and the reader has no way of knowing which parts.
That is a structural problem with books about software — and it is the one this book was designed around rather than ignored.
The prompt was never the hard part. The thinking behind it was.
This book is 108 of those thoughts, written down in the order a business actually runs into them — each one ending in a prompt you can paste, not a principle you have to interpret.
Same question. Same model. Two very different inputs.
A founder asking about positioning. On the left, the way most people ask. On the right, framework 1.1 from module one — and what each one gets back.
Without a framework
Most people- No industry, stage or customer attached
- No format asked for, so you still have to process it
- Ask again tomorrow and you get something else
With framework 1.1
C.A.R.E- Own same-day dispatch visibility — the one metric their current vendor hides
- Price per shipment, not per seat — matches how they already budget
- Position against spreadsheets, not rivals — that is the real incumbent
- Role and context attached, so the answer is about your business
- Format specified, so it arrives ready to act on
- Repeatable — your co-founder runs it and you can compare
A printed book that does not go out of date.
Four decisions that separate this from every other book of prompts on the shelf.
Every page has a live twin
Scan the code on any framework and the current version of that prompt opens on your phone. The paper stays fixed; the prompt keeps moving.
Organised by decision, not by topic
Chapters follow the order a business hits problems — strategy, model, market, sales, team, operations, money — so you read the one you need this week.
Frameworks that point at each other
Each one names the two or three it pairs with, so finishing a pricing question hands you the positioning question that follows it.
The prompts are free, forever
No account, no paywall, no trial on the website. The book earns its price by explaining when to reach for which one — not by locking the text away.
Ten modules. 108 frameworks. 276 pages.
Every framework follows the same shape: what it is, when to use it, the prompt, and what it pairs with next.
Act as a Pre-Mortem facilitator. Project or decision : [DESCRIBE WHAT YOU ARE ABOUT TO DO] Timeline : [HOW LONG THIS WILL TAKE] Team involved : [ROLES RESPONSIBLE FOR EXECUTION] Resources committed : [BUDGET, TIME, PEOPLE] Run a Pre-Mortem: SCENARIO: It is [DATE 12 MONTHS FROM NOW]. This project has failed. Not partially, completely. What happened? Generate 10 specific reasons it failed, across: Execution failures (team, timeline, quality) Market failures (wrong assumptions about customers) Resource failures (budget, capacity, dependencies) Strategic failures (wrong direction or timing) External failures (competition, regulation, market shift) Then: rank the top 3 by likelihood × severity. For each top failure: one prevention action and one owner. Pre-Mortem Analysis Imagine Failure Write Individually Identify Top 3 Assign Prevention Project has failed one year Each person lists every Group finds the most likely, Each failure mode gets a from now reason it failed most serious failure modes named owner and action PRO TIP The Pre-Mortem's greatest value is not the list of failure modes — it is the social permission it creates for people to raise concerns. In a team that is committed to a plan, raising doubts feels disloyal. The Pre-Mortem makes it the job. Run it before every significant commitment and watch concerns surface that would have stayed silent until they became problems.
This is one page of the book, and the page its QR code opens. Both say the same thing today. Only one of them can be corrected next year.
“I wrote the book I kept trying to find — the one that answers the question I am actually stuck on, on the day I am stuck on it.”
Most business books are read once and shelved. This one was built to be scanned at a desk, mid-problem, with the model already open in the next tab. Every framework had to earn its page by being something I would reach for again.
The QR codes are not a gimmick. They are how the printed version stays honest — when a technique changes, the page behind the code changes with it, and nobody has to buy a second edition.
Draft copy — rewrite in your own words before launch.
If you make decisions for a living, it was written for you.
Five groups get the most out of it. Each has its own page with the modules that matter first.
Keep it on the desk. Not on a shelf.
108 frameworks in print, every prompt live on this site, updated as the models change.
Paperback · 276 pages · published by Notion Press
Store links to be added before launch