Houston, TX · Government agencies & mission-driven orgs
Custom software for government
and mission-driven agencies.
Software, cloud, cyber and operations. Fixed price, in your own environment, and you own the source code at the end. If the systems you already bought do not talk, that work is in scope too.
- NAICS 541511 · 541512 · 541519 · 541370
- Entity Texas LLC
- SAM.gov UEI ENCPSJY88WN1
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 seven systems we built — a permit counter, a records office, a district's state reporting, a city's month-end close, an access review, a zoning notice map and an agenda office, 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 cases 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.
- Available
Federal prime
SAM.gov UEI ENCPSJY88WN1. Ready to bid as a prime.
Software, cloud, cyber and operations — the work a product never quite covers.
-
Systems that do not talk.
A case system, a finance system and an identity store from three vendors. The process runs on people copying data between them by hand.
-
A workflow that was never built.
Intake, review, status and reporting still live in email and spreadsheets, because no product matched how the work actually runs.
-
Security treated as a finding.
Access lives in a spreadsheet, logging is an afterthought, and the first real review is a finding. The system was never designed to be trusted.
-
A cloud move nobody will fund as a replacement.
The vendor is gone, the database is unsupported, and every quote has been a rip-and-replace. The job is to move it in stages, in the accounts you already have.
What we actually sell
Programs are not short of products. They are short of software, cloud, cyber and operations built to how the work actually runs. That is the job, including the joins no vendor ever shipped.
The work we take.
Shapes of problem rather than a product menu. The full list, with what each one builds and how long it takes, is on what we build.
-
Case and workflow systems
Development services, licensing, code enforcement, 311
Work arrives, goes to several departments, and then nobody can say whose move it is. The status field says "in review" and has said so for three weeks.
-
Statutory deadlines and clocks
City secretary, records, legal
A statute gives you ten business days, the clock stops for a clarification and restarts when it is answered, and today it is tracked in a spreadsheet somebody maintains by hand.
-
Regulatory reporting and validation
PEIMS coordinators, finance, grant administrators
You submit a file to the state or a federal agency, it comes back rejected as a list of codes against record numbers, and somebody spends a fortnight correcting records one at a time.
-
Reconciliation between systems that disagree
Finance, utility billing, treasury
Two systems hold different totals for the same money and closing the month means a person comparing exports by eye. Everybody knows which differences are “normal” and nobody has written it down.
-
Identity, access, and offboarding
IT, internal audit, HR
Somebody asks who still has access after leaving and answering it means exporting user lists from six systems into a spreadsheet that is out of date before the meeting.
-
Mapping and spatial analysis
Planning, GIS, public works, utilities
The question is “what is near this” — who must be notified, which parcels flood, what a main isolates — and today somebody measures it by hand on a plat and hopes.
-
The layer between systems
Everybody, and therefore nobody
Each system you own is individually fine. The gap is between them, which is why no vendor owns it and why the answer to most questions is a person doing an export.
-
Public-facing portals
Anything a resident or applicant touches
People telephone to ask where their thing is, because the only way to find out is to telephone.
-
Getting off a spreadsheet
Whoever maintains the spreadsheet, and their successor
The process runs on a workbook one person understands. It works, it is unauditable, and it leaves when they do.
-
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.
This work shows up in education, permitting, data and records — and in any program with the same problems. Those are settings, not a limit.
Those are the headings a solicitation gets written under. What actually gets built is one of the shapes above — each with what goes into it, roughly what it takes, and something working you can open. The whole catalog is here, and there is a PDF of it for the people who need to forward one.
All of them, built
You do not have to take any of that on trust.
Every category above has a complete working application behind it, and three more cut across all of them — an access review, a zoning notice map and an agenda office — running on invented data for places that do not exist. Seven in total. 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
- Agendas and notices three business days back from a meeting, against this city's own holidays
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 a product already does the job, we will say so on the first call. The rest of the time the work is to build it.
After handover, operations and maintenance keeps the system running: $1,000 – $1,500 / mo for upkeep, $5,000 – $8,000 / mo if it needs to keep changing. Sustainment is part of the work.