A quarter of dbt development, shipped in one week
Problem
Coastal Community Bank had no analytics engineering practice. Reporting logic lived in ad hoc SQL and analyst tribal knowledge. Standing up a dbt foundation the traditional way was scoped at a full quarter, and the team could not pause its reporting load that long.
Approach
I founded the bank’s first dbt project: database architecture, development standards, and best-practice guidelines written before the first model. Then I put Codex coding agents inside that guardrail. Agents drafted staging and intermediate models from documented source contracts; I ran every output through the same QA and code review bar a human analyst would face. The agents did the typing; the standards did the governing.
Result
The initial data model build, scoped at one quarter, shipped in one week: roughly 13x faster. The standards and training I authored mean the analyst team now extends the project without me in the loop.
Takeaway
AI coding agents are a force multiplier only when the surrounding engineering discipline already exists. Build the guardrails first, then add the speed.