From the State Government edition of September 22, 2026
South Carolina CIO reports Bradley scale metrics while saying AI ROI still unproven
South Carolina Division of Technology / Office of the State CIO (Nathan Hogue) · State shared digital services / AI Center of Excellence · South Carolina, United States (with Lexington County local adoption noted)
- Publisher
- Government Technology — South Carolina CIO on AI: Is the Juice ‘Worth the Squeeze?’
- Original publication
- 2026-09-22
- Source retrieved
- 2026-09-23
- Event date
- 2026-09-17
What happened
Why now: 2026-09-22 GovTech interview updates South Carolina’s Bradley resident assistant with as-of-2026-09-17 usage (~20,000 people; nearly 70,000 questions; ~6,000/month; ~187/day; three-quarters of feedback positive) and situates ~250 tracked AI use cases under a proviso requiring central review for operational compatibility, security, and privacy. CIO Nathan Hogue says task completion inside chat is “not there yet,” stresses data quality/CDO funding, shared services and modernization, and states leaders are still trying to figure out whether “the juice is worth the squeeze,” estimating ~15% personal capacity gain from internal AI pilots without claiming enterprise ROI.
Why it matters
Contemporaneous state-CIO evidence that citizen-assistant scale metrics can advance while enterprise ROI, autonomous tasking, and data foundations remain unresolved—useful counterweight to vendor FCR claims on the same Bradley program.
Evidence and measured results
Reporter Ashley Silver quoting Hogue; Bradley metrics dated as of Sept. 17; Copilot/ChatGPT internal pilot referenced qualitatively; Lexington County adoption noted. Not an independent statistical evaluation.
Limitations and uncertainty
Bradley metrics are operator-reported via journalism, not an audit. 75% positive feedback lacks sample/methodology. 15% capacity gain is personal estimate. Overlaps thematically with 2026-09-21 Tyler Bradley resource but adds dated usage, proviso governance, and explicit ROI uncertainty.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; 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 expanding resident AI assistants need credible ROI language while CIOs admit enterprise returns remain unclear.
- Stakeholders
- State CIO / CoE
- Agency digital leads
- Chief data officer
- Shared-services and cyber leads
- Budget/legislative staff
- Discovery questions
- How do you define juice-worth-the-squeeze for Bradley versus internal copilots?
- What does proviso review reject most often?
- Which life-and-safety systems block AI value until modernized?
- What shared identity-proofing is required before transactional chat?
- Value hypothesis
- A bounded KPI and intake-design engagement can turn engagement metrics into decision-grade ROI evidence without promising savings.
- Potential engagement
- 6–8 week AI value-measurement and CoE intake playbook aligned to the proviso.
- Unsupported claims
- Enterprise ROI proven for Bradley
- Autonomous end-to-end service completion
- 15% capacity gain as statewide productivity fact
Pre-sales engineering
Role takeaway
- Fit
- Strong fit for disclosed resident Q&A and internal policy retrieval; weak fit for autonomous multi-step citizen transactions today.
- Architecture and integration
- Optional Bradley chat; agency model clones; shared Tyler digital layer; centralized logging/monitoring; CDO-led data construct.
- Prerequisites
- Use-case intake under proviso
- Content/data quality standards
- Identity-proofing for any transactional step
- Shared cyber baselining
- Constraints
- Task completion in chat not available yet
- Legacy application debt
- Operator-reported metrics only
- Security
- Central review for security/privacy; layered shared controls; avoid shadow agency bots outside intake.
- Proof of value
- Separate engagement vs outcome KPIs
- Sample audit of positive-feedback methodology
- Track proviso acceptance/rejection reasons
- Compare agency-clone quality to Bradley core
Delivery
Role takeaway
- Work
- CoE process hardening, data standards rollout, Bradley content ops, and modernization sequencing for AI-enabling systems.
- Dependencies
- CDO hire/function
- Tyler digital contract deliverables
- Agency security remediation tracking
- Strategic plan publication
- Ownership
- State CIO organization with CoE facilitation; agencies own use cases.
- Skills and adoption
- Agency teams need intake literacy; staff need data stewardship skills before broader copilots.
- Governance checkpoints
- Proviso review gate
- Monthly Bradley metric quality review
- Shared-services onboarding checklist
- ROI narrative review before budget claims
- Acceptance criteria
- Published ROI measurement plan
- All production bots through intake
- Disclosure UX verified
- Data-quality prerequisites documented per use case
- Risks
- Metric theater without outcomes
- Local Bradley clones drifting from security baseline
- Over-promising in-chat task completion
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?
Bradley remains optional, disclosed AI chat grounded for resident Q&A; agency clones of the model spreading; internal policy-manual chatbots; identity-proofing and accessibility via expanded Tyler digital-services contract; shared logging/monitoring/firewall services.
Governance
Who approves, reviews and stays accountable for outcomes?
State proviso mandates central AI use-case submission for compatibility/security/privacy review; AI Center of Excellence convenes agencies; statewide IT strategic plan nearly finished (publication expected within six months per article).
Security and privacy
What data, permissions and controls need testing?
Layered shared cyber services and routine agency audits cited; Hogue ties AI value to accurate, tagged, privacy-handled data and a funded chief data officer with AI responsibilities.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Resident Bradley optional with AI disclosure; internal bots for new-staff policy Q&A; personal ~15% capacity estimate is anecdotal, not a workforce study.
Procurement
What should contracts, pricing and exit terms secure?
Expanded Tyler digital-services contract for consistent web presence, accessibility, and identity-proofing; major private-sector partners brief CoE (Siemens, Boeing, BMW) without constituting vendor evaluations.
Operating model
Which teams own the service once it runs?
Protect/promote/pursue strategy shifting toward data foundations and shared services; modernization prioritized for life-and-safety systems; ROI measurement still formative.
Publication history
- 2026-09-22State Government · Issue 174 resources
Stable resource ID: south-carolina-cio-bradley-roi-juice-squeeze-20260922