CivicLoop by Ta-Tech Solutions Purpose: The complete record of what was submitted to the Prince George's County Executive Exchange Expo: Technology Edition - Vendor Registration (Microsoft Forms, 17 pages). This is the consistency anchor. Every word said in the written submission and the live pitch on May 23 must agree with what is written here.
Note: confirm these against what was actually entered in the form.
| Field | Value |
|---|---|
| Company Name | ta-techsolutions (Ta-Tech Solutions) |
| Primary Contact Name | Valantine Angwafor |
| Title / Role | Founder (confirm) |
| Email Address | tsi.angwafor@tatech.dev |
| Phone Number | (as entered - confirm) |
| Company Website | tatech.dev (or tatech-corporate.netlify.app until the SSL cert is live) |
| Company Type | (as entered - likely Small Business / Startup) |
| Business Classification | Minority-Owned; Maryland-Based (confirm which were checked) |
Q9. Do you want to present your solution?
Yes.
Q10. Which County challenges can your solution address?
311 / Community Relations (only - single, focused selection by design).
The four 311 sub-challenges and how CivicLoop maps to each:
| County challenge | CivicLoop |
|---|---|
| Reducing call wait times and service delays | Voice / text / photo self-service intake plus AI auto-routing. Fewer calls, no queue. |
| Improving service request tracking and accountability | Every request has a status, an owner, a deadline clock, and an append-only timeline. Cannot be closed without a resolution note and proof. |
| Expanding multilingual and accessible communication tools | Every surface and notification in many languages. Voice and SMS intake are themselves accessibility features. Built to WCAG 2.1 AA, VPAT provided. |
| Creating proactive communication systems with residents | Automatic status updates to the resident in their language, on their channel, at every step. |
Q11. For the problem selected above, describe your solution.
CivicLoop is an AI-driven 311 and community-relations platform built for county and municipal government.
What it does: Residents report any issue (pothole, broken streetlight, missed collection, noise) by voice, text, or a photo with a map pin. No account and no app download are required. From the moment it is filed, every request becomes a living record with its own tracking number, status, assigned owner, deadline clock, and complete history, visible at the same time to the resident, the assigned staff member, and County leadership.
How it directly solves the selected problems:
- Reducing call wait times and service delays: Residents self-serve through voice, text, and photo intake instead of waiting on hold. AI instantly classifies each request and routes it to the correct department, so staff time goes to resolving issues rather than triaging them. The system also predicts which requests are about to miss their service deadline before it happens.
- Improving service request tracking and accountability: Every request carries a status, an owner, and an append-only timeline of every action taken. A request cannot be closed without a resolution note and proof. Leadership sees a live dashboard of volume, category mix, service-level health, and a map of activity across the County.
- Expanding multilingual and accessible communication tools: Every resident-facing surface and every notification is available in many languages. Voice intake lets a resident who cannot or does not type file a request by speaking, and SMS serves residents without a smartphone. The platform is built to Section 508 / WCAG 2.1 AA, and we provide a VPAT.
- Creating proactive communication systems with residents: Every status change (received, assigned, in progress, resolved) automatically notifies the resident in their language, on their preferred channel, with no staff action required.
Use cases and prior implementations: CivicLoop is purpose-built for this initiative and is in active development for a working demonstration. It is built on the Ta-Tech Solutions platform engine already running in production across our healthcare platforms, which provides multi-tenant isolation, role-based access, audit logging, a multi-language pipeline, offline-first operation, and an event-and-automation engine. The proven foundation is in use today; the 311-specific layer is what we have built on top of it. We would welcome the opportunity to demonstrate the full resident-to-resolution flow live.
Q12. What type of technology does your solution utilize?
- Artificial Intelligence / Machine Learning
- Automation / RPA
- Data Analytics / Dashboards
- Mobile or Web Applications
- Cloud-Based Platforms
(IoT / Smart Infrastructure deliberately NOT selected - CivicLoop is software driven by people, not sensors.)
Q13. What stage is your solution currently in?
Prototype. (Options were: Concept / Prototype / Active in Market / Government-Ready or Previously Implemented. Prototype is the honest pick: a working solution in active build, on an engine already in production.)
Q14. Do you have experience working with government agencies?
(As entered. Honest context if asked: Ta-Tech's PolyHealth platform is being built for a Cameroon Ministry of Health evaluation and a regional public-hospital pilot - government-sector experience, though international and early-stage.)
Q15. How quickly could your solution be deployed?
1 to 3 months. Roughly two weeks to configure for the real County (departments, category tree, routing rules, staff accounts, branding), then the pilot runs.
Q16. Will you be able to provide a live demonstration or prototype?
Yes.
Q17. What equipment or setup will you require?
Minimal. CivicLoop is a web-based platform, so we will bring our own laptop and a smartphone (the smartphone shows the resident-side reporting experience). From the venue we would need only: a display or projector with a standard HDMI connection, reliable internet or WiFi access, and a power outlet. No installation, no special hardware, and no advance setup on the County's part is required.
Q18. Biggest technology gaps in local government today?
The biggest gap is the "black hole": systems that take information in but never close the loop. A resident files a request, a patient is referred, an applicant submits a permit, and then nothing comes back. No status, no accountability, no resolution they can see. Closely related is fragmentation. Agencies run on disconnected systems, so the resident becomes the integration layer, repeating themselves at every door. Third, accessibility and language access are still treated as features to add later rather than requirements built in from the start, which leaves real residents unserved and creates compliance risk. Fourth, much "modernization" simply gives staff a new place to do the same manual work instead of removing it. The common thread is technology that is busy rather than useful. The gap is not a lack of software. It is a lack of software that actually closes loops, connects across agencies, and reduces effort.
Q19. One innovative solution PG County should implement?
A single, multilingual front door for County services, backed by a connected view of the resident. Today a resident has to know which agency owns their problem before they can ask for help, and each agency sees only its own slice. The County should let any resident raise any need in plain language, by voice or text, in the language they actually speak, and route it to the right agency automatically. Behind that door, with the resident's consent and strict privacy controls, the County would see a coherent picture of a household across services instead of six disconnected records. This is where civic technology is heading: not a portal per department, but one understanding of the resident. It would start narrow and provable (a single agency, such as 311) and extend deliberately to Health and Human Services and beyond. The hard part is privacy and trust, and that must be designed in from day one, not bolted on later.
Q20. Barriers to adopting new technology, and how to overcome them?
The biggest barrier is risk aversion, and it is earned: governments have been burned by large, all-at-once implementations that failed publicly. The answer is to start small. A real pilot, one agency, one workflow, with clear success metrics, proves value before a major commitment. A second barrier is vendor lock-in. Governments stay on systems that no longer work because leaving is too costly. This is overcome with open standards and data portability, so the jurisdiction can always take its data and go. A third is staff fatigue, because "new technology" has often meant more work. Technology has to be built around the actual staff workflow and remove manual steps, not add a screen for the same effort. A fourth is compliance and security uncertainty, overcome by building to recognized standards (NIST, Section 508, US data residency) and being transparent about what is done today versus what is in progress. Trust is built by being small, open, useful, and honest.
Q21. Final Confirmation
Confirmed. "I understand that if selected, I will be expected to present a solution aligned with County challenges, including a demonstration and an implementation overview." This matches the May 23 plan exactly.
Next: 13 - Presentation Readiness.