CHAPTERS
- 2:34 – 3:05
Setting the scene: visiting IITM’s Innovation Hub and pitching the builder-focused podcast
Amrit opens by framing IIT Madras as “the best place to build” and sets up the goal: meet builders at the Sudha and Shankar Innovation Hub. The episode is positioned as a behind-the-scenes look at how the podcast is made and why it exists.
- •On-location context at IITM’s innovation spaces
- •Focus on builders and what they’re creating
- •Core question: what makes IITM the best place to build?
- •Episode premise: a behind-the-scenes format
- 3:05 – 3:44
Why the BTS episode exists and how AskIITM led to the podcast
Amrit and Piyush explain the motivation for sharing process details even if nobody explicitly asked. They connect the podcast to AskIITM’s origins as a digital successor to the older counseling system.
- •BTS intent: explain the ‘why’ and ‘how’ of the show
- •AskIITM as a replacement for pre-2009 counseling
- •Timeline context: multi-year run and large video volume
- •Transition from student-focused content toward broader stories
- 3:44 – 4:14
Learning from content data: short-form assumptions vs. audience appetite for depth
They describe early assumptions that audiences wouldn’t watch beyond a minute, then explain how consistent publishing produced data showing demand for longer, deeper content. This becomes a key justification for the podcast format.
- •Initial belief: ‘people are impatient’
- •Consistency yields analytics and clearer audience segmentation
- •Discovery: a real audience wants deep dives
- •Some topics can’t be explored in 1–2 minutes
- 4:14 – 5:15
The ‘Hyperloop is real’ moment: confronting perception gaps about IITM innovation
Amrit recounts a Bangalore demo day where a parent accused them of lying about IITM’s Hyperloop work—highlighting how far behind public perception can be. This story reinforces the need to showcase real builders and projects through long-form conversations.
- •Demo day anecdote reveals audience skepticism
- •Hyperloop at IITM: real team and real track
- •‘Stuck in the past’ perception problem
- •Podcast as a corrective: show, don’t just claim
- 5:15 – 6:06
Defining the show’s tone: framing, art direction, and humility over hype
They discuss figuring out visual framing and the desired conversational vibe—inviting, not boastful. The team intentionally avoids the ego-driven style common in celebrity/billionaire podcasts, aiming instead for builder humility shaped by iteration and failure.
- •Iterating on frame/background/art direction
- •Goal: make guests ‘lean in’—authentic conversation
- •Avoiding boastful, status-driven podcast tropes
- •Builder culture: failing, learning, then cracking problems
- 6:06 – 6:46
Format inspirations and running jokes: props, cups, and the set’s ‘IKEA-ness’
They cite ‘Breakfast with Champions’ as a reference point for the vibe they wanted. The conversation becomes playful as they address audience curiosity (real or not) about the cups and reveal the intentionally simple, mostly IKEA set dressing.
- •Reference: ‘Breakfast with Champions’ as a model
- •Set identity as part of the show’s feel
- •Recurring bits: what’s in the cups; fake plants
- •Lean production aesthetic rather than flashy studio
- 6:46 – 8:00
Guest selection in a ‘problem of plenty’ ecosystem
They explain that the challenge isn’t finding guests—there are many builders connected to IITM—but deciding who to feature first. A key filter is meaningful affiliation with the IITM ecosystem, which they argue people never fully leave.
- •No dearth of builders; abundance creates ordering challenges
- •Guests are current or former ecosystem members
- •‘Once part of IITM, you don’t really leave’
- •Selecting a sequence rather than gatekeeping access
- 8:00 – 9:10
Scheduling constraints: early-morning shoots, noisy spaces, and travel logistics
Practical constraints shape who can come on the show and when—especially since they shoot in Chennai at 7–9 AM to avoid CFI noise and crowding. Aligning calendars and travel for busy builders across cities/countries is a recurring challenge.
- •CFI space gets crowded/noisy; shoots start very early
- •Time blocks can’t disrupt the lab’s daily work
- •Travel to Chennai is a barrier for many potential guests
- •Fortunate turnout: many guests still make it work
- 9:10 – 10:24
Research and briefing: learning complex domains and structuring the interview
They walk through the research pipeline: sometimes the guest’s work is complex enough to require consulting other experts and reading publications. The output is a structured brief that helps the host ask better questions and feel comfortable during recording.
- •Pre-interview education when topics are highly technical
- •Consulting domain experts for clarity
- •Reading papers/publications to extract understandable threads
- •Structured research notes reduce friction during recording
- 10:24 – 12:12
Episode design philosophy: deep tech + personal journeys that inspire builders
They outline two pillars of each conversation: a genuine deep dive into the work, and the guest’s personal story that shaped it. Examples of memorable anecdotes show how human details make episodes relatable and motivating.
- •Pillar 1: go beyond superficial coverage of the tech/product
- •Pillar 2: personal journeys explain what people choose to build
- •Examples: sleep habits, missed ranks, early failures shaping direction
- •Aim: inspiration that nudges viewers to build themselves
- 12:12 – 14:23
Release and distribution system: teasers, platform tailoring, and honest captions
Indu’s release process is described: a Thursday teaser reel to build curiosity, followed by a Friday episode drop across Instagram, YouTube, and LinkedIn. They tailor captions and packaging by platform and avoid clickbait to preserve trust and loyalty.
- •Weekly cadence: Thursday teaser, Friday full release
- •Cross-posting to Instagram/YouTube/LinkedIn
- •Platform-specific captioning and audience expectations
- •Avoiding clickbait to maintain authenticity and retention
- 14:23 – 16:07
Production reality: 4–6 AM call times, cleanup, and why CFI is worth it
The crew explains how early the day starts and how much work goes into making a ‘simple’ setup look clean on camera. They intentionally choose CFI over a studio to visually communicate IITM’s builder culture, and note guests’ emotional nostalgia when returning.
- •Crew starts at 4–5 AM; ~1 hour setup time
- •Significant cleanup because the lab is actively used
- •Studio would be easier, but CFI communicates ‘best place to build’
- •Guests revisit the building and reconnect with memories
- 16:07 – 17:34
Travel cadence and team bonding: road trips, city exploration, and shared rhythm
They describe frequent Chennai trips for shoots (sometimes twice in a week), often driving together. The travel becomes a team-bonding ritual—exploring Chennai after early weekend shoots and gradually building a smoother operating rhythm.
- •Regular travel schedule to Chennai for batch shoots
- •Driving together enables long conversations and bonding
- •Exploring Chennai after finishing shoots by late morning
- •Team cohesion strengthens through repeated trips
- 17:34 – 18:25
Process maturity: early firefighting to a streamlined production workflow
They reflect on the stress and improvisation around the first episode releases, then note how roles and workflows stabilized by the third or fourth episode. While improvements continue, the team now operates with a predictable rhythm and clearer ownership.
- •Early releases were stressful and reactive
- •Workflow became smoother after a few episodes
- •Ongoing iteration still uncovers new tweaks
- •Clear responsibilities reduce last-minute chaos
