Early access · by invitation

AIBA.pro

AI business analyst for process guides, maps and SOPs.

ACME Stores · RA Output (made-up example)AI on
G
BranchFrom RA Output · Site/Location
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
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

Nine documents 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 own templates when you have them

Data dictionary

Every field, its source and format

Exception catalog

What can go wrong and who decides

RACI

Who does, owns and checks each step

UAT and traceability

Test cases tied back to each requirement

Walkthrough script

For the review meeting with the SME

Change report

What a reviewer changed, line by line

Safeguards

Six rules it keeps

Consent before AI

A client's files go to the AI only when that process is marked as agreed. Until then, only the build steps run.

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 on remittance, deduction and payment-advice work, where one account's guide is copied for the next account.

  • 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