Resources & Tools

Built for analysts.
Not for everyone.

Tools I am building, resources I actually use, and prompts that work for real BA tasks.

Tools

Things I am building.

🔄

BA Translator — Beta

Translates vague stakeholder language into structured user stories, acceptance criteria, and spec-ready requirements. Paste messy notes — get something a developer can work with.

📋

Spec Template Library — In Development

A curated library of functional specification templates — from API integrations to feature specs and gap analyses. Built for fintech and investment platforms.

🎓

AI for Business Analysts Workshop — Coming Soon

A practical, hands-on workshop on applying AI to real BA workflows. Requirements gathering, spec writing, vendor management, JIRA — with workflows you can use the next day.

Resources I actually use

Have something to add?
Tell me.

If you use a tool or resource that should be on this list — or want to collaborate on content — reach out.

Get in touch →See my tools
Prompt Library

Prompts for real BA work.

Structured prompts built around specific analysis tasks — with context for how and when to use them.

Gap Analysis
Find gaps between requirements and current state
Review the following requirements document and current system description. Identify all gaps — missing functionality, unclear requirements, and potential compliance issues. For each gap found, state: 1. What is missing or unclear 2. Why it matters (business or regulatory risk) 3. A suggested resolution or decision needed Group results by severity: Critical / Important / Minor. [PASTE REQUIREMENTS DOCUMENT] [PASTE CURRENT SYSTEM DESCRIPTION]
User Stories
Convert stakeholder notes into structured user stories
Based on the following stakeholder interview notes, write structured user stories. Format each story as: As a [specific role], I want [specific feature or capability], so that [clear business value]. Requirements: - Focus on the "what", not the "how" (solution-agnostic) - Include 3–5 acceptance criteria per story - Flag any ambiguous requirements that need clarification - Note dependencies between stories if present [PASTE STAKEHOLDER NOTES]
Spec Review
Review a specification as a developer who will implement it
Review the following functional specification as a senior developer preparing to implement it. Identify and list: 1. Field names or values that are ambiguous or undefined 2. Missing error states, edge cases, or boundary conditions 3. Business rules that are unclear or contradictory 4. Dependencies or prerequisites that are not flagged 5. Any requirement where "done" is not measurable For each issue: quote the exact text, explain the problem, and suggest what clarification is needed. [PASTE FUNCTIONAL SPECIFICATION]
Vendor Management
Analyse a vendor response for vague commitments
I received the following response from a vendor. Analyse it for: 1. Vague commitments — statements that are not measurable or time-bound 2. Scope deflection — implied suggestions that requirements were out of scope 3. Unanswered questions — explicit questions that were not addressed 4. Risk signals — anything that suggests delivery problems ahead For each issue found, quote the exact vendor text and suggest how I should respond. [PASTE VENDOR MESSAGE] [PASTE MY ORIGINAL MESSAGE IF RELEVANT]
Edge Cases
Find missing edge cases in a user story
Review the following user story and its acceptance criteria. Identify all edge cases, error scenarios, and boundary conditions that are not currently covered. For each uncovered scenario: - Describe what happens (or could happen) - Explain the business or technical risk if unhandled - Write a specific acceptance criterion that addresses it Also flag any acceptance criteria that are currently too vague to test. [PASTE USER STORY + ACCEPTANCE CRITERIA]