CHAPTERS
Why this show exists: capturing IIT Madras builders at CFI
Amrit introduces the premise: IIT Madras as the “best place to build,” and the intent to meet builders inside the Sudha & Shankar Innovation Hub/CFI. The episode then sets up a behind-the-scenes look at how the podcast is made and why the team is sharing the process.
- •Show’s core question: what makes IIT Madras the best place to build?
- •Location context: Sudha & Shankar Innovation Hub / CFI as the backdrop
- •Episode intent: a BTS walkthrough of motivations and workflow
- •Hosts introduced: Amrit and Piyush
From campus counseling to “AskIITM”: the origin story and scale
The team traces the podcast/content effort back to “AskIITM,” framed as a digital successor to the counseling that stopped in 2009. They reflect on how the initiative matured over multiple years and hundreds of videos.
- •AskIITM positioned as the digital successor to earlier counseling
- •Timeline reference: the project’s evolution over several years
- •Volume of work: ~350 videos and consistent content output
- •Learning through repetition: consistency generates data and clarity
Content insights: short-form assumptions vs demand for deep dives
They describe an early belief that audiences wouldn’t watch beyond a minute, and how analytics proved otherwise. Over time, they found a segment of viewers that actively wants longer, more detailed conversations—pushing them toward podcast depth.
- •Initial assumption: viewers are impatient and prefer <1-minute content
- •Data changed strategy: an audience exists for long-form depth
- •Some topics can’t be responsibly covered in 1–2 minutes
- •Consistency enables iterative improvement and audience understanding
Breaking outdated perceptions: showcasing real IITM innovation (e.g., Hyperloop)
A moment from a Bangalore demo day illustrates audience skepticism—even when projects are real and demonstrable. This becomes a motivation to bring credible voices onto the show to reduce “cognitive dissonance” about what IITM is building today.
- •Demo day anecdote: a parent doubts IITM’s Hyperloop claims
- •Theme: audiences can be “stuck in the past” about IITM capabilities
- •Solution: bring project founders/leaders (e.g., Suyash, Prof. Satya) to tell it directly
- •Podcast as evidence-building: show, don’t just claim
Tone and art direction: humble conversations over “billionaire podcast” vibes
They discuss deliberately shaping the show’s feel—framing, background, and the emotional posture of guests—so it doesn’t become boastful. Humility is treated as part of the IITM builder culture, rooted in repeated failure and learning.
- •Intentional framing: make viewers feel guests are “leaning in”
- •Avoiding ego/boasting common in some high-production podcasts
- •IITM builder ethos: humility from failing, iterating, and eventually cracking problems
- •Creative reference point: “Breakfast with Champions” vibe
Set dressing and running jokes: what viewers notice (cups, fake plants, IKEA)
The hosts banter about recurring viewer curiosities and the set’s staged elements. The segment humanizes the production and acknowledges the constructed nature of the on-camera environment.
- •Running gag: what’s in the cups (tease for later)
- •Set reality: fake plants and IKEA furniture
- •Light BTS humor to balance the production talk
- •Reinforces the crafted-yet-casual aesthetic
Guest strategy: “problem of plenty” in the IITM ecosystem
They explain that finding guests isn’t hard—there are many builders connected to IITM. The real challenge is prioritizing who comes first and maintaining the thread that guests are part of the IITM ecosystem even after graduating.
- •Guest pool abundance across IITM ecosystem
- •Selection is sequencing: who first, who next
- •Alumni remain connected—“once in the ecosystem, you don’t leave”
- •Show scope includes on-campus builders and graduates
Scheduling realities: early-morning shoots and travel constraints
Operational constraints shape the guest list: shoots happen at 7–9 a.m. to avoid noise and crowding in CFI, and to minimize disruption. Aligning calendars for busy builders—especially those outside Chennai/India—becomes a major bottleneck.
- •CFI is crowded/noisy later—hence 7 a.m. starts
- •Not feasible to occupy the space for hours during peak activity
- •Busy guests + travel makes scheduling difficult (Delhi/Bangalore/US)
- •Fortunate hit rate: many invitees still make time to show up
Research and prep: translating complex work into a good conversation
They describe a structured research pipeline that sometimes requires learning technical domains from scratch and consulting experts. Guests may share publications, and the team works to turn papers into understandable prompts and a comfortable interview flow.
- •Some topics require deep self-education and expert consultation
- •Handling guest publications (conference/journal papers) and extracting meaning
- •Well-structured research notes help hosts stay confident on mic
- •Balancing competence with authenticity—fear of seeming “stupid” is real
Episode architecture: deep tech + personal journey storytelling
The show aims for two parallel tracks: understanding what the guest builds (core tech/product) and why they build it (life journey). They argue personal stories add color, relatability, and inspiration for viewers to start building themselves.
- •Two pillars: technical deep dive and personal journey
- •Work is framed as an outcome of identity and circumstances
- •Story examples: sleep habits, college choice twists, early failures
- •Inspiration goal: viewers relate and feel nudged to build
Release and audience engagement: teasers, platform tailoring, and trust
The team outlines a consistent release cadence: teaser reels first, then full episode release, distributed across Instagram, YouTube, and LinkedIn. They emphasize avoiding clickbait and keeping captions faithful to content to build loyal audience trust.
- •Cadence: teaser on Thursday, episode release on Friday
- •Cross-platform distribution: Instagram, YouTube, LinkedIn
- •Platform-specific captions and packaging based on audience behavior
- •Anti-clickbait principle: match captions to actual episode substance
On-location production at CFI: early call times, cleanup, and why not a studio
The crew details the practical work behind a “simple” frame: arriving at 4–6 a.m., cleaning a messy builder space, and spending about an hour setting up. They choose CFI over a studio because the location itself proves the show’s thesis about IITM as a builder hub.
- •Production day starts ~4–5 a.m.; reach by 5:30–6:00
- •Hidden labor: cleaning, resetting, and assembling the frame
- •Studio would be easier—but CFI signals authenticity and context
- •Guests often nostalgically tour CFI when they return for shoots
Travel cadence and team bonding: road trips, city exploration, shared rhythm
Frequent trips to Chennai (sometimes multiple in a week) become a bonding mechanism for the team, with long drives enabling planning and reflection. Early-morning weekend shoots leave afternoons open to explore the city, deepening team cohesion and local connection.
- •Regular travel schedule to Chennai for shoots (since Oct/Dec references)
- •Preference for driving together—time for conversations and alignment
- •Local immersion: exploring Chennai through someone who lived there
- •Weekend early shoots finish by ~11 a.m., freeing time to decompress/explore
Process maturity: from chaotic launches to a repeatable system
They close by reflecting on the stressful “firefighting” around the first release and how the workflow stabilized by the third or fourth episode. While new issues still pop up, roles are clearer and the production now has a predictable rhythm.
- •Early episodes were stressful and chaotic to ship
- •By episode 3–4, workflow became more streamlined
- •Ongoing iteration: new learnings still emerge episode to episode
- •Team clarity: everyone knows responsibilities; less last-minute panic
