RFI- Automobile Insurance Shopping Access Solutions.docx

Request for Information (RFI)

Issue Date: 07/10/2026 RFI# 154-27-124146

Title: Automobile Insurance Shopping Access Solution

Commodity Codes

Issuing Agency: Commonwealth of Virginia Department of Motor Vehicles

Note: This public body does not discriminate against faith-based organizations in accordance with the Code of Virginia, § 2.2-4343.1 or against a bidder or offeror because of race, religion, color, sex, national origin, age, disability, sexual orientation, gender identity, political affiliation, veteran status, status as a military family, or any other basis prohibited by state law relating to discrimination in employment. Faith-based organizations may request that the issuing agency not include subparagraph 1.f in General Terms and Condition C. Such a request shall be in writing and explain why an exception should be made in that invitation to bid, request for information or request for proposal.

I. PURPOSE: The purpose of this RFI is to gather information from qualified vendors regarding available solutions that provide customers with access to automobile insurance shopping options through DMV digital channels. Information received from this RFI may aid in the development of an invitation for bid or request for proposals to solicit a vendor who can provide a “Click-to Action” button to the Virginia Department of Motor Vehicles.

This RFI is not a formal solicitation, and DMV will not award a contract based on a response to this RFI. Your response to this RFI is not a commitment to provide any products or services for the Department of Motor Vehicles or the Commonwealth of Virginia. This RFI is strictly a means of obtaining product information.

II. BACKGROUND: The Commonwealth is evaluating opportunities to support one of the Governor’s affordability initiatives by Identifying options that may assist Virginia residents with accessing automobile insurance shopping resources. DMV is exploring available marketplace solutions that may provide customers with convenient access to compare automobile insurance options through DMV digital channels.

DMV is seeking information to better understand available industry solutions, technology approaches, implementation considerations, data requirements, customer experience and potential financial models associated with these services.

III. SCOPE: The scope of this RFI Is to identify available solutions that provide DMV customers with direct access to automobile insurance shopping options. DMV is seeking information from qualified vendors regarding solutions that may include, but are not limited to:

Implementation Considerations

Vendors responding to this RFI should

1. Answer all proposed questions in as much detail as possible.

2. Provide supporting documentation; including examples of similar government or public sector customers, if available.

IV. RFI Questions A. Solution Overview

1. Provide an overview of your available solution, recommended approach, and how it would support DMV customers seeking automobile insurance shopping options.

2. Describe whether your solution is a static redirect/link, embedded functionality, hosted platform, SaaS solution, API-based integration, or another model.

B. Technical Requirements and Integration

3. Identify all technical requirements necessary to implement your solution, including system integration, infrastructure, software, authentication, user access, browser compatibility, APIs, and DMV resource requirements.

4. Does your solution require integration with DMV systems, websites, APIs, authentication tools, analytics tools, or other third-party systems? If yes, please describe.

5. Is your solution hosted by the vendor or a third party? If yes, describe the hosting environment and whether it is cloud-based C. Data Exchange, Privacy & Security

6. Identify any customer or DMV data required for your solution. Describe whether data would be transmitted, stored, processed, accessed or used to prepopulate information.

7. Identify whether DMV provided data can be used to prepopulate quote information and describe required data elements

8. Would any information be transmitted back to DMV after a customer clicks the button, requests a quote, accepts a quote, or purchases a policy?

9. Describe your security, privacy, and data protection practices.

10. Is your solution currently approved through COVRamp, FedRAMP, SOC 2, or another security/compliance review? If yes, please provide details.

11. If your solution is not currently approved through COVRamp, describe your ability and willingness to complete required Commonwealth security/cloud review processes.

D. Reporting, Analytics & Revenue Model

12. Does your solution support reporting or analytics, including click activity, referral counts, quote activity, conversion activity, or revenue/reimbursement tracking?

13. Describe your pricing model, including one-time implementation costs, licensing, subscription fees, transaction/referral fees, revenue share, maintenance, hosting, or other costs.

14. Describe any available revenue, reimbursement, or compensation models associated with your solution, including but not limited to referral fees, cost-per-click arrangements, transaction-based compensation, revenue sharing arrangements, or other financial structures if applicable.

15. Explain how revenue is calculated, tracked, reported, audited, and remitted to participating agencies.

16. Identify whether your solution allows DMV to participate without generating revenue or financial compensation.

E. Customer Experiences & Insurance Marketplace Operations

17. Describe how insurance providers are selected, displayed, ranked, or presented to customers. Explain whether results are neutral, sponsored, paid placement, or influenced by insurer relationships.

18. Describe how customers are informed they are leaving DMV services or engaging with a third-party provider.

19. Identify which entity owns and manages customer interactions, customer support, complaints, and insurance-related inquiries after the customer accesses the solution.

20. Describe compliance with accessibility requirements, including WCAG standards or other applicable digital accessibility standards.

F. Implementation & Experience

21. Describe your implementation timeline, ongoing support, maintenance, updates, and any required DMV resources.

22. Provide examples of similar solutions implemented for government, DMV, transportation, insurance, or public-sector customers

V. Submitting a Response Interested vendors should submit a response providing detailed answers to all RFI questions referenced in Section IV, along with supporting documentation.

All responses shall be submitted electronically through eVA. Responses will be accepted until 4:00 PM EST July 31, 2026.

For any questions regarding this RFI, please contact Procurement officer Tammy Harrison, via E mail only at: Tammy.Harrison@dmv.virginia.gov by 2:00 PM EST July 24th, 2026.

image1.png image2.jpg