Service Deck: dbt Audit Service
Slide 1: Title Slide
StoryBrand Element: Character
Copy: Headline: Your dbt runtime is cutting into business hours. Your team can’t debug 600-line models.
Subheadline: Audit roadmap: 50%+ runtime reduction, fix DAG cycles, implement modularity. 3-4 weeks.
Visual Suggestion:
- Hero Image: Split-screen visual showing chaotic dbt dependency graph (left, messy) vs. clean, organized infrastructure (right, structured)
- Placement: Full background or prominent left/right split
- Color/style notes: Use brand colors, professional but approachable. Left side: red/orange tones (chaos). Right side: blue/green tones (clarity)
Stats Included: None on title slide
Slide 2: The Problem (External)
StoryBrand Element: Problem
Copy: Headline: “I can’t get the right information fast enough to make confident, strategic decisions”
Body: 4-hour dbt runs. Data needed by 6 AM. Ingestion (1-2 hours) + dbt (4 hours) = cutting it close.
If something breaks, you’re in trouble. No room to grow. No room to add data sources.
Visual Suggestion:
- Timeline Diagram: Visual timeline showing midnight → 2 AM (ingestion) → 6 AM (dbt complete) → 5 AM (team needs data) with red warning zone
- Placement: Right side of slide, supporting the copy
- Color/style notes: Use red/yellow warning colors for the tight timeline
Stats Included:
- 4-hour dbt runtime (problem)
- 1-2 hour ingestion time
- 5-6 AM business hours start
Slide 3: The Problem (Internal/Emotional)
StoryBrand Element: Problem
Copy: Headline: “I feel exposed and inefficient. I know we’re behind, but I don’t know where to start — and I don’t trust what I see”
Body: Infrastructure built organically without principles. Now you have:
- 600-line models impossible to debug
- Tests failing for years
- No documentation—read code to understand logic
- DAG cycles breaking acyclic structure
- DRY violations everywhere
Client Quote:
“I was always wanting to bang my head against the wall because I was so frustrated. The infrastructure was a huge mess.”
— Emily, Analytics Engineer, Urban Stems
Visual Suggestion:
- Before/After Comparison: Side-by-side showing messy code (600 lines, no structure) vs. clean modular code (100 lines, organized)
- Emotional Imagery: Frustrated person at computer, or visual metaphor of chaos
- Placement: Full slide or left/right split
- Color/style notes: Dark, chaotic imagery on left; clean, organized on right
Stats Included:
- 600+ line files (problem)
- Years of failing tests (problem)
Slide 4: The Guide (Empathy)
StoryBrand Element: Guide
Copy: Headline: “We’ve been there. We’re operators too — and we built Brainforge to solve the problems we faced ourselves”
Body: We’ve been there. 90% engineers. dbt partners. No vendor kickbacks. We build what we run.
Visual Suggestion:
- Team Photo: Authentic photo of Brainforge team
- Supporting Elements: Brief authority signals (logos, certifications)
- Placement: Left side with copy, or background with overlay
- Color/style notes: Warm, authentic, professional
Stats Included:
- 90% engineers (authority)
- No vendor kickbacks (differentiation)
Slide 5: The Plan (Process Overview)
StoryBrand Element: Plan
Copy: Headline: From Chaos to Clarity: Our 3-Step Process
Body: 1. Diagnose (Weeks 1-3) Audit models, tests, dependencies, documentation, architecture. Identify bottlenecks and broken patterns.
2. Design (Week 4) Prioritized roadmap: what to fix first, what’s working, how to scale.
3. Deploy (Optional) Build parallel infrastructure. Implement fixes. Migrate over time. Keep daily operations running.
Visual Suggestion:
- Process Flow Diagram: Three-step visual with arrows: Diagnose → Design → Deploy
- Timeline Visualization: Show 3-4 week audit, then optional implementation
- Placement: Center of slide, prominent
- Color/style notes: Use brand colors, clear step indicators (1, 2, 3)
Stats Included:
- 3-4 weeks for audit (timeline)
- Optional implementation phase
Slide 6: The Plan (What You Get)
StoryBrand Element: Plan
Copy: Headline: Your Audit Roadmap Includes
Deliverables:
- Infrastructure assessment (models, tests, dependencies, docs)
- Prioritized fix list (ranked by impact)
- Architecture recommendations (DRY, DAG cycles, modularity)
- Performance analysis (bottlenecks, optimization strategies)
- Documentation & testing plan
- Implementation roadmap (phased by data mart)
Visual Suggestion:
- Icon Grid: One icon for each deliverable (assessment, prioritization, architecture, performance, documentation, roadmap)
- Checklist Visualization: Visual checklist showing all deliverables
- Placement: Grid layout, 2x3 or 3x2
- Color/style notes: Consistent icon style, brand colors
Stats Included: None (deliverables list)
Slide 7: Success (Outcomes & Metrics)
StoryBrand Element: Success
Copy: Headline: Transform Your dbt Infrastructure
Outcomes:
- 50%+ runtime reduction (4 hours → 2 hours)
- Overnight completion (ready before business hours)
- Modular code (600-line → 100-line blocks)
- Faster onboarding (clear docs, naming conventions)
- Working tests (fix broken tests, data quality standards)
- Scale confidently (add sources, increase cadence)
Client Quote:
“We were able to cut our dbt runtime from 2.5 hours down to 1 hour 40 minutes. That’s an hour saved every single day.”
— Magic Spoon Data Team
Visual Suggestion:
- Bar Charts: Before/after runtime comparison (4 hours → 2 hours)
- Gauge Charts: Show percentage improvements (50% faster, 100% documentation coverage)
- Line Charts: Show trend of improvement over time
- Placement: Mix of charts and metrics, prominent display
- Color/style notes: Green for improvements, clear before/after contrast
Stats Included:
- 50%+ reduction in runtime (% improvement)
- 4 hours → 2 hours (before/after results)
- 2.5 hours → 1 hour 40 minutes (Magic Spoon case study)
- 1 hour saved per day (time to insight/ROI)
Slide 8: Success (Before/After)
StoryBrand Element: Success
Copy: Headline: The Transformation
| Before Brainforge | After Brainforge |
|---|---|
| 4-hour dbt runs cutting into business hours | Data ready overnight, dashboards ready by morning |
| 600-line files impossible to debug | Modular 100-line blocks easy to trace |
| Broken tests failing for years | Working tests maintaining data quality |
| No documentation, read code to understand | Clear documentation and naming conventions |
| Cycles in DAG breaking principles | Clean acyclic graph structure |
| Code repeating itself (DRY violations) | Modular, reusable code following DRY |
| Frustrated team banging heads against wall | Team trusts the infrastructure and enjoys using it |
Visual Suggestion:
- Side-by-Side Comparison: Table format with visual indicators (red X for before, green checkmark for after)
- Transformation Diagram: Visual showing chaos → clarity transformation
- Placement: Full slide, prominent table
- Color/style notes: Red tones for “before”, green tones for “after”
Stats Included: None (qualitative transformation)
Slide 9: Case Study/Proof
StoryBrand Element: Guide (Authority)
Copy: Headline: Urban Stems: From Chaos to Clarity
The Problem:
- Infrastructure built without principles over years
- 600-line models impossible to debug
- Tests failing for years
- New engineer (Emily) completely lost
The Solution:
- Built parallel infrastructure (daily ops continued)
- Applied modularity (600-line → 100-line models)
- Clear naming conventions (hub-and-spoke logic separated)
- Documentation and structure
The Result:
- Debug issues in minutes (not hours)
- Easy to find and fix problems
- Team actually wants to use it
Visual Suggestion:
- Client Logo: Urban Stems logo
- Before/After Metrics: Visual showing improvement (qualitative: frustration → clarity)
- Testimonial Card: Emily’s quote prominently displayed
- Placement: Logo top, metrics center, quote bottom
- Color/style notes: Professional case study layout
Stats Included:
- 600-line files → 100-line files (before/after)
- Minutes instead of hours for debugging (time to insight)
Slide 10: The Agreement (Confidence Guarantee)
StoryBrand Element: Plan
Copy: Headline: The Confidence Guarantee
| Fear | Our Guarantee |
|---|---|
| ”This is going to take forever” | You’ll see results in 3-4 weeks — not months |
| ”Will this disrupt my team?” | We build parallel infrastructure — you keep daily operations running |
| ”Will this create more work for me?” | We handle the audit — you get a clear roadmap |
| ”Will I be left managing it alone?” | We stay hands-on until it works — and can implement fixes if you want |
| ”What if my infrastructure is too complex?” | We’ve audited projects with thousands of models — we can handle it |
Visual Suggestion:
- Checkmark Icons: Green checkmarks for each guarantee
- Guarantee Badges: Visual badges or icons for each point
- Table Format: Clean table with fears on left, guarantees on right
- Placement: Center of slide, prominent
- Color/style notes: Green checkmarks, professional guarantee styling
Stats Included:
- 3-4 weeks timeline (addressing “forever” fear)
Slide 11: Next Steps/CTA
StoryBrand Element: Call-To-Action
Copy: Headline: Stop Flying Blind. Get Clarity on Your dbt Infrastructure.
Body: Stop debugging 600-line models. Stop wondering if your data is trustworthy. Get a clear roadmap.
Primary CTA: “Get Your Free dbt Audit Roadmap”
Secondary CTA: “Schedule a 15-minute call to discuss your dbt challenges”
Visual Suggestion:
- CTA Button Mockup: Prominent button design with primary CTA
- Action-Oriented Imagery: Visual showing transformation or clarity
- Placement: CTA button center or prominent, supporting imagery
- Color/style notes: High contrast CTA button, action-oriented design
Stats Included: None
Slide 12: Contact/Thank You
Content: Headline: Thank You
Body: Questions? Let’s talk.
Contact Information:
- Email: [contact email]
- Website: brainforge.ai
- Schedule a call: [booking link]
Visual Suggestion:
- Contact Card: Clean contact information layout
- Team Photo: Optional team photo or Brainforge logo
- Social Links: Optional social media or LinkedIn links
- Placement: Center of slide, clean and simple
- Color/style notes: Professional, clean, brand-consistent
Stats Included: None
Notes for Designer
Overall Design Direction:
- Professional, technical, but approachable tone
- Consistent visual style across all slides
- Strong use of before/after comparisons
- Clear visual hierarchy
Brand Guidelines:
- Follow existing brand guidelines
- Use brand colors and fonts
- Maintain visual consistency with other Brainforge materials
Visual Consistency:
- Consistent icon style throughout
- Consistent chart style (bar charts, gauge charts, line charts)
- Consistent color palette (red/orange for problems, green/blue for solutions)
- Consistent slide layout structure
Key Visual Elements:
- Slide 1: Strong hero visual (before/after split)
- Slide 2: Timeline diagram showing the problem
- Slide 3: Before/after code comparison
- Slide 5: Process flow diagram
- Slide 7: Multiple charts showing metrics
- Slide 8: Transformation table
- Slide 9: Case study layout with logo and metrics
- Slide 10: Guarantee table with checkmarks
Slide Count: 12 slides (appropriate for service deck)
NO Pricing Section: As per requirements, no pricing/investment section included