Lumi RFP
A brief becomes a decision.
An RFP is not one form and one output. It is a workflow with several moments of responsibility between the first brief and the final proposal.
The workflow starts here
- Solo Software Engineer / Product Builder
- Workflow product
- 2026
- Brief → Proposal
The document is only one moment.
A request for proposal is a process, not a document. It starts as a brief and ends as a decision, and most of the work happens in between.
Brief
Structure
Request
Operations
Proposal
I modelled the workflow first, then built its stages in a modular, API-first Next.js 14 application with server components by default. Each screen follows a moment in the request, from structure through operations and proposal.
Structure
Define what kind of request is entering the workflow.
Request
Turn the brief into a structured request the team can work with.
Operations
Keep active requests visible as they move through the process.
Proposal
Bring the work together in the proposal that closes the loop.
The workflow needs a place to stay visible.
The dashboard gives the operating side of the product its own overview while the request itself continues moving through defined states.
The workflow is the product.
One record moving through defined states inside a modular Next.js application.
Approach
I built the product from scratch by myself from a brief, using a modular API-first architecture and server components by default. The workflow was modelled first, then each stage received the interface it needed.
Experience
Brief, RFP, responses, evaluation, decision — each with its own view.
Reflection
Process tools live or die on how honestly they model the messy middle.