What we will not build, and why that should matter to you.

There are going to be a lot of firms telling you the same things we tell you. Private models. Data that stays put. Hardware you own. Those claims are true of us, and in a year they will be true of a dozen others, so they do not tell you much about who you are dealing with.

What does is the list of things a firm will not do. Capability is easy to claim. A refusal costs something, which is why almost nobody publishes one.

Here is ours.

Surveillance, facial recognition or policing technology

We do not build systems that watch people, identify them, or predict what they will do. Our municipal work is constituent services, permitting and records. It is not enforcement, and we say so in writing before a town engages us.

AI making final decisions about people without a person in the loop

Hiring, firing, credit, benefits. A system can prepare the file, sort the queue and recommend. A person decides, and the record shows who did. We will not build it the other way, and if a vendor offers to, ask them who is accountable when it gets one wrong.

Rip and replace of core systems

Your ERP, your case management system, your records system. They stay the system of record. We make them better rather than replacing them, because a replacement that nobody asked for is a year of disruption sold as progress. If something genuinely needs to go, we will say so, and it will be your decision on your timeline.

Generic chatbots with no process behind them

A chat window on a website that answers nothing in particular is not a product. Everything we build is attached to a specific process with a measurable outcome. If we cannot name the process, we do not build it.

Electrical work or safety certification in-house

On robotics projects, licensed electrical work and formal safety risk assessments to ISO 10218 and ANSI/RIA standards are done by licensed and certified partners under our project management. We are the accountable integrator. We are not the electrician, and we do not certify our own cells.

Regulated data without the right agreements in place

Healthcare, legal, municipal and defense-adjacent work each carry obligations that follow the data. We do not touch regulated data until the agreements that govern it are signed and the architecture satisfies them.

Why publish this

Because some engagements should end in the first meeting, and it is better for both sides when they do. And because a firm that cannot tell you what it will not do has not thought hard enough about what it will.

The full version, with what each item means in practice, is on What we will not do. Use it on anyone else you are talking to as well.