From the Anthropic edition of November 9, 2026
Maryland DoIT opens secondary-competition RFQ for Claude Enterprise licenses (BPM059654), questions due Nov. 13, bids Nov. 17
Maryland Department of Information Technology (via ProposalWorkspace listing) · State government procurement · Maryland, United States
- Publisher
- ProposalWorkspace (bid aggregator)
- Original publication
- Posted Nov 6, 2026; listing updated Nov 9, 2026
- Source retrieved
- 2026-11-10
- Event date
- 2026-11-17
What happened
A bid aggregator lists a Maryland Department of Information Technology secondary-competition purchase order RFQ (FC0003827, BPM059654) for Claude Enterprise licenses, posted November 6 with questions due November 13 and responses due November 17, 2026. Bidders must hold the COTS 2012 master contract and be authorized Anthropic resellers; SaaS terms are subject to the state's Attachment Y Data Use Agreement; the state may buy more or less depending on funding. Seat counts and the full solicitation were not visible.
Why it matters
A live state procurement of Claude Enterprise through a reseller vehicle, newly relevant this week because the question deadline is Nov. 13 and the listing was updated Nov. 9. It shows a state buying Claude Enterprise (not the FedRAMP Claude for Government product) through an existing COTS contract with a data-use agreement, a template other states may follow.
Evidence and measured results
Aggregator listing summarizing state bid documents; no award, quantity or price.
Limitations and uncertainty
Aggregator summary written by AI from bid documents; quantity, seat count and full terms not visible; must be verified against eMMA. Cross-tagged state-government because it is a state agency procurement of Claude Enterprise.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- States want Claude Enterprise seats through existing contract vehicles with enforceable data terms.
- Stakeholders
- State procurement officer
- State CIO / DoIT
- Agency AI leads
- Resellers
- Discovery questions
- Which contract vehicle will you use for Claude?
- What data-use terms apply to SaaS AI?
- How will seats be allocated across agencies?
- Value hypothesis
- Using an existing COTS vehicle with a DUA may shorten procurement time versus a new RFP.
- Potential engagement
- Procurement readiness review covering vehicle, DUA terms and seat governance.
- Unsupported claims
- Seat count or award value
- Maryland selected Claude over competitors
- FedRAMP authorization of Claude Enterprise
Pre-sales engineering
Role takeaway
- Fit
- Claude Enterprise for general state workforce use under a DUA.
- Architecture and integration
- SSO/SCIM, admin console, retention settings, audit export.
- Prerequisites
- Identity integration
- Data classification
- DUA review
- Constraints
- Claude Enterprise not FedRAMP authorized
- Covered-model retention terms
- Security
- DUA must address retention, breach notification, admin data.
- Proof of value
- Pilot configuration meeting DUA
- Retention settings documented
Delivery
Role takeaway
- Work
- Onboard identities, allocate seats, train users, report usage.
- Dependencies
- Award
- DUA terms
- Agency demand
- Ownership
- Maryland DoIT (if awarded).
- Skills and adoption
- Role-based training aligned to state responsible-AI policy.
- Governance checkpoints
- Risk-tier review per use case
- DUA compliance check
- Acceptance criteria
- Proposed: all seats SSO-provisioned
- Proposed: usage reporting monthly
- Risks
- Seat sprawl
- DUA conflicts with retention
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Claude Enterprise is not FedRAMP authorized per Anthropic; Maryland's data-use agreement will govern data handling, including whether covered-model retention is acceptable.
Governance
Who approves, reviews and stays accountable for outcomes?
State AI governance should align license use with the state responsible-AI policy and risk tiers before rollout.
Security and privacy
What data, permissions and controls need testing?
Attachment Y terms will need to address retention, breach notification and admin data.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Reseller-only secondary competition under COTS 2012 master contract; multi-year per-year pricing; MSRP screenshot required.
Operating model
Which teams own the service once it runs?
A statewide license pool implies a central owner for seat allocation and training.
Publication history
- 2026-11-09Anthropic · Issue 118 resources
Stable resource ID: maryland-doit-claude-enterprise-licenses-rfq-bpm059654-20261106