Solicitation Architecture
Architecture support for any government solicitation: an RFI, RFQ, or RFP response, or the questions you send the agency before you bid.
Discuss this engagementWhen it fits
You are responding to an RFI, RFQ, or RFP on Azure or the Microsoft cloud, or you have technical questions to put to the agency, and you need an architect to shape the solution your team will write from.
What changes
A solution architecture, diagrams, and technical approach inputs mapped to the requirements you choose to address, sized to the solicitation in front of you.
What you receive
- Solution architecture and diagrams for the response
- Technical approach outline and section inputs, or a capability response for an RFI
- Technical questions for the agency's question period, with the reasoning behind each
- Traceability from the selected technical requirements to the solution, with risks and assumptions for the capture team
What we agree first
- The solicitation (RFI, RFQ, RFP, or draft) and your response schedule
- A capture or proposal lead who owns scope and win themes
- Your teaming context and pricing constraints
Scope, fee, acceptance criteria, and timing are agreed before work starts.
Scope boundaries
You remain the respondent and own the response, pricing, and compliance. We do not write full proposals, price the bid, guarantee an award, or work for competing respondents on the same solicitation.
View example deliverablesCloud Adoption Framework or Well-Architected: Which One Answers Your Question
The two Azure frameworks answer different questions; use the Cloud Adoption Framework for estate decisions and the Well-Architected Framework for a single workload, and name the control owner where they overlap.
More from Proposal Architecture
What does your team need to settle?
Bring the system, the business goal, and the constraints. Scope, deliverables, and fee are agreed before work starts.
Discuss this engagement