Requirements that survive contact with code.
Business analysts who use AI to turn interviews, documents and legacy systems into specs your team can build from.
- inputingest workshop_recording_03-10.m4a (47 min) + 6 docs
- aitranscribe, tag 5 speakers
- aiextract 23 candidate requirements
- flagconflict: REQ-07 approval limit vs REQ-15 auto-approve
- humananalyst review: 19 accepted, 4 sent back to client
- aidraft 31 user stories with acceptance criteria
- humanwalkthrough with product owner, 3 edits
- doneexport to Jira, BPMN to-be diagram attached
Illustrative session. Figures vary per project.
What we analyse
Analysts lead every engagement. AI does the reading, transcribing and first drafts so people can spend their time on judgment.
Discovery workshops
Structured sessions with your stakeholders, recorded and turned into a shared problem statement within days.
Requirements and user stories
BRD, SRS or backlog-ready stories with acceptance criteria your developers and testers can both use.
Process mapping
As-is and to-be flows in BPMN, with the handoffs, approvals and exceptions people forget to mention.
Legacy system analysis
Business rules recovered from old code, databases and spreadsheets before you rebuild or migrate.
Data and reporting needs
Which numbers matter, where they come from and how often they must be right.
AI use-case assessment
Where AI genuinely saves effort in your operations, where it does not, and what it would cost to try.
How an engagement runs
- 01
Scope
One call to agree the question, the people involved and the deliverable.
- 02
Gather
Interviews, documents and system access. AI transcribes and indexes everything.
- 03
Analyse
Analysts model processes and rules, AI drafts and cross-checks for gaps.
- 04
Validate
Walkthroughs with your team until the spec matches how work really happens.
Who does what
| AI handles | People decide |
|---|---|
| Transcribing and summarising interviews | Deciding which voice wins when stakeholders disagree |
| Finding contradictions across 200 pages | Judging which contradiction actually matters |
| Drafting stories and acceptance criteria | Signing off scope with you |
| Searching legacy code for business rules | Confirming the rule is still how the business works |
Ways to work with us
2 weeks
Discovery sprint
A focused look at one process or product idea, ending in a scoped spec and estimate.
Ask about a discovery sprintFixed scope
Project analysis
Full requirements for a build or migration, handed over to your developers or ours.
Monthly
Embedded analyst
An analyst inside your team, working your backlog sprint by sprint.
Tell us what you are trying to build.
A few lines about the project and your timeline are enough to start the conversation.
Email baservice@baservice.io.vn