Direct answer
What Should Architecture and Interior-Design Firms Automate in a Proposal Workflow?
Separate repeated preparation from the commercial judgement that remains with people.
Separate jobs
Break the proposal workflow into separate jobs
Proposal automation covers too much to guide a sensible decision. A proposal passes through finding evidence, drafting, review, version control, approval and submission. Each step has a different mix of repeated work and judgement.
The repeated parts may suit a controlled first pass. The pursuit lead, principal or commercial owner should keep the judgement-heavy decisions. Tender and RFP responses need related but more tender-specific controls.
Preparation
What could be prepared automatically?
A proposed system could find approved case studies, CVs, capability statements and standard firm information, then place them into the right sections. Where no approved answer exists, it should flag the gap rather than invent one. The source file should remain visible to the reviewer.
Tracking the current version and routing it for review could also be included where the firm's documents and approval path support that. The aim is one review-ready draft, with exceptions sent to a named person.
Why is a template not enough?
A template controls the layout. It does not find the right evidence, separate current material from old copies, send questions to the right owners or record which claims received approval. If staff still search old folders, copy text from previous proposals and chase approvals by email, the page has been standardised. The workflow has not.
Accountability
What should remain human?
People should decide whether the opportunity fits, what the client needs to hear, which past work is genuinely relevant and what the firm can commit to.
Fees, scope, programme, legal wording, exclusions and final claims need accountable review. No proposal should be approved automatically. The named proposal or commercial owner should release the final document.
Here is an illustration, not a client case
What could the workflow look like?
Today, a coordinator might search several folders, copy material from old proposals, ask project leads for updates, combine comments from separate files and send a nearly finished document to a principal.
In a possible future workflow, the coordinator selects the proposal type and question set. A system finds approved material, builds a first draft with its sources, flags missing evidence and sends one working copy through the agreed review path. The principal still changes the argument, confirms commitments and gives final sign-off.
Decision
How do you decide whether to automate it?
Map one recent proposal. Look for repeated handoffs, reliable source documents, a consistent final output and a clear reviewer. Then test the difficult step, such as finding the right evidence in the approved files.
If most of the work is one-off judgement, the inputs are unreliable or nobody owns final approval, do not build yet. A workflow diagnostic can help make that decision. Any hands-on test with files, software proof, build or handover that follows is separately scoped and paid. See more architecture and interior-design workflows.