Go alone or team? How public buyers read a cybersecurity RFP response
Towns, districts and utilities buy cybersecurity through RFPs. Here is what a public buyer checks when a single firm or a team responds, and how partners should prepare a team before they bid.
State and local cybersecurity solicitations increasingly ask for several kinds of work at once: a program assessment, policy and governance, penetration testing, OT assessments for water or wastewater plants, incident-response planning and staff training. Few firms do all of that well, and buyers know it. The real question for a bidder is not “can we win alone?” but “how will the evaluator read our response?”
This post is for MSPs, specialist firms, M/WBE and service-disabled-veteran-owned firms, and governance practices deciding whether to bid alone or as a team on public work. It uses New York procurement rules where they apply, and the federal team-arrangement rules as a widely understood model.
What the buyer must establish
In New York, State Finance Law § 163 defines a “responsible” vendor by its financial ability, legal capacity, integrity and past performance, and requires each state agency to determine the proposed contractor’s responsibility before award. The Office of the State Comptroller’s vendor-responsibility guidance extends that review to subcontractors: a Vendor Responsibility Questionnaire and review are required where the subcontractor is known at award and the subcontract will equal or exceed $100,000 over the life of the contract. Local governments run their own procurement policies, but evaluators borrow the same questions.
The federal rules on contractor team arrangements (FAR Subpart 9.6) say teams are acceptable when the arrangements are “identified and company relationships are fully disclosed in an offer,” and that the government will “hold the prime contractor fully responsible for contract performance, regardless of any team arrangement.” Many public buyers apply the same logic: a team is welcome, a hidden team is not, and the prime answers for all of it.
New York also sets participation goals that make real teaming valuable. The State reported an estimated 31.86 percent MWBE utilization rate for fiscal year 2024-25, the fifth consecutive year it met or exceeded its 30 percent goal. Article 3 of the Veterans’ Services Law sets a statewide 6% goal for service-disabled veteran-owned businesses on contracts for commodities, services and technology valued over $25,000.
How an evaluator reads a single-firm response
A single firm is simplest to evaluate and to manage. It is the right answer when the firm genuinely covers the full scope with named, qualified staff and meets every threshold in the solicitation (years in business, prior public-sector contracts, insurance limits, certifications). Evaluators look hard at the parts of the scope where a generalist is thinnest, usually OT, testing and forensics. A firm that claims all of it without named people for each part invites a low technical score or a responsibility question.
How an evaluator reads a team response
A good team response answers four questions without the evaluator having to ask:
- Who is prime and why? The prime holds the contract and the accountability. The buyer wants to see that the prime manages the whole engagement, not just its own slice.
- Who does each part of the scope? A table that maps each deliverable to a firm and a named person is the clearest evidence a team is real.
- Is each partner responsible in its own right? Past performance, insurance, certifications and, in New York, a vendor responsibility filing where the subcontract reaches the threshold.
- Is the M/WBE or SDVOB participation real work? Evaluators and compliance officers look for a defined scope, named staff and a share of the work that matches the stated percentage.
The responses that lose usually fail one of those four: a partner listed by logo only, a scope table that does not match the price sheet, or a participation figure with no work behind it.
Before you bid as a team: a partner checklist
Agree these in a short teaming agreement before the proposal is written, not the night before it is due:
- Scope by firm and by person, matched to the solicitation’s deliverables and the price sheet.
- Who is prime, chosen on who meets the solicitation’s gates and can manage the whole contract. A firm that fails a firm-age or past-performance gate as prime may still be the right named subcontractor or joint-venture partner.
- Flow-down terms: insurance, confidentiality, data handling, background checks, records retention and the buyer’s security requirements. NIST’s CSF 2.0 GV.SC-05 expects supply-chain security requirements to be “integrated into contracts” with suppliers, and the buyer will expect the same of a prime toward its subcontractors.
- The shares: the percentage of work and fees for each partner, stated the same way in the teaming agreement, the participation plan and the price proposal.
- Exclusivity and non-solicitation for this bid, and what happens if the team does not win.
- One voice to the buyer: the prime’s project manager owns communications, status reports and escalation.
When to walk away
Some solicitations set hard requirements a team cannot satisfy: a minimum number of years in business for the prime, a named certification the team does not hold, or a scope that is mostly hardware resale. A clean no-bid preserves time for the next solicitation and the relationship with the buyer. A response that stretches the truth costs both.
Where SMC fits
Security Medic Consulting provides public-sector governance, assessment and audit leadership. Jim Venuto founded SMC after a career leading security, privacy, GRC and CISO-level work for mid-size and large enterprises and public bodies. On public solicitations, SMC can bid as prime, or join a team as a named subcontractor or joint-venture partner, alongside MSPs, testing and OT specialists, incident-response firms and M/WBE and SDVOB firms. The aim is the arrangement each procurement requires, with every partner doing the work it is best at. That network is the SMC Partner Network, which SMC calls the bench.
If you are weighing a public cybersecurity solicitation and want a governance partner, or want to compare notes on whether to bid at all, Book a free 30-minute call, or write to support@securitymedic.com. The Security Medic partner page describes how SMC works with partners.
Sources
- New York State Senate: State Finance Law § 163
- New York State Office of the State Comptroller (rev. Sept. 6, 2019): Guide to Financial Operations XI.16, Vendor Responsibility
- eCFR: 48 CFR Subpart 9.6, Contractor Team Arrangements
- Office of the Governor of New York (Nov. 18, 2025): Record-setting $3.3 billion in state spending with MWBEs
- NYS Office of General Services: Sample SDVOB solicitation and contract language (Word document)
- NIST (Feb. 26, 2024): The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29