I have spent thirty years running projects, and for most of them I assumed the way to package what I know was software. A proper app, with forms and validation and a settings page for everything. That plan still exists: the Akigo! suite is in development, and it is why this site has a waitlist.
The kit shipped first anyway, and it is a really slimmed-down Akigo! Pulse: the project-intelligence part of the suite, running in the AI you already use. The PM AI Starter Kit is available today at thirtyyearpm.com/kit: thirty dollars, instant download, no subscription. This is why the method went out the door before the software.
The method is older than the software
Nothing in the kit is a new idea, and that is the point. Risk registers, issue logs, change control, decision records, action items, dependencies, the future-state risk assessment before a project starts: every competent PM has run some version of these, and I have run all of them for thirty years, on projects that went well and ones that taught me more.
What separates a project that holds together from one that falls apart is rarely the framework. It is whether the records actually get written, and whether anyone can find them again in month nine. A scored risk has always cost ten minutes and some discipline, so on busy weeks it did not happen, and everyone paid for that later.
The AI did not change the method. It changed who can afford to run it. When the writing is the AI’s job and the judgment stays yours, ten minutes of typing becomes one sentence of plain English.
What a sentence turns into
You tell your AI: “The vendor’s docs slipped two weeks.”
The kit’s procedure takes over from there. The AI asks until it has real answers, probability, impact, owner, response, and it never invents project facts to fill a gap. When it is done, the risk sits as a row in the right tab of a 17-tab Excel workbook, a branded one-page document renders beside it ready to forward, and the dashboard board updates its counts and its ranked list of what needs attention now.
Eleven procedures work this way, from kickoff to closeout: risk, issue, change request, decision, assumption, constraint, action item, dependency, status report, the future-state risk assessment, and lessons learned. The skill installs into ChatGPT, Claude, or Gemini, and every procedure also works pasted into any other AI. I tested each one on real projects before it shipped, because a procedure that only works when a form forces it was never the point.
Why the app went second
An app is a multi-year commitment, and the register nobody maintains is a problem this quarter. Status reports written twice because nobody could find the first one, risks that went stale the week after the steering committee, decisions whose reasoning lives in somebody’s inbox: none of that is waiting for my roadmap, and the kit does something about it now.
There is a quieter reason too. Before I harden thirty years of judgment into native software, I want to see which parts of it people actually reach for. A kit that sells and gets used answers that better than any survey. People who buy it hear about the apps first, and what they run most will influence what gets built first.
What it does not do
It does not phone home. The workbook lives on your machine, your project data never leaves it, and there is nothing to log into. One license per person; use it on your employer’s projects, your clients’ projects, whatever you manage. Everything the kit produces is yours, including every branded document you send to a stakeholder.
Where it stands
The Akigo! suite is still coming: Echo, Flow, Pulse, and Notes, all local-first, built on the same thirty years of experience. The first app is in testing now. The kit is the method, running in the AI you already use.
If you want it today, it is at thirtyyearpm.com/kit. The app will arrive when it’s fully tested and ready. Your status report is due this week either way.