RFQ 27-05706 for Enterprise Customer and Relationship Platform 09.17.26.docx

DOCX document 81 KB Posted

Attached to
RFI 27-05706 for Customer and Relationship Platform
Solicitation number
BD-27-1060-ITD00-ITD00-133583
Issued by
Suffolk County, Massachusetts

About this file

This is a Request for Quotation (RFQ) document issued by the Commonwealth of Massachusetts for an Enterprise Customer and Relationship Platform solution. The RFQ seeks comprehensive enterprise capabilities encompassing customer and organizational relationship management, sales and account processes, service interactions, engagement and workflow automation, data analytics, legal case management, security, and accessibility features. The document serves as a formal solicitation following an earlier Request for Information (RFI 27-05706) that gathered industry feedback on potential solutions. The RFQ specifies detailed technical requirements, functional specifications, and evaluation criteria for vendors interested in providing an integrated platform to support the state's customer relationship and business process management needs.

The RFQ document outlines pricing structures, vendor qualifications, response requirements, and contract terms necessary for interested parties to prepare competitive proposals. The solicitation includes specifications for implementation timelines, ongoing support and maintenance requirements, data security and compliance standards, and integration capabilities with existing state systems. Vendors are evaluated based on their ability to meet functional and technical requirements, demonstrated experience with similar implementations, pricing competitiveness, and proposed service level agreements. The contract award and implementation schedule, along with any renewal or extension options, are specified within the RFQ to provide vendors with a clear understanding of the engagement terms and the state's expectations for service delivery and long-term platform management.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

EOTSS RFI 27-05706

Commonwealth of Massachusetts The Executive Office of Technology Services and Security

Commonwealth of Massachusetts Executive Office of Technology Services and Security

Request for Information Enterprise Customer and Relationship Platform

EOTSS RFI 27-05706

COMMBUYS Bid Number: BD-27-1060-ITD00-ITD00-133583

September 17, 2026

Respondents to this Request for Information (RFI) are invited to respond to any or all of the questions in this document. Responses to this RFI shall serve solely to assist the Commonwealth in understanding the current state of the marketplace with regards to the solicited information or to inform the development of a possible solicitation for a Request for Responses (RFR) or Request for Quotes (RFQ) in the future. This RFI does not in any way obligate the Commonwealth to issue or amend a solicitation or to include any of the RFI provisions or responses in any solicitation. Responding to this RFI is entirely voluntary, and will in no way affect the Commonwealth’s consideration of any proposal submitted in response to any subsequent solicitation, nor will it serve as an advantage or disadvantage to the respondent in the course of any RFR or RFQ that may be subsequently issued or amended.

IN ACCORDANCE WITH M.G.L. C. 66 AND M.G.L. C. 4, § 7 (26), THIS RFI AND ALL RESPONSES HERETO INCLUDING THE WINNING BID SHALL BECOME PUBLIC RECORD, AND CAN BE OBTAINED FROM THE EXECUTIVE OFFICE OF TECHNOLOGY SERVICES AND SECURITY BY SUBMITTING A REQUEST AT https://www.mass.gov/executive-office-of-technology-services-and-security-prr. ANY PORTIONS OF A RESPONSE THAT ARE LABELED AS CONFIDENTIAL WILL STILL BE CONSIDERED PUBLIC RECORD.

General Procurement Information

General Information

Purchasing Entity: Executive Office of Technology Services and Security (“EOTSS”) or (“Agency”)

Address: One Ashburton Place, Eighth Floor, Boston, MA 02108

Procurement Contact: Shawn Johnson

Telephone: 617-626-4593

E-Mail Address: shawn.johnson@mass.gov

RFI File Number and Title: EOTSS RFI 27-05706 - Enterprise Customer and Relationship Platform

Attachments: Attachment A – COMMBUYS Instructions

Forms: Vendor Response Matrix and Required Appendices (included in Section II)

