AI Prompts for Business Analysts: 10 Ready to Copy

These AI prompts for business analysts help with the parts of the job that eat the most time: preparing stakeholder interviews, turning workshop notes into process maps, finding gaps, and writing requirements and user stories that teams can test. Paste a prompt into ChatGPT, Claude, or Gemini, fill in the [brackets] with your project's notes, and review the result before it goes to stakeholders.

Ground rules for BA work with AI

Paste the actual notes, not a summary of them. Ask the model to label what stakeholders said versus what it infers, and tell it never to invent volumes, durations, or savings. Remove confidential data your company does not allow in AI tools.

Where AI helps a business analyst most

AI is most useful for structure: sorting notes, drafting tables, spotting gaps between what people said and what the target state needs, and rewriting vague requirements into testable ones. It is least useful for judgment calls about priorities and politics, which still need you and your stakeholders. Use these prompts to get to a solid first draft faster, then validate it in the room.

Prompts for elicitation

1. Stakeholder interview guide

I am interviewing [role] about [process]. The project goal is [goal]. Write 12 open questions in the order I should ask them, starting broad and ending with pain points and workarounds. Add one follow up for each.

2. Workshop notes cleanup

Here are raw notes from a requirements workshop: [paste notes]. Organize them into decisions, requirements mentioned, open questions, and parking lot items. Quote the note behind each item.

3. Stakeholder map

For a project to [goal], these people are involved: [names and roles]. Build a stakeholder map with interest, influence, what each cares about, and how often to update them.

Prompts for process analysis

4. As-is process table

Turn this process description [paste] into a step table with step number, actor, action, system, handoff, and a flag for any manual workaround.

5. Root cause check

These are the pain points users reported: [list]. For each, name the process step where it starts and the likely cause type: process, people, technology, data, or policy. Mark each as stated or as your hypothesis.

6. Gap analysis table

Compare this as-is process [paste] with this target state [paste]. Produce a gap table with as-is, to-be, gap, gap type, and the change needed to close each gap.

Prompts for requirements

7. Requirements from gaps

From this gap table [paste], write numbered business, functional, and non-functional requirements. Use "The system shall" for functional ones and trace each to a gap row.

8. User stories with acceptance criteria

Write user stories for these requirements [paste] in the form "As a [role], I want [goal] so that [benefit]", each with Given, When, Then acceptance criteria and one edge case.

9. Requirements quality review

Review these requirements [paste] for ambiguity, missing actors, untestable words like "fast" or "easy", and duplicates. Suggest a rewrite for each problem.

Prompts for communication

10. Sponsor summary

Summarize this analysis [paste] for [sponsor role] in under 200 words: the problem, the recommended change, what it needs from them, and the open decisions with dates.

Run a complete gap analysis

To go from workshop notes to a full package in one pass, use the AI Prompt for Business Analysts: As-Is To-Be Gap Analysis. It builds the scope, as-is steps, root causes, to-be process, gap table, traced requirements, user stories, a RACI, and success measures that only use baselines you supplied. The example on the prompt page works through a vendor invoice approval process at a food distributor.

Related prompts

When you need to turn requirements into a product document, the Product Requirements Document (PRD) Writer picks up where the gap analysis ends. Find more in the Business prompts hub, browse more prompts, or share a prompt from your own BA toolkit.