For ERP consultants and business analysts
Agree the change before anyone builds it.
Start from the notes of a workshop, or from the screen the business wants changed. Walk out with the requirements board, the To-Be Process document and the functional specification already written.
No sign-up, nothing to install. Screen capture needs a desktop browser — Chrome, Edge or Firefox.
See it done, both ways.
Two minutes of the real product, nothing mocked up. First a workshop — meeting notes in, requirements board, To-Be Process document approved by the business, functional specification and unit test script out. Then the regular way in — an ERP screen captured, fields added, a BRD and a functional specification generated from it.
No narration — the captions call out each step. Real notes and a real extraction; only the waiting was cut.
Two ways in, one set of references.
However the requirement reaches you — as the notes of a workshop or as a screen someone wants changed — every document afterwards carries the same reference.
Workshop
From meeting notes to signed documents
Copilot or Teams notes, or a requirements document the business already wrote — either way you get a requirements board, one row per requirement, citing the lines it came from.
- Requirements Board in Excel
- To-Be Process document for the business to sign
- Functional specification
- Unit test script from the agreed criteria
Regular
From a screen to a BRD or a spec
Capture a screen from Oracle Fusion, SAP, ServiceNow or NetSuite, add, replace or cover up fields until it reads as the future state, and export the documents.
- The mockup on the real page, in the real style
- Business requirements in plain language
- Functional specification built from the mockup
- PowerPoint walkthrough of the screens
Why screenshots and Word documents go wrong
The screenshot in a slide was never the problem
The requirement travels as a screen grab pasted into Word, an arrow drawn on top, and a paragraph underneath. The developer builds what the document says. The business sees it in UAT and says that isn't what they meant.
Nobody was careless. They just never looked at the same screen.
Today
A screenshot with arrows over it. The same field list retyped into a BRD, then again into a spec. Two days of formatting. Sign-off on a description of the screen, not on the screen itself.
With ReqSnap
The change sits on the real page, at the real resolution, in the real style. The field tables, values and navigation are built from what you drew — nothing is retyped, so nothing drifts. Fix the mockup, re-export, and they correct themselves.
Three steps, about twenty minutes
You don't rebuild the screen in a design tool, and you don't retype the notes. You start from what you already have and change it.
Start from notes or a screen
Paste the notes of the workshop and get a referenced requirement per row — or grab any screen on your display, crop it, and blur anything sensitive.
Agree it before it is built
Check every row against the line it came from, put the To-Be Process document in front of the business, and record who signed it, in which version.
Export the documents
Requirements board, To-Be Process document, functional specification and the test script — all under the same references, all versioned.
The board is the input. The documents are the point.
A screenshot in a slide still leaves you writing the spec by hand. ReqSnap builds the field tables, values and navigation from what you captured, so none of it is retyped.
To-Be Process document
How the process will run, who performs each step, and the requirement-to-solution mapping — the document the business approves, with the approval printed on it.
Business requirements
What's needed and why, how the work runs today and afterwards, and what the business will see — in plain language, with no field types or system terms anywhere near it.
Functional specification
A section per requirement: field tables with type, required flag and permitted values, notifications, acceptance criteria and navigation — every line derived from the board rather than retyped.
- Excel The requirements board with the open questions and assumptions on their own sheets, and the unit test script with a row per acceptance criterion.
- PowerPoint One slide per screen, your notes attached, for the walkthrough.
- Word The screens with captions, for dropping into a document you already have.
- Optional AI draft — review before sharing It drafts how the process runs today, what changes, the business value, system impact and acceptance criteria — the sections a field list can't produce. It uses your own API key, and sends only the text you typed to Anthropic. Never the captured images.
See what comes out before you try it
Two documents produced by ReqSnap, unedited: a BRD for adding payment recipient and supplier notes to an invoice, and an eleven-page functional specification for a billing system evaluation — five screens, twenty new fields, with field tables, acceptance criteria and open questions. Nothing in them was written by hand afterwards.
Word format, so you can drop your own house styling straight onto them.
Your screens never leave your machine
Captured ERP screens carry supplier names, employee names and amounts. There is no account, no upload of your captures, and no server holding your work — they are stored in this browser and nowhere else. Blur anything sensitive and it's burned into the image before it's even stored.
That's also why there's nothing to get approved before you try it.
One thing does leave, and only if you ask it to: switch the AI draft on and the text you typed is sent to Anthropic to write those sections. Your captured screens are never sent, with it on or off. Leave it off and the documents are built entirely here.
Read the full privacy notice — what's stored, what the contact form collects, cookies and your rights.
Contact us
Tell us about your programme
Which ERP you're on, how your team writes its documents today, and what you'd want ReqSnap to produce. We read every one and reply personally.
Fill the form in and it comes straight to us — usually answered the same working day.
Try it on a requirement you're working on today
It opens in a browser tab. The first board takes about a minute.