From the State Government edition of October 2, 2026
Maryland State Innovation Team (Oct 1): Business AI Benchmark of 276 leaders finds 91% use AI but 58% stay at basic use and productivity gains are mostly slight
Maryland State Innovation Team / Office of Governor Wes Moore · State innovation office evidence-building for AI economic and workforce policy · Maryland statewide
- Publisher
- Office of Governor Wes Moore (governor.maryland.gov)
- Original publication
- 2026-10-01
- Source retrieved
- 2026-10-05
- Event date
- 2026-10-01
What happened
At the Oct 1 Maryland Innovation Summit, the State Innovation Team released a Business AI Benchmark. It is a June-July 2026 survey of about 300 senior decision-makers; the report says 276 executive or senior leaders. 91% report using some AI, but 58% are at basic use. 92% of regular users report positive productivity impact, mostly slight (70%) rather than significant (21%). Two-thirds have a dedicated AI budget, 64% plan to have existing staff do more with AI, and only 4% expect headcount cuts. Businesses ask the state for capital, technical assistance, pilots, talent pipelines, training and affordable secure infrastructure. The report notes a likely sample skew toward AI-engaged firms. It finds Public Services and Utilities leaders the least confident in using AI. The release also cites Maryland Community Compass (18,500+ active users, $14M state funding).
Why it matters
Relevant to state government as an example of a state innovation office producing its own AI evidence base before designing programs, and as a check on productivity claims: gains are mostly slight. Its subject is businesses, not agency operations, so relevance to agency AI adoption is indirect. Freshness: released Oct 1 (page updated 19:28 EDT), a few hours before the Oct 1 run started. That run did not capture it, it is not archived, and it is the newest state-produced measurement in this window.
Evidence and measured results
Opened the Oct 1 press release and the 33-page report PDF on innovation.maryland.gov (PDF created Sep 28, cover 'September 2026'). Confirmed the headline percentages, the 276-respondent base, fieldwork dates, the AI-engaged sample-skew caveat, the comparison caveat against an NBER firm sample, and the low confidence of the Public Services and Utilities segment. Community Compass figures are from the release only.
Limitations and uncertainty
Voluntary survey of AI-engaged organizations; self-reported productivity; categorical revenue estimates; not representative of all Maryland employers. Business-focused, not an evaluation of state agency AI. The press release is promotional in tone.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- State leaders design AI economic and workforce programs without local evidence on how far adoption has gone or what gains are real.
- Stakeholders
- State innovation office
- Department of Commerce
- Department of Labor
- Governor's policy office
- Department of Information Technology
- Discovery questions
- Do you have a local baseline of AI adoption?
- How do you validate self-reported productivity gains?
- Which sectors or agencies show the least confidence?
- Would you repeat a survey to track change?
- Value hypothesis
- A repeatable measurement program could help states target AI support where adoption is shallow, with explicit limits on what results mean.
- Potential engagement
- Six-week measurement design and pilot wave for a state innovation or commerce office, including published methodology and limitations.
- Unsupported claims
- That AI raises Maryland productivity significantly
- Statewide adoption prevalence
- Any effect on state agency operations
- Return on Community Compass funding
Pre-sales engineering
Role takeaway
- Fit
- Survey instrument, sampling and reporting design for state AI evidence-building.
- Architecture and integration
- Store survey waves in a governed analytics environment with segment weights and publish dashboards with method notes.
- Prerequisites
- Partner channels for recruitment
- Agreed adoption-level definitions
- Privacy review of respondent data
- Constraints
- Voluntary and AI-engaged sample skew
- Self-reported outcomes
- Not comparable to national studies
- Business focus, not agencies
- Security
- Protect respondent business data; aggregate segments to avoid re-identification of small firms.
- Proof of value
- Documented sampling frame and response rate
- Second wave showing change on core measures
- Segment results with confidence caveats
Delivery
Role takeaway
- Work
- Stand up a repeatable AI-adoption survey with published methods and limits, and link findings to program design.
- Dependencies
- Recruitment partners such as chambers
- Analyst capacity
- Leadership agreement to publish limitations
- Ownership
- State Innovation Team, with commerce and labor departments as program owners.
- Skills and adoption
- Analysts need survey methodology skills; program staff need training to interpret self-reported data cautiously.
- Governance checkpoints
- Instrument and privacy review
- Methodology publication
- Program decisions cite limitations
- Acceptance criteria
- Proposed: response rate and sampling frame published
- Proposed: second wave within 12 months
- Proposed: each headline figure carries a caveat
- Risks
- Sample skew overstates adoption
- Promotional framing
- Policy built on self-reports
- Survey fatigue
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?
Businesses cite uneven data readiness and infrastructure bottlenecks, such as internet reliability and storage costs. That signals state programs may need shared secure infrastructure, not just training.
Governance
Who approves, reviews and stays accountable for outcomes?
Shows a governance practice worth copying: measure locally before setting policy. Self-reported, non-random results should not be used as statewide prevalence figures.
Security and privacy
What data, permissions and controls need testing?
Data security concerns rank among the top barriers to business AI adoption. State-provided secure infrastructure was a stated request; no security outcomes are measured.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Employers expect workforce evolution over reduction (4% expect cuts) and want training programs, which supports state workforce-development roles in AI.
Procurement
What should contracts, pricing and exit terms secure?
Limited direct procurement relevance; requests for affordable secure digital infrastructure could shape future state-sponsored shared services or grants.
Operating model
Which teams own the service once it runs?
A central state innovation team runs research, convenings and products (Community Compass), a hub model other states may compare against.
Publication history
- 2026-10-02State Government · Issue 295 resources
Stable resource ID: maryland-business-ai-benchmark-innovation-team-20261001