# Santosh Sabnis

Santosh Sabnis writes about how cities and businesses can govern technology more effectively, with a focus on public-sector procurement, data rights, and the infrastructure behind AI systems.

- Profile: https://b2binfluencer.marketing/creators/santosh-sabnis/
- LinkedIn: https://www.linkedin.com/in/santoshds
- LinkedIn followers: 2,478
- YouTube: https://www.youtube.com/channel/UCnJNiA2V3BVho1D9XYtAuQw
- Topics: artificial-intelligence, data-governance, ai-infrastructure
- Based on 9 dated posts, latest 2026-09-04

## Summary

Santosh Sabnis is most useful for governance-first explanation of public-sector technology procurement and AI infrastructure.

- Best for: Govtech or enterprise data infrastructure campaigns needing analytical, educational content on governance and data.
- Not for: Consumer lifestyle endorsements, guaranteed sponsored posts, or campaigns needing verified audience demographics and broad reach.
- Check first: Confirm partnership terms, sponsorship availability, and audience demographics or engagement data before contacting.

### Takeaways

- City hardware votes can hide contract rules for data ownership, access, and accuracy.
- Buying software cannot fix outdated civil-service structures or weak chatbot accountability.
- Agents can follow instructions yet damage decisions using stale data; fresher pipelines and human review help.

## Main ideas

- **City technology contracts are governance decisions**: Sabnis argues that city councils may vote on cameras, costs, and contract length without confronting who controls the data and how it can be used. A city’s stated policy may not prevent access that its contract leaves open.
- **AI needs current data and a plan for when it is not current**: An AI system can follow its instructions and still cause harm if it acts on an outdated picture of events. Data freshness and human oversight belong in the system’s design, not as afterthoughts.
- **Software cannot replace municipal reform**: Sabnis’s critique of city AI goes beyond procurement: cities may treat software as modernization while deeper legal and staffing constraints remain. The post makes the stakes concrete with examples, including a chatbot that gave business owners false information about workers’ rights and food safety. Read alongside their technical and contractual proposals, the argument is not that software never helps, but that it cannot substitute for sound governance or reform of the systems around it.

## Work to read

- [The contract, not the camera: a 32.3% false-positive rate and 82 city termination records](https://www.linkedin.com/posts/santoshds_structuralaudit-civicintelligence-procurement-activity-7491495547388923904-pXc5)
- [A governance vacuum: city chatbots, a $640 million deficit and an 18-month hiring pipeline](https://www.linkedin.com/posts/santoshds_structuralaudit-civicintelligence-activity-7467246609521782784-IdnP)
- [The Automation Tax: 10-hour-old data behind a 10-second AI agent](https://www.linkedin.com/posts/santoshds_aiinfrastructure-structuralaudit-activity-7472739793194569728-y0aJ)

## Partnerships

Santosh Sabnis's posts contain no sponsorship policy, media kit, partnership terms, or commercially disclosed collaboration. The three available LinkedIn posts are analytical essays on municipal technology procurement and enterprise AI infrastructure, not campaign or sponsorship content; none announces a sponsor, an affiliate arrangement, or a paid partner. The posts do not say whether they accept sponsorships. Brands planning a campaign should confirm partnership terms and any commercial offer directly before budgeting.

## Alternatives

- Mark Anthony F.: Choose Mark Anthony F. when the campaign's buyer task is the purchasing process itself: showing a city what a cheap software bid really costs once staff build workarounds, and how vendor lock-in appears in data formats, billing configuration, and retraining. The posts offer a reusable teaching sequence: measure the current process cost per month in staff time before signing, then ask three exit questions about data export, what happens if the vendor is acquired, and who does implementation. For a govtech campaign on total cost of ownership or vendor management, this is closer to the buyer's decision than Sabnis's material.
- JORGE CARDENAS MBA, PMP: Choose this creator when the campaign needs a city-side account of digital infrastructure investment rather than a critique of contract terms. The posts argue that broadband is now a fourth core infrastructure asset alongside roads, water, and electricity, and report a specific municipal build: modernized and new data centers, roughly 100 miles of city-owned fiber, a private 5G network, and an AI effort for public safety and infrastructure insight. They frame the city as having moved from being ranked worst-connected to a model for urban connectivity. This is a strong fit for a campaign selling the case for investment or showing municipal leaders what a completed modernization program looks like from the inside.
- Chad Smeltzer: Choose Chad Smeltzer when the campaign audience is engineering, utility, or contractor firms selling into municipalities, and the task is to demonstrate lifecycle cost savings and differentiation rather than review a contract. The posts include a costed inspection comparison — roughly $500 per manhole under a manual method against about $125 using a single-pass 360-degree optical scan, a difference of about $37,500 on 100 manholes before engineering and reporting hours — and argue that firms move upstream by combining technology with engineering judgment and proprietary process instead of chasing bids and cutting fees. That directly serves a campaign about value capture and avoided cost.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/