Jonathan — here's where single-operator work actually fits inside municipal tech.
You run the CIO seat for a top-10 US city. Vendor procurement cycles, department sprawl, citizen-facing landing-page debt, and AI-everywhere pressure are all true at the same time. This page maps where one operator (no RFP, no SOW, async) can sit alongside your vendor stack and ship the small things that compound. If the read is wrong, it's a 5-minute conversation. If it's right, you have an option that didn't exist in the procurement catalog.
SideGuy is a single-operator slot inside the gaps your vendor stack can't reach. Not a procurement vendor. Not an RFP response. A senior operator on text who can ship a landing page, audit a vendor proposal, draft an AI-readiness one-pager, or build an internal SOP search prototype — async, scoped, no retainer. Designed for the work that's too small for a contract and too important to ignore. Pay-per-page or hourly. $100/hr first hour. No demo calls.
1The municipal CIO operator-translation gap
Every city CIO has the same shape of friction:
- Vendor capability is high — Salesforce, ServiceNow, AWS GovCloud, Microsoft Copilot Gov, ESRI, Granicus, all the rest. Capability isn't the problem.
- Department adoption is uneven — Public Works runs differently than IT, runs differently than Library Services, runs differently than Police Records. Each carries SOPs, vendor contracts, and AI-comfort-levels that don't match the CIO office's roadmap.
- Citizen-facing surfaces lag — landing pages, FAQ pages, service-application explainers, accessibility-compliant explainers — these are the surfaces residents touch. They tend to live three CMS migrations behind the actual policy.
- AI procurement is upstream of AI value — by the time an AI tool is RFP'd, contracted, deployed, and trained-on, the underlying model is already 18 months old.
The translation gap: there's no procurement category for "operator who fixes one Tuesday-morning thing in 48 hours, async, no contract." That gap is the lane.
2Four places single-operator work fits inside city ops
Citizen-facing service explainers
One landing page per high-friction service (apply for X, dispute Y, find Z). Plain English. Mobile-first. Accessible. Ships in 24-48 hours per page. SideGuy specialty — 200K+ pages built solo.
Internal "ask the docs" prototype
A scoped prototype: department staff can ask a natural-language question against department SOPs and get a cited answer. Built lean (no enterprise AI procurement), pilot-able in one department, evaluatable before a vendor commitment.
Operator read on a vendor proposal
You get a 200-page proposal from a vendor. Need an operator-honest read on what the vendor is actually delivering vs what the deck implies. SideGuy reads it, writes a 1-page brief, flags the questions you should ask before signing.
Department-level AI-readiness one-pager
A specific department wants AI but doesn't know where to start. SideGuy builds a tight, operator-honest one-pager: 3 places AI lands quickly, 2 places it doesn't, what to ask before buying. Department head walks into the budget meeting prepared.
3Honest 80/20 — what kills these in gov tech
Procurement, not capability — and the FOIA-readability of every artifact
The work itself is straightforward. A landing page is a landing page. A doc-search prototype is a doc-search prototype. What kills it in gov:
- Procurement classification. Is this a sole-source <$10K direct buy? A piggyback off an existing master agreement? A Procurement Card transaction? The right path depends on your city's thresholds + finance dept's appetite.
- FOIA readability. Every email, draft, and artifact is potentially public record. Honest draft language has to survive a public records request. SideGuy writes accordingly — no shade, no opinions about other vendors in writing.
- Vendor neutrality. A single operator can't recommend a specific enterprise SaaS vendor without procurement implications. The work has to be platform-agnostic or framed as "options to evaluate," not "buy this."
- Pilot-to-production gap. A scoped pilot is easy. Crossing into production usually requires a Master Services Agreement, COI insurance certs, security review, etc. Knowing where the natural cliff is upfront = scoping the work below it.
SideGuy's lane sits below the cliff: work that fits direct-buy thresholds, ships as deliverables (not retainers), and has artifacts that read clean if FOIA'd. The pilot might prove a vendor case. SideGuy doesn't try to become the vendor.
4How it actually fits — what SideGuy is + isn't
The SideGuy slot, made specific for City of SD
What SideGuy IS
- Single senior operator, async, text-first
- $100/hr first hour, $100-300 per shareable, $1-10K per scoped build
- Pay-as-you-go, no retainer, no minimum
- Deliverables-defined (landing page, brief, prototype)
- Vendor-neutral by design
- FOIA-readable artifacts as default
- Encinitas-based, SD-region available in-person if needed
What SideGuy is NOT
- Not a procurement vendor or RFP response
- Not a managed-services contract
- Not a replacement for your enterprise SaaS
- Not building a long-term implementation team
- Not a sales-cycle org — async and direct
- Not bidding for the multi-million-dollar work
- Not selling demos or doing slide decks
- ⚖️ 6 New California AI Laws · Operator Guide
Async, no calendar — just text or email when something fits
If anything in the City of SD's tech / AI / landing-page / SOP-search stack ever needs the kind of work above, you know how to reach me. No follow-up needed; this brief lives at this URL forever — share it inside the office if it's useful, ignore it if it isn't.