14 - Executive Summary

CivicLoop by Ta-Tech Solutions Prepared for: Prince George's County Executive Exchange Expo, 2026-05-23 Tagline: Every request seen. Every loop closed. Autopilot when you want it. Purpose: The one-page briefing for a busy reviewer. Read this first.

What CivicLoop is

CivicLoop is an AI-driven 311 / community-relations platform purpose-built for Prince George's County. It replaces a 1.5-star app residents currently cannot file requests through with a system the County controls, residents trust, and staff want to use. EN + ES from day one, voice + text + photo intake, an agent console and Director dashboard, and a ten-component AI layer that routes, predicts, detects duplicates, classifies sentiment, proactively communicates, AND now runs an Autopilot orchestrator (off/route/full, set by the County on a single dial), a predictive issue forecast for the next 7 days, a self-healing SLA escalator, and a Loop AI persona that lives inside Slack-style department channels. NPS-measured satisfaction (auto-survey on every resolved request) and equity transparency by council district are first-class panels on the director dashboard. A separate public portal at /public publishes the County's weekly numbers to anyone, no account, no PII. Open311 / GeoReport v2 standards compliant in both directions, so the County is never locked in.

Why us, in three lines

1. Phase 1 of a County Intelligence Platform, not a pothole app. 311 today, HHS tomorrow, the same engine underneath. The pitch is the start of a multi-agency relationship, not a one-shot software sale.
2. A proven engine, not a greenfield gamble. CivicLoop is built on the Ta-Tech platform engine that already runs PolyHealth (live pilot, 142 pages, 210 tables) and four other deployed apps. Half of what CivicLoop needs already exists in production: auth, RBAC, 2FA, multi-tenancy, audit logging, document generation, the agentic layer. Nine days to a pitch is realistic because we did not start from zero.
3. The standards-first, anti-lock-in posture. Every request the County files through CivicLoop is reachable via Open311. Every byte of County data is exportable any day, by anyone with County credentials. If the County leaves us, the data leaves with them through the same open standard it came in by. That is the opposite of the incumbent.

What the panel will see live

The Maria-pothole flow, end to end:

1. Maria opens CivicLoop in Spanish on her phone, no account. She taps the photo button and snaps a picture of the pothole. The AI reads the photo: it picks the category (pothole) automatically AND it reads the street sign in the background and fills the address as "7700 Riggs Rd, Hyattsville MD". She taps the mic, says "es muy profundo" and the browser speaks it back: "Le escuche: es muy profundo". Total resident effort: under twenty seconds. The success page shows a tracking QR she can scan from any other phone to pull up the same status.
2. The AI routes the request to DPWT at high priority, classifies sentiment, predicts SLA risk against the department's open queue, checks for duplicates in the last 72 hours, and notifies Maria by SMS with her tracking number.
3. An agent picks it up in the queue, schedules a follow-up visit (Maria gets SMS + email + a .ics calendar invite), replies in the same thread Maria reads on /track, attaches a proof-of-resolution photo, and closes the loop. Maria gets a resolved SMS in Spanish AND a one-tap 1-5 survey link. If she disagrees, she replies and it auto-reopens.
4. The Director Dashboard surfaces the same request on the predicted- breach card, in the "rising this week" trend, AND as a colored dot on a live PG County heat map - click the dot, the workspace opens. The new panels show alongside: Equity ("District X waits 2.3x longer than District Y"), Forecast (the expected count for the next 7 days per category and district, with confidence), NPS (avg score, CSAT %, NPS from the auto-survey), and Upcoming visits (the County's commitments for the next 48 hours).
5. The closing move: the County Admin opens /admin and flips the Autopilot dial from off to route to full. The next inbound request routes, assigns, and notifies itself in under ten seconds. The admin clicks Run self-heal now and the department channel lights up with a @first-name heads-up. Then the admin opens /public on a phone - "this URL is public, no account, no PII, ready for the press, ready for the Council, ready today."

The panel will probe each AI step; the system answers in plain language, with confidence, and shows its work. Every step fails safe.

The offer

A no-cost, time-boxed pilot, scoped to the agency the County wants proven first (311). Success criteria are defined up front with the County. We absorb the build cost; the County absorbs the demo of value. If the County says yes at pilot end, the engagement scales by agency on a per-agency, transparent SaaS model with no per-request gouging and a published exit clause. See document 11 for the structure.

What is asked of the County

A pilot agreement, a single 311 staff sponsor, and access to the open data the platform will ingest. Everything else is on us.

What is in this packet

This is document 14 of 14. The rest:

• 01-09 Vision, competitive landscape, domain model, roles, system architecture, screens, AI components, integrations, security.
• 10-11 The 9-day build plan and the pilot proposal.
• 12-13 Our vendor-registration responses and the presentation plan.

Online: civicloop-docs.netlify.app. Source repository available on request. Every section is also downloadable as a standalone PDF in this packet.

Contact: tsi.angwafor@tatech.dev Company: Ta-Tech Solutions Motto: Built for the realities of public service.