Every platform makes choices about what to build. Here are the principles that decide what ships in Txtra and, just as important, what doesn't. Publishing them is a way of being held to them.
Compliance is the floor, not a feature
The first question about any new capability isn't "will campaigns want it", it's "does it hold the compliance floor." Consent, STOP and HELP, quiet hours, registration, these aren't features you toggle; they run under everything. A capability that would make the platform faster or flashier by cutting one of those corners doesn't ship, no matter how much it might sell. That's the non-negotiable, and it's why "compliance-first" is in the foundation rather than the marketing.
Build to the real cockpit
Txtra's features map to the actual work of running a texting program, send, converse, build the audience, read the results, not to a wishlist of impressive-sounding capabilities nobody uses. If a feature doesn't correspond to something a real campaign actually does, it doesn't earn a place. The product vocabulary matches the cockpit on purpose.
Party-agnostic, always
Txtra is built for campaigns of any party, and that shapes what we build. Nothing in the platform advantages one side, and the nonpartisan election coverage treats every race the same way. A feature that only made sense for one party's playbook isn't a Txtra feature.
Honest about what the tool does
We'd rather tell a campaign a hard truth, that a tactic won't work, that a shortcut is a compliance risk, than sell an easy lie. That honesty shows up in the product: reports that show real outcomes instead of vanity metrics, AI that marks its own work instead of hiding it, and release notes that record what actually shipped. A tool you can trust is worth more than one that flatters you.
The takeaway
Compliance first, built to the real work, party-agnostic, and honest, those four principles decide what ships and what gets cut. They're the reason the roadmap looks the way it does, and the reason some obvious-seeming features will never be on it.
Frequently asked questions
What's the first thing Txtra asks about a new feature?
Whether it holds the compliance floor. Consent, STOP and HELP, quiet hours, and registration run under everything, and a capability that cuts one of those corners doesn't ship regardless of demand.
Why does Txtra's product vocabulary match the cockpit?
Because features are built to the real work of running a texting program, send, converse, build the audience, read results, not to a wishlist of impressive-sounding capabilities nobody uses.
Is Txtra built for one party?
No. It's party-agnostic by design. Nothing advantages one side, and the nonpartisan election coverage treats every race the same.
Reflects current product principles as of the date above.
Keep reading: The Txtra roadmap and compliance in Txtra.