Twelve roles. One memory. One gate that fails on an unsourced claim.
Each role is a specialized skill invoked by the accountable human, never on a timer and never unattended. All twelve read and write the same specification, so the writer knows what the market analyst found, and the web engineer ships what the strategist decided.
Get early accessThe roster, by function
The strategist
Works alongside you on category and positioning decisions. Your thinking partner: nothing is generated or shipped without your eyes on it.
The positioning lead
Keeps your messaging system current as your company, product and market evolve, so every role works from the same positioning.
The market analyst
Tracks competitor releases and buyer language to uncover market shifts, sharpen differentiation and keep every claim traceable to a source.
The writer
Turns your strategy into clear, credible content while maintaining a consistent company voice across every public channel.
The AI-search analyst
Measures your visibility across SEO and generative AI search each month, benchmarking performance against the targets that matter to you.
The brand designer
Keeps your visual identity consistent across every asset and interface, from individual content to your website.
The web engineer
Builds and ships your website, connecting every claim to the proof behind it.
The chief of staff
Maintains quality across the entire system. If a claim can't be traced to a source, it doesn't go live.
The researcher
Builds and maintains an interconnected knowledge base of trusted sources, continuously identifying what has changed since the last review.
The dependency watcher
Monitors external dependencies (from writing rules to npm packages and tailored upstreams) for drift. When something changes, it proposes an update for your approval. Nothing upgrades automatically.
The content reviewer
Explains the uncommitted strategy and research changes in plain language before they commit, so you can approve or push back. It commits only what you approve.
The website reviewer
Explains what changed on the live site in plain language before it ships, so a non-developer knows what a visitor now sees. It commits only what you approve.
What keeps it a department, not a chatbot
One shared memory
Every role reads the same specification and the same source ledger. Nothing gets re-derived or contradicted between roles.
A hard quality gate
Before anything ships, a check runs against the document: every number needs a source tag or an explicit label as inferred or assumed. An untagged claim, a dead link or a banned phrase fails the build. No override.
Manual invocation, always
There is no cron job running the workforce. A human decides when strategy gets revisited and when content ships, because that judgment does not scale by schedule.
How does an AI marketing workforce avoid making things up?
Tabula Rasa's workforce writes against a shared specification where every statistic carries a source tag, an inferred label, or an assumption label with a way to validate it. A quality gate scans every document before it ships and fails the build on an untagged number, a dangling citation, a dead link, or banned filler language.
See what the gate has already caught.
We run our own dashboard in public: the specification, the decision archive and every flag the gate has caught on this company's own marketing.
Running in Public