This Request for Information (“RFI”) does not commit the Commonwealth of Massachusetts (“Commonwealth”) or Agency to pay any costs incurred in the preparation of a Bidder’s response to this RFI or to purchase any products or services. The purpose of this RFI is to elicit the advice and best analysis of knowledgeable persons in the vendor community to enable the Commonwealth to craft a potential future solicitation for Enterprise Customer and Relationship Platform. Responses to this RFI should include information that will be useful to the Commonwealth in subsequently drafting more detailed procurement solicitation(s) related to the Enterprise Customer and Relationship Platform.

The Agency may amend this RFI at any time prior to the date the responses are due. Any such amendment will be posted to the Commonwealth’s procurement website, CommBUYS (www.commbuys.com).

Bidders must submit their bids through the Commonwealth’s online procurement system, COMMBUYS, as detailed in Attachment A. Bidders are advised to check this site regularly, as this will be the sole method used for notification of changes.

Eligible Bidders

This RFI is open to all Bidders. For future planning, Bidders are encouraged to describe their ability to offer their proposed solution under Massachusetts Statewide Contracts, whether for direct-sale as an existing Statewide Contract vendor, or for resale through existing agreement with a current Statewide Contract reseller.

Event Calendar

All times in this RFI are in prevailing Eastern Time. Responses must be received no later than the response due date and time indicated below or they will not be evaluated. Bidders must have their responses fully loaded and accepted in COMMBUYS prior to the RFI Response Due date and time listed below. Bidders are urged to allow sufficient time to upload their entire response.

Procurement Step
Due Date
Time
RFI Release Date
9/17/2026
3:00 PM
Bidder Questions Due
9/28/2026
3:00 PM
Commonwealth Responses posted to COMMBUYS (estimated date)
10/2/2026
3:00 PM
RFI Response Due
10/16/2026
3:00 PM

Issuing Agency

The Executive Office of Technology Services and Security is responsible for the development of IT policy and implementation and oversight of all information technology investments for the Commonwealth and its respective agencies. EOTSS has broad statutory authority to effectuate the goals prompting IT consolidation in Chapter 64 of the Acts of 2017, as memorialized and articulated in M.G.L. c. 6A, s. 7A and M.G.L. c. 7D. As the lead enterprise IT and cybersecurity organization for the Executive Branch, EOTSS provides responsive digital and security services, and oversees and manages the enterprise technology and digital infrastructure and services for over 125 state agencies and over 43,000 state employees. EOTSS provides Enterprise Cybersecurity and Risk Management services, Infrastructure and Network services, End-User Support and IT services, Digital and Data services, Strategy Management and Consulting services, and additional IT-focused services to the Executive Branch and other Commonwealth users.

Description and Purpose of the RFI

Purpose

The purpose of the Enterprise Platform initiative is to identify the best-fit enterprise platform for EOTSS current and future business requirements. This RFI seeks information from qualified vendors regarding enterprise capabilities for customer and organizational relationships, sales and account processes, service interactions, engagement, workflow, data, analytics, automation, legal case management, security, accessibility, and related business processes.

EOTSS is seeking factual information regarding functional breadth, architecture, integration, data, security and compliance posture, accessibility, scalability, administration, implementation, commercial structure, total cost of ownership, and long-term platform strategy. Detailed requirements and standardized vendor-response expectations are provided below.

Information Solicited

Background.

EOTSS supports a complex Commonwealth enterprise environment spanning multiple organizations and operating entities. The desired platform should provide a durable foundation for enterprise relationship management and related business processes while supporting hierarchical administration and billing, integration with the broader enterprise technology ecosystem, strong governance and security controls, accessible digital experiences, transparent commercial packaging, and future vetted AI capabilities.

Detailed Requirements and Questions.

Each Respondent must address the detailed requirements and appendices that follow using the published Requirement IDs and standardized response values. Clearly identify configuration, low-code, custom development, third-party, professional-services, partner, and roadmap dependencies.

Table of Contents

0. Material Assumptions

1. Executive Overview

2. Business Capability Scope

2.1 Hierarchical Account, Administration, and Billing

3. Customer and Relationship Management

4. Sales and Revenue Processes

