← Fivetran
Something new at Fivetran

Grow a second maintainer without adding headcount

Published Oct 29, 2026

You’re the customer success / solutions lead. Your team is in the room.

Run your first brief, free

The setting

's lets data teams build, transform, govern and validate their data workflows, either in a web browser or with command-line tools.

Broader dbt access has not produced broader responsibility for production models.

Sponsors want continuity without new headcount, while prospective maintainers need time their current responsibilities already consume.

Who you’d be doing this for

“My manager asked who would cover my leave, and everyone looked at me to train someone.”

Raul Russo · Lead Analytics Engineer · a character in this brief

The sole regular maintainer at an Enterprise customer considering the pilot.

What is at stake

Six of eight Enterprise customers depend on one person to maintain their dbt models. You need to weigh proof of independent maintenance against the practice time customers will actually protect.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • independent practice vs protected customer time
  • repeatable programme vs project-specific complexity
  • internal capability vs external coverage
  • observable activity vs demonstrated independence

Why Fivetran

Expansion across business units depends on customers trusting more than one person to maintain their dbt transformations in Snowflake.

Written with these in mind

Technical customer success practitionersAdoption programme buildersOutcome-focused solutions advisors

Not your kind of problem? 54 more at Fivetran, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Fivetran. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

  • In August 2026, a practitioner write-up on dbt in regulated (GxP) environments said a transformation repository might change four times a week rather than four times a year, and that change controls built for quarterly releases lead people to make changes directly in the warehouse.

    Analytics Engineering in Regulated Environments | dbt (opens in a new tab) · sakaradigital.com · Aug 27, 2026

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Run your first brief, free

Where similar work appears

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about people starting something and never quite finishing it.

The same setting, from another role

Each is set around Fivetran’s dbt platform, written for a different role. They’re separate briefs, not the same scenario.