Podcast & MediaWebsite & information architectureCanada · US · UK · Australia

The owned home for a rented audience

Fifty-five episodes, world-class guests, and every one of them living on somebody else’s platform. Thirty-one pages at launch, built to scale past five hundred.

55+Episodes given an owned homepreviously only on rented platforms
31Pages at launchscaling to 500+ URLs by year three
4English-language marketsCanada, US, UK, Australia
121Pre-launch QA itemschecked before go-live
EngagementStrategy front-loaded, then build
Period2025
ScopeWebsite development · Digital strategy · Information architecture · UI/UX design · CMS templates
The short version

A fifteen-month-old podcast with world-class guests and fifty-five-plus episodes was operating entirely on rented platforms — YouTube, Spotify, Apple, Amazon, Instagram, LinkedIn — with no website, no email capture and no search visibility. The gap was infrastructural, not creative. I built the owned home: thirty-one pages at launch on a content model one founder can operate, architected to scale past five hundred URLs.

The diagnosis01 / 03

The show was not the problem — the absence of infrastructure was

Fifty-five episodes and a guest list most shows would envy, distributed across six platforms, none of them owned. No website, no email capture, no indexable surface, and no single URL that was the canonical answer to the brand’s own name.

A rented audience is a real audience right up until the platform changes its mind. Everything in this build exists to convert that into something the show holds itself.

The strategy02 / 03

Front-loaded before a single layout

Business-goal research and a brand audit came first, then a competitor analysis across six established shows, then ICP and persona development for the two audiences that actually pay — sponsors and guests.

The information architecture was built around a three-layer offering hierarchy: the core podcast, bridge content, and the commercial surface. Eight user flows were mapped before layout, so the structure answered real journeys rather than a navigation convention.

  • Three-layer hierarchyCore podcast, bridge content and commercial surface — so sponsorship and speaking do not have to interrupt the show to be findable.
  • Eight user flows, mapped firstListener, sponsor, guest, event organiser and press each have a path that was designed rather than inherited.
  • A one-founder content modelDynamic CMS templates for episodes, guests and show notes, so publishing does not require a developer.
What went live03 / 03

A canonical home, and the surfaces that make it earn

Thirty-one pages at launch: structured show notes and guest metadata so every episode and guest is indexable, a media kit and press kit for sponsors, a newsletter lead magnet for owned-audience capture, and an enquiry funnel that gives sponsorship somewhere to land.

One hundred and twenty-one items were checked against a pre-launch QA list before it went live.

Email capture went from none to one. That sounds trivial written down, and it is the difference between an audience you reach and an audience you own.
What this engagement proves(03)
  1. 01

    Distribution is not infrastructure

    Six platforms and fifty-five episodes still amounted to no owned surface, no capture and nothing indexable. Reach and ownership are different assets.

  2. 02

    The architecture has to outlive the launch

    Thirty-one pages that scale to five hundred URLs is a content model decision made at the start, not a migration problem inherited at year three.

  3. 03

    Build for the person who has to run it

    Dynamic templates and structured metadata exist so a single founder can publish without a developer. If it can only be maintained by its builder, it was built wrong.

Fifty-five episodes given a canonical home, thirty-one pages built to scale past five hundred, and an owned audience that no longer depends on a platform’s goodwill.

Hari Prasad Yarragolla

Recognise anyof this?

Prefer email? Write to yarragollahari@gmail.com directly.

Let’s talk.

Tell me what you are building — a storefront, a site, an internal tool, or the systems and agents behind them. I will tell you what I would build first.

  • Quick response.You will hear back from me — not an account manager reading a script.
  • A sitemap and a mockup.You see the real structure and design of what you are commissioning, before any money changes hands.
  • Clear next steps.A scope, an order of work, and an honest view of what it is worth — including if the answer is that you do not need a rebuild.
Website developmentCustom Shopify developmentShopify LiquidNext.js buildsE-commerce developmentAPIs & endpointsSystems integrationInternal tools & micro-SaaSAWS infrastructureAI automationAI agentsVoice agents