Claude Prompt Library

30 Claude Prompts That Build Strategy Frameworks

30 copy-paste prompts

Describe your business or decision and Claude returns a filled-in, color-coded framework as a previewable HTML artifact: classic and competitor SWOT, TOWS, PESTLE, Porter's Five Forces, BCG and risk matrices, gap and VRIO analysis. Each one ends with a clear strategy takeaway, not just a grid.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ€” no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

SWOT Variations

5 prompts

Classic 2x2 SWOT Analysis

1/30

You are a strategy consultant who turns messy business context into a clean SWOT board. <context> I need a complete, color-coded SWOT analysis rendered as one self-contained HTML file with inline CSS so I can preview it instantly as an artifact and drop it into a deck. </context> <inputs> - Business / unit being analyzed: [WHAT IT IS] - What it sells and to whom: [PRODUCT AND CUSTOMER] - Stage and size: [E.G. SEED STARTUP, MID-MARKET, ENTERPRISE LINE] - Recent wins and pain points: [WHAT IS GOING WELL / BADLY] - Market context: [TRENDS, REGULATION, ECONOMY] - Top competitors: [NAMES] </inputs> <task> Build a 2x2 SWOT grid: Strengths (green), Weaknesses (amber), Opportunities (blue), Threats (red), each quadrant with 4-6 concrete, specific bullet points drawn from my inputs. Below the grid, add a short "Strategic implication" line per quadrant and one bottom-line takeaway naming the single most important move. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Points must be specific and evidence-led, not generic ("strong brand" is banned unless tied to a fact). - Accessible contrast, clear quadrant labels and icons, print-friendly. </constraints> <format> Return the full HTML as an artifact, then list the two assumptions you made that I should verify. </format>

Builds a color-coded 2x2 SWOT grid with specific points and a strategic takeaway as a previewable artifact.

๐Ÿ’ก

Pro tip: Paste 3-4 real bullet facts (a churn number, a funding round, a new entrant) so Claude grounds each quadrant instead of guessing.

Competitor SWOT (Head-to-Head)

2/30

You are a competitive-intelligence analyst who profiles rivals objectively. <context> I need a SWOT analysis of a specific competitor, not my own company, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Competitor name and what they do: [NAME PLUS PRODUCT] - How they position and price: [POSITIONING, PRICE TIER] - What I know about their customers: [SEGMENTS] - Their recent moves: [LAUNCHES, FUNDING, HIRES, PRESS] - My company (for the head-to-head note): [WHO WE ARE] - Where we compete directly: [OVERLAP] </inputs> <task> Build a color-coded SWOT of the competitor with 4-6 specific points per quadrant. Add a right-hand "So what for us" column that translates each of their strengths into a threat we must counter and each weakness into an opening we can exploit. End with a 2-3 line head-to-head verdict on where we can realistically win. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Stay objective about the competitor; no wishful thinking in their Strengths quadrant. - Every "So what for us" note must be an action, not an observation. </constraints> <format> Return the full HTML as an artifact, then flag which claims about the competitor are inferred vs. confirmed. </format>

Produces a competitor SWOT with a 'so what for us' action column and head-to-head verdict as a previewable artifact.

๐Ÿ’ก

Pro tip: Drop in the competitor's pricing page and latest changelog so Claude reasons from real moves, not reputation.

Personal / Career SWOT

3/30

You are an executive career coach who runs honest, useful self-assessments. <context> I want a personal SWOT for my career, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - My role and field: [TITLE AND INDUSTRY] - Career goal (next 2-3 years): [WHERE I WANT TO BE] - My strongest skills and proof: [SKILLS PLUS EVIDENCE] - Gaps or things I avoid: [WEAK SPOTS] - Market trends affecting my field: [WHAT IS CHANGING] - Risks to my path: [LAYOFFS, AUTOMATION, COMPETITION] </inputs> <task> Build a color-coded personal SWOT with 4-6 candid points per quadrant tied to my goal. Add a "Leverage" note under Strengths (how to use it now) and a "Close the gap" note under Weaknesses (concrete first step). End with a 90-day focus: the one strength to lean on and the one gap to fix. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Be direct but constructive; weaknesses must be actionable, not vague labels. - Tie every opportunity and threat to my stated goal. </constraints> <format> Return the full HTML as an artifact, then suggest two questions to ask a mentor based on the gaps. </format>

Creates a candid personal career SWOT with leverage notes and a 90-day focus as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude a recent piece of real feedback (a review line, a rejection reason) so Weaknesses are grounded, not self-flattering.

Product / Feature SWOT

4/30

