{"id":2598,"date":"2026-01-06T09:11:26","date_gmt":"2026-01-06T15:11:26","guid":{"rendered":"https:\/\/izendestudioweb.com\/articles\/?p=2598"},"modified":"2026-01-06T09:11:26","modified_gmt":"2026-01-06T15:11:26","slug":"from-do-the-woo-to-openchannels-fm-how-bob-dunn-is-expanding-the-open-web-podcasting-space","status":"publish","type":"post","link":"https:\/\/mail.izendestudioweb.com\/articles\/2026\/01\/06\/from-do-the-woo-to-openchannels-fm-how-bob-dunn-is-expanding-the-open-web-podcasting-space\/","title":{"rendered":"From \u201cDo the Woo\u201d to OpenChannels.fm: How Bob Dunn Is Expanding the Open Web Podcasting Space"},"content":{"rendered":"

Podcasting around WordPress and WooCommerce has evolved significantly over the past decade. Few people embody that evolution better than Bob Dunn, who transitioned from running a single WooCommerce-focused show, Do the Woo<\/strong>, to building a wider podcast network, OpenChannels.fm<\/strong>. His journey offers valuable lessons for business owners, product teams, and developers who want to create sustainable, community-driven content in the open web ecosystem.<\/p>\n

This article explores why and how Bob rebranded, the operational and technical realities behind running a multi-host network, and what it takes to grow a sponsorship model without losing focus on community and authenticity.<\/p>\n

Key Takeaways<\/h2>\n
    \n
  • Rebranding from a niche show to a broader network<\/strong> can unlock new audiences and topics while still serving an existing community.<\/li>\n
  • Running a multi-channel, multi-host podcast network<\/strong> requires clear structure, flexible processes, and a strong editorial vision.<\/li>\n
  • Technical production choices<\/strong>\u2014hosting, recording, and workflow tools\u2014directly impact scalability and quality.<\/li>\n
  • A sustainable sponsorship model<\/strong> depends on trust, relevance, and long-term relationships rather than quick advertising wins.<\/li>\n<\/ul>\n
    \n

    Why Rebrand \u201cDo the Woo\u201d into a Broader Podcast Network<\/h2>\n

    \u201cDo the Woo\u201d started as a focused podcast around WooCommerce and the businesses built on it. Over time, Bob saw a bigger opportunity: the conversations naturally extended into open source<\/strong>, WordPress<\/strong> at large, and the wider open web ecosystem<\/strong>. Merchants, agencies, and product creators were all wrestling with topics that went beyond just WooCommerce.<\/p>\n

    Rather than bolt everything onto one show, Bob chose to create OpenChannels.fm<\/strong>, a dedicated network for multiple podcasts covering:<\/p>\n

      \n
    • Open source software and communities<\/li>\n
    • Open web technologies and standards<\/li>\n
    • Developer and founder stories<\/li>\n
    • Commerce and business models around open platforms<\/li>\n<\/ul>\n

      From Single Show to Network Strategy<\/h3>\n

      The rebrand was not simply a name change. It was a strategic shift from \u201cone podcast with a clear niche\u201d to \u201ca network of related shows\u201d that could:<\/p>\n

        \n
      • Attract different audience segments (store owners, plugin developers, agency leaders, SaaS founders)<\/li>\n
      • Experiment with show formats without confusing existing listeners<\/li>\n
      • Make room for new hosts and fresh voices<\/strong> who bring their own angles to the open web<\/li>\n<\/ul>\n
        \n

        Rebranding isn\u2019t about abandoning your niche; it\u2019s about creating a structure that lets your content grow without diluting what already works.<\/strong><\/p>\n<\/blockquote>\n

        \n

        Building a Multi-Channel, Multi-Host Podcast Format<\/h2>\n

        Scaling from a single-host podcast to a multi-show network is both an editorial and operational challenge. For OpenChannels.fm, Bob adopted a model where multiple hosts can lead different shows while still aligning with a shared mission: highlighting builders, thinkers, and makers in the open web world<\/strong>.<\/p>\n

        Defining Clear Channels and Themes<\/h3>\n

        Each channel or show on the network is structured around a specific focus area. For example:<\/p>\n

          \n
        • A show centered on WooCommerce and eCommerce<\/strong> use cases<\/li>\n
        • Another dedicated to developer-focused discussions<\/strong> around open source tooling<\/li>\n
        • Shows featuring founder stories<\/strong> and product journeys in the WordPress ecosystem<\/li>\n<\/ul>\n

          This clarity makes it easier for:<\/p>\n

            \n
          • Listeners to subscribe to what\u2019s most relevant to them<\/li>\n
          • Hosts to plan content without overlapping topics excessively<\/li>\n
          • Sponsors to match their message with the right audience segment<\/li>\n<\/ul>\n

            Empowering New Hosts While Maintaining Consistency<\/h3>\n

            Bringing in additional hosts adds diversity of viewpoints but also requires a baseline of consistency. Bob\u2019s approach emphasizes:<\/p>\n

              \n
            • Guidelines, not scripts<\/strong> \u2013 giving hosts flexibility in how they conduct conversations<\/li>\n
            • Shared values<\/strong> \u2013 open source, community focus, and practical value for listeners<\/li>\n
            • Lightweight editorial oversight<\/strong> \u2013 ensuring episodes fit within the broader OpenChannels.fm mission<\/li>\n<\/ul>\n

              For business owners and agencies considering similar networks\u2014whether for internal thought leadership or industry content\u2014this balance between structure and autonomy is crucial for long-term growth.<\/p>\n

              \n

              Operational Challenges of a Growing Podcast Network<\/h2>\n

              Running a single podcast is manageable for one person; running a network is a different story. Scheduling, coordination, and consistency become much more complex once multiple hosts, guests, and formats are involved.<\/p>\n

              Scheduling and Communication<\/h3>\n

              Coordinating multiple time zones, availability windows, and guest preferences means your tools and processes matter. Common elements in a setup like Bob\u2019s include:<\/p>\n

                \n
              • Shared calendars for recording slots<\/li>\n
              • Standardized guest intake forms (bio, headshot, consent, topics)<\/li>\n
              • Automated reminders to reduce no-shows or last-minute confusion<\/li>\n<\/ul>\n

                For agencies and product companies, adopting similar workflows can help scale content without overwhelming the team.<\/p>\n

                Editorial and Production Workflow<\/h3>\n

                To keep episodes flowing, a simple but repeatable pipeline is key. A typical flow looks like:<\/p>\n

                  \n
                1. Topic selection and guest confirmation<\/li>\n
                2. Recording and initial quality review<\/li>\n
                3. Editing and post-production (audio cleanup, intros\/outros, leveling)<\/li>\n
                4. Publishing to the network and syndication platforms<\/li>\n
                5. Promotion across email, social, and partner channels<\/li>\n<\/ol>\n

                  The more shows you have, the more important it becomes to standardize assets such as intro music, branding guidelines, show notes format, and publishing checklists.<\/p>\n

                  \n

                  The Technical Side: Tools, Hosting, and Production Choices<\/h2>\n

                  Behind every polished episode is a technical stack that must be reliable, maintainable, and flexible enough to support new hosts and shows.<\/p>\n

                  Recording and Collaboration Tools<\/h3>\n

                  For remote-first podcasts like OpenChannels.fm, common choices include:<\/p>\n

                    \n
                  • Online recording platforms<\/strong> that capture local audio tracks for higher quality<\/li>\n
                  • Backup recording methods in case of connectivity issues<\/li>\n
                  • Team communications through Slack, email, or project management tools to coordinate episodes and handoffs<\/li>\n<\/ul>\n

                    Business owners and developers planning their own networks should choose tools that are easy for non-technical hosts and guests to use. Complexity kills momentum.<\/p>\n

                    Podcast Hosting and Distribution<\/h3>\n

                    As a WordPress-focused creator, Bob has long been part of the open web ecosystem, which extends naturally to how content is distributed. A typical setup might combine:<\/p>\n

                      \n
                    • A podcast hosting provider<\/strong> for audio files and RSS feeds<\/li>\n
                    • A WordPress site<\/strong> to serve as the content hub, show notes archive, and SEO-friendly front-end<\/li>\n
                    • Distribution to platforms like Apple Podcasts, Spotify, and others through the primary RSS feed<\/li>\n<\/ul>\n

                      This combination allows for strong control over branding and content while still reaching listeners where they already consume podcasts.<\/p>\n

                      \n

                      Evolving the Sponsorship and Revenue Model<\/h2>\n

                      One of the most significant shifts in moving from Do the Woo to OpenChannels.fm is the sponsorship model. With more shows and topic areas, there are more surfaces for partners to engage\u2014but also more responsibility to keep sponsorships relevant and respectful of the audience.<\/p>\n

                      From Single-Show Sponsorships to Network Partnerships<\/h3>\n

                      Under a single-show model, sponsorships are typically attached to every episode in a straightforward way. In a network model, Bob can offer:<\/p>\n

                        \n
                      • Show-specific sponsorships (e.g., eCommerce tools supporting WooCommerce-focused content)<\/li>\n
                      • Network-wide campaigns that appear across multiple aligned shows<\/li>\n
                      • Longer-term partnerships that evolve with the network\u2019s growth<\/li>\n<\/ul>\n

                        This structure gives sponsors more options while ensuring that promotions are relevant to each audience segment. For example, a hosting provider focused on high-traffic WooCommerce stores may prefer episodes that highlight performance, scalability, and security.<\/p>\n

                        Balancing Revenue with Community Trust<\/h3>\n

                        Monetization only works if listeners trust that sponsored content is chosen carefully. Bob\u2019s approach emphasizes:<\/p>\n

                          \n
                        • Working with companies that are active contributors<\/strong> to the open web ecosystem<\/li>\n
                        • Maintaining clear boundaries between editorial decisions and sponsorships<\/li>\n
                        • Prioritizing long-term relationships over one-off ads<\/li>\n<\/ul>\n
                          \n

                          The most successful sponsorships feel like a natural extension of the conversation, not an interruption to it.<\/strong><\/p>\n<\/blockquote>\n

                          \n

                          Staying Involved While Making Space for Others<\/h2>\n

                          One of the most interesting aspects of Bob\u2019s transition is his shift from being \u201cthe voice\u201d of a show to becoming a curator and facilitator<\/strong> for many voices. Rather than stepping away completely, he stays engaged through:<\/p>\n

                            \n
                          • Occasional hosting and guesting on episodes<\/li>\n
                          • Guiding the editorial direction of the network<\/li>\n
                          • Supporting new hosts as they develop their own styles and audiences<\/li>\n<\/ul>\n

                            This hybrid role allows him to remain connected to the community while building a platform that can grow beyond a single personality. For founders and agency owners, this approach mirrors the transition from \u201csolo operator\u201d to \u201cleader of a brand and team.\u201d<\/p>\n

                            \n

                            Conclusion: Lessons for Open Web Creators and Businesses<\/h2>\n

                            Bob Dunn\u2019s journey from Do the Woo to OpenChannels.fm shows what it looks like to thoughtfully expand from a niche podcast to a full-fledged network centered on the open web. The key lessons for business owners, developers, and product teams include:<\/p>\n

                              \n
                            • Start with a focused niche, then expand when your audience and topics naturally outgrow it.<\/li>\n
                            • Use clear channels and themes to manage multiple shows without confusing listeners.<\/li>\n
                            • Invest early in simple, repeatable workflows and tools that support multiple hosts.<\/li>\n
                            • Treat sponsorships as partnerships, aligning with brands that genuinely serve your audience.<\/li>\n<\/ul>\n

                              For anyone building content around WordPress, WooCommerce, or broader open source technologies, this model demonstrates how to scale without losing your community-driven roots.<\/p>\n

                              <\/html><\/p>\n","protected":false},"excerpt":{"rendered":"

                              From \u201cDo the Woo\u201d to OpenChannels.fm: How Bob Dunn Is Expanding the Open Web Podcasting Space<\/p>\n

                              Podcasting around WordPress and WooCommerce has evolved sign<\/p>\n","protected":false},"author":1,"featured_media":2597,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[34,104,109],"class_list":["post-2598","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-development","tag-hosting","tag-wordpress"],"jetpack_featured_media_url":"https:\/\/mail.izendestudioweb.com\/articles\/wp-content\/uploads\/2026\/01\/unnamed-file-5.png","_links":{"self":[{"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/posts\/2598","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/comments?post=2598"}],"version-history":[{"count":1,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/posts\/2598\/revisions"}],"predecessor-version":[{"id":2599,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/posts\/2598\/revisions\/2599"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/media\/2597"}],"wp:attachment":[{"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/media?parent=2598"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/categories?post=2598"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mail.izendestudioweb.com\/articles\/wp-json\/wp\/v2\/tags?post=2598"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}