One meeting in. A whole project out.
Below is what a single 40-minute requirements workshop produces — a structured BRD, the project memory pulled out of it, and the ambiguities read straight back to you. Nothing here was written by hand.
The sample transcript is one click away on the tool page. Free, no account.
1 · The document
A BRD you could send
Sixteen sections, MoSCoW-prioritised, grounded only in what was actually said — no invented figures, no invented dates. This is an extract.
1. Executive Summary
Customer onboarding is currently a manual process taking four to five days on average, and up to nineteen days for enterprise customers with multiple business units. The delay is contributing to first-month churn and is now the constraint on how quickly new customers can be signed.
The Customer Onboarding Portal automates provisioning for standard customers and gives customer administrators direct control over their own users. The target is production readiness before the Q4 renewal cycle begins.
2. Business Objectives
| ID | Objective | Measure |
|---|---|---|
| BO-01 | Remove manual effort from standard onboarding | No human action required for single-business-unit customers |
| BO-02 | Reduce time from contract to product access | Under one hour from countersignature |
| BO-03 | Reduce first-month support load | Fewer user-management tickets in the first 30 days |
3. Scope
In scope
- Automated account provisioning triggered by contract countersignature
- Customer-administered user management: invite, deactivate, change role
- Live licence-count integration with the billing platform
- Audit logging of all user account changes
Out of scope
- SAML single sign-on — explicitly deferred beyond this release
4. Requirements
REQ-001 · Functional · Must The system must provision a new customer account within one hour of contract countersignature, for standard single-business-unit customers.
REQ-002 · Functional · Must A customer administrator must be able to invite, deactivate and change the role of users within their own organisation without contacting support. Roles are limited to administrator, standard user and read-only.
REQ-003 · Functional · Must The system must check the customer's available licence count against the billing platform at the moment a user is invited, and prevent the invitation when no licence is available.
REQ-004 · Functional · Must The system must record an audit entry for every user account change, capturing the actor, the timestamp, and the before and after values. This applies to changes made by internal staff as well as by the customer.
REQ-005 · Functional · Must A failed provisioning attempt must alert the Customer Success team and leave the account in a state that can be retried, rather than partially created.
REQ-006 · Non-functional · Should Administrative screens should respond quickly enough not to impede routine user management.
⚠ REQ-006 has no measurable threshold. Flagged for review — see below.
5. Assumptions and Dependencies
- The CRM emits a countersignature event the portal can subscribe to.
- The billing platform's API exposes live seat counts. Unverified.
6. Constraints
- Production readiness required before the Q4 renewal cycle — end of September.
2 · The project memory
Everything the meeting knew, kept
The same transcript also becomes structured rows. Every one carries an id, so the next meeting updates it in place rather than creating a second copy of the same fact.
Requirements
- REQ-001Provision a new account within one hour of countersignatureFunctional · Must
- REQ-002Customer admins manage their own usersFunctional · Must
- REQ-003Check licence availability at the moment of invitationFunctional · Must
- REQ-004Audit every user account changeFunctional · Must
- REQ-005Failed provisioning alerts and stays retryableFunctional · Must
- REQ-006Administrative screens respond quicklyNon-functional · Should
Stakeholders
Pulled from who spoke and what they were answerable for.
STK-001Priya Raman
VP Customer Operations · Sponsor
STK-002Daniel Osei
Customer Success lead
STK-003Marta Kowalska
Engineering
STK-004Tom Fielding
Sales Engineering
Risks
Scored by impact and likelihood, owned by a named stakeholder.
RSK-001The billing platform API may not expose live seat counts, forcing the design back onto the nightly export.
6 · High · Owner STK-003
Decisions
Recorded with the reason, because the reason is what gets forgotten.
DEC-001Integrate directly with the billing platform API rather than continue with the nightly export.
The portal needs the seat count at the moment of the request.
Open questions
Nobody in the room could answer these, so they stay on the record.
OQ-001What audit log retention period does the SOC 2 auditor require?
Owner STK-001 · to confirm with Legal
Boundary and glossary
What was ruled out, and the terms the room defined for itself.
OOS-001SAML single sign-on — deferred beyond this release
Out of scope
GLO-001Account — the customer organisation, not an individual login
Glossary
GLO-002User — an individual login within an account
Glossary
INT-001Billing platform — source of truth for licence counts
Integration
3 · The part that argues back
What it read back to you
Inside a project, the review pass reads your own requirements and reports what is ambiguous, what contradicts an earlier meeting, and what the project implied but never wrote down.
- FND-001mediumon REQ-006
No measurable threshold given
This requirement describes desired behaviour without a number anyone could test against, so two developers could both satisfy it and disagree.
“it shouldn't feel slow”
- FND-002highon REQ-004
Retention period never established
The project commits to an audit trail for SOC 2 but has recorded no retention period, and the question raised in the meeting was left with Legal. REQ-004 cannot be built to completion without it.
Both of these came out of a single meeting. Conflict detection needs two — it compares what was agreed in week one against what was agreed in week four, which is the kind of contradiction nobody notices in the room.
Try it on the same transcript, or on yours.
The sample is loaded with one click. Bring your own when you want to see it on a project you actually recognise.