You are a product strategist who pressure-tests a single product or feature. <context> I need a SWOT for one specific product or feature, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - Job it does for users: [CORE JOB-TO-BE-DONE] - Adoption / usage signals: [METRICS OR ANECDOTES] - Where it falls short: [KNOWN COMPLAINTS, GAPS] - Adjacent trends and demand: [WHAT USERS WANT NEXT] - Competing or substitute features: [ALTERNATIVES] </inputs> <task> Build a color-coded SWOT focused on the product/feature with 4-6 specific points per quadrant. Tag each Opportunity and Threat with a rough effort/impact label (e.g. high-impact / low-effort). End with a build/improve/kill recommendation and the single next bet for this feature. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Anchor Strengths and Weaknesses in usage signals, not opinions. - Keep it about THIS feature, not the whole company. </constraints> <format> Return the full HTML as an artifact, then list the one metric that would change your build/kill call. </format>

Builds a product-or-feature SWOT with effort/impact tags and a build/improve/kill call as a previewable artifact.

๐Ÿ’ก

Pro tip: Include a couple of raw user quotes so Claude can sharpen Weaknesses into real, fixable complaints.

Pre-Launch / Go-No-Go SWOT

5/30

You are a launch advisor who runs a final pre-launch readiness check. <context> We are about to launch and I want a decision-grade SWOT, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - What we are launching: [PRODUCT / CAMPAIGN / MARKET ENTRY] - Launch date and goal: [WHEN AND TARGET] - What is ready and strong: [ASSETS, TEAM, PROOF] - What is shaky or unfinished: [RISKS, GAPS] - Market timing and demand signals: [CONTEXT] - What could go wrong externally: [COMPETITOR, REGULATORY, ECONOMIC] </inputs> <task> Build a color-coded launch SWOT with 4-6 points per quadrant focused on readiness. Add a risk-severity dot (low/med/high) to each Threat and Weakness. End with a clear Go / Go-with-conditions / No-Go recommendation, the conditions to clear first, and the top mitigation for the worst threat. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - The recommendation must be decisive, not a hedge. - Conditions must be specific and checkable before launch. </constraints> <format> Return the full HTML as an artifact, then list the single blocker that should override a Go decision if unresolved. </format>

Produces a decision-grade pre-launch SWOT with severity dots and a go/no-go call as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude your hard launch date; a fixed deadline forces sharper Go-with-conditions logic than an open one.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

Matrix & Quadrant Frameworks

5 prompts

TOWS Strategy Matrix

6/30

You are a strategy consultant who turns a SWOT into action via the TOWS matrix. <context> I have SWOT inputs and want a TOWS matrix that crosses them into strategies, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Strengths: [LIST] - Weaknesses: [LIST] - Opportunities: [LIST] - Threats: [LIST] - Business goal this should serve: [GOAL] - Constraints (budget, time, team): [LIMITS] </inputs> <task> Build a 2x2 TOWS grid with four color-coded cells: SO (use strengths to seize opportunities), WO (fix weaknesses to seize opportunities), ST (use strengths to defend threats), WT (minimize weaknesses and avoid threats). Put 2-3 concrete, named strategies in each cell. End with a prioritized shortlist of the top 3 strategies to start this quarter and why. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Each strategy must combine a specific factor pair, not restate the SWOT. - Strategies must respect my stated constraints. </constraints> <format> Return the full HTML as an artifact, then explain which quadrant deserves the most attention given my goal. </format>

Builds a TOWS matrix that crosses SWOT factors into named SO/WO/ST/WT strategies as a previewable artifact.

๐Ÿ’ก

Pro tip: Feed in the SWOT bullets verbatim; TOWS is only as good as the specificity of the factors you cross.

BCG Growth-Share Matrix

7/30

You are a portfolio strategist who maps products onto the BCG matrix. <context> I want my products or business units plotted on a BCG growth-share matrix, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Products / units to plot: [LIST WITH ONE-LINE EACH] - Rough market-growth rate per item: [HIGH / LOW OR %] - Rough relative market share per item: [HIGH / LOW OR LEADER/FOLLOWER] - Revenue or weight of each: [SO BUBBLES SIZE] - Strategic goal: [GROW, MILK, EXIT] </inputs> <task> Build a four-quadrant BCG matrix (Stars, Cash Cows, Question Marks, Dogs) with growth on the Y axis and share on the X axis. Place each product as a labeled, sized bubble in the right quadrant and color-code by quadrant. Below the chart, give a recommended action per product (invest / hold / harvest / divest) with one-line reasoning. End with where to reallocate budget. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG positioning only, Google Fonts allowed. - Bubbles must be readable and labeled; legend included. - Actions must follow standard BCG logic for each quadrant. </constraints> <format> Return the full HTML as an artifact, then note which placements are most sensitive to my growth/share estimates. </format>

Plots products on a four-quadrant BCG matrix with sized bubbles and invest/harvest actions as a previewable artifact.

๐Ÿ’ก

Pro tip: Even rough high/low calls work; ask Claude to mark any product it considers borderline between two quadrants.

Risk Probability-Impact Matrix

8/30

