Early access · by invitation

AIBA.pro

AI business analyst for process guides, maps and SOPs.

ACME Stores · Sales order guide (made-up example)AI on
G
BranchFrom the sales order · Store Code
Which rule fills the Branch column?
From the branch list, by the Branch Code.
✓ ACME kickoff notes.txt · line 2
Add as a dated correction?
Add correction
Your BA team

Eight senior BA roles on every process

Each role owns one part of the work and shows what it delivered, what is open and what it needs from you. A daily stand-up shows every role across all your processes.

Seat A1Demo · made-up company

Lead BA

Runs the engagement: answers your brief, checks that the other seven roles agree, and turns every conflict into an open question.

ACME · Remittance adviceBrief answered; the team's outputs agree, 1 conflict raised as an open question.

Close
Seat A2Demo · made-up company

Process BA

Turns the approved process guide into the process map, the PDD and the SOP.

ACME · Remittance adviceProcess map drafted from the approved guide; PDD and SOP in ACME's template.

Close
Seat A3Demo · made-up company

Requirements BA

Reads the discovery calls and writes down the AS-IS steps, pain points, decisions and open questions.

ACME · Remittance adviceDiscovery pack from the kickoff call: 3 pain points, 2 decisions, 1 open question.

Close
Seat A4Demo · made-up company

Data BA

Documents every field, where it comes from and where it goes, and checks the data for quality problems.

ACME · Remittance adviceData dictionary and source-to-target mapping; 2 data quality findings.

Close
Seat A5Demo · made-up company

Quality BA

Writes the UAT cases and checks the developer's output against the approved rules.

ACME · Remittance advice18 UAT cases; developer output checked: 1 difference, tied to its guide rule.

Close
Seat A6Demo · made-up company

Process Improvement BA

Looks for waste, bottlenecks and quick wins, and states the payback for the SME to confirm.

ACME · Remittance adviceCopy-paste into the sheet takes 2 hours a day: quick win, payback to confirm with the SME.

Close
Seat A7Demo · made-up company

Agile BA

Turns the approved process into user stories with acceptance criteria, ready for your backlog.

ACME · Remittance advice12 user stories with acceptance criteria, 2 not ready.

Close
Seat A8Demo · made-up company

Comms BA

Drafts the e-mails: open questions per person, change notices and meeting confirmations.

ACME · Remittance adviceOpen-question e-mail to Ben, meeting confirmation drafted.

Close
Seat B1 · Wing B, Finance & Accounting

Planned seat: Bookkeeper. Not built yet.

Close
Seat B2 · Wing B, Finance & Accounting

Planned seat: AP and AR. Not built yet.

Close
Seat B3 · Wing B, Finance & Accounting

Planned seat: Bank Reconciliation. Not built yet.

Close
Seat B4 · Wing B, Finance & Accounting

Planned seat: Month-end Close. Not built yet.

Close
Seat C1 · Wing C, Payroll

Planned seat: Timekeeping. Not built yet.

Close
Seat C2 · Wing C, Payroll

Planned seat: Payroll Checker. Not built yet.

Close
Seat C3 · Wing C, Payroll

Planned seat: Statutory & Compliance. Not built yet.

Close
Seat C4 · Wing C, Payroll

Planned seat: Payslip Release. Not built yet.

Close
Seat D1 · Wing D, Marketing

Planned seat: Content Writer. Not built yet.

Close
Seat D2 · Wing D, Marketing

Planned seat: Social Media. Not built yet.

Close
Seat D3 · Wing D, Marketing

Planned seat: Campaigns. Not built yet.

Close
Seat D4 · Wing D, Marketing

Planned seat: Analytics. Not built yet.

Close
Seat E1 · Wing E, Customer Service

Planned seat: Inbox Triage. Not built yet.

Close
Seat E2 · Wing E, Customer Service

Planned seat: Reply Drafting. Not built yet.

Close
Seat E3 · Wing E, Customer Service

Planned seat: Escalations. Not built yet.

Close
Seat E4 · Wing E, Customer Service

Planned seat: Service Quality. Not built yet.

Close

Scroll or pinch to look around

Wing A holds the eight BA roles that work on every process; select a desk to see what each one does, with an example from the made-up ACME demo. The finance and accounting, payroll, marketing and customer service wings are planned and not built yet.

How it works

Four steps

Give it the files

A finished guide to copy, the files to fill, the input samples, and the AI summary or transcript of the discovery meeting.

It drafts each rule

Rule by rule, in the base guide's own wording. Every rule quotes the cell or line it rests on, and code checks that the quote is really there.

You correct it

Paste the learnings from each meeting, or say it in the chat. Each becomes a dated instruction, and the newest correction wins.

Only the changes move

When a correction comes in, AIBA updates the rules it touches and leaves every approved rule as it was.

What you get

Twelve outputs from one process

Process guides

One rule per column, each with its source

Process map

BPMN, plus a picture for slides

PDD and SOP

In your client's own Word template when there is one

Discovery pack

From a call transcript: AS-IS steps, pain points, numbers, open questions

Gap analysis

Today's practice against the approved process, line by line

Developer output check

Every difference tied to the rule it breaks, UAT pass or fail

Data dictionary

Every field, its source and format

Metrics and baseline

Defined on real fields, measured from your data; targets stay yours

Agile backlog

Stories with Given/When/Then, ready for Jira or Azure Boards

Lean toolkit

SIPOC, FMEA, waste and bottleneck candidates to verify

Exceptions, RACI, UAT

What can go wrong, who owns each step, and the tests

E-mail drafts

Open questions per person, change notices, meeting confirmations

Safeguards

Six rules it keeps

Your files stay in our project

AI steps run on Google's Vertex AI in our own cloud project, with caching off. Usage limits apply, and the AI only does BA work.

No quote, no claim

An answer without a source found at its place is shown as unconfirmed, and an unsourced rule becomes an open question.

Each person sees their own

An account opens only the processes it was given. Any other process looks like it doesn't exist.

BA work only

Anything that isn't business-analysis work on a process is refused, and the person is signed out.

Lessons, not data

What one process teaches goes into a shared playbook only as a general technique, and only after the owner approves it.

Clean at the end

When an engagement ends, one step lists and removes every copy of that client's files.

Who it's for

Business analysts and shared-services teams

Built in shared-services work, where one account's process guide is copied for the next account, and every rule has to be traceable.

  • Business analystswho replicate one account's process guide for the next
  • Shared-services leadswho need one standard process with each customer's exceptions written beside it
  • SMEswho review a draft and want to see where every rule came from

Early access

By invitation. Tell us the process you need documented, and we'll set up a private workspace for it.

Request early access