Case Study: How an Architecture Studio Rebuilt Its Proposal Process

Starting point

Picture a 12-person architecture studio working on residential, office and boutique hotel projects, producing 15-20 proposals a month. Proposals come from a Word template, pricing lives in a separate spreadsheet, and the final document goes out as an email PDF. On paper the process works, yet three chronic problems persist:

• Preparation time: reworking shared text takes half a day per proposal.
• Version chaos: among files named "proposal_final_v3_revised.pdf", nobody knows which price is current.
• No visibility: whether the proposal was opened is unknown; follow-up depends on memory.

Step 1: Separate the fixed from the variable

The work began by comparing the last 30 proposals. Studio introduction, methodology, deliverable drawing lists and contract terms were nearly identical every time. Those went into a permanent template. Only the project description, floor area, phase plan and pricing table actually changed.

Step 2: Turn services into a catalogue

Concept design, construction documentation, structural coordination, interior design, 3D visualisation and site supervision were each defined with a unit (square metre, item, month) and a default unit price. Building a proposal stopped being a writing task and became a selection task.

Step 3: Phased pricing with options

Instead of one total, the studio moved to three columns: required services, recommended additions, optional items. Clients could tick optional lines themselves. That single change moved negotiation from "lower the total" to "which items do we need in this phase".

Step 4: Digitise approval and revisions

PDFs gave way to a shared online proposal link. Clients could review on a phone, request revisions on the document itself and approve the final version in one click. Because every revision was stored as its own version, the "which price is valid" question disappeared.

Step 5: Automate follow-up

Open notifications and scheduled reminders were switched on. Each morning the studio manager could see which proposals had been opened and which were approaching expiry on a single screen. Calls were now driven by data rather than recollection.

Operational effects typically observed

Studios undertaking this kind of rebuild commonly report: a clear reduction in preparation time, fewer revision-related errors, a single searchable proposal history and better-timed follow-up calls. Actual results vary with project complexity and team discipline.

Lessons from the case

• The biggest barrier to proposal speed is not writing — it is re-deciding everything each time.
• Without a service catalogue, pricing varies by whoever prepares it; a catalogue institutionalises consistency.
• Optional pricing lines convert discount pressure into a scope conversation.
• Follow-up without visibility is guesswork dressed as selling.

How to apply it in your studio

Lay out your last 20 proposals, mark the repeating sections and extract your service catalogue. Then split pricing into required, recommended and optional. Finally, automate follow-up. Try Flowpare free and you can stand this up within a week.