You are a risk manager who builds clear probability-impact heat maps. <context> I need a risk matrix for a project or initiative, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Project / initiative: [WHAT IT IS] - Known risks: [LIST AS MANY AS YOU HAVE] - Anything keeping me up at night: [TOP WORRIES] - Timeline and stakes: [DEADLINE, BUDGET, CONSEQUENCES] - Risk appetite: [LOW / MEDIUM / HIGH] </inputs> <task> Build a 5x5 probability (Y) by impact (X) heat-map grid with green/amber/red zones. Place each risk as a labeled marker in its cell, then render a ranked risk register table below: risk, probability, impact, score, owner placeholder, and a concrete mitigation per risk. Add 2-3 risks I likely overlooked. End with the top 3 risks to mitigate first. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Cell colors must follow a consistent green-to-red scale; legend included. - Mitigations must be specific actions, not "monitor closely". </constraints> <format> Return the full HTML as an artifact, then explain how you scored probability and impact so I can adjust. </format>

Builds a 5x5 risk heat map plus a ranked register with mitigations as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to surface the risks you didn't list; the overlooked ones are usually the dangerous ones.

Effort-Impact Prioritization Matrix

9/30

You are an operations strategist who ruthlessly prioritizes a backlog. <context> I have a list of initiatives and want them plotted on an effort-vs-impact matrix, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Initiatives / tasks to prioritize: [LIST] - What 'impact' means here: [REVENUE / RETENTION / TIME SAVED] - Team capacity: [HOW MUCH WE CAN TAKE ON] - Hard deadlines on any item: [IF ANY] - Strategic theme for the quarter: [FOCUS] </inputs> <task> Build a 2x2 effort (X) by impact (Y) matrix with quadrants Quick Wins, Big Bets, Fill-Ins, and Time Sinks, color-coded. Place each initiative as a labeled dot in its quadrant. Below, render a do-now / schedule / maybe / drop list with one-line reasoning per item. End with the recommended order of execution for this quarter. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Dots must be labeled and non-overlapping where possible; legend included. - Be opinionated; do not leave everything in the middle. </constraints> <format> Return the full HTML as an artifact, then name the one item I should kill outright to free capacity. </format>

Plots initiatives on an effort-impact 2x2 with quick-wins/big-bets quadrants and a do-now list as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude your real capacity; constraints turn a pretty chart into an actual sequenced plan.

Stakeholder Power-Interest Grid

10/30

You are a stakeholder-management advisor for a major initiative. <context> I need a power-interest grid to plan how to manage stakeholders, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Initiative / change: [WHAT IT IS] - Stakeholders (name or role): [LIST] - Their rough power over the outcome: [HIGH / LOW PER PERSON] - Their interest / stake: [HIGH / LOW PER PERSON] - Known supporters and skeptics: [WHO] - My goal with them: [WHAT I NEED] </inputs> <task> Build a 2x2 power (Y) by interest (X) grid with quadrants Manage Closely, Keep Satisfied, Keep Informed, and Monitor, color-coded. Place each stakeholder as a labeled marker. Below, give a tailored engagement plan per stakeholder: cadence, channel, and the one message that wins them over. End with the two relationships most critical to invest in first. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Engagement tactics must be specific to the person's position, not generic. - Mark anyone who is a swing vote distinctly. </constraints> <format> Return the full HTML as an artifact, then suggest how to convert the most important skeptic. </format>

Builds a power-interest stakeholder grid with per-person engagement plans as a previewable artifact.

๐Ÿ’ก

Pro tip: Flag who is a skeptic vs. supporter in the inputs so Claude tailors the winning message, not just the cadence.

External Environment Analysis

5 prompts

PESTLE Macro-Environment Scan

11/30

You are a strategy analyst who scans the macro environment with PESTLE. <context> I want a PESTLE analysis of the forces shaping my market, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Business / market: [WHAT AND WHERE] - Geography / regions: [MARKETS] - Time horizon: [NEXT 1-3 YEARS] - Known external pressures: [WHAT YOU ALREADY SEE] - The decision this informs: [WHY YOU NEED IT] </inputs> <task> Build a color-coded six-panel PESTLE board: Political, Economic, Social, Technological, Legal, Environmental. Give 3-5 specific, current factors per panel relevant to my market, and tag each factor as opportunity or threat with a likely time-to-impact (now / 1yr / 3yr). End with the 3 forces that most affect my decision and how to position for each. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Factors must be specific to my market and geography, not textbook generalities. - Each panel clearly labeled and color-coded; legend for opportunity vs. threat. </constraints> <format> Return the full HTML as an artifact, then list which factors you are least confident about so I can research them. </format>

Builds a six-panel PESTLE board with tagged factors and a positioning takeaway as a previewable artifact.

๐Ÿ’ก

Pro tip: Name your exact geography; regulation and economics differ enough by region to make a generic PESTLE useless.

Porter's Five Forces Analysis

12/30

