15 AI Prompts for Executives You Can Copy and Paste Today

Most "AI prompts" lists hand you one-liners that produce generic output. These are different. Each prompt below is built the way an executive would brief a sharp analyst: a defined role, real context slots, a precise task, hard constraints, and a fixed output shape. That structure is the whole difference between a paragraph you have to rewrite and a draft you can send with light edits. If you want the reasoning behind the design, our guide to prompt engineering breaks it down.

How to use these: copy the prompt, replace anything in [BRACKETS] with your specifics, and paste it into your AI tool of choice. Each one includes a short note on why it works and which variables to swap. Use an enterprise-tier tool with proper data terms before you paste in anything sensitive.

Strategy

1. The Strategic Options Generator

You are a seasoned strategy advisor who has sat in the room for hundreds of executive
decisions. Context: [company: stage, industry, revenue, key constraint]. The decision
on the table is [decision]. Task: generate three genuinely distinct strategic options,
not three flavors of the same one. For each, give the core bet, the two strongest
arguments for it, the two biggest risks, and the type of company it best fits.
Constraints: no hedging, no "it depends," rank the options at the end with a one-line
reason. Format: one short paragraph of framing, then the three options as labeled
blocks, then your ranked recommendation.

Why it works: it forces genuine divergence ("distinct, not three flavors of the same one") and ends with a committed recommendation, which is where most AI strategy output goes soft.

Swap your variables: [company profile], [decision]. To bias toward speed over thoroughness, add "keep each option under 100 words."

2. The Pre-Mortem

You are a skeptical operator known for spotting how plans fail. Context: [company],
and we are about to [decision or launch]. Task: assume it is twelve months later and
this has failed badly. Write the post-mortem. Identify the three most likely causes of
failure, ranked, and for each name the earliest warning signal we could watch for now.
Constraints: be specific to our situation, not generic. No reassurance. Format: a
ranked list of three failure modes, each with cause, warning signal, and one
preventive move.

Why it works: pre-mortems surface risks that optimistic planning hides, and forcing an "earliest warning signal" turns vague worry into something you can actually monitor.

Swap your variables: [company], [decision or launch]. Change the horizon from twelve months to fit your planning window.

3. The Competitor Teardown

You are a competitive analyst briefing a busy CEO. Context: our company is [profile];
the competitor is [competitor] and they just [move]. Task: explain what this move
likely signals about their strategy, who it threatens, and the two most sensible
responses available to us. Constraints: distinguish clearly between what is known and
what you are inferring. No speculation dressed as fact. Format: TL;DR in three bullets,
then Signal, Threat, and Our Options as short sections.

Why it works: the "known versus inferred" constraint keeps the analysis honest, which is exactly what you need before you react to a competitor.

Swap your variables: [profile], [competitor], [move].

Board

4. The Board Update Drafter

You are a chief of staff who writes crisp board memos. Context: [company, stage, key
metrics this period]. Here are my raw notes: [paste notes]. Task: draft the board
update. Cover performance versus plan, the three biggest wins, the two biggest emerging
risks, and one specific ask of the board. Constraints: use only the numbers I provide,
flag anything you would want confirmed, no marketing tone, under 400 words. Format: a
one-paragraph opening, then labeled sections, then the ask in bold.

Why it works: it turns scattered notes into board-ready structure while the "use only the numbers I provide" constraint prevents invented figures, the fastest way to lose board trust.

Swap your variables: [metrics], [paste notes]. Match your board's format by adding "mirror the structure of this prior update: [paste]."

5. The Tough-Question Rehearsal

You are the toughest, most financially literate member of my board. Context: [company
and the update I am about to present, pasted below]. Task: ask me the eight hardest
questions you would ask in the meeting, in the order most likely to come up. Then, for
each, give a one-line note on what a strong answer must address. Constraints: go after
the weak spots in the numbers and the story, not softballs. Format: numbered questions,
each with a short "a strong answer covers" note.

Why it works: rehearsing against a hostile-but-fair board member is the cheapest way to walk in prepared, and asking for the "order most likely to come up" mirrors the real room.

Swap your variables: paste the actual update or narrative you plan to present.

Hiring

6. The Role Scorecard Builder

You are an experienced executive recruiter. Context: we are hiring a [role] at
[company profile] to own [core outcome]. Task: build a hiring scorecard. Define the
mission of the role in one sentence, the four to six outcomes the person must deliver
in the first year, and the specific competencies each outcome requires. Constraints:
outcomes must be measurable, not vague traits. No generic "team player" language.
Format: Mission, Outcomes (numbered, each measurable), Competencies mapped to
outcomes.

Why it works: scorecards built on measurable outcomes make interviews and later performance reviews objective, instead of a referendum on likeability.

Swap your variables: [role], [company profile], [core outcome].

7. The Reference-Check Question Set

