Business Analyst · free plan
An AI business analyst who elicits requirements live
A transcript of a requirements workshop is not a requirements document. The Business Analyst persona works the room while the conversation is still live: pinning the problem before anyone jumps to a solution, asking what done looks like, chasing acceptance criteria and MoSCoW priority, and making the group separate a must from a nice-to-have. You leave with a BRD-lite and user stories instead of forty minutes of audio to re-listen to.
What she does in the room
Your one job is to collect business requirements from the people in this meeting and record them. That is the whole role.
Once oriented, probe for problem framing, MoSCoW priority, acceptance criteria, actor and outcome, and what done looks like. Prefer current-vs-future process questions and short 'why does that matter' clarifications. Do not solution or design.
The questions she actually asks
She opens by working out what the session is for, then presses on whatever is vague or unowned. These are her real prompts, not paraphrases:
- “What is this session about — what problem brings everyone here today?”
- “Who is affected by this, or who are the key stakeholders?”
- “What would a good outcome of this meeting look like?”
- “What does done look like for that?”
- “Who is the actor, and what outcome do they need?”
- “Is that a must, should, or could?”
- “What acceptance criteria would prove it works?”
What she listens for
Across the meeting she is collecting the business problem, goals and success criteria, requirements (with acceptance criteria when stated), non-functional requirements, stakeholders, out-of-scope items, pain points with the current way of working, use cases, decisions, action items, and risks / dependencies / assumptions / constraints. She records only what participants actually said — when something is missing she asks rather than fills it in.
Captured as structured items
- Problem statement
- Goal
- Requirement
- Non-functional requirement
- Stakeholder
- Out of scope
- Pain point
- Use case
You walk out with
- BRD-lite
- User stories
- RAID / action log
Session presets
- Kickoff
- Backlog grooming
- Requirements workshop
Meetings people use this for
- Requirements workshops
- Discovery sessions
- Backlog grooming
- Project kickoffs
- Stakeholder interviews
Getting her in the call
Paste a Teams or Zoom join link, pick Business Analyst, and she dials in as a named participant — no tenant install and no admin consent. She introduces herself as Ava by default; you can rename her and change her voice per persona in settings.
Included on the free plan. The 60-minute trial needs no credit card.
Adjacent personas
Different meeting, different seat. These are the personas closest to this one:
- Requirements LeadA full elicitation session you want someone to run — problem, use cases, requirements, NFRs, risks, and recommendations.
- Product ManagerRoadmap and product discovery — outcomes, bets, and prioritization.
- UX ResearcherResearch and usability sessions — goals, quotes, jobs-to-be-done, and findings.