hardDesignCase StudyMidSeniorLead
How do you turn discovery into a proposed architecture and a written proposal that survives procurement?
7 min readUpdated 2026-08-15
Answer
Short answer
Design around the constraints the customer cannot change, offer two options and a recommendation, and write the document so a stranger can evaluate it — with an explicit assumptions register, priced exclusions, acceptance criteria and change control, because procurement turns your prose into contract schedules.
Was this answer helpful?
Likely follow-ups
- Procurement asks you to remove the assumptions section because it "reads as caveats". What do you do?
- How do you write the proposal differently when you know a competitor is bidding a lower-cost delivery model?
- The customer's architect wants a technology in the design that you think is wrong. How does that land in the document?
- What do you hand to the delivery team on day one after signature, and what do they always complain is missing?
Related questions
- You have been handed a scope and a budget, and the budget cannot buy the scope. What do you put in front of the customer?hardAlso on solution-design and proposals5 min
- You are reusing a component that has run without incident for years in another product. What does your test strategy have to say about it?hardAlso on assumptions6 min
- You are asked to design a product that does not exist, and the setup is missing details you would need in real life. Do you point that out?mediumAlso on assumptions5 min
- How much design detail do you commit to in a proposal, knowing the architecture will change in month two and the document becomes the contract?hardAlso on solution-design6 min