You are a hiring advisor who has caught bad hires at the reference stage. Context: the
role is [role] and the candidate's stated strength is [strength], stated weakness is
[weakness]. Task: write ten reference-check questions designed to verify the strength,
probe the weakness, and surface anything the candidate may have smoothed over.
Constraints: open-ended questions only, no yes/no, and include two that ask the
reference to compare the candidate to others they have managed. Format: a numbered
list grouped under Verify, Probe, and Compare.

Why it works: open-ended, comparative questions get references to reveal more than the polite defaults, which is where the real signal lives.

Swap your variables: [role], [strength], [weakness].

Email

8. The Difficult Email Rewriter

You are a calm, senior communicator. Context: I need to send a sensitive email.
Situation: [what happened, who the reader is, what I need from them, and the
relationship stakes]. Here is my rough draft: [paste]. Task: rewrite it to be direct
and warm without groveling. Constraints: under [150] words, a single measured line of
acknowledgment at most, active voice, close with a clear next step. Format: subject
line plus body.

Why it works: it fixes the two failure modes of hard emails at once, over-apologizing and burying the ask, while keeping your intent intact.

Swap your variables: [situation], [paste draft], word limit.

9. The Inbox-to-Actions Triage

You are my executive assistant. Context: below is a long email thread I have not fully
read: [paste thread]. Task: tell me what actually happened, what decision is being
asked of me, the options on the table, and what you would recommend and why.
Constraints: separate facts from opinions in the thread, flag anything time-sensitive,
under 200 words. Format: What happened, The decision, Options, Recommendation.

Why it works: it converts a noisy thread into a single decision with a recommendation, so you engage the substance instead of re-reading forty messages.

Swap your variables: [paste thread].

10. The Warm Follow-Up

You are a relationship-driven operator. Context: I met [person, role, company] at
[context] and want to follow up to [goal]. What I remember about the conversation:
[details]. Task: draft a short follow-up that references something specific we
discussed, offers something useful before asking for anything, and makes the next step
easy to say yes to. Constraints: no flattery, under 120 words, one clear call to
action. Format: subject line plus body.

Why it works: the "offer something useful before asking" instruction produces follow-ups that get replies, because they lead with value rather than a request.

Swap your variables: [person], [context], [goal], [details].

Analysis

11. The Document Interrogator

You are a meticulous analyst reviewing a document for an executive. Context: this is a
[contract / report / proposal] and my main concern is [concern]. Document: [paste].
Task: identify the five most important things I should know, the three biggest risks or
unfavorable terms, and any assumption the document depends on that may not hold.
Constraints: quote the relevant line for each point, do not soften unfavorable terms,
flag anything ambiguous. Format: Key points, Risks, Load-bearing assumptions.

Why it works: forcing a quoted line for each point keeps the model anchored to the actual document instead of paraphrasing it into something friendlier.

Swap your variables: [document type], [concern], [paste].

12. The Numbers Sanity-Check

You are a skeptical CFO reviewing a model. Context: here are the assumptions and
outputs: [paste]. Task: pressure-test it. Identify the two or three assumptions the
result is most sensitive to, point out anything that looks internally inconsistent, and
name the one assumption that, if wrong, breaks the conclusion. Constraints: do not
invent numbers, use only what I provide, show your reasoning briefly. Format: Most
sensitive assumptions, Inconsistencies, The single biggest risk to the conclusion.

Why it works: it finds the load-bearing assumption in a model, which is the number worth arguing about before you present it.

Swap your variables: [paste assumptions and outputs].

13. The One-Page Synthesis

You are an editor who compresses without losing substance. Context: below is a long
[report / deck / research doc]: [paste]. Task: compress it to a one-page synthesis for
a busy executive. Constraints: keep every load-bearing fact, drop the filler, no new
information, plain language. Format: a three-bullet TL;DR, a short So What, and the
three decisions or actions this document implies.

Why it works: the "So What" and "decisions implied" sections force the summary to answer the executive's real question, which is not what the document says but what to do about it.

Swap your variables: [paste document].

Meetings

14. The Meeting-to-Memo

You are a chief of staff. Context: here are my raw notes from a meeting: [paste]. Task:
turn them into a clean decision memo. Capture the decisions made, the open questions,
the action items with an owner and a date each, and a one-line summary at the top.
Constraints: if an owner or date is missing, mark it as TBD rather than guessing,
separate decisions from discussion. Format: Summary, Decisions, Open questions, Action
items table.

Why it works: it produces the artifact people actually use after a meeting, and the "mark TBD rather than guess" rule stops the model from inventing commitments no one made.

Swap your variables: [paste notes].

15. The Agenda Architect

You are a facilitator who runs tight meetings. Context: the meeting is [purpose], with
[who is attending], and we have [duration]. The outcomes I need are [outcomes]. Task:
build an agenda that reaches those outcomes. For each item give an objective, a time
box, and the decision or output it should produce. Constraints: total time must fit the
duration, put the highest-stakes item early, no open-ended "discussion" blocks without
a target. Format: a time-boxed agenda with an objective and expected output per item.

Why it works: tying every agenda item to a required output and a time box is what separates a meeting that decides things from one that just talks.

Swap your variables: [purpose], [attendees], [duration], [outcomes].