Stop 4 of 10 · Weekly
The RFP response
A compliance matrix built from the requirement list, section drafts written out of the account Project, a source check on every claim, and one rule about price that never bends.
Sixty requirements and eleven days
The Rio Seco Unified solicitation runs to ninety pages: sixty-two numbered requirements, four narrative sections, a compliance matrix template, security questionnaires and a commercial attachment. Fadi has eleven days and three other accounts. The response gets written on the last two evenings, which is how a claim nobody checked reaches a public procurement file.
The order matters more than the speed. Matrix, then sections, then the source check, then the commercial attachment somebody else completes.
The matrix first
Attached is the Rio Seco Unified solicitation. I am the cloud architect responding on behalf of the platform vendor. Extract every numbered requirement into a matrix with these columns: requirement identifier, the requirement in one sentence, my proposed compliance status of compliant, partially compliant or exception, and where in the response it will be answered. Do not fill the status column with a guess. Where the solicitation is ambiguous about what is being asked, mark it AMBIGUOUS and write the clarification question I should submit before the question deadline. List those questions together at the end.
The clarification list is the free win. Every solicitation has six requirements that mean something different than they read, and the question deadline is usually two weeks before the response deadline.
Sections drafted from the Project, not from memory
The account Project already holds the architecture document, the decision log and the compliance mapping. Drafting from those means the response cannot contradict the design, which is what happens when a proposal writer starts from a previous response for a different agency.
Using the architecture document, decision log and compliance mapping in this Project, draft the technical approach section for the Rio Seco response, answering requirements 3.1 through 3.14 in order. Every factual claim about a service capability, control or limit carries the document it came from in square brackets. Where the Project material does not support a claim the requirement is asking for, write NOT VERIFIED and say what document would settle it. Do not write a performance figure, a percentage or a timing under any circumstances unless it appears in the attached material. Match the district's own vocabulary from the solicitation rather than our product names where the two differ.
Go back through the section you just drafted. List every sentence that contains a number, a certification, a compliance claim or a comparison. For each one, give me the source it came from, or say that it has no source in the attached material. Do not fix anything. I want the list, because I am going to open each source myself before this is submitted.
Read that list against the actual pages. It usually runs to about a dozen lines, and one or two of them will be things Claude reasoned into existence because the sentence needed a figure.
The pricing rule
Fadi writes the dimensions and the assumptions. He never writes a rate, a discount, a programme fund or a total. The commercial attachment goes to the deal desk with the assumption table from stop six attached, and comes back priced and approved. This rule does not bend for a friendly agency or a short deadline.