Brainforge Knowledge

2026-02-16_cso_leads_39629ac1

2 min read

CSO Leads

Date: February 16, 2026 Source: Granola Meeting ID: 39629ac1-485c-41c9-a4d9-bd80b46b2176 URL: https://notes.granola.ai/t/39629ac1-485c-41c9-a4d9-bd80b46b2176

Participants:

  • Uttam Kumaran (Brainforge)
  • Clarence Stone (Brainforge)
  • Rico Rejoso (Brainforge)
  • Elizah Pineda (Brainforge)
  • Zoran Selinger (Brainforge)
  • Demilade Agboola (Brainforge)
  • Pranav Narahari (Brainforge)

Summary

DBT Model Development Support

  • Uttam offering to help Pranav ship more DBT models efficiently
    • Will demonstrate AI-assisted development workflow
    • Show how to write PRs and test them properly
    • Available for early morning pairing sessions or async help via Slack
  • Daxer platform access being set up for Pranav
    • Separate GitHub repo for platform code
    • Focus on orchestration and workflows, not setup complexity
    • Cursor integration for streamlined development

Client Infrastructure Issues

  • Ongoing server problems with external vendor causing project delays
    • Issue persists since moving to current infrastructure
    • Client aware of the situation
    • Need to escalate to Robert for resolution
    • External vendor creating hostage situation

Weekly Priority Management Process

  • Client requesting structured weekly reviews and project management
    • Want Monday priority sheet reviews
    • Seeking more guidance on week-to-week basis
  • Recommended approach:
    1. 15-minute standing Monday calls
    2. Maintain priority tracker spreadsheet for client
    3. Mirror priorities in Linear for internal tracking
    4. Add change log sheet for priority shifts
  • Current descriptions too weak - need better scoping
    • Either push client for better descriptions or propose improvements
    • Proper scoping essential for accurate estimates
    • Time spent on definitions is billable and necessary

Resource Allocation and Hour Management

  • Current monthly subscription model creating hour overruns
    • $20k monthly contract should equal ~100-125 hours
    • Currently running ~150 hours per month
    • Need to establish clear hour boundaries with clients
  • Strategy for managing scope:
    1. Communicate hour limitations upfront
    2. When exceeding hours, require deprioritization of other tasks
    3. Push for automation where possible
    4. Limit concurrent project work to maintain efficiency
  • Sam’s time allocation needs clarification
    • Should report to delivery leads, not be billed to individual AI clients
    • Team structure: ABC client gets Casey, Mustafa, and Sam

Efficiency and Client Management

  • Need to slow down delivery pace to hit target margins
    • Current speed creating unsustainable expectations
    • Client interruptions causing 5-10% efficiency loss per switch
    • Document switching costs to justify structured approach
  • ABC client as model relationship
    • “Can do no wrong” type of client
    • Represents ideal client profile for future growth
    • Contrast with current high-maintenance ecommerce clients

Graph View