AI for business analysts
Ultramarine Work turns workshop notes into requirements with testable acceptance criteria, then drafts the source-to-target mappings and the UAT scripts that trace to those requirements. It works from the files in your project folder.
Returns-portal-FRD.docxExampleFunctional Requirements: Customer Returns Portal
FR-4.2 Return eligibility
FR-4.2.1 The portal shall let a signed-in customer start a return on any order line delivered within the last 30 days. Given a line delivered 29 days ago, when the customer selects Start return, then the portal shows the reason list. Given a line delivered 31 days ago, when the customer selects it, then the portal shows the returns policy and no Start return button.
FR-4.3 Refund method
FR-4.3.1 The portal shall refund to the original payment method, except that gift card amounts return as store credit. Given an order paid half by card and half by gift card, when the return is approved, then the refund splits in the same proportion. Open question OQ-7 asks whether shipping is refunded on a partial return.
CheckedThe split-tender rule in FR-4.3.1 is not in the workshop notes, so Finance must confirm it.
How it works
- 1
Load the project folder
Drop in the workshop notes, the data dictionaries and field exports, the current FRD, the mapping workbook you inherited, the exported process maps, the UAT scripts from the last release and the open defect log.
- 2
Name the next deliverable
Ask it to draft the requirement rows, the mapping rows or the test scripts. Each row and script cites the file and line it came from, and anything it could not find is flagged as an open question.
- 3
Verify in the configured system, then decide
Read each requirement against what was actually configured, and confirm it with the stakeholder who asked for it. Nothing goes into Jira, the ERP configuration or the cutover runbook until you approve it, and you own the baseline.
Ask it for
“Turn the workshop notes into an FRD for the customer returns portal, numbered requirements with Given, When, Then acceptance criteria.”
Returns-portal-FRD.docx“Map the 22 customer master fields from the Oracle export to the Salesforce Account object, and flag every row that still needs a business decision.”
Customer-master-S2T-mapping.xlsx“Reconcile the loaded customer balances to the legacy trial balance extract and list every account whose balance differs by more than $1.”
Customer-balances-reconciliation.xlsx“Draft the interface spec for the nightly vendor file into the ERP, with source and target fields, transformation rules and error handling for rejected rows.”
Vendor-file-interface-spec.docx“Write UAT scripts for the new dunning process, one per scenario at each level, with exact test data, expected results and the requirement ID each traces to.”
UAT-scripts-dunning.xlsx“Check the requirements traceability matrix against the UAT scripts, and mark requirements with no test case and IDs that were renumbered mid-project.”
RTM-coverage-gaps.xlsx
Inside the Business & Systems Analysis mode
Data migration and interface mapping
Each field gets a target and transformation rule, each interface a method, frequency and error handling, and the reconciliation supports the go/no-go call.
Technical requirements and specifications
Requirements come out numbered, each with acceptance criteria a test can pass or fail and a trace to the script that tests it.
- Office skills
- Excel, Word, PowerPoint, PDF
- Tools
- Read, edit and write files, Search files, Run code, Search and read the web, View images
- Connectors
- SharePoint, Google Drive, Gmail, and additional custom connectors
- House style
- Your fonts, layouts and rules, on every file
Who it’s for
Business analysts, business systems and ERP, CRM or HCM functional analysts, and the QA analysts and test leads who verify system changes.
Questions
Will it invent requirements, acceptance criteria or test cases?
It can, so the skills tell it to cite the source file for the numbers and statements it uses, and to note what it could not find or reconcile instead of guessing. Whatever it cannot trace comes back as an open question, and you reject any test step that names a field or an error message the story never mentioned.
Does it check the requirements traceability matrix?
It does, and the gaps it finds are the usual ones: requirements with no test case, tests with no requirement, IDs that were renamed along the way. The cross-check runs the matrix against the stories, specs and UAT scripts in the folder, and you judge whether each gap matters before the baseline goes back to the sponsor.
Can it validate the migration before go/no-go?
Yes, it builds the reconciliation from the exports in the folder, with row counts, control totals on balances, column profiles and the stratified sample you name. The tolerances are the ones you set. It cannot query the ERP or CRM, so every figure depends on the extracts you provide, and the go or no-go decision stays with you.
Is it safe to put our requirements and ERP data into an AI tool?
Ultramarine Work changes files only in the project’s folder. When a request needs it, it can read files elsewhere on your computer, never passwords, keys or app data, and you can turn that off in settings. The model runs on Paper Instruments’ servers, so the content it works on is sent there to be processed. Paper Instruments is SOC 2 Type II, and our security and compliance details are on our compliance page.
Who decides what the requirements say?
You and your stakeholders make that call. Ultramarine Work drafts and checks, but the approved baseline, the priority calls and the question of whose requirement loses are yours. A requirement the business never asked for is scope you will have to defend later, so every line needs a source.