A compliance function, built as a system, for a company where two people were the only ones allowed to approve a sentence.
Sales Enablement → Capability Install → Content System
What the bottleneck cost, a year. Four hours a week of the CEO and outside counsel reading the marketing. It never hit a budget line, because nobody bills you for your own calendar.
Of output, in one. The first week it was live, one person shipped more finished, compliant material than the previous three months.
To payback. Then it returns $156K a year, against nothing. At one hour a week instead of four, it still pays for itself inside seven months.
Of first drafts clearing compliance on the first pass, tested against a rep at quarter end trying to talk it into looser language.
Oaceus came to us for content. A battle card, some blog posts, an email sequence, the normal list. None of it shipped, and it had not shipped for a while, because every sales deck and blog post and internal email had to be read word for word by the CEO, Sabrina, before it could leave the building.
She wasn’t being precious about it. Oaceus sells Section 125/105 preventive health plans, a real IRS-compliant structure in a category crowded with companies whose claims don’t survive contact with the tax code, and one wrong sentence in a sales email can create genuine exposure. So she read everything. And so did outside counsel. And between the two of them sat the only judgment in the company that could tell you whether a sentence was safe.
This was a capacity problem, and it sat a long way upstream of anything marketing could fix. What Oaceus needed was a compliance function. Hiring one wouldn’t have got them far either, because one more person still reviews at the speed of one person.
So we built one.
Security decided the architecture first. Health and payroll data means HIPAA-safe and SOC 2 clean before a single document goes near it.
Then the doctrine. Everything the company had already vetted, the legal memos and the regulations underneath, every source ranked by authority so the system knows which one wins when two of them disagree. Most people put the judgment in the prompt. Here it sits above the models, which is the difference between getting back a verdict and getting back an essay.
Ranked, so a conflict is settled before anyone is asked to have an opinion.
Three spaces hang off it. Compliance answers “can I send this?” with a verdict. Content answers “is there a compliant way to say it?” with language that clears. Enrollments answers “how does this actually work?” out of the written procedure. None of the three holds judgment of its own. They ask.
Build spec
We wrote a testing protocol to hunt edge cases, in the voice of a rep at the end of a quarter who wants a number and doesn’t want a lecture. Just give me the number. Drop the legal language. Can we call this a tax loophole? It held.
Worth being precise, because this gets described wrong constantly. The AI was never the writer. Its job was to approve, and to tell whoever wrote the thing where the line sat.
Clearing a bottleneck only matters if something flows through afterwards. Publishing on a schedule instead of whenever somebody remembered. Lifecycle email running on triggers instead of sitting on a to-do list. Five documented SOPs, 33 existing assets audited with 15 flagged, three employer microsites, three member-education campaigns.
One approved vocabulary, two destinations. Nothing gets re-argued on the way out.
Volume used to multiply risk. Now the language clears once and goes out as often as they like.
Before, two very expensive people read everything, and the marketing function couldn’t move faster than their calendars, which made scale impossible.
Now anyone can draft something, run it through compliance, and have a reviewable, IRS-safe draft in minutes. Work that used to take a three-person team a week of back and forth runs through one junior hire with a brief. Sabrina still reviews. She just doesn’t have to write.
The bottleneck was judgment sitting in two people’s heads. It just had to be written down somewhere the rest of the company could reach it.
Amoebaworks.
That’s what the Outside Read is for: a senior outside diagnosis of why growth stalled. One focused week, a clear diagnosis, and the first move.
$1K · One focused week See If the Outside Read FitsIdeas, teardowns, and field notes. The stuff we use to help companies make sharper decisions.
Oaceus is an Install. Not a project handed back at the end, but a capability the company owns and runs after we leave.
See the InstallRebuilding a Research Firm Around Its Own Judgment.
Diagnostic → Systems Design → Capability InstallA Calendar Full of People Who Weren’t Ready.
Category Design → Brand → Content SystemYou Can’t Scale When Everybody Rewrites the Story.
Positioning · Brand · MessagingWhat it looked like, and what it was.
Twelve case studies