Reqflow
Requirements you can stand behind.
Reqflow interviews your customer's people, records every requirement in their own words, and gives you a versioned document to attach to the SOW.
- Omar Haddad, Finance / Payroll Lead, has answered: “One change since the document was approved: from next quarter the payroll cutoff for adding a new hire to the current cycle moves from the Wednesday to the Monday before the cycle closes. Anyone entered after that Monday is paid retroactively in the next cycle.”
- The assistant asks: “Got it – the I‑9 completion triggers verification, payroll setup, badge issuance and start‑date alignment. Regarding the new payroll cutoff moving to Monday, which downstream activities or outcomes that currently rely on the Wednesday cutoff will be impacted?”
- Omar answers: “Bank details and tax forms have to be in the HRIS by that Monday too. Hiring managers often send them on the Tuesday, so I'd expect about one new hire in five to miss the cycle.”
- A disagreement is found: “the cutoff for adding a new hire to the current pay cycle is the Wednesday prior to the cycle’s close” against “moves from the Wednesday to the Monday”.
- The assistant asks: “Omar, you’ve noted two differing statements: 1) We can’t process a new hire in the current cycle if they’re added after the Wednesday cutoff (as mentioned by the finance team), and 2) the cutoff moves from Wednesday to Monday (as you’ve indicated). Which of these should be the official rule, or how should it be phrased?”
- Written down from the answer: Assumption, “One new hire in five miss the cycle”.
- Omar answers: “What I said later holds. From next quarter the cutoff is the Monday before the cycle closes.”
- The assistant asks: “Got it, Omar—the official rule will be that the payroll cutoff moves to the Monday before the cycle closes, and hires entered after that Monday will be paid in the next cycle. Does that capture the intended change?”
- The disagreement is settled.
- The admin issues StRS v2, hash f419d3e6.
The scope is decided before the work starts. So are the losses.
Presale analysis you are not paid for — and much of it goes to bids you lose.
With ReqflowThe assistant interviews your customer’s people instead of an analyst in meetings. Stop when you have enough to estimate.
Arguments about whether something was in scope.
With ReqflowA numbered, hashed version of the document to attach to the SOW, and every requirement shows who said it, in their own words.
Rework after a requirement was understood differently.
With ReqflowReqflow finds where people contradict each other and takes it to the person at your customer who decides.
Workshops you cannot get everyone to.
With ReqflowYour customer’s people answer by link, when it suits them, without an account.
From setup to a document your customer signs off
- Set up a project and invite your customer's people Pick the documents you need in plain words and add people by email. Invitations, reminders and progress stay in one place, so you know where the project stands without a status meeting.
Where the project stands: who has answered, how much is covered and what still waits for answers. Fictional example. - Your customer's people answer when it suits them — no accounts, no meetings They open a link, on a phone if they like, and pick up where they left off. They are asked only about what is still unknown.
The interview on a phone, from the link in the email, with no account. Fictional example. - Every requirement shows who said it — and disagreements reach whoever decides A traceability matrix links each requirement to the person and the quote it came from. When people disagree, Reqflow brings it to whoever owns that area at your customer.
A requirement with who said it, in their words, and the needs it answers. Fictional example. - A versioned document you can attach to the SOW Stakeholder, system and software requirements (StRS, SyRS, SRS) from day one, with gaps marked in the text. Each version has a number and a hash; publish it to Confluence and Jira, or export PDF and Word. A change after sign-off is marked against the approved version.
A draft from day one, with what nobody has said yet marked in the text. Fictional example.
Follow every requirement back to the person who said it
Open any requirement to see who said it, the words they used, the need it answers and the documents it goes into.
- Records aren’t edited by hand: what people said is what they are made from.
- If a record looks wrong, the person who said it is asked again in their next interview.
- A requirement with no reason yet is marked, not hidden.
A document you can put your name to
Software vendors and integrators with 10–150 people
Teams that deliver projects at a fixed price, where the scope agreed up front decides the margin.
- For the owner
- Scope your customer agreed to, in their people’s words, to point to when a phase is disputed — and fewer analyst hours spent on presales.
- For presales and analysts
- The assistant runs the interviews. You decide what the documents say and issue them.
- For tech leads
- Every requirement traces back to a person and a quote, and goes to Confluence and Jira when you publish.
Pay for the projects you run, not for seats
A plan covers the customer projects you run at once. Invite as many people as you need: they never pay. The demo is free, with no card.
$149 a month
3 active customer projects · 2,000 chat turns a month.
The assistant asks. People decide.
- Your data is stored in Singapore.
- Everyone in a project sees what was written down. Only the vendor’s project administrators see whole conversations.
- Contradictions go to the person who decides at your customer, never to the assistant.
- We do not use your projects or interviews to train AI models.
See whether Reqflow fits your fixed-price projects
Tell us about your company and how you agree scope with your customers. We will email you when your access is ready.
Nothing to pay · Confirm your email · A 20-minute call only if you want one