5. Service and Customer Support

6. Customer Engagement

7. Workflow and Business Process Automation

8. Platform and Extensibility

9. Data Architecture

10. Integration Architecture

11. Artificial Intelligence

12. Security, Risk, and Compliance

12.1 Security Certifications, Authorizations, Attestations, and Compliance Posture

13. Scalability, Reliability, and Performance

14. User Experience

14.1 Accessibility and Inclusive-Design Compliance

15. Analytics and Reporting

16. Administration and Governance

17. Implementation Approach

18. Data Onboarding and Transition

19. Commercial Model and Total Cost of Ownership

20. Product and Vendor Strategy

21. Vendor Response Matrix

22. Questions Designed to Expose Hidden Cost and Complexity

23. Questions Vendors Must Answer Without Marketing Language

24. Future-State and Innovation Questions

25. Enterprise Qualification Questions

26. Required Appendices Requirements EOTSS seeks information on an enterprise customer and relationship platform that can serve as a governed foundation for customer, organization, contact, relationship, sales, service, engagement, workflow, data, analytics, automation, legal case management, and related business processes across multiple Commonwealth entities. The platform should support enterprise-scale administration and billing hierarchies, integration with the broader technology ecosystem, security and accessibility, transparent commercial packaging, data portability, and vetted AI capabilities. Responses should distinguish native capability from configuration, low-code, custom development, third-party products, professional services, partner dependencies, and roadmap functionality.

0. Material Assumptions

Requirement ID
Priority
Requirement
ASM-001
Critical
What assumptions about scale, organizational structure, architecture, delivery model, governance, licensing, or customer responsibilities materially shape your proposed solution, and what would change if those assumptions differ?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

1. Executive Overview

Requirement ID
Priority
Requirement
EXE-001
High
How would your proposed enterprise customer and relationship platform serve as a durable foundation for managing customers, organizations, contacts, relationships, sales and account processes, service interactions, engagement, workflow, data, analytics, automation, legal case management, and related business processes across the Commonwealth?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

2. Business Capability Scope

Requirement ID
Priority
Requirement
CAP-001
Critical
How does your platform deliver the required enterprise business capabilities across relationship management, sales, service, engagement, workflow, content, reporting, analytics, AI-assisted work, data management, self-service, mobile use, administration, and extensibility, and where are material gaps or external dependencies?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

2.1 Hierarchical Account, Administration, and Billing

Requirement ID
Priority
Requirement
HAB-001
Critical
How would your solution support an EOTSS master administrative account, Secretariat or Independent Entity sub-accounts, and agency or department child accounts with delegated administration, policy inheritance, usage and entitlement visibility, billing attribution, roll-up reporting, and auditable lifecycle management?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

3. Customer and Relationship Management

Requirement ID
Priority
Requirement
CRM-001
Critical
How does your platform model and maintain people, organizations, accounts, affiliations, hierarchies, interactions, cases, communications, preferences, history, identity resolution, and a governed unified relationship view across business functions and data sources?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

4. Sales and Revenue Processes

Requirement ID
Priority
Requirement
SAL-001
High
How does your platform support lead, prospect, opportunity, account planning, activity, pipeline, and forecasting processes, including configuration, extensibility, analytics, approvals, and any separately licensed or third-party dependencies?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

5. Service and Customer Support

Requirement ID
Priority
Requirement
SVC-001
Critical
How does your platform support enterprise case and request management, routing, service levels, knowledge, self-service, contact-center integration, agent productivity, and configurable legal case management with appropriate security, audit, and reporting controls?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

6. Customer Engagement

Requirement ID
Priority
Requirement
ENG-001
High
How does your platform support governed customer engagement across segmentation, journeys, communications, digital channels, consent and preferences, and campaign capabilities, and which elements are native, integrated, partner-provided, or separately licensed?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

7. Workflow and Business Process Automation

Requirement ID
Priority
Requirement
WFL-001
Critical
How does your platform design, execute, govern, monitor, version, test, deploy, recover, and audit automated and human-in-the-loop business processes across platform and external systems, including applicable quotas and licensing limits?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

