01
The operational problem
When scope, selections, terms, attachments, and approvals are spread across documents, teams lose track of which version is current and what the client has actually approved.
PROJECT FINANCE
A project-linked proposal workflow turns real products, services, terms, taxes, and payment stages into controlled, numbered commercial documents.
Evidence statusImplemented system
02
The system response
We built proposal creation into the project workflow, with atomic numbering, linked line items, controlled document states, terms, taxes, attachments, and payment schedules.
03
Operational impact
Teams can move a proposal from draft to approval without losing the project decisions, commercial terms, or supporting records behind it.
PROJECT FINANCE
Implemented scope
03Proposal Workflow
- 01
Atomic proposal numbering and connected project line items
- 02
Draft, sent, approved, declined, invoiced, and archived states
- 03
Terms, attachments, taxes, payment schedules, and audit metadata
04
Technical foundation
SwiftSwiftUITypeScriptFirebase Cloud FunctionsFirestore
05
Implementation notes
Claims on this page describe implemented scope at a high level. Private interfaces and live operational data are not published.
Operational impact