Most teams put off building real data organization until they can afford to hire for it. Crewdata is a lab exploring whether you can have it from day one — not a copilot, not another observability layer, but an operating model built around AI agents that own domains, escalate what they can't resolve, and document their decisions.
Most data problems aren't data problems. They're organization problems. Crewdata starts from three convictions about how to fix that.
A team with great tools but no organization produces mediocre results. A team with clear organization — even with modest tools — produces reliable ones. We don’t sell skills to agents. We give them an organization to operate within.
Most data problems aren’t talent problems. The people are there. What’s missing is the structure that lets them operate at scale — clear ownership, working escalation, outputs the rest of the business can actually trust.
A tool waits to be used. A teammate takes ownership. Crewdata agents don’t just execute instructions — they own a domain, escalate what doesn’t fit, document their decisions, and learn from what went wrong.
Data is never the first priority in a startup. Not the second. Not the third. But it's exactly what investors ask about when they're deciding whether to keep investing.
By the time a team is big enough to tackle data seriously, the debt is already there. Every shortcut taken when data wasn't the priority. Every model built to answer one question, now answering ten. Every ownership decision deferred because there was always something more urgent.
And when the org gets larger? The team fragments. Domains, tribes, squads. Twenty people in data can still mean twenty different mental models of the same problem. A strong central governance team helps — but it doesn't fix the fragmentation. The sins just move around.
That's the observation we kept coming back to. And it's what led to Crewdata — a lab exploring whether a small team can have real data organization from day one, before the debt arrives, before the fragmentation happens.
Built by Pol Martí — data leader who has built data organizations from scratch, more than once. This is what he kept seeing break.
A coordinated row tells you everything is running. The displacement — the element that breaks the line — is where the organizational work lives. The incident nobody owns. The metric that moved before anyone noticed. The escalation that stalled because it wasn’t clear whose job it was.
In a small team, nobody is assigned to catch this. There’s no data quality manager. No governance lead. No escalation path. The aggregate looks fine until it doesn’t, and by then it’s someone else’s crisis.
The lab is building the organization that catches the displacement before it becomes a problem — and knows exactly what to do with it when it does.
A CDO. A data director. Domain managers. Analysts — each trained on one slice of your business. Operating within a hierarchy with explicit escalation rules.
These are the roles that keep data reliable in a mature organization. In most teams, they don’t exist. There’s one person, or two, doing all of it. Crewdata builds that structure as a system of AI agents — so your team has ownership, escalation, and documentation from day one, not once you can afford to hire for it.
Human review is part of the design. Agents escalate what they can’t resolve. Decisions are documented. The humans on your team stay in control of what matters — they just stop doing the work the org should be handling automatically.
First incident flows in production. Data quality escalation end-to-end.
Agent memory, cross-domain ownership, semantic layer integration.
Whatever the lab learns gets written down. Plain language, dated, reproducible. We won't share code or implementation details — but we will share what works, what breaks, and what surprises us along the way.
We’ll send the next note when it’s ready. No newsletter loop. No growth hacking. Just what the lab learns — and what you can use.