CivicLoop by Ta-Tech Solutions Purpose: Prepare for any eventuality at the May 23 Executive Exchange Expo. The demo plan, every hard question a panelist can ask with a strong answer, the traps to avoid, the failure plan, and the logistics checklist. Read this until the answers are reflex.
"Prince George's County's 311 today is a black hole. A resident reports a problem and never hears back, so trust erodes and the same complaint gets filed five times. CivicLoop closes the loop. A resident reports by voice, text, or photo in their own language, AI routes it instantly, the resident is kept informed at every step, and leadership sees the whole County on a live dashboard. It is built on an engine already running in production, so this is a new product on a proven foundation, not a build from zero."
Three words to land every time: closes the loop.
The hero flow, end to end, on real demo data, in English and Spanish (see Document 06, Section 2 and Document 10, Section 4):
assigned now, not only in_progress). Agent also schedules a
follow-up visit with the resident; the resident gets SMS + email.ics calendar invite./admin and flip the Autopilot dial
from off to route to full while the panel watches a fresh
inbound request route, assign, and notify itself in under ten
seconds. Then click Run self-heal now and show the
department channel light up with a @first-name heads-up. Then
open /public on your phone (or a second tab) - "this URL is
public, no account, ready for the press, ready for the Council."Demo discipline: one main flow, deep, polished, ending on the Autopilot dial and the public portal. Do not wander into secondary screens unless asked. If asked, show briefly and return.
"You said Prototype. Is this real or vaporware?"
"It is real and you are about to see it run. The honest label is Prototype because the 311 product itself is in active build. But it is built on the Ta-Tech engine that is already in production - multi-tenant isolation, security, audit logging, the multi-language pipeline, offline-first behavior. The hard half is proven. What you see today is the 311 layer on top of it, working end to end."
"What is your government experience?"
"Ta-Tech's healthcare platform, PolyHealth, is being built for a Ministry of Health evaluation and a regional public-hospital pilot. So we have government-sector experience, and it is recent. CivicLoop is our first product purpose-built for US local government, and we are being transparent that PG County would be our flagship public-sector partner in the States. That is also why we are starting with one agency and a real pilot, not a county-wide rollout."
"Why should we trust a company we have never heard of?"
"Start small. That is the whole proposal - one agency, one workflow, a real pilot with clear success metrics, before any large commitment. You are not betting the County on us. You are running a low-risk pilot against an incumbent that is already failing publicly."
"Is your company in good standing?"
(Have this resolved before May 23 - file any overdue items on Maryland Business Express. If asked and resolved: "Yes." If still in progress: be honest that it is being brought current, do not bluff.)
"How is this different from the current PGC311 app?"
"PGC311 is rated 1.5 stars and residents report they cannot even submit a request. It is a form that leads to a black hole. CivicLoop is the opposite: multiple ways in including voice, AI that routes and predicts, automatic status updates, and a closed loop that ends in a confirmed resolution with proof. The contrast is not subtle."
"Is the AI real, or is it theater?"
"Every AI action does real work, shows its work, and fails safe. When it classifies and routes a request, it records why, with a confidence score, in an audit log a human can review. It is never a black box. If confidence is low, it routes to a human, it does not guess. Probe any AI decision in the demo and it will show you its reasoning." (See Document 07 for the full standard.)
"What about residents with no smartphone, or who do not speak English?"
"That is designed in, not bolted on. SMS intake serves residents with no smartphone. Voice intake serves residents who cannot or do not type, in the language they speak. Every surface and every notification is multilingual. This is also how the County meets its own Language Access for Public Services Act."
"Does it integrate with what we already have? Are we locked in?"
"CivicLoop speaks Open311 / GeoReport v2, the open civic-issue standard. Your data is yours and is portable. If the pilot does not work for you, you can take your data and go. No lock-in is a feature, not a risk."
"What if the internet goes down at a site, or during the demo?"
"The engine is offline-first - a service worker, local store, and a sync queue. And for the demo specifically, we have a recorded backup demo video, so a network failure does not stop the pitch."
"What about StateRAMP / GovRAMP authorization?"
"Architected to NIST 800-53, the framework underneath StateRAMP. The formal authorization is a months-long process by design and it runs on the standard timeline - it does not block a pilot. The pilot runs under a documented security posture while authorization proceeds. That is the normal, accepted path for a new entrant, and we say so plainly rather than implying a status we do not hold."
"Where does the data live?"
"US region only. All data for a US County tenant is stored and processed in a US cloud region. Region pinning per tenant is supported."
"Accessibility - can you give us a VPAT?"
"Yes. CivicLoop is built to Section 508 / WCAG 2.1 AA from the first commit, and we ship a VPAT / Accessibility Conformance Report you can drop straight into your procurement file."
"Is resident data secure? What about privacy?"
"Minimal collection - a resident can file with just a phone number. Public facts and private facts are separated in the data model itself; the public map never exposes resident identity. Every action, staff or AI, is in an immutable audit log. No automated decisions are made about people - the AI routes requests, it does not judge residents."
"What does it cost?"
(See Document 11. Lead with the pilot, not a price list.) "The pilot is scoped and priced to be a low-risk yes. Let us talk about the pilot scope first, then the numbers follow from it."
"How long to implement, and who supports it?"
"About two weeks to configure for the real County - your departments, category tree, routing rules, SLA policies, staff accounts, branding. Then the pilot runs. Ta-Tech supports it directly; changes you ask for land fast through the engine's delivery pipeline, not a quarterly release."
"What happens after the pilot?"
"If it works, you expand it - more categories, more departments. And 311 is Phase 1. The same engine and the same connected-resident idea extend to Health and Human Services and beyond. But that is your decision to make after the pilot proves itself, not a commitment you make now."
"Why 311 and not a bigger agency like HHS?"
"Discipline. 311 is the fastest place to show real value: the incumbent is failing, the flow is demonstrable, and the regulatory drag is low. We would rather do one agency completely than five agencies shallowly. HHS is explicitly Phase 2 - the architecture already leaves the seam for it."
"What is your roadmap?"
"Phase 1 is 311, deep. Phase 2 is the connected-resident view extending to Health and Human Services. The long arc is a County Intelligence Platform - but every phase has to earn the next one."
| Failure | Plan |
|---|---|
| Live demo breaks (network, device) | Switch to the recorded backup demo video. Keep narrating. Do not apologize repeatedly - "let me show you the recorded run" and continue. |
| A feature is not finished | "That is on the build plan for the pilot configuration - here is the design and the part that is working today." Honest, calm. |
| A question you cannot answer | "I do not want to guess. I will follow up with a precise answer by [date]." Write it down visibly. |
| A hostile panelist | Stay flat and factual. Agree where you can ("you are right to push on that"), then answer. Never get defensive. |
| Time runs short | You can cut to: report -> AI routes -> resident notified -> dashboard. Those four beats are the whole story. |
Back to 00 - Index.