Prompt Kit: The Ambition Unlock

This kit turns the article's core argument — that collapsing execution cost demands expansion, not contraction — into four working prompts. Each one forces a specific strategic conversation: surfacing the opportunities your org has been self-censoring, turning domain expertise into buildable specs, making the economic case for expansion over cuts, and compressing the gap between insight and action.

How to use this kit

These prompts are designed for leaders, operators, and domain experts who are ready to stop asking "how many people can we cut?" and start asking "what can we build now that was previously impossible?" Run them in any capable AI assistant — ChatGPT, Claude, or Gemini all work well.

Prompt 1 (Ambition Audit) is the starting point for any leadership team. Run it before your next strategy session.
Prompt 2 (Domain Expert → Builder) is for the non-engineers in your org who know what software should exist but have never been able to build it.
Prompt 3 (Expansion Economics Brief) builds the board-ready case for investing in growth instead of pocketing the savings.
Prompt 4 (Insight-to-Action Compression) is for operators who want to redesign specific workflows so the org moves at the speed of insight.

You can run them independently or in sequence. If you run 1 first, the opportunities it surfaces will feed directly into 3 and 4.

Prompt 1: The Ambition Audit

Job: Surface every opportunity your company has been self-censoring because execution cost made them "not worth proposing" — then rank them by potential impact.

When to use: Before strategic planning, board meetings, or any conversation where headcount and AI investment are on the table. Especially useful when your leadership team is defaulting to the cost-reduction frame.

What you'll get: A structured inventory of suppressed opportunities across your business — the ideas that never got proposed because they were too niche, too speculative, or too expensive to staff — ranked by a new viability score based on collapsed execution costs.

What the AI will ask you: Your company, industry, current team size, what your team spends most of its time on, the types of ideas that typically get killed in prioritization, and any markets or capabilities you've considered but shelved.

Prompt 2: Domain Expert → Builder Roadmap

Job: Help a non-engineer with deep domain expertise identify what they can now build with AI tools — and produce a concrete spec for their highest-impact project.

When to use: When you're a domain expert (healthcare, education, logistics, finance, legal, operations, etc.) who has always known what software should exist for your field but couldn't build it. Also useful for leaders trying to unlock builder capacity across non-engineering teams.

What you'll get: A prioritized list of tools you could build based on your domain knowledge, plus a detailed specification for the #1 project — written clearly enough that you could hand it to an AI coding tool and start building the same day.

What the AI will ask you: Your domain, your daily workflows, the problems you solve manually that should be software, and the workarounds you've built with spreadsheets, sticky notes, or willpower.

Prompt 3: The Expansion Economics Brief

Job: Build a rigorous, board-ready argument for why your company should invest in expansion — not headcount reduction — in response to AI-driven execution cost collapse.

When to use: When you need to persuade a board, executive team, or investors that the Whoop model (hire more + invest in AI) beats the "lean and mean" model. When the default conversation in your org is about cuts and you need to shift it to growth.

What you'll get: A structured strategic brief with the economic logic, historical parallels, specific opportunity sizing, and a concrete investment plan — written in the language that boards and C-suites actually respond to.

What the AI will ask you: Your company's financials (roughly), industry, current AI investments, what the "cut" camp is proposing, and what expansion opportunities you see but can't yet articulate in economic terms.

Prompt 4: Insight-to-Action Compression Map

Job: Identify the specific workflows in your organization where the lag between "someone has an insight" and "the organization acts on it" is destroying value — then redesign each one so insight goes directly to tested prototype.

When to use: When you know your org is slow to act on good ideas, when insights die in status meetings and Jira backlogs, or when you want to pilot the "speed of insight" model the article describes on a real workflow in your company.

What you'll get: A detailed map of your org's worst insight-to-action bottlenecks, redesigned compressed workflows for each one, and a pilot plan you can start running this week.

What the AI will ask you: Your company, the teams or functions you want to focus on, specific examples of insights that took too long to act on (or died entirely), and what tools your team currently uses.