The Week AI Regulation Got Specific: Four Hot Zones for Series A Founders

This week’s signals

Nebraska made chatbot disclosure law. Nebraska LB 525, the Conversational AI Safety Act, passed the state’s unicameral legislature. It requires disclosure to minors that a chatbot is AI, disclosure to any user when a reasonable person might not know, and a prohibition on AI representing itself as providing professional mental or behavioral health care. Per a Troutman Pepper Locke state AI tracker published April 12, 2026, the Nebraska bill was one of three AI-specific bills that cleared state legislatures in the same stretch, alongside Maryland HB 895 on algorithmic pricing and Maine LD 2082 on AI-assisted therapy.

Tennessee turned AI companion training into a felony. Tennessee SB1493 makes “knowingly training AI to simulate human emotional relationships” a Class A felony, with penalties in the 15 to 25 year range, effective July 2026. A RoboRhythms roundup published April 13 placed it inside a wider wave: Washington signed a disclosure and crisis-services mandate this month, New York activated its suicide-detection protocols under S-3008C, and Missouri queued a health omnibus with AI restrictions.

The compression window is now. Maine’s legislature closes April 15, and the Troutman tracker lists bills “pending concurrence” or “advanced from committee” in Hawaii, Oklahoma, California (six distinct bills), Connecticut, Louisiana, Missouri, Minnesota, and Tennessee. End-of-session pressure is what finally pushes narrow bills across the line.

The thread connecting them

Up until this quarter, most AI regulation conversation among founders centered on whether a product was “high risk” under a broad framework. The EU AI Act. Colorado’s AI Act. TRAIGA in Texas. Those frameworks are still real, and they still matter. But the bills moving right now are narrower, more surgical, and more personal. They target specific product categories: chatbots for minors, AI therapy, emotional companionship, algorithmic pricing. And they increasingly attach criminal liability to named individuals rather than civil penalties to legal entities.

That is the category that just picked up felony-level penalties in Tennessee. A 20-person Series A can now unwittingly operate a product whose core feature is a Class A felony in one state.

Broad frameworks come with rulemaking periods, guidance documents, and enforcement runways. Narrow product-category bills tend to be self-executing. They become law, and the product either complies or does not.

Segment lens

For CEOs and board members. The governance question is no longer “are we EU AI Act ready?” That one has an answer and most teams know where they stand. The newer question is whether anyone at the company maintains an inventory of which AI features in the product could be classified as therapy, healthcare, companion, minor-directed, or pricing-related. Six months ago that list was maybe three items. In a lot of SaaS products it is now closer to seven, and nobody has written it down.

For Series A founders shipping something that talks to users in any emotionally intelligent way. Four hot zones define the near-term risk surface. Therapy and mental health (Maine, Nebraska). Minor-directed conversation (Nebraska, Washington, New York). Emotional companionship (Tennessee). Algorithmic pricing (Maryland). If your product even gestures at one of these, the compliance homework this week is not abstract. It is a specific set of disclosures, opt-outs, and product-copy changes that a founding engineer can ship in an afternoon, if someone asks them to.

One thing to do

Ask one engineer to spend two hours this week reading the product’s three most-used AI prompts and classifying them against those four hot zones. Not a committee review. Not a legal memo. A scan. The teams who get caught flat-footed in Q3 will be the ones whose CTO cannot answer “does our product ever respond to a user’s emotional state?” without looking it up. The teams who are fine are the ones where someone, somewhere, already has the list.