You are an industry analyst who structures competition with Porter's Five Forces. <context> I want a Porter's Five Forces analysis of my industry, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Industry / market: [WHAT IT IS] - My position in it: [LEADER / CHALLENGER / NEW ENTRANT] - Key suppliers and how concentrated: [DETAIL] - Key buyers and their leverage: [DETAIL] - Known substitutes: [ALTERNATIVES] - Barriers to entry you see: [DETAIL] </inputs> <task> Build a five-force diagram (central Rivalry, surrounded by Supplier Power, Buyer Power, Threat of New Entrants, Threat of Substitutes). For each force give a strength rating (low/med/high) with a colored bar and 2-3 specific drivers. Below, summarize overall industry attractiveness and end with 2-3 strategic moves to improve my position against the strongest force. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG layout only, Google Fonts allowed. - Ratings must be justified by the drivers listed, not asserted. - Clear visual hierarchy with the central rivalry force emphasized. </constraints> <format> Return the full HTML as an artifact, then name the single force that most caps profitability in this industry. </format>

Builds a rated Porter's Five Forces diagram with drivers and strategic moves as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude your position (incumbent vs. entrant); the same forces read very differently from each seat.

Competitive Landscape Map

13/30

You are a market analyst who maps the competitive landscape on two axes. <context> I want a positioning map of competitors on a 2x2 of two axes that matter in my market, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Market / category: [WHAT IT IS] - Two axes that differentiate players: [E.G. PRICE vs. BREADTH] - Competitors to plot: [LIST WITH ONE-LINE EACH] - Where I sit (or want to sit): [MY POSITION] - What customers value most: [KEY BUYING FACTOR] </inputs> <task> Build a labeled 2x2 positioning map with the two axes named on each side. Plot each competitor as a labeled dot and place me distinctly (e.g. a star). Identify and shade any white-space gap on the map. Below, explain each player's position in one line and end with the clearest open positioning I could own and why it fits demand. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG positioning only, Google Fonts allowed. - Dots labeled and readable; my position visually distinct; axes clearly named. - The white-space callout must tie to what customers value. </constraints> <format> Return the full HTML as an artifact, then suggest an alternative pair of axes that might reveal a different opening. </format>

Builds a two-axis competitive positioning map with white-space callout and a positioning recommendation as a previewable artifact.

๐Ÿ’ก

Pro tip: Pick axes that buyers actually weigh; plotting on vanity dimensions produces a pretty but useless map.

Scenario Planning 2x2

14/30

You are a foresight strategist who builds scenario-planning matrices. <context> I want a 2x2 scenario matrix built on two critical uncertainties, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Decision / strategy at stake: [WHAT] - Two critical uncertainties (high-impact, unpredictable): [E.G. REGULATION TIGHT/LOOSE, DEMAND HIGH/LOW] - Time horizon: [E.G. 3 YEARS] - My current plan / bet: [WHAT YOU ASSUME] - What I most want to protect: [STAKES] </inputs> <task> Build a 2x2 matrix from the two uncertainties, creating four named, color-coded scenarios. For each scenario give a vivid one-paragraph narrative, the implication for my strategy, and one early-warning signal to watch. End with the no-regret moves that pay off in every scenario and the one bet that only wins in a single quadrant. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Scenarios must be genuinely distinct, not optimistic/pessimistic shades of one. - Each scenario gets a memorable name and a watch-for signal. </constraints> <format> Return the full HTML as an artifact, then flag which scenario my current plan is most exposed to. </format>

Builds a 2x2 scenario matrix with four named futures, signals, and no-regret moves as a previewable artifact.

๐Ÿ’ก

Pro tip: Choose two uncertainties that are both high-impact AND truly unpredictable; certainties make boring scenarios.

Market Attractiveness Scorecard

15/30

You are a market-entry analyst who scores opportunities on weighted criteria. <context> I want to compare potential markets or segments on a weighted attractiveness scorecard, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Markets / segments to compare: [LIST 2-5] - Criteria that matter to me: [E.G. SIZE, GROWTH, COMPETITION, FIT, MARGIN] - Rough weight per criterion: [IF YOU HAVE PREFERENCES] - Any data points per market: [NUMBERS YOU KNOW] - My capabilities / constraints: [WHAT WE CAN SERVE] </inputs> <task> Build a weighted scorecard table: criteria as rows with weights, markets as columns, color-coded 1-5 cell scores, and a weighted total per market with the winner highlighted. Justify each notable score in a footnote. End with a recommended market, the runner-up, and the single criterion that would flip the decision. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Cells color-scaled low-to-high; totals math must be correct and shown. - Scores must reflect the data and constraints I gave, not optimism. </constraints> <format> Return the full HTML as an artifact, then run a quick sensitivity note: which weight change would change the winner. </format>

Builds a weighted, color-scaled market attractiveness scorecard with a sensitivity note as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude your real weights; the winner often changes when you weight margin over raw market size.

Internal Capability Frameworks

5 prompts

VRIO Resource Analysis

16/30

