Houston, TX · Government agencies & mission-driven orgs
Custom software for schools,
cities and public agencies.
You already bought the systems. We build what was never made to connect them — fixed price, in your own environment, and you own the source code at the end.
- NAICS 541511 · 541512 · 541519
- Entity Texas LLC
- SAM.gov Registration in progress
Evaluating a bid or working a requirement? The capability statement has the registrations and who to call, on one page. Federal buyers and primes start here.
Or skip all of it and go use one of the six systems we built — a permit counter, a records office, a district's state reporting and a city's month-end close, with thousands of sample records and rules you can edit. No sign-up, nothing to install.
Bottleneck Fire review has held 14 of the last 30 permits past target. Visible here before it is a complaint at a council meeting.
This one is real, and you can operate it — 240 sample cases, plan review, inspections and fees.
How agencies contract with us.
Start with a purchase order or a subcontract. NAICS, NIGP, SAM status and the Texas paperwork are on the procurement page.
- Available
Direct award
Purchase order or award under your bid threshold — commercial, state and local.
- Available
Subcontract
We work under a prime that already holds the vehicle, including on federal work.
- In progress
Federal prime
SAM.gov registration is in progress. We finish it before we bid as a prime.
Almost never a missing product. Almost always the space between the ones you have.
-
Systems that do not talk.
A body buys a permitting system, a finance system and a records system across twelve years from three vendors, and the process runs on people moving data between them by hand.
-
Reporting nobody can produce.
The number the board asks for exists, in three places, in three shapes. Producing it takes a week, and by the time it lands the question has moved on.
-
A counter queue that is really a software problem.
Intake on paper, review in email, status by telephone. The queue at the counter is the visible part of a process nobody designed.
-
A migration nobody wants to start.
The system works, the vendor is gone, the database is a version nobody supports, and every quote to move it has been for a replacement nobody can fund.
The part that ends up in the minutes
A public body has usually bought the right software already. What it has never been sold is the work of making any of it fit how the office actually runs, because that work is different in every building and no product company can package it.
Four categories, plus accessibility on every public-facing build.
-
Education systems
K-12 districts, education service centers and education agencies
Student data that lives in six systems, reporting that eats a week every cycle, and parent-facing tools nobody wants to open.
-
Permitting and licensing
Cities, counties and civilian regulatory agencies
Permit intake on paper, plan review in email, inspections in a spreadsheet, and a counter queue that exists because none of them talk.
-
Data and systems integration
Any agency running more than one system of record
The layer between the systems you already bought. Migrations, interfaces, and the reporting nobody can produce because the data is in three places.
-
Records and case workflow
Clerks, records programs and legal teams at federal, state and local agencies
FOIA and public records requests answered by hand, retention schedules tracked in a binder, and decades of paper nobody can search.
-
Accessibility
WCAG 2.1 AA — exceeds Section 508
Section 508 requires WCAG 2.0 AA. Public-facing work is built to 2.1 AA, which exceeds it, and tested with a keyboard and a screen reader before handover. VPAT on request.
All of them, built
You do not have to take any of that on trust.
Each category above has a complete working application behind it, plus an access review that cuts across all of them — running on invented data for places that do not exist. Not screenshots and not a scripted tour — real systems with thousands of sample records, the actual statutory and accounting arithmetic, and rule sets you can edit and watch every figure in the building recompute.
- Permits and inspections 240 cases, plan review, fees, inspections
- Public information requests four statutory clocks, tolling, Attorney General deadlines
- State reporting 4,300 student records, real rule codes, allotment at risk
- Month-end close six ledgers reconciled, and it grades its own explanations
- Access review who still has the keys, across six systems nobody joined up
- Zoning notice map who must be written to before a rezoning, measured not guessed
What these are, and what they are not — everything runs in your browser, nothing is a client record, and anything you change is yours alone.
Five things that are true of every engagement.
- Fixed price
- Agreed before work starts and invoiced against milestones. No hourly billing and no change-order arithmetic.
- Your infrastructure
- Built and deployed in the entity’s own cloud accounts, under the entity’s own contracts.
- You own the source
- Delivered to your repository under a license permitting unrestricted use, modification and resale. No seat licenses.
- 90 days warranty
- Defects are ours for ninety days after handover, at no cost.
- Nothing switches off
- If the relationship ends the system keeps running. There is no kill switch and no renewal you are hostage to.
If an off-the-shelf product does what you need, buy the product. We will say so on the first call, and we would rather say it then than after a procurement.
After handover, operations and maintenance is how the system stays running — $1,000 – $1,500 / mo to keep it alive, $5,000 – $8,000 / mo if you want it to keep moving. Agencies buy sustainment, not just launches.