If your customer logo wall has a federal agency, a state government, or a major municipality on it, you already know two things. First: that logo opens more enterprise sales doors than ten startup logos combined. Second: getting a quote, a name, or a face out of that customer to put next to the logo is one of the hardest things a B2B marketing team will ever attempt.
Public sector testimonials are different from commercial ones in almost every meaningful way — different approval chain, different legal review, different naming conventions, different photography rules, different publication risk. Most marketing teams treat them like a regular testimonial request and watch the response disappear into a procurement office for six months. This article is the playbook for treating them as the genuinely different beast they are.
Why public sector customers almost never give testimonials
Before you can fix the process, you have to understand why it usually fails. Six structural forces make a public sector customer reluctant to put their name next to a vendor quote.
1. Anti-endorsement policy
Most federal agencies, many state governments, and a growing number of municipalities have explicit policies forbidding employees from endorsing commercial products. The policy is usually written to preserve procurement neutrality — if the agency endorses Vendor A today, Vendor B has grounds to challenge a future RFP award. This is not a personal reluctance; it is a written rule that the contact you are asking would be violating.
2. Procurement neutrality risk
Even where no formal anti-endorsement policy exists, public sector contacts know that any quote attributed to them will be cited by your sales team in future RFPs. Their procurement and legal teams are aware of this and will block the testimonial precisely to prevent that downstream use.
3. FOIA and public records exposure
In many jurisdictions, communications between a vendor and a government employee are subject to public records requests. Your testimonial request email, the back-and-forth on quote wording, and the final approval thread can all be requested and published. This makes individual employees risk-averse in a way commercial customers never are.
4. Personal-name vs office-name confusion
A commercial testimonial usually attributes a quote to a person — Jane Smith, VP of Operations. A public sector testimonial may need to attribute to the office, the program, or the agency rather than the individual, because the individual cannot endorse but the program might be allowed to acknowledge usage. The naming rules are not intuitive and vary by jurisdiction.
5. Photography and likeness policies
Many agencies prohibit using employee photos in commercial marketing materials. Even when the agency permits the quote, the headshot you would normally pair it with may be off-limits.
6. Long review cycles
A commercial testimonial typically takes 2-4 weeks from request to publication. A government testimonial typically takes 2-6 months because the approval chain runs through legal, communications, the agency PR office, and sometimes the inspector general before it reaches whoever signs off.
7. Election and administration cycles
In the year before an election or during a transition between administrations, almost no agency will approve any new external communication. The window for getting a testimonial approved closes for 6-12 months at a stretch.
What this means for your testimonial strategy
The combination of those seven forces means you should not try to extract a public sector testimonial in the same shape as a commercial one. The commercial format — named individual, headshot, candid quote — will fail review almost every time. What you need instead is a format that survives procurement and legal review while still doing the work a testimonial needs to do.
For background on what testimonials are doing in the first place, our case study vs. testimonial breakdown and our guide on collecting testimonials from customers cover the commercial baseline. The four formats below are the public-sector adaptations.
Four formats that survive procurement review
Format 1 — The case study without a personal name
Replace the named individual with the office or program. The Office of Information Security at the [Agency Name] is approvable in jurisdictions where Jane Smith, CISO is not. The case study describes the deployment, the outcomes, and the program-level decisions without ever attributing a quote to a specific person.
This format trades emotional impact for survivability. It will not do the same job as a candid personal testimonial, but it will hold up to a FOIA request and a procurement review and the logo will be allowed to stay.
Format 2 — The aggregated outcome attribution
Instead of a quote from any single customer, publish a metric across the customer cohort: Used by 47 federal agencies and supports 2.3 million users. The phrasing avoids endorsement language ("loved by", "trusted by", "preferred by") and replaces it with usage facts.
This format works because facts about deployment are not endorsements and are not subject to most anti-endorsement policies. The Census-style framing also signals scale, which often matters more to enterprise buyers than the emotional content of an individual quote.
Format 3 — The third-party speaking on behalf of the agency
Sometimes the agency cannot endorse but a third party who worked with the agency can. A systems integrator, a contractor, or an academic researcher may be willing to say we deployed [Product] for [Agency] and the outcome was X, attributed to themselves rather than to the agency.
This format requires a willing third party, but it produces a quotable testimonial that does not violate the agency's policy because the agency is not the one speaking.
Format 4 — The conference talk or public presentation
Government employees who would never approve a marketing testimonial sometimes give conference talks describing their deployment. The conference recording, the slide deck, or a public press release becomes a quotable artifact.
You are not asking the agency to write a testimonial; you are quoting publicly available statements they have already made. This format requires monitoring conferences and public communications, but the resulting "testimonial" is bulletproof — it was already approved when the talk was approved.
The seven-step playbook for getting a public-sector testimonial published
Once you have picked a format, the request process matters as much as the format itself. The playbook below has produced the highest approval rate in our experience.
Step 1 — Identify the right contact, which is rarely your sales contact
Your sales contact is the person who bought the product. The person who approves an external testimonial is almost never that person — it is the agency communications office, the public affairs officer, or in some cases the inspector general's communications liaison. Asking the wrong person produces a polite refusal; asking the right person produces an actual review.
Step 2 — Pre-approve the format with the customer's legal team
Before you draft anything, send a one-page description of what you intend to publish (program-level case study, no personal names, no photos, deployment facts only, agency name and logo only) to the customer's communications office and ask whether that format would be approvable in principle.
If the answer is no, you save weeks of drafting work. If the answer is yes, you have a green-light memo you can reference when the actual draft enters review.
Step 3 — Draft the lowest-risk version first
Draft the testimonial in the most conservative format you think the customer might accept. Resist the temptation to start with a strong version and negotiate down — the negotiation costs you weeks and tends to produce the same conservative version anyway.
Step 4 — Run a separate FOIA-aware review
Ask explicitly: if a citizen submitted a public records request for our communications about this testimonial, would anything in our email thread be problematic for you? The question signals you understand the FOIA exposure and produces faster cooperation.
Step 5 — Build in a re-approval step at every administration change
Public sector personnel turnover is high. The contact who approved your testimonial in 2024 may be gone in 2026, and the new administration may revoke the approval. Build a 12-month re-confirmation cadence into your customer relationship.
Step 6 — Publish with a removable design
Design the testimonial placement so it can be removed in under an hour. If a customer revokes approval mid-cycle, you need to comply within the day. A modular component on your site that can be disabled per-customer with a content-management toggle is far better than a hardcoded section.
Step 7 — Document everything
Keep a written record of every approval, including the named approver, the approval date, the format approved, the publication scope, and any restrictions. When a future inspector or auditor asks, the documentation closes the question in 10 minutes rather than 10 weeks.
What public-sector testimonials are worth
A public-sector logo on your site is worth more than a commercial logo of similar size. Procurement officers in adjacent agencies use them as social proof when shortlisting vendors. Enterprise buyers in regulated industries use them as a signal that the product survived government-grade review. The credibility transfer is large enough that a single approved federal-agency testimonial can move enterprise pipeline by more than ten startup testimonials combined.
If you have already navigated the procurement process to win the contract, the marginal effort to add a testimonial is small relative to the marginal pipeline value. The trick is doing it in a format that holds up to the seven structural forces above. The four formats and seven-step playbook in this article are the version that has worked. The version that does not work — asking the contracting officer for a candid quote and a headshot — produces silence. You have done the hard part by winning the customer. The testimonial is just a question of asking in a shape the agency can answer.