Software RFP Template (English)

1) Project context
- What is changing in the business or workflow that makes this build necessary now?

2) Outcome for phase one
- What must improve for users or internal operators at launch?

3) Primary workflow
- Describe the main user journey from entry to completion.

4) Must-ship scope
- List the 3-7 capabilities that absolutely need to ship in phase one.

5) Admin and operator ownership
- Who updates content, approvals, settings, and edge-case decisions after launch?
- What must be editable without engineers?

6) Timeline and budget assumptions
- Preferred launch window:
- Budget range under consideration:
- Which tradeoffs are acceptable if the timeline gets tight?

7) Known constraints
- Compliance, migration, integrations, approvals, or legacy system dependencies.

8) Questions for vendors
- What would you remove from phase one first if the timeline slipped?
- Which workflows usually expand scope in projects like this?
- What should we clarify before asking for a fixed quote?