How it works
From documents to confirmed requirements
Four steps, each one checked by the people who do the work.
- 1
Start from your documents
RFPs, process maps and policies give us a first model of the system. Anything taken from a document stays unverified until its owner confirms it.
- 2
Ask the right people
Each person gets a few questions about the part of the work they know best, once your sponsor has approved them.
- 3
Have a short conversation
Talk with an AI interviewer in the browser, or type. It repeats back what it heard and asks if it got it right.
- 4
Confirm in writing
Nothing counts until the person confirms it, and they choose who sees each statement.
The product
Something for everyone involved
Each person sees what they need, and nothing they don’t.
A few minutes, not a workshop
Each person answers a handful of questions about their own area, by voice or by typing, whenever it suits them. Afterwards everything comes back in writing. They fix anything we got wrong and decide whether it carries their name.
- Questions sized to their role
- Say “hold on” any time; it waits
- Edit any statement in their own words
One honest picture of progress
A single number for how much of the system is defined well enough to build, broken down by business unit. Below it: what is holding the design up, and who owns each item. Nobody is contacted until the sponsor approves them.
- Coverage by business unit and design area
- Blockers with an owner and a day count
- Approves every suggested person
Requirements with a paper trail
Every requirement links to the person who said it and their exact words, checked against the transcript. When two people disagree, the disagreement becomes a decision to make, with the evidence for each side, before design starts.
- Traced to a person and a quote
- Conflicts surfaced as decisions
- Gaps found before build, not during
Trust
Built for the people answering
Requirements are only as good as the trust behind them.
No one is contacted without approval
Your sponsor approves the roster. Suggestions from interviews wait for their sign-off.
Quotes are checked
Each requirement keeps the exact words it came from, and is flagged if they can’t be found in the transcript.
People control attribution
Named, unnamed, or sponsor-only, chosen per statement by the person who said it.
Quiet hours are respected
No texts or calls outside the hours each person sets.
Planning a Salesforce project?
Tell us about it. We’ll show you how Discovery and rapid prototyping get you from requirements to working software with fewer surprises.
Get in Touch