Case study 01 · Coastal Community Bank dbt · Codex · Snowflake

A quarter of dbt development, shipped in one week

13x
faster than the traditional scope
1 wk
to ship the initial model build
4
gates every model passes before merge

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.

Agent-assisted dbt workflow agents do the typing · standards do the governing
Development standards + best-practice guidelines · govern every step below
Gate 1 · Human
Source contract
documented inputs, grain, and definitions
Agent · Codex
Agent draft
staging + intermediate models from the contract
Gate 2 · Automated
Automated tests
dbt tests and CI checks on every model
Gate 3 · Human
Human review
same QA and code review bar as analyst work
Gate 4 · Ship
Merge
nothing lands without passing all four gates
fails tests or review ⤺ back to agent draft

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.

Case study 02 · Coastal Community Bank AI agents · semantic layer · governance

Cutting ad hoc workload from 90% to 15%: a playbook

~90%
of team time on ad hoc, before
15%
projected, after the agent rollout

Problem

The analytics team spent roughly 90% of its time on ad hoc requests. That is a team functioning as a human query interface, with no capacity for the strategic work it was hired for.

Approach

Rather than another dashboard mandate, I introduced AI analytics agents as the self-service layer. The playbook:

  1. Build a governed dbt semantic layer so the agent queries certified definitions, not raw tables.
  2. Pilot with the highest-volume request categories.
  3. Publish metric dictionaries so agent answers are auditable.
  4. Route what agents cannot answer to analysts as properly scoped projects, not interruptions.

Result

The strategy is projected to cut non-value-add ad hoc workload from about 90% of team time to as low as 15%, converting most of the team’s calendar from reactive queries to leveraged analytical work.

Takeaway

Self-service failed for a decade because it asked stakeholders to learn tools. Agents flip it: stakeholders ask questions in English, and governance moves into the semantic layer where analysts control it.

Case study 03 · Dolly / Taskrabbit experiment design · A/B testing · decision support

A decision-support tool that moved two metrics 50%

-50%
reschedule rate
+50%
partnership volume
-15%
apartment-move cancellations, via A/B program

Problem

At Dolly, Retail Ops reschedules were eroding partner trust and revenue. Intuition-driven fixes were not moving the number.

Approach

I built a decision-support tool that put the right data in front of ops at decision time, then led the experimental design to measure impact honestly: clean control groups, pre-registered metrics, and enough runtime to trust the readout. The same discipline ran the company A/B testing program, including the test series that cut apartment-move cancellations by 15%.

Result

Reschedule rate down 50%. Partnership volume up more than 50%. Measured, not estimated.

Takeaway

Decision-support beats reporting. A dashboard shows what happened; a tool changes what happens next.

Want the story behind a number?