Washington Saves Takes a Strategic Step Forward
The retirement savings landscape in the United States continues to evolve rapidly, and Washington State is making headlines with a significant procurement move. Washington Saves, the state's auto-enrollment individual retirement account (IRA) program, has recently issued a Request for Proposals (RFP) seeking a qualified program administrator, alongside a Request for Information (RFI) targeting potential multi-state partnership opportunities. This dual-track approach signals not just a maturing of state-sponsored retirement programs, but also a sophisticated understanding of how collaborative procurement strategies can drive better outcomes for participants and taxpayers alike.
For procurement professionals, government contractors, and business owners watching the public sector space, this development offers a compelling case study in how large-scale program administration procurements are structured — and what best practices look like when states venture into uncharted collaborative territory.
Understanding the Washington Saves Program
Washington Saves is part of a broader national movement to expand retirement savings access to workers who lack employer-sponsored plans. Much like Oregon's OregonSaves, Illinois' Secure Choice, and California's CalSavers, Washington's program is designed to automatically enroll private-sector employees into a state-facilitated IRA unless they actively opt out.
The program represents a significant administrative undertaking. Managing auto-enrollment, contribution tracking, investment options, participant communications, and compliance across potentially hundreds of thousands of workers requires a robust, experienced program administrator. That's precisely why the RFP process is so consequential — the vendor selected will effectively be the operational backbone of the program for years to come.
By simultaneously issuing an RFI for multi-state partnerships, Washington is signaling something equally important: a willingness to explore shared infrastructure, pooled resources, and coordinated governance with other states running similar programs. This is a forward-thinking procurement posture that deserves closer examination.
The RFP and RFI: Two Documents, One Strategic Vision
What the RFP Covers
The RFP for a program administrator is a formal solicitation designed to identify and select a vendor capable of handling the full operational scope of Washington Saves. Typically, an RFP of this nature would cover:
- Platform capabilities: The technology infrastructure needed to onboard employers, manage participant accounts, process contributions, and provide reporting.
- Investment management: The range of investment options offered to participants, including default investment selections.
- Customer service operations: Call centers, digital support, and multilingual capabilities to serve a diverse workforce.
- Compliance and regulatory expertise: Navigating federal ERISA exemptions, state law requirements, and ongoing regulatory changes.
- Fee structures: How the program administrator will be compensated, often through asset-based fees charged to participant accounts.
For vendors responding to this type of RFP, the bar is high. The state isn't just buying a software platform — it's selecting a long-term partner responsible for the financial futures of working Washingtonians.
What the RFI Reveals
The RFI for multi-state partnerships is arguably the more strategically interesting document. An RFI (Request for Information) is typically used earlier in the procurement lifecycle to gather market intelligence before formal solicitation. In this context, Washington is essentially asking: Who is out there, what have they built, and what would a collaborative model look like?
Multi-state partnerships in the retirement savings space could take several forms:
- Shared technology platforms where multiple states use the same administrative infrastructure
- Joint procurement where states collectively issue a single RFP to gain negotiating leverage with vendors
- Data-sharing agreements that allow states to track participant portability as workers move across state lines
- Coordinated regulatory frameworks that reduce compliance complexity for employers operating in multiple states
The potential benefits are substantial. States that pool their procurement power can negotiate better fee structures, share development costs for technology improvements, and create more seamless experiences for participants and employers. For vendors, multi-state partnerships mean larger, more stable contracts — but also more complex performance requirements.
Why Multi-State Procurement Collaboration Matters
The Washington Saves RFI for multi-state partnerships isn't happening in a vacuum. It reflects a growing recognition among state governments that going it alone on complex program administration is often inefficient and expensive.
Consider the economics: if Washington State has 500,000 potential program participants and a neighboring state has 400,000, a joint procurement might attract more sophisticated vendors, drive down per-participant administrative costs, and create a more robust competitive field than either state could achieve independently.
This model has precedents beyond retirement savings. Multi-state procurement consortiums exist in healthcare, technology infrastructure, and educational services. The National Association of State Procurement Officials (NASPO) and its ValuePoint cooperative purchasing program are prime examples of how states leverage collective buying power to achieve better outcomes.
For procurement professionals, the lesson is clear: when evaluating whether to pursue a standalone or collaborative procurement strategy, the analysis should go beyond immediate cost savings. Factors like long-term vendor stability, technology scalability, participant experience, and political sustainability all weigh in favor of thoughtful partnership structures.
Lessons for Procurement Professionals
Whether you're managing a public-sector procurement or running an RFP process in the private sector, the Washington Saves approach offers several practical takeaways.
Start With Market Intelligence Before You Formalize
The decision to issue an RFI before (or alongside) the RFP is a best practice that many organizations skip in their rush to get to vendor selection. An RFI allows you to:
- Understand the current vendor landscape and what solutions actually exist
- Identify potential partnership or consortium opportunities you hadn't considered
- Refine your RFP requirements based on what the market can realistically deliver
- Signal your intentions to the market and begin building vendor relationships early
If you're preparing an RFP for a complex program or service, consider whether a preliminary RFI or market sounding exercise would sharpen your procurement strategy. Tools like CreateYourRFP can help you structure both documents effectively, ensuring you ask the right questions at the right stage of the process.
Define Evaluation Criteria That Reflect Long-Term Value
One of the most common mistakes in RFP processes is over-weighting short-term cost at the expense of long-term value. For a program like Washington Saves, selecting a vendor based primarily on the lowest fee proposal could be disastrous if that vendor lacks the operational capacity to scale, the technology to adapt to regulatory changes, or the customer service infrastructure to support a diverse participant base.
Best-practice evaluation frameworks typically include:
- Technical capability (does the vendor have the platform and expertise to do the job?)
- Financial stability (will this vendor still be operating in five years?)
- Implementation approach (how will they manage the transition and go-live?)
- References and past performance (have they done this before, and successfully?)
- Total cost of ownership (what are all the costs over the contract term, not just the headline fee?)
Weighting these criteria transparently in your RFP — and communicating those weights to vendors — leads to better proposals and more defensible selection decisions.
Build Flexibility Into Your Contract Structure
Multi-state partnerships, by their nature, require contract structures that can accommodate changing membership, evolving regulatory requirements, and shifting participant volumes. Washington's interest in multi-state collaboration suggests they're thinking carefully about how to build a program that can grow and adapt.
For any long-term service contract, consider including:
- Performance benchmarks with defined remedies for underperformance
- Scalability provisions that address how pricing and service levels change as volume grows
- Technology refresh requirements to ensure the vendor keeps the platform current
- Exit and transition provisions that protect the program if the relationship needs to end
These structural elements are often negotiated after vendor selection, but they should be signaled in the RFP itself so that vendors understand the expectations from the outset.
Communicate Clearly and Consistently
Large-scale procurements like Washington Saves attract significant vendor interest, which means the procurement team will field many questions, clarification requests, and informal inquiries. Managing this communication process fairly and consistently is both a legal requirement in public procurement and a practical necessity for maintaining a competitive, credible process.
Best practices include:
- Posting all questions and answers publicly so all vendors have equal access to information
- Setting clear deadlines for questions, proposals, and follow-up communications
- Designating a single point of contact for vendor inquiries to prevent inconsistent messaging
- Documenting all vendor interactions to support the defensibility of the final selection decision
The Vendor Perspective: Responding to Complex Public-Sector RFPs
If you're a vendor considering a response to the Washington Saves RFP — or any complex public-sector solicitation — the multi-state angle adds both opportunity and complexity to your calculus.
On the opportunity side, a program administrator selected by Washington that also positions itself well for multi-state partnerships could find itself managing retirement savings programs across multiple states, representing a dramatically larger and more stable revenue base than a single-state contract.
On the complexity side, multi-state operations require:
- Technology platforms built for configurability across different state rules
- Compliance teams capable of monitoring regulatory developments in multiple jurisdictions
- Customer service operations that can handle diverse employer and participant populations
- Governance structures that satisfy multiple state oversight bodies simultaneously
Vendors who invest in building these capabilities — and who can articulate them clearly in their RFP responses — will have a significant competitive advantage as more states explore collaborative models.
When crafting your response, focus on telling a coherent story about your organization's capacity, not just listing features and capabilities. Evaluators reading dozens of proposals respond to vendors who demonstrate they understand the program's goals and can translate their capabilities into meaningful outcomes for participants.
The Bigger Picture: State-Sponsored Retirement Programs as a Procurement Frontier
Washington Saves is one of a growing number of state-sponsored retirement programs that represent a genuinely new frontier for public procurement. These programs sit at the intersection of financial services, technology, government administration, and social policy — which makes them both complex to procure and consequential to get right.
As more states launch or mature their programs, the procurement lessons learned in Washington, Oregon, Illinois, California, and elsewhere will shape how this space develops. Multi-state partnerships, if successfully implemented, could eventually lead to a small number of highly capable program administrators managing retirement savings for workers across many states — a consolidation that could drive both efficiency and innovation.
For procurement professionals watching this space, the key is to stay informed about how these programs are structured, how vendors are evolving their offerings, and how collaborative models are performing relative to standalone programs. The Washington Saves RFP and RFI together represent a snapshot of where sophisticated public procurement is heading.
Practical Next Steps for Your Own RFP Process
Whether you're in the public or private sector, the Washington Saves procurement offers a useful framework for thinking about your own RFP processes. Here are a few actionable steps to take away:
Assess whether a collaborative or consortium approach makes sense for your procurement. If other organizations in your sector are buying similar services, explore whether joint procurement could improve your outcomes.
Use RFIs strategically to gather market intelligence before committing to formal RFP requirements. The information you gather can dramatically improve the quality of your solicitation.
Invest in clear, well-structured RFP documents that communicate your requirements, evaluation criteria, and contract expectations unambiguously. Poorly written RFPs produce poor proposals. If you need support structuring your documents, tools like CreateYourRFP are designed to help organizations build professional, comprehensive RFPs efficiently.
Think long-term in your evaluation criteria — especially for complex, multi-year programs where vendor stability and adaptability matter as much as initial pricing.
Document everything — from market research and RFI responses through to final vendor selection — to ensure your process is transparent, defensible, and replicable.
The Washington Saves RFP and RFI process is still unfolding, and the ultimate outcomes — which vendor is selected, whether multi-state partnerships materialize, and how the program performs — will be worth watching closely. For now, the procurement approach itself offers a valuable model for anyone navigating complex, high-stakes vendor selection processes.