You are a strategy professor who tests resources for durable advantage with VRIO. <context> I want a VRIO analysis of my company's resources and capabilities, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Company and what it does: [DETAIL] - Key resources and capabilities to test: [LIST, E.G. TECH, BRAND, DATA, TEAM, NETWORK] - What rivals can or cannot copy: [WHAT YOU KNOW] - How the resource is organized / used: [DETAIL] - The advantage you think you have: [HYPOTHESIS] </inputs> <task> Build a VRIO table: each resource as a row, with four color-coded yes/no columns (Valuable, Rare, Inimitable, Organized) and a final "Competitive implication" column (competitive disadvantage / parity / temporary advantage / sustained advantage). End with which resource is your real moat and how to protect or deepen it. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Yes/no calls must be justified in a tooltip or note, not asserted. - The implication column must follow strict VRIO logic. </constraints> <format> Return the full HTML as an artifact, then list the resource closest to becoming a sustained advantage and what it is missing. </format>

Builds a VRIO table classifying each resource's competitive implication with moat guidance as a previewable artifact.

๐Ÿ’ก

Pro tip: Be honest about 'Inimitable'; most resources fail there, and that is exactly the insight VRIO is meant to surface.

Capability Gap Analysis

17/30

You are an organizational strategist who maps the gap between today and the goal. <context> I want a gap analysis between our current state and our target state, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Goal / target state: [WHERE WE WANT TO BE BY WHEN] - Capability areas to assess: [E.G. PRODUCT, GTM, OPS, DATA, TALENT] - Where we are today per area: [CURRENT STATE] - Known blockers: [WHAT IS IN THE WAY] - Resources available: [BUDGET, TEAM, TIME] </inputs> <task> Build a gap-analysis table: capability area, current state, target state, gap size (color-coded small/medium/large), and a concrete closing action with owner placeholder and rough timeline per row. Add a simple current-vs-target bar visual per area. End with the critical-path gap that blocks the others and the first 30-day action. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Gap sizes color-scaled; closing actions must be specific and resourced. - Sequence actions by dependency, not just size. </constraints> <format> Return the full HTML as an artifact, then identify which gap, if ignored, makes the goal impossible. </format>

Builds a current-vs-target gap analysis table with sized gaps and closing actions as a previewable artifact.

๐Ÿ’ก

Pro tip: Define the target state in measurable terms; a fuzzy goal produces fuzzy gaps that no one can close.

Core Competency Map

18/30

You are a corporate strategist who isolates true core competencies. <context> I want a map of our competencies sorted into core, supporting, and non-core, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Company and market: [DETAIL] - Things we do well: [CAPABILITIES LIST] - What customers actually pay us for: [VALUE] - What we could outsource without harm: [GUESSES] - Strategic direction: [WHERE WE ARE HEADING] </inputs> <task> Build a three-zone map (color-coded): Core (drives value, hard to copy, opens future markets), Supporting (needed but not differentiating), and Non-Core (candidates to outsource or cut). Place each competency in a zone with a one-line rationale. End with what to double down on, what to standardize, and what to stop doing in-house. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - A competency is only Core if it meets all three core tests; justify placements. - Be willing to put popular activities in Non-Core if they do not differentiate. </constraints> <format> Return the full HTML as an artifact, then challenge one competency I likely over-rated as Core. </format>

Builds a three-zone core competency map with invest/standardize/stop guidance as a previewable artifact.

๐Ÿ’ก

Pro tip: Use the test 'do customers pay specifically for this?' to keep nice-to-have skills out of the Core zone.

McKinsey 7S Alignment Check

19/30

You are an organizational-design consultant who diagnoses alignment with the 7S model. <context> I want a McKinsey 7S analysis to check whether our organization is aligned, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Organization / team: [WHAT IT IS] - Strategy: [CURRENT STRATEGY] - Structure: [HOW WE ARE ORGANIZED] - Systems / processes: [KEY ONES] - Shared values / culture: [WHAT WE STAND FOR] - Style, staff, skills: [LEADERSHIP STYLE, PEOPLE, CAPABILITIES] - The change or strain we feel: [WHY THIS NOW] </inputs> <task> Build a 7S diagram (Shared Values at center, the other six around it) with a short current-state summary per element and a color-coded alignment rating (aligned / strained / misaligned). Add a misalignment matrix flagging the worst-conflicting pairs (e.g. Strategy vs. Structure). End with the top 2 misalignments to fix and the order to fix them. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG layout only, Google Fonts allowed. - Ratings must be justified by the inputs; central Shared Values visually emphasized. - The fix order must respect that soft elements take longer to change. </constraints> <format> Return the full HTML as an artifact, then name the one element dragging the rest out of alignment. </format>

Builds a McKinsey 7S diagram with alignment ratings and a misalignment fix-order as a previewable artifact.

๐Ÿ’ก

Pro tip: Be candid about Shared Values vs. stated values; the gap there usually explains the other misalignments.

Strengths-Based Value-Chain Map

20/30

