Solicitation Amendment M0026326QR0010002 SF 30.pdf

R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Section C - Description/Specifications/Statement of Work

Miscellaneous text in this section has been modified to:

See Attachment in section J for Performance Work Statement. (Updated 4/8/2026)

M0026326QR0010002

Section J - List of Attachments

The following attachments were added:

PWS Revised

The following attachments were deleted:

PWS

Section L - Instructions, Conditions, & Notices to Offerors or Quoters

Miscellaneous text in this section has been modified to:

Miscellaneous text in this section has been modified:

RFQ No. M0026226QR001

Prospect Messaging Licenses

Industry Questions and Government Responses

1. Industry Question: Does this project require the entire platform and all related services to be completely embedded into a FedRAMP operation?

: Government Response The potential vendors must obtain FedRAMP certification. The process occurs outside the agency (with a third-party accreditation vendor or the FedRAMP joint authorization board (JAB).

2. Industry Question: Message Volume Clarification (PWS 5.1.4) PWS 5.1.4 specifies "up to 40,000 SMS text messaging communications per month from each license." To appropriately size infrastructure capacity, can the Government clarify whether this represents maximum peak capacity expected during surge recruiting periods, or anticipated average monthly usage per recruiter across normal operations?

Government Response: PWS 5.1.4 represents anticipated average monthly usage per recruiter.

3. Industry Question: FedRAMP IL4 Authorization Timeline (PWS 5.1) PWS 5.1 requires FedRAMP Impact Level 4 authorization. Can the Government confirm whether FedRAMP IL4 authorization must be completed prior to proposal submission (April 8, 2026), or may authorization activities occur during the implementation period between contract award and operational delivery (September 22, 2026), with interim security authorization in place?

Government Response: FedRAMP authorization must be completed prior to quote submission.

4. Industry Question: Infrastructure Deployment Approach (PWS 5.1) Does the Government require a standalone FedRAMP IL4 authorization specific to the messaging application itself, or will platforms deployed within already-authorized FedRAMP High cloud environments

(AWS GovCloud, Azure Government Cloud) with component-level security authorization and RMF compliance be considered acceptable?

: Government Response The Government does not require a stand-alone FEDRAMP IL4 authorization specific to the messaging application. Platforms deployed within already-authorized FedRAMP High cloud environments with component-level security authorization and RMF compliance will be considered acceptable.

5. Industry Question: Pricing Structure Format (Section B) Section B includes a Base Year (CLIN 0001) and three Option Years. Should offerors submit a single all-inclusive unit price per license for each CLIN, or does the Government expect an itemized cost breakdown by component (platform licensing, messaging delivery, help desk support, security maintenance)?

Government Response: Please provide Government with all-inclusive unit price per license for each clin.

6. Industry Question: IDIQ Maximum Quantity Utilization (Section B) Section B specifies a Government maximum of 1,400 total licenses that may be ordered over the contract term (minimum 350). Can the Government clarify the anticipated utilization timeline for orders beyond the base 350 licenses? Specifically: (a) Will additional license orders occur within the base year, or primarily during option years? (b) Are additional licenses intended for expansion within Marine Corps Recruiting Command, or for other Marine Corps commands /sibling services? (c) Should offeror's structure pricing to incentivize larger orders through volume-based discounts, or maintain flat per-license pricing across all order quantities?

:Government Response As stated in the chart in section B, the government estimates ordering 350 licenses per clin with defined ordering periods of September 22-September 21 each year. (a) At this time the government doesn't anticipate ordering more than limits stated for each clin on the contract. (b) No, not at this time. (c) This is a firm fixed price contract. Ordering quantities can range from 1 licenses per order up to 350 per order as stated in section B of solicitation. Flat per-license pricing for all ordering quantities is sufficient.

7. Industry Question: Payment Structure and Progress Payments-Given the significant upfront investment required for FedRAMP IL4 authorization, security infrastructure, and platform deployment in the base year, will the Government consider: (a) Monthly or quarterly progress payments tied to achievement of technical milestones (e.g., FedRAMP assessment completion, platform deployment, user onboarding phases), or (b) Performance-based payments for incremental capability delivery during the implementation period? This would enable the contractor to maintain adequate cash flow during the high-investment base year while ensuring the Government receives value at each stage of implementation.

:Government Response (a) Contractors will be paid at the task order level, when orders are produced you will invoice, and then you will be paid. Task Orders are not subject to advance payments. (b) This is a firm fixed price contract; payment is rendered after performance received.

8. Industry Question: AI-Powered Support Acceptability (PWS 5.13) PWS 5.13 requires help desk capability with on-call training.

Will the Government accept AI-powered help desk systems (with human escalation for complex issues) that provide 24/7 automated support, or is human-staffed help desk required for all tier-1 support inquiries?

:Government Response The Government will accept AI-powered help desk systems.

9. Industry Question: Our software is deployed in the customer environment and meets FedRAMP security controls. We do not host the software in a public commercial environment that has pre-existing FedRAMP certification, although we have achieved an ATO with DHA which does require FedRAMP compliance. Is this fine?

Government Response: No, vendor must be FedRAMP IL4 compliant.

10. Industry Question: You are requesting 14 million messages per month. Can you provide the nature of that traffic (types of messaging) and the general flow (constant, bursts, etc.)?

Government Response: Messaging patterns will primarily be burst-based rather than constant. The intent is to send initial outreach messages in bursts to large groups of leads, typically ranging from 100-1,000+ recipients at a time. Due to varying areas of operation and differences in user size and market conditions. It is not feasible to project a consistent monthly volume.

11. Industry Question: How many applications would send messages to our platform to make up that 14 million?

: Government Response We would use the platform to send/receive messages, so however many apps/licenses the vendor would give us.

The potential recruits would respond via SMS messaging.

12. Industry Question: Do you want us to install it in a Navy cloud environment?

: Government Response No cloud requested.

13. Industry Question: Do you want to manage the infrastructure and app once we install it or do you want us to do that?

: Government Response No, vendor will manage infrastructure and app, we will maintain user management i.e. creating/deleting accounts, assigning permissions etc.

14. Industry Question: My main question is related to FedRAMP IL4: We do not currently hold FedRAMP certification, so I wanted to understand whether this requirement is strictly mandatory for participation, or if the contracting authority allows any of the following approaches: Exceptions or waivers for certain components, Use of non FedRAMP platforms if data is segregated or handled in specific ways, Submission of supporting documentation as an interim measure, Any alternative compliance pathways accepted. Your guidance will help us determine the appropriate next steps and ensure we comply with all requirements before preparing a formal response.

Government Response: FedRAMP IL4 is mandatory, no waiver process or workarounds.

15. Industry Question: We do not currently support the following feature requirements for the RFQ: Automated Drip Campaigns, AI / NLP assisted automation. Are these two pieces of functionality essential components of the SMS project?

Government Response: They are essential.

16. Industry Question: Monthly Message Volume Capacity: PWS Section 5.1.4 requires each license to support up to 40,000 SMS messages per month. With a minimum order of 350 licenses, this totals 14,000,000 messages monthly or 168,000,000 messages annually.

Can the Government confirm if the 40,000 figure is the intended monthly requirement per license, or if it represents an annual ceiling?

Government Response: 40,000 SMS messages is a projected monthly average per license.

17. Industry Question: Implementation and Integration Scope: Section B identifies a single CLIN for "Platform Licenses". Does the Government anticipate this requirement to be a "plug-and-play" solution implemented by Government personnel, or is the contractor expected to provide implementation and integration services (specifically with the Appian-based MCRISS) bundled within the fixed unit price? If the latter, would the Government consider adding a separate CLIN for Professional Services/Implementation to ensure a clear distinction between software and service costs?

Government Response: Integration with the Appian-based MCRISS is not needed. The solution is expected to operate as a standalone platform.

18. Industry Question: MCRISS Compatibility: Does the Government require the messaging platform to integrate with the Appian-based Marine Corps Recruiting Information Support System (MCRISS), or is this intended to function as a standalone system?

Government Response: Integration with the Appian-based MCRISS is not needed. The solution is expected to operate as a standalone platform.

19. Industry Question: Data Synchronization: Will the platform be required to pass real-time data (e.g., lead status, sentiment tags, or opt-out records) back to MCRISS via API?

Government Response: Integration with the Appian-based MCRISS is not needed. The solution is expected to operate as a standalone platform.

20. Industry Question: List Sourcing: Will prospect contact lists be provided via an automated export from MCRISS, and is there a preferred file format (e.g., CSV, JSON) for the campaign uploads required in Section 5.2?

Government Response: Lists will be exported from MCRISS, CSV is preferred file format.

21. Industry Question: Throughput Strategy: To ensure high deliverability for the required message volume, does the Government require Dedicated Short Codes, or is the preference for 10-Digit Long Codes (10DLC)?

Government Response: We are open to most reliable and cost-effective code.

22. Industry Question: Code Provisioning: Does the Government currently possess the SMS codes intended for use, or must the contractor provision new codes prior to the September 22, 2026, start date?

Government Response: The Government does not possess the SMS codes.

23. Industry Question: Call Forwarding Infrastructure: For the requirement in Section 5.10, is the contractor expected to provide the telephony infrastructure for "call forwarding," or will the Government provide the destination numbers for routing?

Government Response: Contractor shall provide the telephony infrastructure.

24. Industry Question: NLP Automated Actions: For the response categorization required in Section 5.3, should the AI trigger automated actions (e.g., updating a lead status in MCRISS or auto-opting-out a user) or simply tag the sentiment for recruiter review on a dashboard?

Government Response: We are requesting no AI trigger automated actions. Our recruiters are trained to overcome disinterest and refusals when conducting prospecting activities. AI trigger automation would eliminate their ability to do so.

25. Industry Question: Management Scope: Should Sections 5.2, 5.7, and 5.9 be interpreted as requiring an enterprise-level automated marketing and campaign management suite--including cross-geography duplicate detection and real-time ROI dashboards--or are these features expected to be native to the SMS platform itself?

Government Response: A full enterprise level marketing and campaign management suite is not required. The expectation is for an SMS platform with built-in messaging capabilities with analytics. (response tracking, opt-out metrics. Cross-geography duplicate detection is highly preferred.

26. Industry Question: FedRAMP IL4 Gateway: Section 5.1 mandates FedRAMP Information Impact Level 4 (IL4). Is an existing IL4 Authorization to Operate (ATO) a mandatory requirement at the time of award, or will the Government accept a FedRAMP Moderate/High authorization with a documented path to IL4?

Government Response: IL4 Authorization is mandatory, vendor must be FedRAMP IL4 certified at time of quote submission.

27. Industry Question: Data Archival Strategy: Given the "Single Source of Record" requirement in PWS Section 5.5, the anticipated message volume will generate massive data logs. Does the Government have a preferred strategy (e.g., Data Lake or external escrow) for long-term archival to remain within secure cloud storage limits?

Government Response: The Government does not have a preferred strategy for long term archival. Contractor will provide strategy.

28. Industry Question: Definition of "Delivery": The solicitation requires delivery within 10 days of award. Does "delivery" constitute the provisioning of user accounts/licenses, and what Government-side network approvals or Certificate Authority (CA) trust requirements should be anticipated that might affect this timeline?

Government Response: End user should be able to use the accounts/licenses within 10 days of award.

52.212-1 ADDENDUM

The instructions contained in FAR 52.212-1. Instructions to Offerors-Commercial Items are applicable to this solicitation, but are tailored as follows:

Paragraph (e) "Multiple offers" is not applicable.

The addendum contains the additional instructions below applicable to this solicitation:

Solicitation number M00263-26-Q-R001 is issued as a Request for Quote (RFQ) using the commercial procedures in accordance with FAR Part 12.201 . This is a Small business set aside acquisition and the North American Industrial Classification System (NAICS) code for this requirement is with a size standard of 517810 $40 Million Dollars.

1. GENERAL INSTRUCTIONS

A. General Information. The Regional Contracting Office, Parris Island (RCO-PI) intends to award a single-award Firm Fixed Price (FFP) contract as a result of this solicitation. The objective of this requirement is to provide a contract that enables the Marine Corps Recruit Command (MCRC) to acquire Prospect Messaging Licenses at award and throughout the term of the contract.

(a) The Government intends to evaluate offers and award a contract without discussions.

Therefore, the offeror's initial offer should contain the offeror's best terms from a price and technical standpoint. Offerors are cautioned to examine this solicitation in its entirety and to ensure that their quote contains all necessary information, provides all required documentation and is complete in all respects.

(b) Use of general or vague statements such as "standard procedures will be used" will not satisfy this requirement. Unnecessary elaboration or presentations beyond what is sufficient to present a complete and effective solution are not desired and may be construed as a lack of understanding of the requirement.

(c) Quotes must be prepared in accordance with these instructions. Failure to do so may result in the offeror's submission being determined unacceptable and ineligible for award. Each offeror's submission shall be screened by the Contract Specialist upon receipt to ensure completeness and compliance with the instructions contained in this solicitation.

B. Confidential Information. The Freedom of Information Act (FOIA) and its amendments generally provide the public the right to access agency records when a member of the public so requests. If an offeror's submissions contain information that he/she believes should be withheld from such requestors under FOIA on the grounds that they contain "trade secrets and commercial or financial information", 5 U.S.C. (S) 552, the offeror should mark its submissions as set forth in FAR 52.215-1(e).

C. Communication Procedures. The Contract Specialist is the point of contact for this acquisition. Address any questions or concerns to the Contract Specialist. Written requests for clarification shall be sent to the Contract Specialist via email.

The Contract Specialist for this acquisition is:

Mr. Kerry O. Smith

Phone:843-228-1980.

Email address: kerry.o.smith.civ@usmc.mil

The Contracting Officer for this acquisition is:

Kacy M. Mohead

Phone:(843) 228-2188.

Email address: kacy.m.mohead@usmc.mil

Solicitation information and amendments will be posted to the Contract Opportunities website at https://SAM.

gov. Offerors shall e-mail written questions requesting clarification of the Request for Quote to the Contract Specialist (kerry.o.smith.civ@usmc.mil). The Government will accept vendor questions no later than days 10 after issue date of the solicitation. Questions received after this date/time may not be answered.

*NOTE: Your email subject line for submitted questions should read:

"RFQ M00263-26-Q- R001 QUESTIONS, insert contractor name."

II. PREPARATION INSTRUCTIONS

A. Request for Quote Submission. The completed and signed SF1449, CLIN specifications, price quotes, and all other requirements requested in the RFQ must be received in its entirety by the date and time specified in Block 8 of the SF 1449. Quote submission shall be made electronically via email.

M0026326QR0010002

mailto:kacy.m.mohead@usmc.mil

SUBMISSION CHECKLIST: Ensure each of the following is provided and annotated in your submitted quote.

_____ Completed and Signed SF1449 (The offeror shall complete block 17 to include Offeror name, Point of Contact, Cage code, Duns code, and Tax ID #, 23, 24, and 30 the "Signature of Offeror /Contractor" Block 30 a, b, and c).

_____ Quote on company letterhead or preferred proprietary quotation

(Must include pricing - unit price and total price).

_____ Offeror shall complete all required Representations and Certifications provided in the solicitation.

_____ Delivery date - the expected number of days to delivery from time of award. Offeror shall provide 10 days for delivery after receipt of order.

_____ Offer is valid for 60 days from closing date of solicitation.

_____ No exception to any Terms and Conditions has been taken, or if so, clearly cited. Include a cover letter delineating any exceptions taken to the solicitation terms and conditions. However, offerors are cautioned that any noncompliance with the terms and conditions of the solicitation may cause their quotes to be determined unacceptable.

_____ Offeror must acknowledge any amendments to the RFQ.

_____ SAM-validated and NAICS Code 517810 compliant.

_____ Offeror shall provide Country of Origin for all quoted items.

_____ Offeror shall provide documentation that clearly demonstrates that the item quoted meets all requirements and specifications.

_____ Offeror shall submit FedRAMP Authorization letter (ATO) or a System Security Plan (SSP) that explains the company's ability and capability to meet FedRAMP requirements.

*NOTE: When submitting your quote electronically via email, your email subject line should read:

"RFQ M00263-26-Q-R001- QUOTE SUBMISSION, from insert contractor name."

B. Disposition. No quotes will be returned to the offeror.

III. PERFORMANCE REQUIREMENTS

The quote must demonstrate an understanding of and ability to meet all requirements set forth herein. The offeror shall provide sufficient detail to substantiate that the products offered conform to the requirements shown above. The offeror shall demonstrate that the quote follows the requirements, terms, and conditions of the RFQ. Comprehensive responses to the requirements of this RFQ are required to enable the Government to evaluate the offeror's understanding of and capability to accomplish the requirements of the Government.

Technical Acceptability and Past Performance evaluation criteria will be listed in section M of Solicitation.

IV. OFFEROR SUBMISSION INSTRUCTIONS

Electric submission via email is required. Offerors must submit their quotes via email to the following email addresses: kerry.o.smith.civ@usmc.mil, kacy.m.mohead@usmc.mil. Send email to the Primary point of contact (POC) and also copy (cc) the secondary point of contact (POC). The submission must arrive by the stated deadline in order for a quote to be considered complete and to be evaluated. Failure of any portion of the quote to arrive by stated deadline will result in rejection of the entire quote.

Note: Offerors submitting via email must ensure that attachments do not exceed 5 MB; offerors with attachments larger than 5MB must split their response into multiple emails to meet the 5MB attachment limitation. In addition, .zip files will be filtered and removed by the MCRDPI firewall. Offerors must rename the .zip file or send in an alternate format. For ease of submission files should be in PDF format.

Government Points of Contact:

Primary POC Secondary POC

Mr. Kerry O. Smith Kacy M. Mohead

Phone:843-228-1980. Phone:(843) 228-2188.

Email address: kerry.o.smith.civ@usmc.mil Email address: kacy.m.mohead@usmc.mil mailto:kerry.o.smith.civ@usmc.mil

(End of clause)

MCRD PARRIS ISLAND, PO BOX 19001

PARRIS ISLAND, SC 29905-9001

UNITED STATES

KERRY SMITH, Email: kerry.o.smith.civ@usmc.mil Telephone: 843-228-1980 AdminBy:

SCD: PAS:

(1) Update Performance Work Statement language at Section 6.2

(2) Provide Government responses to industry questions at Section L.

(3) Incorporated Language in Section L, Section II, Submission Checklist.