SA-301i · Module 1

Solution Architecture in Proposals

3 min read

The solution architecture section is the center of the proposal. It is not an appendix. It is the evidence that you have designed a solution — not copied a template, not hand-waved at "AI-powered automation," but designed a concrete implementation that addresses the specific problem validated in the previous section. The architecture diagram is not decoration. It is proof of competence.

Do This

  • Include C4 Level 1 and Level 2 diagrams annotated for the client's context — show how the solution integrates with their systems
  • Map every architectural component to a success criterion — the reader should trace any success metric to the component that delivers it
  • Call out the technology selections with one-sentence rationale — "PostgreSQL for the analytics store because the client's team has PostgreSQL expertise and the query patterns require relational joins"

Avoid This

  • Present a generic architecture diagram that could apply to any client — the diagram must reflect this client's systems and constraints
  • Describe the solution in marketing language without technical substance — "our AI-powered platform" means nothing in a proposal
  • Include the architecture as an appendix — it is the central evidence, not supporting material