You are an operations strategist who finds advantage across the value chain. <context> I want a value-chain analysis showing where we add the most value and where margin leaks, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Business and what it delivers: [DETAIL] - Primary activities (inbound, ops, outbound, marketing/sales, service): [HOW EACH WORKS] - Support activities (infra, HR, tech, procurement): [DETAIL] - Where you think you win: [HYPOTHESIS] - Cost or quality pain points: [PROBLEMS] </inputs> <task> Build a value-chain diagram with primary activities as horizontal stages and support activities as bands above them. Color-code each activity by whether it is a strength (green), neutral (grey), or a margin/quality leak (red), with a one-line note each. End with the 2 activities to turn into differentiators and the 1 leak to plug first. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG layout only, Google Fonts allowed. - Each activity classified and justified; standard value-chain structure. - Recommendations tied to customer-visible value, not just cost. </constraints> <format> Return the full HTML as an artifact, then note which strength is most defensible against competitors. </format>

Builds a color-coded value-chain map flagging strengths and margin leaks with priorities as a previewable artifact.

๐Ÿ’ก

Pro tip: Mark where cost is high but customer-visible value is low; that mismatch is your fastest margin win.

Decision & Trade-Off Tools

5 prompts

Weighted Decision Matrix

21/30

You are a decision analyst who structures choices with a weighted matrix. <context> I need to choose between options and want a weighted decision matrix, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Decision to make: [WHAT] - Options to compare: [LIST 2-6] - Criteria that matter: [LIST] - Rough weight per criterion: [IF YOU HAVE THEM] - Any hard constraints / dealbreakers: [IF ANY] - What I am optimizing for: [GOAL] </inputs> <task> Build a weighted decision matrix: criteria as rows with weights, options as columns, color-coded 1-5 scores per cell, weighted totals, and the winner highlighted. Flag any option that violates a dealbreaker. End with the recommended option, the close runner-up, and a one-line reason the winner wins. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Weighted-total math must be correct and visible; cells color-scaled. - Respect dealbreakers even if an option scores high overall. </constraints> <format> Return the full HTML as an artifact, then show which single weight change would flip the recommendation. </format>

Builds a weighted decision matrix with scored options, totals, and a sensitivity flag as a previewable artifact.

๐Ÿ’ก

Pro tip: Set weights before you see scores; deciding the weights afterward is how people rig the matrix toward a favorite.

Cost-Benefit Quadrant

22/30

You are a financial strategist who frames decisions on a cost-benefit quadrant. <context> I want a cost-benefit analysis of options on a 2x2, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Decision / options: [WHAT YOU ARE WEIGHING] - Costs to consider (money, time, risk): [DETAIL] - Benefits to consider (revenue, savings, strategic): [DETAIL] - Time horizon: [WHEN BENEFITS LAND] - Tolerance for cost: [BUDGET / APPETITE] </inputs> <task> Build a 2x2 cost (X) by benefit (Y) matrix with quadrants No-Brainer, Worth It, Marginal, and Avoid, color-coded. Plot each option as a labeled dot. Below, give a tabular cost-benefit breakdown per option (quantify where possible, label assumptions where not) and a simple payback or ROI note. End with the clear recommendation and the biggest hidden cost to watch. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Separate quantified figures from assumptions clearly; dots labeled. - Note intangible costs/benefits the numbers miss. </constraints> <format> Return the full HTML as an artifact, then flag the assumption that most affects whether this is worth it. </format>

Builds a cost-benefit 2x2 with plotted options and an ROI breakdown as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to surface hidden and intangible costs; the obvious dollar cost is rarely what kills a project.

Pros / Cons / Mitigations Board

23/30

You are a balanced advisor who pressure-tests a single decision. <context> I am weighing one specific decision and want a structured pros/cons board that also handles the cons, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - The decision (yes/no or this-vs-that): [WHAT] - Why I am leaning a certain way: [INITIAL LEAN] - What is at stake: [STAKES] - Constraints: [BUDGET, TIME, REVERSIBILITY] - What I am afraid of: [WORRIES] </inputs> <task> Build a three-column board: Pros (green), Cons (red), and for each Con a Mitigation column (how to reduce or neutralize it). Weight each pro and con as high/medium/low. Add a steelman of the opposite choice so I do not fool myself. End with a clear recommendation, the confidence level, and the one condition that would change it. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Every serious con needs a real mitigation, not a dismissal. - The steelman must be genuinely persuasive, not a strawman. </constraints> <format> Return the full HTML as an artifact, then state how reversible this decision is and whether that should raise or lower the bar. </format>

Builds a weighted pros/cons board with mitigations and a steelman as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask for the steelman of the choice you are NOT leaning toward; it is the cheapest way to catch a blind spot.

Build vs. Buy vs. Partner Matrix

24/30

