Skip to content
AI & automation · United States

AI & automation in the United States, where the work genuinely differs.

Automation work in the US runs into fragmented state privacy law rather than one federal standard. Nineteen-plus state acts now carry different thresholds, different opt-out mechanics and different definitions of sensitive data, and an automation that treats the country as one jurisdiction will be compliant in some states and not others.

Practice

Why this page exists

Not the same work with a place name attached.

A service-by-location page earns nothing when it recombines two pages that already exist. This one exists because ai & automation in the United States runs into constraints it does not meet elsewhere — and those constraints change the sequence of the work, not just its wording.

01

What changes

Automation work in the US runs into fragmented state privacy law rather than one federal standard. Nineteen-plus state acts now carry different thresholds, different opt-out mechanics and different definitions of sensitive data, and an automation that treats the country as one jurisdiction will be compliant in some states and not others.

02

The binding constraint

Consent and opt-out handling has to be keyed to the contact's state, not the company's. Several newer acts — Nebraska, Montana, Delaware — apply at thresholds low enough to catch businesses that assumed they were exempt.

03

What we would do first

Map which state rules actually apply to your contact base before building the workflow, then encode the strictest applicable rule as the default.

04

Measurement in the United States

Separate national, state, metro and service-area demand, then join qualified calls, forms and booked work back to the correct market level.

Markets

Where this applies in the United States.

Business Profiles, addresses and service areas belong only to eligible operations. State pages do not create local eligibility by themselves.