5 Reasons dbt Wizard transforms your partner practice

Generic AI tools — Copilot, Cursor, ChatGPT — can write SQL. What they do not understand is your dbt project: which model a column comes from, what tests are already defined, which downstream models break if you rename a staging table, or what a metric's grain is relative to the model that produces it. dbt Wizard is grounded in your actual project — lineage, compiled state, tests, and metric definitions — before it writes a single line. That grounding is what makes its output trustworthy where generic AI output requires extensive review.

Wizard works in 4 modes: 

• Build: Generate a model with tests, docs, and semantic definitions from a description
• Refactor: Rename or restructure with all refs following automatically
• Investigate: Trace lineage to find root causes and propose validated fixes
• Migrate: Move models without breaking dependencies. 

It is available as a free CLI that installs with a single command, or fully hosted in the dbt platform. Install the Wizard CLI in under a minute — it works with any existing dbt project on dbt Core or dbt Cloud: 

curl -fsSL https://public.cdn.getdbt.com/dbt-wizard/install/install-wizard.sh | sh

Here are 5 reasons dbt Wizard transforms your partner practice.

[CTA_MODULE]

1. Seamlessly interact across business, metadata, and data layers

The most expensive part of an analytics engagement is not writing SQL — it is the translation loop between what the customer needs in business language and the data model that answers it. Translating that into the correct source tables, join logic, existing model dependencies, and appropriate test coverage is expert work that consumes senior engineering time on every project.

Wizard compresses this loop. An engineer describes the requirement in plain language. Wizard reasons across existing models, identifies upstream sources from lineage, proposes the model structure, and produces a complete output including tests and documentation — all consistent with what is already in the project. When the customer later asks why a metric looks wrong, Wizard traces the answer through the model graph rather than hallucinating a response.

2. Build beyond transformations — governance from the first line

Most dbt models are built in the same sequence: write the SQL first, add tests when there is time, write documentation when the customer asks. The result is analytically correct models with fragile governance — tests that were afterthoughts, documentation that does not match the actual logic, and semantic definitions that were never written at all.

Wizard's Build mode changes the default. Describe the requirement, and Wizard produces the SQL transformation, the schema.yml test definitions, the column-level documentation, and the semantic metric definitions — simultaneously, and matching the project's existing conventions. It then self-validates before surfacing the edit: the proposed model compiles, the tests do not duplicate existing ones, the documentation follows project style, and no downstream refs break. Problems are caught before they ship, not discovered in production.

3. Solve problems from any angle — any starting point, any schema

Partner engagements do not arrive in a standard form. Some start with no dbt project at all. Some involve extending a mature project with hundreds of models. Some work from a layered architecture — bronze raw data, silver conformed, gold business-ready. Some in regulated industries map source data to a recognised industry schema: FHIR for healthcare, CDM for retail, standard financial data models for banking.

Wizard handles all of these starting points. For greenfield work, it generates staging models from source schema introspection. For existing projects, it traces what already exists before proposing anything, so nothing new breaks what is working. For layered architectures, it understands each layer's role and produces models appropriate to it. For industry schema mappings, provide the target specification as context, and Wizard generates models that map the customer's source data to those conventions — correctly and consistently, across the full schema.

For partners doing data lake modernisation work, Wizard can introspect the bronze schema from Parquet files registered in Unity Catalog or the Fivetran Iceberg REST Catalog and propose the full silver and gold layer structure. The source-of-truth is the lake, not a warehouse table — and Wizard reasons from it directly.

4. Build agent-ready models — not just analyst-ready

A model that is analyst-ready produces correct numbers in a dashboard. An agent-ready model needs more: complete column-level documentation so the agent understands what each field represents, comprehensive tests so the agent can trust the data, metric definitions with unambiguous grain, and documented lineage so the agent can explain where a number came from. Without this completeness, agents either hallucinate explanations or refuse to answer.

Fivetran and dbt's joint product vision as of June 2026 is explicitly oriented toward an agent-ready future where dbt models are the governed data layer that agents reason over. Wizard is the practical tool that gets a project there. It validates metadata completeness before a model ships, flags semantic definitions that are missing or ambiguous, and checks test coverage against the assertions agents will make from the model's output. A model that passes Wizard's validation is a model an agent can be trusted to reason from.

5. Deliver faster in the transformation layer too

Partners who have adopted Fivetran already know what pipeline acceleration looks like: sources configured in 15 minutes, schema drift handled automatically, first data in the warehouse before the project is formally scoped. That speed is the foundation of differentiated delivery. But it is only half the story. The time between data landing in the warehouse and a production-quality dbt model running on it — particularly for complex business logic, unfamiliar schemas, or industry-specific data models — has not changed as dramatically. Senior analytics engineering time is still finite and expensive.

dbt Wizard closes this second gap, offering model comprehension, model generation, model extension, and model governance — all accelerated within the same dbt project that Fivetran's Integrated Scheduling is already triggering. Partners who can configure Fivetran sources in 15 minutes and produce governed, tested, documented dbt models in hours are delivering analytics capabilities in days that previously took months. When outcomes arrive faster than the customer expected, scope expands, and the engagement grows. The practice that masters Fivetran and dbt Wizard sets the delivery standard the market competes against.

Additionally, the dbt Wizard CLI is free and installs in under a minute. It works immediately with any existing dbt project — no new procurement, no tool evaluation, no customer infrastructure change required. The fastest way to validate its impact is to bring it to the next engagement and measure model comprehension time on an unfamiliar project.

The last gap in partner delivery speed is closing

Fivetran compressed the pipeline layer. dbt Quickstarts compressed the most common transformations. Activations compressed the activation layer. dbt Wizard closes the remaining gap: custom transformation work grounded in expert knowledge of the customer's data, business logic, and project. Install the CLI. Bring it to the next engagement. Measure the difference.

Install:  docs.getdbt.com/docs/dbt-ai/wizard-cli   

Product:  getdbt.com/product/dbt-wizard   

Agent vision:  fivetran.com/blog/fivetran-dbt-an-open-agent-ready-future

[CTA_MODULE]