Whether your data team is two people, twenty, or doesn’t exist yet, the kind of organization most companies actually need — clear ownership, real escalation, decisions on the record — is one nobody can afford to hire on day one. Crewdata fills those roles with AI agents — not a copilot, not another observability layer: one who does the work, another who reviews it and tries to refute it, and a paper trail when they decide. We’re not here to replace your stack. We’re here to operate it.
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 incidents don’t start with bad data. They start with a change nobody announced, a metric defined two different ways, or a decision made in a meeting that never reached the model. An organization with clear ownership, working escalation, and decisions on the record isn’t bureaucracy — it’s how the translations stop getting lost.
A tool waits to be used. A teammate takes ownership. Crewdata agents don’t just execute instructions — they own a piece of the work, document their decisions, and hand them to someone who will try to refute them.
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, born as a lab in 2026: can a small team have a 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.
Crewdata is built to catch the displacement — and to put what it did on the record, with a date.
On Sep 1, 2026, at 09:08, a freshness check on one source table came back red in jaffle_shop, our own test environment, and became a case inside Crewdata.
The engineer role looked at where that table comes from: it is loaded in the same batch as its parent table, so their freshness can never diverge, and the parent already carries the precise check.
Its verdict, at 09:33: the alarm was redundant. It did not fix a failure; it proved there was none, and proposed removing the second, coarser check.
At 09:45 another role, in its own working copy, tried to refute that reasoning and could not.
Neither of them is a person. They are the same model in two different positions — one that does, one that reviews — and that is the point: whoever executes is not whoever approves.
The change waited for a human signature. It landed in the repository on Sep 7, with the case number and the signer’s ID written into the commit itself.
What it taught us: most of what came back red that month was not broken data. Of the seven changes the organization has landed since August, four turn off a check that was structurally redundant, one corrects a false positive in another check, and two make a check stricter.
And what we watch for: the organization proved one alarm redundant. It has not yet been asked to build anything new, and we say so.
Sep 2026 · The case is on film above. Screens cropped, never retouched.
Formula 1 teams don’t test new setups in a race. They test them in a simulator that replicates the car, the track, the temperature, the tyre wear, the driver’s reflexes — every variable that matters. By the time a setup reaches the track, it’s been run against thousands of scenarios.
Data organizations have no equivalent. New ownership models, new escalation rules, new governance structures — they all get tested live, on real data, with real teams, against real consequences. When something breaks, you usually find out months later: after the dashboard goes wrong, after the postmortem, after the people who made the call have moved on.
Crewdata is built as that simulator. A complete fictional company — with domains, dashboards, dependencies, and a team of agents operating as the data org — running close enough to reality that we can ask the questions you can’t ask in production. Its name is jaffle_shop. Every dated case on this page happened there.
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. In some companies they were never even on the hiring plan. Crewdata builds that structure as a system of AI agents, so a small team gets the structure it could not hire — and a team of zero has somewhere to start.
Human review is part of the design. Nothing reaches production without a human signature; what an agent may touch is written down in code, not decided by the agent. You decide the business.
Sep 7, 2026, in the repository of our test environment. Seven agent commits since Aug 6, 2026, each carrying a human signer’s ID.
Assisted pilot, installed in your own environment. For small data teams running dbt on BigQuery.
Write to hello@crewdata.aiWhatever we learn gets written down. Plain language, dated. We won't publish the code — but we will show what it did, cropped from real screens, and what broke, and what surprised us along the way.