Coworker is an AI teammate platform aimed at companies whose agents keep re-reading the same Slack threads, CRM records, docs, and Jira tickets on every prompt. Today's launch is OM2, an "organizational memory" layer that connects through a single MCP, ingests data from more than 50 enterprise tools, and distills it into a permission-aware graph of the customers, projects, people, and decisions that make up a business. The pitch to founders and operators is simple: over half of enterprise AI token spend goes into rebuilding context from scratch, and OM2 is designed to do that work once and reuse it.
Under the hood, OM2 combines specialized language models and classical ML to extract discrete facts (who was involved, what was decided, which accounts are affected) and keeps refreshing them as new information lands in connected systems. It also converts repetitive tool-chain queries into deterministic lookups so common questions stop paying full LLM tax, and it pairs with Coworker's model routing to send simple retrieval to cheap models while reserving frontier models for real reasoning. Access controls are baked into every node in the graph, and the platform runs on single-tenant infrastructure with SOC 2, GDPR, and CASA Tier 2 posture. OM2 works with Claude, ChatGPT, Gemini, and open models hosted on Coworker itself, so teams are not locked into one vendor's memory.
Coworker was founded by Alex Calder (CEO) and Bradford Church (CPO), both former Uber operators, and came out of stealth earlier this year with a $13M seed round to build a general-purpose AI teammate. OM2 is the follow-up to their original OM1 memory architecture, and it matters now because the industry conversation is shifting from bigger context windows to cheaper, governed retrieval. It is available today at coworker.ai.
Comments (11)
Sign in to join the discussion.
P
Priya NandakumarSep 4, 2026
The 50% token bill stat in the tweet copy is the entire pitch. Everything else in the thread could have been cut.
S
Sifiso DlaminiSep 4, 2026
building something adjacent, roughly 3 weeks from launch lol. the token bill framing is smart positioning, everyone stares at that invoice on Monday.
M
Marco BeltránSep 4, 2026
ok wait, permanent company memory is the actual unlock every RAG demo has been faking for two years. curious what happens when a doc gets deleted, does OM2 forget or hoard?
A
Ashwini R.Sep 4, 2026
naive q from someone who just started as a PM: if my manager writes something in Slack that contradicts the wiki, which one does OM2 believe?
T
Tomiwa AdebayoSep 4, 2026
Before I forward this to security: SOC2 Type II? SSO via Okta? And where does the memory actually live, your infra or ours?
H
Hanako ShiroSep 4, 2026
The launch video pacing is genuinely tight, but that brain emoji in the tweet is doing a lot of unpaid labor.
L
Leo MintzbergSep 4, 2026
Reminds me of an internal tool we prototyped at Meta in 2019 called Recall. Killed by reorg. Rooting for you to actually ship it.
Z
zk_dmitriSep 4, 2026
permanent memory of a company on centralized servers is just a honeypot with extra steps. put the embeddings on-chain and we talk.
N
Nadia VolkovaSep 4, 2026
the thumbnail composition is fine but the OM2 wordmark is set way too tight against the frame edge. give it air.
C
Callum WeatherbySep 4, 2026
Really curious about the model layer here. Are you routing across providers under the hood, or is this married to one lab? Happy to chat off-record.
G
greg from marketingSep 4, 2026
I still think most companies would be fine with a well-organized Notion. Fight me.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Coworker
Right context, right model, anywhere you work.
Right context, right model, anywhere you work.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Coworker is an AI teammate platform aimed at companies whose agents keep re-reading the same Slack threads, CRM records, docs, and Jira tickets on every prompt. Today's launch is OM2, an "organizational memory" layer that connects through a single MCP, ingests data from more than 50 enterprise tools, and distills it into a permission-aware graph of the customers, projects, people, and decisions that make up a business. The pitch to founders and operators is simple: over half of enterprise AI token spend goes into rebuilding context from scratch, and OM2 is designed to do that work once and reuse it. Under the hood, OM2 combines specialized language models and classical ML to extract discrete facts (who was involved, what was decided, which accounts are affected) and keeps refreshing them as new information lands in connected systems. It also converts repetitive tool-chain queries into deterministic lookups so common questions stop paying full LLM tax, and it pairs with Coworker's model routing to send simple retrieval to cheap models while reserving frontier models for real reasoning. Access controls are baked into every node in the graph, and the platform runs on single-tenant infrastructure with SOC 2, GDPR, and CASA Tier 2 posture. OM2 works with Claude, ChatGPT, Gemini, and open models hosted on Coworker itself, so teams are not locked into one vendor's memory. Coworker was founded by Alex Calder (CEO) and Bradford Church (CPO), both former Uber operators, and came out of stealth earlier this year with a $13M seed round to build a general-purpose AI teammate. OM2 is the follow-up to their original OM1 memory architecture, and it matters now because the industry conversation is shifting from bigger context windows to cheaper, governed retrieval. It is available today at coworker.ai.
Comments (11)
The 50% token bill stat in the tweet copy is the entire pitch. Everything else in the thread could have been cut.
building something adjacent, roughly 3 weeks from launch lol. the token bill framing is smart positioning, everyone stares at that invoice on Monday.
ok wait, permanent company memory is the actual unlock every RAG demo has been faking for two years. curious what happens when a doc gets deleted, does OM2 forget or hoard?
naive q from someone who just started as a PM: if my manager writes something in Slack that contradicts the wiki, which one does OM2 believe?
Before I forward this to security: SOC2 Type II? SSO via Okta? And where does the memory actually live, your infra or ours?
The launch video pacing is genuinely tight, but that brain emoji in the tweet is doing a lot of unpaid labor.
Reminds me of an internal tool we prototyped at Meta in 2019 called Recall. Killed by reorg. Rooting for you to actually ship it.
permanent memory of a company on centralized servers is just a honeypot with extra steps. put the embeddings on-chain and we talk.
the thumbnail composition is fine but the OM2 wordmark is set way too tight against the frame edge. give it air.
Really curious about the model layer here. Are you routing across providers under the hood, or is this married to one lab? Happy to chat off-record.
I still think most companies would be fine with a well-organized Notion. Fight me.