8. Platform and Extensibility

Requirement ID
Priority
Requirement
PLT-001
Critical
How can EOTSS configure and extend the platform through metadata, low-code/no-code, APIs, events, SDKs, reusable components, and custom development while preserving security, observability, lifecycle governance, upgradeability, and supportability?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

9. Data Architecture

Requirement ID
Priority
Requirement
DAT-001
Critical
How does your platform participate in enterprise data architecture, including its data model, master-data and system-of-record patterns, quality, lineage, synchronization or federation, retention, residency, bulk interfaces, and customer data and metadata portability?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

10. Integration Architecture

Requirement ID
Priority
Requirement
INT-001
Critical
How does your platform integrate through APIs, events, messaging, webhooks, batch, identity, and middleware patterns, and what limits, monitoring, failure handling, versioning, licensing, premium connectors, or third-party dependencies apply?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

11. Artificial Intelligence

Requirement ID
Priority
Requirement
AI-001
Critical
What generally available AI capabilities can be used with the platform, and how are model choice, data use and training, security, privacy, governance, human oversight, evaluation, licensing, consumption, cost controls, and the ability to restrict or disable AI managed?

To what extent does the solution align with EOTSS’ GenAI Policy: www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy/download

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

12. Security, Risk, and Compliance

Requirement ID
Priority
Requirement
SEC-001
Critical
How does the proposed solution protect enterprise data and operations through identity, least-privilege authorization, encryption and key management, audit logging, monitoring, vulnerability and incident management, privacy, residency, and independently evidenced security and compliance controls?

To what extent can the solution accommodate the following data types:

· Personally Identifiable Information

· Payment Card Information

· Family Educational Rights and Privacy Act Data

· Protected Health Information

· Federal Tax Return Information

· Criminal Offender Record Information

· Criminal Justice Information

· Social Security Administration Data

· Active FedRamp Certification (Y/N, level)

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

12.1 Security Certifications, Authorizations, Attestations, and Compliance Posture

Requirement ID
Priority
Requirement
SEC-CERT-001
Critical
What current certifications, authorizations, attestations, assessments, and regulated-data compliance claims apply specifically to the proposed products, services, hosting environments, regions, and SKUs, and what scope, exceptions, inherited controls, customer responsibilities, and incremental costs apply?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

13. Scalability, Reliability, and Performance

Requirement ID
Priority
Requirement
SRP-001
Critical
What documented production scale, performance characteristics, availability commitments, operating limits, resiliency and disaster-recovery objectives, and comparable enterprise deployment evidence demonstrate that the proposed architecture can support Commonwealth-wide use?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

14. User Experience

Requirement ID
Priority
Requirement
UX-001
High
How does the platform provide accessible, responsive, role-appropriate experiences for employees, administrators, developers, external users, and mobile users, including configurable workspaces, self-service, supported devices, and evidence of usable enterprise-scale performance?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

14.1 Accessibility and Inclusive-Design Compliance

Requirement ID
Priority
Requirement
ACC-001
Critical
How does each material user experience in the proposed scope conform to applicable WCAG, Section 508, and EOTSS accessibility requirements, and what current product-specific VPAT/ACR evidence, known exceptions, testing results, remediation commitments, dependencies, and costs apply?

To what extent does the solution comply with the Commonwealth’s Enterprise Digital Accessibility Policy?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

15. Analytics and Reporting

Requirement ID
Priority
Requirement
ANL-001
High
How does the platform provide governed operational reporting, dashboards, ad hoc analysis, embedded analytics, and integration with enterprise BI and data platforms, including refresh, scale, query, export, retention, security, and licensing limits?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

16. Administration and Governance

Requirement ID
Priority
Requirement
ADM-001
Critical
How does the platform support centralized governance and delegated administration across business units, account levels, environments, configurations, releases, security, audit, usage, capacity, licensing, health, and operational lifecycle management?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

17. Implementation Approach