You are a strategy advisor who frames sourcing decisions cleanly. <context> I need to decide whether to build, buy, or partner for a capability, and want a comparison matrix, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - The capability / need: [WHAT] - Why it matters strategically: [ROLE IN STRATEGY] - Internal capacity and skills: [WHAT WE HAVE] - Timeline pressure: [HOW URGENT] - Budget: [RANGE] - Known vendors or partners: [IF ANY] </inputs> <task> Build a comparison matrix with Build / Buy / Partner as columns and criteria as rows (cost, speed, control, fit, risk, long-term strategic value), color-coded ratings per cell. Add a short narrative on the strategic trade-off (control vs. speed). End with a recommendation, the deciding factor, and the one risk to manage in the chosen path. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Ratings justified by my inputs; the strategic-value row weighted heavily. - If the capability is core, bias toward build unless inputs strongly say otherwise. </constraints> <format> Return the full HTML as an artifact, then explain how the answer changes if the capability is core vs. commodity. </format>

Builds a build-vs-buy-vs-partner comparison matrix with a sourcing recommendation as a previewable artifact.

๐Ÿ’ก

Pro tip: State whether the capability is core to your moat; that single fact usually decides build vs. buy.

OKR Strategy Tree

25/30

You are a strategy operator who turns one goal into a clean OKR tree. <context> I want my top goal broken into an objectives-and-key-results tree, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - The overarching goal / mission for the period: [WHAT] - Time period: [QUARTER / YEAR] - Teams or areas involved: [LIST] - Constraints and current baseline metrics: [NUMBERS] - What 'winning' looks like: [TARGET OUTCOME] </inputs> <task> Build a visual tree: one top Objective, 3-4 measurable Key Results under it (each with baseline to target), then 2-3 supporting initiatives per Key Result. Color-code by team or by confidence. Make sure each Key Result is outcome-based and measurable, not a task list. End with the single Key Result that most determines whether the Objective is hit. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG layout only, Google Fonts allowed. - Key Results must be measurable with a number and a deadline; no vague verbs. - Initiatives must clearly ladder up to their Key Result. </constraints> <format> Return the full HTML as an artifact, then flag any Key Result that is secretly a task, not an outcome. </format>

Builds a visual OKR strategy tree with measurable key results and laddered initiatives as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude baseline numbers; without a 'from X to Y' a key result is just a wish dressed as a metric.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Boardroom-Ready Strategy Outputs

5 prompts

One-Page Strategy on a Page

26/30

You are a strategy director who compresses a plan onto a single visual page. <context> I want our whole strategy on one page (vision, where-to-play, how-to-win, priorities, metrics), rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Vision / north star: [WHAT] - Where we play (markets, segments): [DETAIL] - How we win (our edge): [DIFFERENTIATION] - Top 3-5 strategic priorities: [LIST] - Key metrics and targets: [NUMBERS] - Time horizon: [PERIOD] </inputs> <task> Build a single-page strategy canvas with clearly bounded, color-coded blocks: Vision banner, Where to Play, How to Win, Strategic Priorities (with one-line each), and a Metrics strip with targets. Keep it scannable in 30 seconds by an exec. End with the one sentence that captures the whole strategy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Everything fits one printable page; no block over three lines. - Specific and committed; no vague mission-statement filler. </constraints> <format> Return the full HTML as an artifact, then give the 15-word elevator version of this strategy. </format>

Builds a single-page strategy canvas with vision, where-to-play, how-to-win, and metrics as a previewable artifact.

๐Ÿ’ก

Pro tip: Force a real 'how we win' edge; if it could be any competitor's strategy, it is not a strategy.

Board-Ready SWOT + Action Plan

27/30

You are a chief of staff preparing a board slide that pairs analysis with action. <context> I need a board-ready SWOT that is immediately followed by an action plan, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Company / unit: [WHAT] - Current performance snapshot: [KEY METRICS] - Strengths and weaknesses: [LISTS OR FACTS] - Opportunities and threats: [LISTS OR CONTEXT] - Board's key concern: [WHAT THEY WILL ASK] - Resources for action: [BUDGET, TEAM] </inputs> <task> Build a clean SWOT grid up top, then an action-plan table below mapping each priority action to the SWOT factor it addresses, an owner placeholder, a timeline, and a success metric. Use a restrained, executive color palette. End with the single recommendation you want the board to approve and the resource ask. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Board-appropriate tone: confident, specific, no hype. - Every action must trace to a SWOT factor and carry a metric. </constraints> <format> Return the full HTML as an artifact, then draft the one-sentence ask you would say out loud to the board. </format>

Builds a board-ready SWOT paired with a traced action plan and resource ask as a previewable artifact.

๐Ÿ’ก

Pro tip: Name the board's likely toughest question in your inputs so Claude addresses it inside the action plan, not after.

Turnaround Diagnostic Dashboard

28/30

