Stage 1 — Business Request
⏱️ At a Glance This is the project's permanent record of why it exists. Review or edit the Problem Statement, Solution, and Delivery Approach here, then trigger document generation — either all at once or one at a time.
Purpose: Capture the initial problem statement, solution direction, and delivery approach that form the foundation for all downstream documentation.
📍 Pipeline position: Stage 1 of 9 — see the full pipeline map.
The Three Sub-Steps
| # | Sub-step | What It Captures |
|---|---|---|
| 1 | Problem Statement | The business problem and objectives, in the requester's own words. |
| 2 | Solution | Explored solution options and the recommended approach. |
| 3 | Delivery Approach | The delivery plan, timeline, and key milestones. |
Each sub-step shows an Edit button so you can refine the original request at any time — even after documents have already been generated from it.
Generating Documents From This Stage
Once the Problem Statement, Solution, and Delivery Approach are accurate, you have two paths:
- Click "One-Click Synthesize (All 3 Docs)" at the top of the page to generate the BRD, SRD, and FSD together in a single pass, or
- Move to Stage 2 — Specification and generate each document individually for more granular control.
⚡ Use One-Click Synthesize for straightforward projects. For anything with nuanced requirements, generate documents individually so you can review and refine each one before moving on.
Worked Example — Gate Secure
Gate Secure is a security checkpoint application — a deliberately informal, real-world example of what gets typed into the Problem Statement field.
Problem Statement (as entered)
"I need an application for security people to use at gate to store the vehicles getting in & out at the gate. Because security mens are now entering in physical notebook now."
Notice this is rough, conversational English — not a polished paragraph. DeX's AI still extracts the core pattern from it:
- What's broken: Vehicle entry/exit logging is done in a physical notebook.
- Who's impacted: Security personnel staffing the gate.
- The implied need: A digital system to record vehicles entering and leaving.
This is exactly what gets expanded into the Executive Summary and Background sections of the generated BRD
Worked Example — Contractor Sync
For a more fully-specified Problem Statement — written as a single dense paragraph capturing the failure, the impacted group, and a quantified cost — see the Problem Definition walkthrough from the project creation brief, which uses Contractor Sync as its running example.
What's Next
➡️ Stage 2 — Specification — Generate the BRD, SRD, and FSD from this Business Request.