Section openings that earn the next paragraph

An evaluator reads the first sentence of every section. They read the second sentence about half the time. By the third, you’ve either earned the rest of the page or you haven’t. This post is six section openings from real awarded proposals — anonymized — and what they do that gets the read.

Opening 1 — claim before context

Our incident-response process resolves 87% of severity-1 events within the SLA window. The remaining 13% are documented case-by-case in section 6.4.

The claim is in sentence one. The exception is in sentence two. There is no setup, no “incident response is an important capability for any platform,” no “we believe.”

What this does: it gives the evaluator a number and a hook. They can score sentence one. They can read sentence two if they care about the exceptions. If they don’t, they can move on knowing what the section claims.

The pattern: number first, scope of claim second, context (if any) third. Most teams reverse the order — context, scope, number — and the number gets buried below the fold.

Opening 2 — the comparator

The current state vendor’s case-management system writes audit logs on data modifications. Our system also writes audit logs on every read. The functional difference, illustrated below, is the reason your data-integrity audit closed without a finding under our predecessor agency contract.

Three sentences. The competitor’s behavior is named. Ours is named. The buyer-facing implication is named. There is no “we are pleased to offer” in the building.

What this does: it sets a comparator the evaluator can hold both vendors against. The evaluator was going to make this comparison anyway, on the back of an envelope, after they finished reading. This opening makes the comparison for them, on the page, in the form they’d have made it.

Opening 3 — the constraint that becomes an asset

Section 6.2.4 of the RFP specifies that the proposed solution must be deployed in a single Azure region, with no cross-region replication. Our standard architecture is single-region by design. We will not need to disable a feature to meet this requirement; we built the platform around it.

Most bidders address constraint clauses defensively: “we comply with the single-region requirement.” This opening flips the framing. The constraint isn’t a hurdle; it’s a structural fit.

What this does: it shows the evaluator the bidder read the constraint, understood the implication, and engineered around it. Bidders who appear to be retrofitting compliance score lower than bidders who appear to have been built for the requirement, even when the substance is identical.

The pattern: name the requirement clause, name the structural alignment, name the absence of compromise. Three sentences.

Opening 4 — the verb-led sentence

We migrated the agency’s claims-processing backlog from legacy mainframe to cloud in 73 days, against a 90-day target. The migration touched 41 million records.

No “our team has extensive experience in.” No “we are uniquely positioned to.” The sentence starts with what we did. The number lands in the same sentence. The scale lands in the second sentence.

What this does: it forces specificity. A sentence that starts with a verb cannot hide behind adjectives. The reader either finishes the sentence with a fact or the sentence falls apart.

The discriminator post walks through the structural reason verb-led discriminators outscore adjective-led ones. Section openings inherit the principle.

Opening 5 — the negative claim

Our platform has not been the subject of a customer-data breach in the seven years it has been in production. The audit history is in appendix C.

A negative claim about your own performance is unusually credible because it’s hard to fake. “We have a strong security record” is something every vendor writes; “we have not had a breach in seven years, history in appendix C” is something a buyer can verify, and that they know they can verify.

What this does: it transfers the burden of proof from the claim (“strong security record”) to the evidence (“appendix C”) and signals that the bidder welcomes the verification.

The pattern: a specific negative claim about your own track record, time-bounded, with a verifiable pointer. Used sparingly — once per major section, at most — these are among the highest-leverage sentences in a proposal.

Opening 6 — the question the evaluator was about to ask

A reasonable evaluator at this point asks: how does the proposed price reconcile with the staffing model in section 4? It does, and section 5.3 walks through the math line by line.

This works only when the writer has been disciplined enough to know what the evaluator is going to ask, and where in the document the answer is. When it works, it does two things: it acknowledges the evaluator as a thinking participant in the document, and it routes them to the answer instead of leaving them to find it.

What this does: it makes the document feel like it was written for the evaluator, not at them. Most proposals feel like the latter. The few that feel like the former are remembered in the debrief.

The pattern: name the question explicitly, answer in one phrase, route to the section that owns the full answer. The VisibleThread analysis of high-scoring federal proposals notes this pattern: cross-references made by the writer score higher than cross-references the evaluator has to construct themselves.

What all six openings share

Three properties.

They put a fact in the first sentence. Not a thesis, not a setup, not a “we are excited to.” A fact that can be scored.

They presume the evaluator’s attention is finite. The opening is engineered to earn the next paragraph, not to fill space.

They’re verifiable. Every claim has either a number, a comparator, an appendix pointer, or a structural reason behind it. None of them are adjective-driven.

The opposite — openings that introduce, that contextualize, that “we believe” their way into the section — fail not because the rest of the section is bad but because the section never got read.

How to write them

A simple drill, used in red-team review: take any section opening in your draft and ask three questions.

1. What is the fact in the first sentence? If there isn’t one, rewrite.
2. What can the evaluator score from this opening? If the answer is “nothing concrete,” rewrite.
3. Could a competitor write the same opening with their name on it? If yes, it isn’t yours; rewrite.

The first two cuts are mechanical. The third is the swap test applied at the section level. A section opening that survives the swap test is doing real work.

The takeaway

Openings are the highest-stakes paragraph in the document. Half a section’s score is decided in the first sentence; the other half is decided in whether the evaluator finishes reading. Get the opening right and the rest of the section gets a fair hearing. Get it wrong and the rest doesn’t matter.