You are a turnaround consultant who diagnoses a struggling business fast. <context> A part of the business is underperforming and I want a turnaround diagnostic that combines a SWOT with a root-cause and 90-day plan, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - The struggling unit / product: [WHAT] - Symptoms (declining metrics): [NUMBERS] - Suspected causes: [HYPOTHESES] - Constraints (cash, time, morale): [DETAIL] - What must not be touched: [SACRED COWS / NON-NEGOTIABLES] </inputs> <task> Build a diagnostic dashboard: a compact SWOT, a root-cause panel (symptom to likely cause to evidence to check), a quick-win list (color-coded by speed), and a 30-60-90 day stabilization plan. Use urgency-appropriate but calm color coding. End with the single highest-leverage move to stop the bleeding in the first two weeks. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Distinguish symptoms from causes clearly; quick wins must be genuinely fast. - Respect the stated non-negotiables in every recommendation. </constraints> <format> Return the full HTML as an artifact, then list the first metric you would expect to move if the plan works. </format>

Builds a turnaround diagnostic dashboard with SWOT, root causes, and a 30-60-90 plan as a previewable artifact.

๐Ÿ’ก

Pro tip: Separate symptoms from causes in your inputs; turnarounds fail when teams treat the symptom and miss the cause.

Investor-Facing Market & Moat Slide

29/30

You are a startup advisor who builds the market-and-moat slide investors expect. <context> I am fundraising and want a single slide combining market opportunity, competitive positioning, and our moat, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Company and one-liner: [WHAT WE DO] - Market size signals (TAM/SAM or proxies): [NUMBERS] - Key competitors and how we differ: [DETAIL] - Our defensibility / moat: [WHY IT LASTS] - Traction proof: [METRICS] - The raise and use of funds: [AMOUNT, PLAN] </inputs> <task> Build an investor slide with: a market-size visual (nested TAM/SAM/SOM or a clean stat band), a mini competitive positioning map placing us in the white space, a three-point moat panel, and a traction strip. Use a clean, confident venture aesthetic. End with the one defensibility argument that should land hardest with investors. </task> <constraints> - One self-contained responsive HTML file; CSS/SVG visuals only, Google Fonts allowed. - Numbers must be presented honestly with labeled assumptions; no inflated TAM. - Moat points must be specific and hard to copy, not buzzwords. </constraints> <format> Return the full HTML as an artifact, then flag the weakest claim an investor will probe and how to shore it up. </format>

Builds an investor market-and-moat slide with sizing, positioning, and defensibility as a previewable artifact.

๐Ÿ’ก

Pro tip: Have Claude label every TAM assumption; investors discount a market number the moment they smell a top-down guess.

Quarterly Strategy Review Snapshot

30/30

You are a strategy operator who runs a sharp quarterly review. <context> I want a quarterly strategy review snapshot that scores progress and re-prioritizes, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Strategic priorities this quarter: [LIST] - Target vs. actual per priority: [NUMBERS] - What changed in the market: [SHIFTS] - New risks or opportunities that emerged: [DETAIL] - Resources for next quarter: [CAPACITY] </inputs> <task> Build a review snapshot: a status board scoring each priority (on-track green / at-risk amber / off-track red) with target-vs-actual, a short "what we learned" panel, a mini refreshed SWOT capturing what changed, and a re-prioritized list for next quarter. End with the one priority to drop and the one to add, with reasoning. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Status colors must match the target-vs-actual data; be honest about misses. - Next-quarter list must reflect capacity, not wishful overload. </constraints> <format> Return the full HTML as an artifact, then name the assumption from last quarter that turned out wrong. </format>

Builds a quarterly strategy review snapshot with status scoring and re-prioritization as a previewable artifact.

๐Ÿ’ก

Pro tip: Be honest in the target-vs-actual inputs; a review that paints everything green teaches the team nothing.

Frequently Asked Questions

Use a prompt that gives Claude a clear role (strategy consultant), your real business context as bracketed inputs, and asks for a color-coded 2x2 grid plus a strategy takeaway returned as a self-contained HTML artifact. The classic 2x2 SWOT prompt on this page does exactly that, so you get a previewable, paste-ready board instead of a wall of text.
Yes. Because Claude can return HTML/CSS as an artifact, these prompts ask for a rendered, color-coded grid, matrix, or diagram you can preview instantly and drop into a deck. You get a filled-in SWOT, TOWS, PESTLE, Porter's Five Forces, or BCG matrix as a real visual, not a bulleted list.
Replace every [BRACKETED PLACEHOLDER] with real facts: actual metrics, competitor names, recent moves, and constraints. The more concrete your inputs, the less Claude has to guess, and the prompts deliberately ask it to flag which points are inferred versus confirmed so you know what to verify.
Use SWOT for a quick internal-and-external snapshot, TOWS to turn that SWOT into action, PESTLE or Porter's Five Forces to analyze the external environment, BCG to manage a product portfolio, VRIO or value-chain analysis to test internal advantage, and a risk or decision matrix to choose between options. This page has a prompt for each.
No. Claude writes the HTML and CSS for you and renders it as a previewable artifact. You just paste a prompt, fill in your inputs, and copy the finished framework. If you want it in a slide, screenshot the artifact or copy the underlying HTML.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.