Requirement ID
Priority
Requirement
IMP-001
Critical
How would you implement the proposed platform in a complex Commonwealth enterprise, including methodology, governance, target architecture, resources, configuration, integration, testing, deployment, organizational readiness, hypercare, timeline, dependencies, and major risks?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

18. Data Onboarding and Transition

Requirement ID
Priority
Requirement
DTR-001
Critical
How would you discover, profile, cleanse, map, transform, load, validate, reconcile, cut over, and monitor existing enterprise data while addressing history, documents, permissions, quality, retention, federation or archival options, restart/recovery, and contingency planning?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

19. Commercial Model and Total Cost of Ownership

Requirement ID
Priority
Requirement
COM-001
Critical
How is the complete commercial model structured across user and platform licensing, editions, environments, storage, integrations, automation, analytics, AI, support, services, third parties, consumption and overage, and what five-year TCO and SKU-level assumptions should EOTSS use to model Small, Medium, and Large environments?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

20. Product and Vendor Strategy

Requirement ID
Priority
Requirement
VEN-001
High
How do product maturity, enterprise adoption, roadmap and investment priorities, security investment, partner ecosystem, customer support, financial viability, and known material limitations demonstrate your ability to sustain a multi-year enterprise platform relationship?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

21. Vendor Response Matrix

Requirement ID
Priority
Requirement
VRM-001
Critical
How should EOTSS classify your support for each requirement as generally available, configured, low-code, custom, third-party, roadmap, or unsupported, and what evidence, dependencies, limitations, and commercial impacts explain that classification?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

22. Total Cost and Implementation Considerations

Requirement ID
Priority
Requirement
HCC-001
Critical
Please identify any material technical, operational, licensing, service, partner, capacity, environment, storage, integration, AI, security, reporting, portability, upgrade, organizational hierarchy, transition, product lifecycle, or commercial packaging considerations that may affect total cost, implementation complexity, ongoing customer effort, or the Commonwealth’s ability to maintain, transition, or adapt the solution over time.

Where applicable, please identify significant dependencies, assumptions, or limitations, including circumstances in which additional products, services, licensing, configuration, development, or customer resources may be required. Please also describe relevant product and licensing lifecycle practices, including end-of-sale or end-of-life practices, successor or replacement offerings, SKU or packaging changes, and circumstances in which functionality included in an existing offering may transition to a different product, edition, tier, or separately licensed offering.

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

23. Capability Maturity and Supporting Experience

Requirement ID
Priority
Requirement
NML-001
Critical
For material capabilities described in your response, please indicate their current level of availability and maturity, including whether they are generally available and in production use today or require configuration, customization, development, third-party products or services, or professional services.

Please also identify material limitations or dependencies; relevant roadmap items; significant additional costs or customer responsibilities; and, where available, examples of comparable production implementations or other evidence demonstrating the capability in practice.

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

24. Future-State and Innovation Questions

Requirement ID
Priority
Requirement
FSI-001
High
What practical future-state opportunities would you recommend to simplify processes, improve data and customer experience, increase governed automation and vetted AI use, strengthen operating effectiveness, and reduce total cost of ownership while distinguishing current capability from roadmap concepts?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

25. Enterprise Qualification Questions

Requirement ID
Priority
Requirement
ENT-001
Critical
What quantitative scale, governance, security, resiliency, integration, extensibility, data, administration, compliance, support, roadmap, partner-ecosystem, and financial evidence demonstrates that the proposed platform is suitable for sustained enterprise-wide Commonwealth use rather than a departmental or niche deployment?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

26. Required Appendices

Requirement ID
Priority
Requirement
APP-001
Critical
What concise supporting appendices and evidence can you provide to substantiate your response, including vendor profile, architecture, integration, data, security, AI, accessibility, implementation, resources, risks, assumptions, exceptions, roadmap, references, commercial details, five-year TCO, and vendor commitments?

Vendor response: Provide a concise factual response, identify material dependencies or limitations, and cite supporting evidence where available.

General Instructions

