Architecture and Proposal Writing 101
No honest method wins every bid. Price, incumbency, procurement rules and timing can outweigh the best technical answer. What a good method does is win more of the right bids, stop weak pursuits early and learn from every result. This twelve-part series follows one fictional bid from the moment the RFP arrives to the lessons log after the award: the bid/no-bid decision, reading stakeholders and the room, discovery, requirements and assumptions, win themes, TOGAF, CAF and WAF used without theatre, architecture views that answer real questions, flows and ownership, transition states, estimating and pricing, writing and presenting, and red-team review. Written in plain language for solution architects, proposal teams, sales and delivery leads, and the executives who approve the bid.
12 articles
- Part 1Win before you write: the bid/no-bid decisionThe most expensive proposal is the one that should never have been written. Before anyone opens a template, a bid team has to prove the opportunity is winnable, deliverable and commercially sound. Part 1 of a 12-part series, following one fictional bid from first read to final result.11 min read
- Part 2There is more than one client: reading stakeholders, procurement and the roomThe person you meet in discovery may not score your proposal, and the person who scores it may not make the decision. Part 2 of the series shows how to map everyone who judges a bid, read the signals the RFP does not state, and answer the concern beneath the question.8 min read
- Part 3Discovery: the questions that change the answerDiscovery is not a questionnaire. Its job is to find the facts that change the shape, effort, risk or price of a solution, before they are discovered the expensive way. Part 3 of the series, with the one clarification answer that reshaped the Rivermark bid.9 min read
- Part 4Make it easy to award the point: requirements, assumptions and traceabilityAn evaluator with a scoring sheet cannot award a point they cannot find. Part 4 of the series covers answering requirements in the client’s own structure, separating facts from assumptions and commitments, and using a traceability matrix to catch gaps before an evaluator does.8 min read
- Part 5Features are not reasons: win themes, value and proofA list of features tells an evaluator what you offer. It does not tell them why choosing you is the safer, better decision. Win themes, honest value and the right proof do that work.9 min read
- Part 6TOGAF, CAF and WAF without the framework theatreNaming a framework proves nothing. Used properly, TOGAF frames the change, a cloud adoption framework exposes the organisational work, and a well-architected review tests the workload. Here is how to use each in a proposal without the theatre.8 min read
- Part 7One diagram cannot answer every question: architecture layers and viewsA single dense diagram tries to serve every evaluator and serves none of them. A purposeful architecture pack gives each audience a view that answers its own question, in an order that builds understanding.9 min read
- Part 8Components do not prove it works: flows, ownership and operationsA list of components shows what a solution contains. Evaluators need to watch one real request travel through it, see who handles each exception, and know who owns the service the day after launch.9 min read
- Part 9The target is only half the architecture: as-is, bridge states and to-beA clean target architecture is worth little if the client cannot reach it safely. The as-is, the bridge states in between and the to-be are where evaluators decide whether a bid is believable, and where most proposals go quiet.10 min read
- Part 10Architecture and price must describe the same solutionA proposal loses credibility the moment its diagram contains something its price does not. How to turn an architecture into work packages, state estimates with honest confidence, find the work everyone forgets and build commercials an evaluator can trust.9 min read
- Part 11Write for two readers: assembling and presenting the proposalEvery proposal is read twice: by a scorer working through a sheet of criteria, and by a decision-maker deciding whether to trust you. How to structure, write and present a response that serves both, and the ten habits that quietly lose trust.8 min read
- Part 12Red-team, submit and learn from evidenceWriters cannot see their own gaps. Independent reviews that read like a sceptical evaluator, a disciplined submission and an honest lessons log are what turn one bid into a better next one, whether it was won or lost.11 min read
Working through any of this in your own organisation?
These articles come out of delivery work rather than theory. If the problems in this series look familiar, a short scoping conversation is usually the quickest way to work out what is worth doing first.
Talk to CloudNala