Analyst structures the full BA lifecycle — discovery, requirements, stories, UAT, and retained artifacts — in one defensible workspace.
Built for evidence-heavy BA work
A different kind of BA tool. Purpose-built for the work that produces, signs, and retains structured evidence — so the record holds up long after the project closes.
Lifecycle first
Six phases, one workspace. Each layer feeds the one above it.
Traceability built in
Every requirement links to elicitation, stories, UAT, and retained artifacts.
Evidence that holds
Artifacts are versioned, signed, and locked. The record outlives the project.
Analyst is purpose-built for business analysts who produce and defend structured evidence. When a stakeholder asks for the record, you point at a complete, signed, versioned artifact — here is the evidence, and here is who approved it.
1.0 Workspace →Compliance needs an export filtered by date range — comes up every quarter before audit.
Got it. What priority and which project?
High. ACME CRM. Audit starts Q3, about 6 weeks out.
@Analyst log as REQ-042, priority High, ACME CRM
Ask Analyst runs in four modes: Coach, Builder, Auditor, and Explainer. It drafts BRDs, SOPs, and playbooks on request — but nothing changes without your explicit review and sign-off. AI is a proposer, not an author.
2.0 AI →Every requirement links to elicitation, stories, UAT cases, and retained artifacts. Traceability isn’t a report you generate — it’s built into the workspace from day one. The gap queue watches continuously; blockers surface the moment they form.
3.0 Traceability →Manual handoffs create delays, duplicated work, and...
source baseline captured
No artifacts yet
Create upstream evidence first
Handoff from intake to review
as-is · handoff · 0 requirements
Exception review loop
as-is · exception · 1 requirements
Auto-triage request
to-be · control · 0 requirements
Route low-risk requests through auto-review
1 process links · 1 stories · validatio...
Manual exception review remains for flagged requests
0 process links · 0 stories · validatio...
As an intake analyst, I can auto-triage low-risk requests
0 AC · validation missing
No artifacts yet
Create upstream evidence first
No artifacts yet
Create upstream evidence first
Manual exception review remains for flagged requests
Handoff from intake to review
Auto-triage request
Analyst generates BRDs, SOPs, and Playbooks from your approved requirements and process artifacts. Review the draft, accept it, and it copies to the Library as locked evidence — source snapshots sealed, version history preserved.
4.0 Knowledge →AI is a proposer, not a writer. Accepted drafts copy into Library as official evidence; source snapshots stay locked.
Generation cancelled
BRD (generation failed)
Business Requirements Document: Vertex Logistics Freight Portal
BA Engagement Playbook: Carrier Onboarding & Integration Initiative
Vertex Logistics SOP — Freight Exception Handling Procedure
Accepted artifacts and locked evidence packs, indexed by project ID and retention policy.
Business Requirements Document: Vertex Logistics — Freight Visibility Platform
accepted by Jordan Mercer
signature pending
BA Engagement Playbook: Carrier Onboarding & Integration Initiative
accepted by Jordan Mercer
signature pending
Vertex Logistics SOP — Freight Exception Handling Standard Operating Procedure
accepted by Jordan Mercer
signature pending
Send tokenized sign-off requests directly from any requirement or artifact. Stakeholders approve without creating an account.
MAY 21, 2026Auditor mode scans your workspace for traceability gaps and drafts a plain-language risk summary before the audit arrives.
MAY 13, 2026Export a requirement plus all linked artifacts, UAT results, and signatures in a single defensible download.
APR 30, 2026Improved BRD drafts with structured source snapshots, version history, and full inline edit before Library acceptance.
APR 23, 2026“Illustrative pilot scenario: the evidence is already linked when the review starts, so the BA can explain the record instead of rebuilding it.”
Sample BA review
Representative workflow, not a customer claim
“Illustrative handoff: requirements, stories, UAT, and the BRD stay connected so sign-off has a clear evidence trail.”
Sample sign-off package
Representative workflow, not a customer claim
Analyst is being shaped for independent BAs, small teams, and evidence-heavy enterprise pilots. Customer proof will be published only after approval.
Example scenarios →