Please note that this RFI is issued solely for the purpose of obtaining information. Nothing in this RFI shall be interpreted as a commitment on the part of the Commonwealth to enter into a contract with any Respondent.

· This RFI has been posted on September 17, 2026.

· Respondent Questions. Potential Respondents who have questions regarding this RFI may submit them via COMMBUYS to the contact listed in Section 1 above by September 28, 2026. Respondents may only make inquiries and request clarification concerning this RFI by written questions via e-mail. Responses to inquiries and clarification questions will be provided electronically to all interested parties via a posting on COMMBUYS.

· Informational Sessions. There will be no informational session associated with this RFI.

· Response Submission. All responses to this RFI are due no later than 3:00 PM on October 16, 2026. Respondents should submit one (1) electronic copy via COMMBUYS. All responses must include on the first page the official name (if any) of the firm or entity submitting the response. Please consecutively number all pages of the response.

· Response Content. Vendors should provide a response to each applicable requirement and question in Section II and complete all required response matrices and appendices.

· Response Format. The Commonwealth requests a point-by-point response using the Requirement IDs and standardized response values in Section II. If a Respondent does not respond to an item, the response should state that fact and, where possible, explain the reason.

· Additional Information. The Commonwealth retains the right to request additional information from Respondents. The Commonwealth may, at its sole discretion, elect to request formal presentations from certain vendors and/or create an RFR or RFQ which will include the detailed requirements and key success criteria for the procurement and be based, at least in part, on the responses received from this RFI. The Commonwealth may request further explanation or clarification from any and all Respondents during the review process.

Miscellaneous

Enterprise Information Security Standards and Policies

