DnG Demo Prep Call
Date: March 2, 2026 Source: Granola Meeting ID: 671fe356-6411-4b87-b9d9-7a1b48bb02d5 URL: https://notes.granola.ai/t/671fe356-6411-4b87-b9d9-7a1b48bb02d5
Participants:
- Uttam Kumaran (Brainforge)
- Pranav Narahari (Brainforge)
- Luke Scorziell (Brainforge)
Summary
Demo Strategy & Requirements
- Current demo approach needs refinement for Wednesday DnG call
- Built Teams-like interface with dummy data but not client-ready
- Need clearer requirements and scripted demo flow
- Options discussed:
- Polished clickable demo (24hrs insufficient)
- UI mockups in slides
- Simple cursor/ChatGPT demonstration
Technical Demo Scope
- Client unfamiliar with MCP servers and knowledge bases
- Focus on showing Adobe tenant integration pain point
- Demonstrate natural language querying capabilities
- Avoid overwhelming with too many features
- Teams integration preferred for adoption concerns
Demo Development Process
- Luke to create initial slides/mockups using Gemini or Lovable
- Control own destiny approach - don’t rely on engineering for sales demos
- Engineering team (Pranav) can enhance after initial static version
- Buffer time needed for any engineering work (expect 2x longer)
Platform Limitations
- Clarence’s work platform not ready for demo use
- Team not trained on new tools yet
- Stick to proven technologies for client-facing demos
- Don’t bank on unproven solutions for immediate needs
Client Meeting Context
- Wednesday 10 AM call with DnG
- Client concerned about team adoption over technical capabilities
- Previous call showed low technical sophistication
- Branding and familiar interface (Teams) important for buy-in
Alternative Demo Approaches
- Use existing ChatGPT/cursor to show MCP functionality
- Screen recording of Brainforge Slack bot as similar example
- Focus on concept demonstration vs. polished product
- “Slingshot” branding concept (David vs. Goliath theme)
Next Steps
- Luke: Create static demo using slides/Lovable by Tuesday
- Pranav: Stand by to enhance Luke’s initial version if time permits
- Team: Test operating MCP adoption process as secondary priority
- All: Establish clearer demo development workflow for future sales calls