All products and services provided to the Commonwealth must comply with all applicable policies adopted by the Agency, which shall be made available to Bidder prior to contract execution. At a minimum, all goods and services provided to the Commonwealth must comply with the Enterprise Information Security Standards and Policies (https://www.mass.gov/handbook/enterprise-information-security-policies-and-standards). As applicable, Bidders shall provide information that demonstrates that their security practices meet the requirements detailed in these policies.

Accessibility for IT Solutions Contract Language

The Commonwealth of Massachusetts’ Enterprise Digital Accessibility Policy drives ongoing efforts to make Massachusetts’ Digital Assets, including those delivered by a third-party, accessible and usable by all persons as required by state and federal laws. Where a Deliverable includes a Digital Asset, such Deliverable must meet the Commonwealth’s Digital Accessibility Standards.

The Commonwealth’s Digital Accessibility Standards include the Web Content Accessibility Guidelines (WCAG) version 2.1 level A and AA developed by the World Wide Web Consortium (W3C). Bidder must comply with the digital accessibility obligations set forth in the Vendor Digital Accessibility Contract Language and Vendor Digital Accessibility Testing Obligations and any subsequent versions or amendments.

During the bidding process and upon request, Bidder shall cooperate and provide the Commonwealth, or any third-party digital accessibility service provider procured by the Commonwealth, access to test its digital products for accessibility at no additional cost to the Commonwealth, if applicable.

Promotional Materials

Bidder must not reference the Agency or the Commonwealth in any promotional or marketing materials, including but not limited to use of the Agency’s or the Commonwealth’s name or logo, without first obtaining the Agency’s prior written approval for such use. Bidder must not use the Commonwealth’s seal in any promotional or marketing materials.

Bidders are discouraged from including extraneous promotional or marketing materials in their responses to this RFI and excessive promotional or marketing materials may detract from the Bidders’ overall score.

Review Rights

Responses to this RFI may be reviewed and evaluated by any person(s) at the discretion of the Agency including non-allied and independent consultants retained by the Agency for the sole purpose of evaluating and analyzing responses.

No Reimbursement.

By submitting a response, Respondents agree that any cost incurred in responding to this RFI, or in support of activities associated with this RFI, shall be the sole responsibility of Respondent. The Commonwealth shall not be held responsible for any costs incurred by Respondents in preparing their respective responses to this RFI.

EOTSS GenAI Policy

The Commonwealth consistently seeks to realize the benefits of new technology, in particular generative artificial intelligence (AI). Contractor must comply with the Enterprise Use and Development of Generative Artificial Intelligence Policy issued by EOTSS on January 31, 2025, as it may be amended from time to time. Please follow this link to the policy: www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy/download.

Bidder Responses

Bidders must provide a complete point-by-point response to Section II, including the standardized capability response matrix, security/compliance and accessibility disclosures, commercial schedules, five-year TCO, sample bills, and required appendices.

ATTACHMENT A – COMMBUYS Instructions

Interested Bidders must submit their response using COMMBUYS.

Useful links:

1. Job aid on how to submit a quote: https://www.mass.gov/doc/how-to-create-a-quote-in-commbuys/download

1. Webcast: How to Locate and Respond to a Bid in CommBuys, which will familiarize bidders with CommBuys terminology, basic navigation, and provide guidance for locating bid opportunities in CommBuys and submitting an online quote.

1. Bidders MUST have their complete bid fully loaded and submitted prior to the time and date listed in the calendar. COMMBUYS will not allow for bids to be submitted after the posted time.

Bidder may contact the CommBuys Help Desk at CommBuys@state.ma.us or call during normal business hours (8AM – 5PM, Monday – Friday) at 1-888-627-8283 or 617-720-3197.

Written questions via the Bid Q&A on COMMBUYS

The “Bid Q&A” provides the opportunity for Bidders to ask written questions and receive written answers from the Strategic Sourcing Team (SST) regarding this Bid. All Bidders’ questions must be submitted through the Bid Q&A found on COMMBUYS (see below for instructions). Questions may be asked only prior to the Deadline for Submission of Questions stated in the Procurement Calendar. The issuing department reserves the right not to respond to questions submitted after this date. It is the Bidder’s responsibility to verify receipt of questions.

Please note that any questions submitted using any other medium (including those that are sent by mail, fax, email or voicemail, etc.) will not be answered. To reduce the number of redundant or duplicate questions, Bidders are asked to review all questions previously submitted to determine whether the Bidder’s question has already been posted.

Bidders are responsible for entering content suitable for public viewing, since all of the questions are accessible to the public. Bidders must not include any information that could be considered personal, security sensitive, inflammatory, incorrect, collusory, or otherwise objectionable, including information about the Bidder’s company or other companies. The PMT reserves the right to edit or delete any submitted questions that raise any of these issues or that are not in the best interest of the Commonwealth or this Bid.

All answers are final when posted. Any subsequent revisions to previously provided answers will be dated.

It is the responsibility of the prospective Bidder and awarded Bidder to maintain an active registration in COMMBUYS and to keep current the email address of the Bidder’s contact person and prospective contract manager, if awarded a contract, and to monitor that email inbox for communications from the Purchasing Department, including requests for clarification. The Purchasing Department and the Commonwealth assume no responsibility if a prospective Bidder’s/awarded Bidder’s designated email address is not current, or if technical problems, including those with the prospective Bidder’s/awarded Bidder’s computer, network or internet service provider (ISP) cause email communications sent to/from the prospective Bidder/Awarded Bidder and the Purchasing Department to be lost or rejected by any means including email or spam filtering.

Locating Bid Q&A

Log into COMMBUYS, locate the Bid, acknowledge receipt of the Bid, and scroll down to the bottom of the Bid Header page. The “Bid Q&A” button allows Bidders access to the Bid Q&A page.

Appendix B – Vendor Response Form

Commonwealth of Massachusetts The Executive Office of Technology Services and Security

Commonwealth of Massachusetts Executive Office of Technology Services and Security

Vendor Response Form Enterprise Customer and Relationship Platform

EOTSS RFI 27-05706

COMMBUYS Bid Number: BD-27-1060-ITD00-ITD00-133583

September 17, 2026

Respondents to this Request for Information (RFI) are invited to respond to any or all of the questions in this document. Responses to this RFI shall serve solely to assist the Commonwealth in understanding the current state of the marketplace with regards to the solicited information or to inform the development of a possible solicitation for a Request for Responses (RFR) or Request for Quotes (RFQ) in the future. This RFI does not in any way obligate the Commonwealth to issue or amend a solicitation or to include any of the RFI provisions or responses in any solicitation. Responding to this RFI is entirely voluntary, and will in no way affect the Commonwealth’s consideration of any proposal submitted in response to any subsequent solicitation, nor will it serve as an advantage or disadvantage to the respondent in the course of any RFR or RFQ that may be subsequently issued or amended.

IN ACCORDANCE WITH M.G.L. C. 66 AND M.G.L. C. 4, § 7 (26), THIS RFI AND ALL RESPONSES HERETO INCLUDING THE WINNING BID SHALL BECOME PUBLIC RECORD, AND CAN BE OBTAINED FROM THE EXECUTIVE OFFICE OF TECHNOLOGY SERVICES AND SECURITY BY SUBMITTING A REQUEST AT https://www.mass.gov/executive-office-of-technology-services-and-security-prr. ANY PORTIONS OF A RESPONSE THAT ARE LABELED AS CONFIDENTIAL WILL STILL BE CONSIDERED PUBLIC RECORD.

Vendor Response Matrix Instructions: Provide one concise response for each category below. Responses should be factual and open-ended, identify supporting evidence, assumptions, dependencies, limitations, and commercial impacts, and select the

Vendor / Respondent

Primary Contact

Response Date

0. Material Assumptions

Requirement ID
Vendor Response

ASM-001

1. Executive Overview

Requirement ID
Vendor Response

EXE-001

2. Business Capability Scope

Requirement ID
Vendor Response

CAP-001

2.1 Hierarchical Account, Administration, and Billing

Requirement ID
Vendor Response

HAB-001

3. Customer and Relationship Management

Requirement ID
Vendor Response

CRM-001

4. Sales and Revenue Processes

Requirement ID
Vendor Response

SAL-001

5. Service and Customer Support

Requirement ID
Vendor Response

SVC-001

6. Customer Engagement

Requirement ID
Vendor Response

ENG-001

7. Workflow and Business Process Automation

Requirement ID
Vendor Response

WFL-001

8. Platform and Extensibility

Requirement ID
Vendor Response

PLT-001

9. Data Architecture

Requirement ID
Vendor Response

DAT-001

10. Integration Architecture

Requirement ID
Vendor Response

INT-001

11. Artificial Intelligence

Requirement ID
Vendor Response

AI-001

12. Security, Risk, and Compliance

Requirement ID
Vendor Response

SEC-001

12.1 Security Certifications, Authorizations, Attestations, and Compliance Posture

Requirement ID
Vendor Response

SEC-CERT-001

13. Scalability, Reliability, and Performance

Requirement ID
Vendor Response

SRP-001

14. User Experience

Requirement ID
Vendor Response

UX-001

14.1 Accessibility and Inclusive-Design Compliance

Requirement ID
Vendor Response

ACC-001

Analytics and Reporting

Requirement ID
Vendor Response

ANL-001

16. Administration and Governance

Requirement ID
Vendor Response

ADM-001

17. Implementation Approach

Requirement ID
Vendor Response

IMP-001

18. Data Onboarding and Transition

Requirement ID
Vendor Response

DTR-001

19. Commercial Model and Total Cost of Ownership

Requirement ID
Vendor Response

COM-001

20. Product and Vendor Strategy

Requirement ID
Vendor Response

VEN-001

21. Vendor Response Matrix

Requirement ID
Vendor Response

VRM-001

22. Total Cost and Implementation Considerations

Requirement ID
Vendor Response

HCC-001

23. Capability Maturity and Supporting Experience

Requirement ID
Vendor Response

NML-001

24. Future-State and Innovation Questions

Requirement ID
Vendor Response

FSI-001

25. Enterprise Qualification Questions

Requirement ID
Vendor Response

ENT-001

26. Required Appendices

Requirement ID
Vendor Response

APP-001

image1.png

File details come from the government source that posted it. Updated .