<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Marissa Cohen on Medium]]></title>
        <description><![CDATA[Stories by Marissa Cohen on Medium]]></description>
        <link>https://medium.com/@marissacohen?source=rss-2164795c8ae7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SwxqmQYUvsl1_siei-5Agw.png</url>
            <title>Stories by Marissa Cohen on Medium</title>
            <link>https://medium.com/@marissacohen?source=rss-2164795c8ae7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:10:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marissacohen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reddit Just Released Its First Report to Grow Your Brand with Insider Insights]]></title>
            <link>https://medium.com/@marissacohen/reddit-just-released-its-first-report-to-grow-your-brand-with-insider-insights-bea45d0c3c2c?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bea45d0c3c2c</guid>
            <category><![CDATA[reddit]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[reddit-marketing]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <category><![CDATA[consumer-behavior]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 18:09:55 GMT</pubDate>
            <atom:updated>2026-08-28T17:25:47.694Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Reddit Just Published Its First Report to Grow Your Brand with Community Insights</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gAgIvmLFMXXLn-zdOjrMqA.png" /></figure><p>In August 2026, Reddit released its first-ever beauty industry report, and the data reveals something fundamental shifting in how people think about beauty: they’re done taking beauty advice from the top down.</p><p>Called The People’s Beauty Index, the report analyzed two years of authentic community conversations across Reddit’s beauty subreddits. The insights aren’t predictions of what will trend next. They’re evidence of what’s already happening in how people actually talk about, think about, and purchase beauty products.</p><p>The headline is stark: Posts mentioning “fix,” “hide,” “cover,” “correct,” and “conceal” decreased 32% year-over-year, while posts mentioning “embrace,” “highlight,” “enhance,” and “emphasize” increased 220% year-over-year.</p><p>Beauty culture is shifting language. And language is how shifts become permanent.</p><p><strong>The Real Signal Hiding in the Data</strong></p><p>The report’s most important finding isn’t about products or trends. It’s about credibility.</p><p>Nearly 7-in-10 beauty shoppers said they feel more confident about their purchase after reading about it on Reddit.</p><p>That’s not engagement. That’s trust. And trust is the currency that actually moves purchases.</p><p>For years, beauty brands built credibility through influencer endorsements and expert claims. Reddit shows that credibility now comes from lived experience. It comes from someone who actually tried the serum, shaved their head, found the SPF that doesn’t pill, and came back with notes.</p><p>This matters because Reddit’s beauty communities don’t work because Reddit is a great platform. They work because they’re built on peer recommendation. When someone asks “how do I do makeup for hooded eyes?”, the people answering aren’t makeup artists or influencers. They’re people with hooded eyes who’ve actually solved this problem.</p><p>That’s a different form of authority. And it’s way more powerful.</p><p><strong>What People Actually Want Now</strong></p><p>The report title says it all: “People are moving from ‘tell me what’s trending’ to ‘show me what actually worked for you.’”</p><p>This shift is visible across every community Reddit analyzed. In r/MakeupAddiction, views to mentions of “eyeshadow palette” grew 56% and views to mentions of “tutorial” grew 38%. People aren’t looking for product recommendations. They’re looking for how-tos from people who’ve figured it out.</p><p>Real people are becoming the new gut check. From sunscreen to botox to short nails to natural hair, people want lived experience before they buy, try, or change. Views to mentions of “facials” increased 19x in r/LAHotGirlies year-over-year. In r/SkinCareAddiction, the most asked question isn’t “what’s the best product?” It’s “where are y’all getting botox?” and “what actually works for my skin type?”</p><p>Communities aren’t being built around products. They’re being built around problems. And the solutions come from people who look like you and have already been through it.</p><p><strong>The Taste Shift</strong></p><p>Here’s what’s radical about Reddit’s report: it shows taste is community-built now.</p><p>The report explicitly states: “Reddit is where people are learning to trust their own taste instead of conforming to one version of beauty.”</p><p>This isn’t abstract. It’s measurable. Views to mentions of “confidence” in r/AskWomenOver40 grew 97% year-over-year. In communities dedicated to celebrating aging, accepting baldness, growing out nails, and embracing natural texture, people aren’t performing beauty for an algorithm. They’re building it together.</p><p>The report frames it beautifully: “Fixing is out. Celebrating is in.” Reddit’s specific and varied beauty communities allow people to move beyond fixing and toward something more self-accepting. That shift — from fixing to celebrating — is the inflection point.</p><p><strong>What This Means for Brands</strong></p><p>For beauty companies, this report is a roadmap with two immediate applications:</p><p><strong>Quick Wins:</strong> What problems can we solve with what we already have? If r/MakeupAddiction users are searching for “eyeshadow palette” 56% more than before, and “tutorial” 38% more, there’s demand for educational content paired with products. If r/LAHotGirlies is asking “where are y’all getting botox?”, there’s opportunity in serving that community’s specific needs.</p><p><strong>Long-Term Insights:</strong> Which communities, creators, or product categories are we currently overlooking? Reddit shows you where people are solving problems that mainstream marketing doesn’t address. That’s where unmet demand lives.</p><p>The bigger insight: on Reddit, beauty is not dictated from the top down. It is tested, debated, and refined by the people living it who are offering confidence through community.</p><p><strong>Why Social Listening Matters Now</strong></p><p>The report’s core finding should reshape how brands think about social listening: communities aren’t just conversations. They’re problem-statement forums.</p><p>You might come to Reddit with one beauty question, but you stay for the honest advice from real people. You arrive looking for how to do makeup for hooded eyes. You discover a whole community of people with hooded eyes who’ve figured out techniques that work. You learn their tricks. You ask your own questions. You become part of the community.</p><p>That’s social listening at its most valuable. It’s understanding demand before you build supply. It’s seeing which product categories matter to specific groups of people. It’s credibility because it’s peer-driven, not algorithm-driven.</p><p><strong>The Bottom Line</strong></p><p>The report frames it this way: “In a filtered internet, people are finding confidence through community.”</p><p>That’s the real story. In an age of Instagram filters, TikTok trends, and algorithm-driven recommendations, people are gravitating toward unfiltered conversations with people who look like them, have solved similar problems, and can offer real solutions.</p><p>Reddit’s beauty report proves this is real. The platform that grew because it let people talk about anything is now showing us what people actually care about: conversations with people who look like them, solutions that work for their specific bodies, and permission to define beauty on their own terms.</p><p>Brands that internalize this will win. Not by predicting the next trend. But by listening to communities. By understanding the specific problems people are solving. By building products and positioning them in ways communities will actually recommend to each other.</p><p>Reddit just gave brands the data to do exactly that. The question is: which brands will actually listen?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bea45d0c3c2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Issa Rae’s Microdrama Hit 75 Million Views in One Week (And Why Studios Are Racing to…]]></title>
            <link>https://medium.com/@marissacohen/how-issa-raes-microdrama-hit-75-million-views-in-one-week-and-why-studios-are-racing-to-8f043a5b8382?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f043a5b8382</guid>
            <category><![CDATA[screentime]]></category>
            <category><![CDATA[ip]]></category>
            <category><![CDATA[tik-tok]]></category>
            <category><![CDATA[short-form]]></category>
            <category><![CDATA[influencer-marketing]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 02:56:50 GMT</pubDate>
            <atom:updated>2026-08-18T02:56:50.304Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How Issa Rae’s Screen Time Hit 75 Million Views in One Week (And Why Studios Are Racing to Replicate It)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4p3n3KnN_GLqO2QTZiMrw.png" /></figure><p>Issa Rae’s production company, Hoorae Media, just did something that most studios have been trying and failing to do for years: launched a serialized microdrama on a social platform and had it break 75 million views in the first week.</p><p>Not a music video. Not a trend-jacking short. A narrative thriller with a beginning, middle, and end. Structured like television. With recognizable actors. Released in one-minute episodes directly on TikTok.</p><p>And people came back for all 27 episodes.</p><p>This isn’t a viral accident. This is a masterclass in how to leverage native platforms for premium storytelling at scale. It reveals something fundamental about how content grows in 2026: the platform isn’t the distribution channel. The platform is the creative medium.</p><p><strong>The Setup That Worked</strong></p><p>Screen Time has a simple premise: a double-date movie night where a mysterious figure hijacks the TV, forcing two couples to confess secrets that threaten to unravel their relationships. It escalates from awkward admissions to relationship-ending revelations. Each episode ends on a cliffhanger. Each cliffhanger makes you want the next episode.</p><p>But the genius isn’t in the concept. The genius is in how Hoorae positioned it.</p><p><strong>1. Platform Partnership, Not Platform Adaptation</strong></p><p>Hoorae didn’t create Screen Time and then “adapt it for TikTok.” They created it <em>with</em> TikTok as the creative medium from day one. The announcement wasn’t made on a studio press release — it was made at an industry event, framed as a partnership between Issa Rae (the creator) and TikTok (the platform). This immediately signaled to the algorithm and to audiences that this was native content, not legacy media trying to go viral.</p><p>The partnership extended to a companion platform: PineDrama, TikTok’s newer vertical-video microdrama hub. By committing to multiple series with both platforms, Hoorae signaled long-term strategy, not one-off experimentation.</p><p>This matters because TikTok’s algorithm favors content made <em>for</em> the platform, not imported to it. A show that “looks good on TikTok” performs differently than a show designed from pixel one to be TikTok-native. Screen Time was the latter.</p><p><strong>2. Zero Friction on Day One</strong></p><p>The series released free, with ad support. Without a paywall or exclusive app to download, viewership was frictionless and primed for growth. Anyone on TikTok could watch episode one immediately.</p><p>This is a simple but critical difference from how studios have historically launched premium content. Netflix requires a subscription. Apple TV+ requires a subscription. Disney+ requires a subscription. Each of these is friction. Each requires a decision before watching.</p><p>Screen Time required one decision: start watching. That’s it. The algorithm could circulate it freely. Friends could share links. The word-of-mouth barrier was removed.</p><p>The result: 22 million views on episode one alone.</p><p><strong>3. Production Quality That Elevates</strong></p><p>Hoorae invested in premium casting and production. The cast includes Brittney Jefferson (Rap Sh!t), Eric C. Lynch (Queen Sugar), and recognizable TV talent. The cinematography is tight. The editing is sharp. It looks like a real drama, not user-generated content trying to be a drama.</p><p>This matters because it signals permission to the audience. When user-generated content looks polished, viewers trust it more. When a major creator like Issa Rae backs something, it carries cultural weight.</p><p>But there’s a subtlety here: the show doesn’t <em>feel</em> like legacy media. It doesn’t have the pacing of network television (which would feel slow on TikTok). It doesn’t have the aesthetics of prestige streaming (which would feel pretentious on TikTok). It’s high-quality production in a native format. That combination is rare and powerful.</p><p><strong>4. Format Optimization for the Platform</strong></p><p>One-minute episodes. That’s the entire secret.</p><p>Not “episodes that fit TikTok’s video limit.” Episodes <em>designed</em> to be exactly one minute. This isn’t a constraint — it’s a creative choice. One minute is long enough for escalation, too short for boredom, perfect for the compulsive watch-next behavior that drives social platform viewing.</p><p>The cliffhangers are brutal. Episode ends. You need to know what happens. Episode two is right there. You watch it. New cliffhanger. You watch episode three. By episode 15, you’re in a viewing session. By episode 27, you’ve invested emotionally in a show you started casually.</p><p>This is the power of native formatting. Traditional episodic drama is built for weekly viewing with plot arcs that span seasons. TikTok viewing is built for binge consumption with escalation happening across minutes, not weeks.</p><p>Hoorae designed for the format. That’s why it works.</p><p><strong>5. Meta-Narrative Positioning</strong></p><p>Here’s the brilliance most people miss: the show is about screen addiction and phone-based manipulation, and it’s released on TikTok, which is literally designed to be addictive and manipulative.</p><p>The platform and the story are running the same psychological game simultaneously. You’re watching a show about people trapped in screens while you’re trapped in a screen. The irony is intentional. It’s commentary wrapped in entertainment.</p><p>This creates conversation beyond the show itself. People don’t just watch it — they talk about what it means that Issa Rae is showing us stories about phone addiction by <em>using our phone addiction against us</em>. That’s meta-narrative leverage that free-standing content doesn’t have.</p><p><strong>6. Retention Over Vanity Metrics</strong></p><p>Episode one raked in 22 million views. That’s the headline. But the real insight is in the retention.</p><p>Episode 27 (the finale of Act 1) still got 2.4 million views. That’s an 89% drop from episode one — which sounds bad until you realize it means 11% of the original audience made it all the way through 26 episodes in the first week. For reference, most serialized TV shows would celebrate 5% retention across a season.</p><p>Hoorae released episode tracking data that showed sustained engagement through the entire arc. This isn’t a one-hit viral moment. This is an audience that committed to the story.</p><p>That retention data becomes the proof point for studios: “We can hold audience on social platforms.” That’s the insight that’s already reshaping how entertainment companies think about TikTok.</p><p><strong>What This Means for Entertainment’s Future</strong></p><p>Screen Time’s success isn’t an outlier. It’s a template.</p><p>Studios now have proof that:</p><ul><li>Premium storytelling can be native to social platforms</li><li>Audiences will commit to serialized content on TikTok</li><li>Platform partnerships create distribution muscle that proprietary apps can’t match</li><li>Format optimization (one-minute episodes) drives engagement more than cinematic production</li><li>Free, ad-supported models can reach scale faster than subscription models</li></ul><p>This is why other studios are racing to replicate it. It’s why TikTok and other platforms are investing in original content. It’s why streaming services are launching ad-supported tiers and thinking about social-native formats.</p><p>The old model was: create premium content, distribute through owned channels (Netflix, Disney+), hope it drives subscriber value.</p><p>The new model is: create premium content <em>native to social platforms</em>, build audience there first, monetize through platform partnerships.</p><p>Screen Time proved the new model works. At scale. With quality content. With major talent.</p><p><strong>The Limiting Factor</strong></p><p>There’s one constraint Hoorae had that most studios don’t: Issa Rae’s credibility.</p><p>She spent years building an audience on YouTube with The Mis-Adventures of Awkward Black Girl before Insecure made her a mainstream success. That gave her permission to take risks on new platforms. Her audience trusted her to deliver quality. TikTok trusted her to bring seriousness to their platform.</p><p>Not every studio has a Issa Rae. Most have legacy franchises, recognizable IP, studio prestige — but they don’t have a creator with that specific blend of platform credibility and mainstream legitimacy.</p><p>That’s the real bottleneck. Studios can invest in production. They can hire talent. They can study format optimization. But they can’t buy audience trust. That has to be earned through years of consistent creative work.</p><p>The studios that will win the short-form content game are the ones that partner with creators who already have that trust, rather than trying to build it from studio credibility alone.</p><p><strong>What Comes Next</strong></p><p>Hoorae announced multiple microseries in development with TikTok. Screen Time Act 2 is coming. The partnership is expanding.</p><p>This signals that what worked once wasn’t a one-off. It’s a repeatable playbook:</p><ol><li>Partner with a major creator (not a studio)</li><li>Design content natively for the platform</li><li>Optimize for format (one-minute episodes, rapid cliffhangers)</li><li>Release free with platform support</li><li>Obsess over retention metrics</li><li>Use success to build long-term platform presence</li></ol><p>That playbook is now the standard other studios are trying to replicate. Netflix is developing short-form content. Disney is expanding creator partnerships. Warner Bros. is thinking about TikTok differently.</p><p>Screen Time didn’t just break viewership records. It rewrote how entertainment companies think about where premium storytelling lives in 2025.</p><p>And the most important insight? It’s not on a streaming service. It’s not behind a paywall. It’s not where studios built their distribution infrastructure over the last decade.</p><p>It’s where audiences already spend their time, in a format designed for how they actually consume content, made by creators they already trust.</p><p>The irony is rich: studios spent billions building proprietary streaming platforms only to discover that the future of premium content distribution isn’t proprietary at all. It’s native to the platforms where culture already lives. Issa Rae didn’t need Netflix to reach 75 million people. She needed TikTok, Hoorae’s production expertise, and a story designed for one-minute episodes.</p><p>That’s the business model every studio is now scrambling to understand. And Screen Time just gave them the proof they needed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f043a5b8382" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disney TikTok Deal Promises to Disrupt the Future of Entertainment]]></title>
            <link>https://medium.com/@marissacohen/disney-tiktok-deal-promises-to-disrupt-the-future-of-entertainment-985dff486a34?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/985dff486a34</guid>
            <category><![CDATA[tik-tok]]></category>
            <category><![CDATA[disney]]></category>
            <category><![CDATA[influencer-marketing]]></category>
            <category><![CDATA[entertainment]]></category>
            <category><![CDATA[ip]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 02:56:38 GMT</pubDate>
            <atom:updated>2026-08-18T08:09:07.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w2j196bBUD__LUFeBMXrIg.png" /></figure><p>In August 2026, The Walt Disney Company and TikTok announced something that should have shocked the industry but instead felt inevitable: creators can now officially access and remix clips and assets from Disney, Pixar, Marvel, Star Wars, and FX directly into their own content. More than simply a licensing footnote, this is a fundamental shift in how the entertainment industry thinks about intellectual property (IP).</p><p>For decades, the model was simple: studios created content, locked it down, and controlled every place it could appear. Unauthorized use meant cease-and-desist letters. Fan content meant copyright strikes. The IP was the studio’s most valuable asset, and protecting it meant keeping it close.</p><p>Disney’s TikTok deal inverts this completely. They’re not just allowing creators to use their IP. They’re building infrastructure to make it frictionless. Creators get official access to asset libraries spanning hundreds of films and series. Their TikTok videos appear not just on TikTok — they appear in a dedicated vertical feed directly inside the Disney+ app. Revenue is tiered. Career pathways are explicit. The studio gets cultural relevance and fresh content. Creators get reach and monetization.</p><p>The entertainment industry has realized something that took a decade to absorb: the IP isn’t valuable because it’s locked down. The IP is valuable because it’s alive in culture. And culture lives with creators.</p><p><strong>The Shift</strong></p><p>For years, studios treated fan content as a threat. Creators making remixes, parodies, and reimaginings were copyright violators. The studios’ legal teams would send takedowns. YouTube would demonetize. TikTok would flag.</p><p>But something changed. Studios realized that the most culturally relevant content about their IP wasn’t being created in studio lots. It was being created by teenagers on TikTok, streamers on Twitch, and creators on YouTube. Their content was driving discourse, building fandom, and creating the context in which official content would be consumed.</p><p>The data proves it. According to internal TikTok data, fans shared an average of 6.5 million Film and TV-related posts on TikTok each day last year, underscoring the depth and daily momentum of entertainment fandom on the platform. More significantly, nearly half of surveyed viewers said they went on to watch a movie or TV show on a streaming service or television after discovering entertainment content on TikTok.</p><p>Protecting the IP meant killing the very thing that made it culturally alive.</p><p>Disney’s move with TikTok says: we’d rather own the relationship with creators than fight them.</p><p><strong>What This Actually Means</strong></p><p>On the surface: TikTok creators can now use official Disney assets in their videos. Participating creators get featured on both TikTok and in a dedicated vertical video feed (called “Verts”) on Disney+ itself. There’s a structured reward system.</p><p>Beneath the surface: Disney is solving a creator-economy problem that every studio will face by 2030.</p><p>Right now, creators who want to build on existing IP have limited options. They can make fair-use parodies and hope they don’t get struck. They can license content at prohibitive cost. Or they can just accept that their content will be removed and demonetized.</p><p>None of these options scale. None of them enable the kind of rapid, creative iteration that defines modern creator culture.</p><p>Disney’s infrastructure solves this. TikTok will offer their creators access to assets related to hundreds of films and series from Disney’s vast library of enduring franchises and beloved IP. Their use is tracked. Permissions are managed. Rights are clear. The studio maintains control over brand usage while actually enabling it at scale.</p><p>But there’s something more sophisticated happening: Disney has created the <strong>Disney Creator Ambassador Program</strong>, a tiered system that gives top creators special rewards, exclusive event access, and explicit career development pathways. This isn’t just about distributing content. It’s about institutionalizing relationships with the next generation of creative talent.</p><p>This is a glimpse of entertainment’s future. It’s not studios releasing finished products and hoping audiences consume them. It’s studios releasing IP infrastructure and letting creators build the culture around it.</p><p><strong>Why This Matters</strong></p><p>The entertainment industry spent the last five years protecting IP from AI. They sued over training data. They fought over generative rights. They tried to control the narrative about how their content could be used.</p><p>But the real disruption wasn’t coming from AI. It was coming from creators. From culture. From the fact that the most valuable expression of a character or story often happens in the hands of someone the studio didn’t hire.</p><p>“The best storytellers are fans first,” said Asad Ayaz, Chief Marketing and Brand Officer, The Walt Disney Company. “That has always been true at Disney, and today, fans are celebrating our stories in entirely new ways. This collaboration creates a new bridge between the stories we tell and the creativity they inspire, giving creators a bigger stage to share what they’ve made, and audiences more to discover on Disney+ every day.”</p><p>Disney’s move signals acceptance of this reality. It says: we can’t control culture, but we can participate in it. We can’t dictate what fans do with our IP, but we can make it easier and build relationships around it.</p><p>This is the direction the entire industry is moving. Warner Bros. will have a similar deal with another platform within 12 months. Universal will follow. Netflix will build creator programs. Every studio will realize that IP locked down is IP dying. IP distributed is IP thriving.</p><p><strong>The Cultural Implication</strong></p><p>Here’s what’s most significant: studios are no longer positioning themselves as content creators competing with other content creators. They’re positioning themselves as infrastructure for culture.</p><p>Disney isn’t saying “watch our content.” They’re saying “build with our IP.”</p><p>This changes the power dynamic. Creators gain agency. They’re not just consuming or remixing — they’re co-producing. Their content shapes how audiences understand and relate to the IP. But it also changes what it means to be a fan. Fandom was always about creative participation. Fan fiction, fan art, fan videos — these were the ways fans kept stories alive. Studios mostly tolerated this. Some studios actively supported it.</p><p>Now studios are institutionalizing it. Through the jointly-run Disney Creator Ambassador Program, Disney and TikTok will enable best-in-class creators to unlock special rewards and provide them with increased visibility, access to exclusive events and career development pathways. They’re saying fan participation isn’t just okay — it’s the primary way the IP evolves.</p><p>That’s not a small shift. That’s a fundamental realignment of who gets to tell stories in the entertainment ecosystem.</p><p><strong>The Next Phase</strong></p><p>The Disney-TikTok deal is phase one: creators can use official clips and assets to build their own content. The pilot launches in the US with intention to expand to other markets.</p><p>But fans will enjoy a shared Disney experience with TikTok videos that will be refreshed regularly to engage subscribers more deeply in timely fan conversations, building stronger communities, and ultimately, helping them engage with more story formats across Disney+. This isn’t just about TikTok anymore. It’s about Disney+ becoming a platform that surfaces creator content alongside official content.</p><p>What comes next is even bigger: creators directly interacting with characters. Influencers having conversations with AI-generated versions of movie characters. Not interviewing actors at a press junket, but having seamless, interactive experiences with the IP itself.</p><p>This is the future of entertainment IP. It’s not about protecting the story. It’s about enabling infinite expressions of the story through different creators and different platforms.</p><p><strong>The Industry Response</strong></p><p>The studios that understand this — that treat IP as infrastructure rather than product — will own culture. The ones that keep trying to control it will watch it drift away to platforms and creators they can’t reach.</p><p>Disney just made a bet that they understand. “Creators are at the heart of everything we do at TikTok. Their creativity extends the life of films and shows into conversations that fans discover and share,” said Dawn Yang, Global Head of Entertainment, TikTok. “Together with Disney, we’re bringing the authentic creator expression of the TikTok community to Disney+, inviting audiences to experience the shared creativity that makes fandom so powerful.”</p><p>The question now isn’t whether other studios will follow. It’s how quickly they’ll move. Because the data is clear: fans don’t just want to consume Disney stories. They want to participate in them. And creators are the infrastructure through which that participation happens.</p><p>Disney just gave them permission. And they gave themselves distribution. That’s the real innovation here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=985dff486a34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Film Studios Promised 2030. Their Data Infrastructure Is Still 1995.]]></title>
            <link>https://medium.com/@marissacohen/film-studios-promised-2030-their-data-infrastructure-is-still-1995-e5c729300bd4?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5c729300bd4</guid>
            <category><![CDATA[film]]></category>
            <category><![CDATA[media-and-entertainment]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[television]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 02:23:45 GMT</pubDate>
            <atom:updated>2026-08-17T02:23:45.299Z</atom:updated>
            <content:encoded><![CDATA[<h3>Five Studios Promised 2030. Their Infrastructure Is Still 1995.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TWAvDDMv_VRNqA3o8lpVTA.avif" /></figure><p>In August 2019, the five major Hollywood studios made a public commitment. Through MovieLabs — a nonprofit joint venture of Paramount, Sony, Universal, Disney, and Warner Bros. — they published “The Evolution of Media Creation,” a white paper that became known as the MovieLabs 2030 Vision. The commitment was explicit: by 2030, the entertainment industry would operate on cloud-native workflows with zero-trust security and software-defined systems.</p><p>The vision is bold. AI-powered tools would generate realistic 3D environments for directors to walk through and edit. Rotoscoping and background removal would be automated. Color grading would be completed on first-pass by AI, with directors choosing from a set of looks. Assets would live in the cloud from creation, eliminating the need to move massive files between systems. Every participant in a production would be identified, verified, and have access permissions efficiently managed.</p><p>It’s a future where technology empowers storytellers to work faster, iterate more, and achieve higher quality than ever before.</p><p>But here’s the problem: the white paper lays out key principles that will form the foundation of this technological future, but it doesn’t address the two structural barriers that will actually prevent studios from reaching 2030 prepared. The technology to execute this vision exists. The commitment exists. What’s missing is the infrastructure foundation to make it real. <a href="https://movielabs.com/the-2030-vision-white-paper-section-4/">MovieLabs</a></p><p><strong>The First Problem: Data That Can’t Be Found</strong></p><p>Legacy entertainment infrastructure is a archaeological layer cake. A studio built its asset library in 1998 using one system. Added VFX infrastructure in 2005 with another. Migrated animation to a third system in 2015. Cloud migration started in 2022 and is still incomplete.</p><p>Now a technical director needs to find every version of a character rig — wet, dry, old, young, clothed, unclothed — across three decades of projects. These assets exist somewhere. But finding them means manually searching across disconnected databases with different schemas, different naming conventions, different access patterns.</p><p>The obvious solution is to dump everything into cloud storage and use search. But this is where the email inbox metaphor breaks down: you search for an asset, get “no results found,” and then discover it existed all along under a slightly different naming convention that the search algorithm didn’t recognize.</p><p>This isn’t a complaint about search technology. This is a structural problem: you can’t efficiently query data when the data lives across systems designed decades apart, never intended to talk to each other.</p><p>By 2030, studios will need to solve this. Not perfectly. But well enough that a human can ask “show me every version of this character” and actually get every version. Not 80% of versions. Not “the recent ones.” All of them.</p><p>The efficiency gain isn’t just convenience. It’s the difference between an AI system that can train on complete asset history and one that trains on whatever happens to be in one system. One produces better results. The other produces hallucinations.</p><p>This directly conflicts with MovieLabs’ 10 principles. Principle 1 states: “All assets are created or ingested straight into the cloud and do not need to be moved.” But studios can’t move assets they can’t find. They can’t ingest data that exists across incompatible systems. The principle assumes a solved problem. It isn’t solved.</p><p><strong>The Second Problem: Collaboration Across Organizational Boundaries</strong></p><p>Inside a studio, even sharing IP is hard. An animation team and a VFX team both need the character rig, but animation needs version 3 (frozen mid-project) while VFX needs version 5 (latest). Animation doesn’t want VFX accidentally overwriting their version. VFX doesn’t want animation’s changes conflicting with their work. IT locks it down with permissions that make collaboration glacially slow.</p><p>Now scale that to cross-enterprise collaboration.</p><p>Netflix greenlit a project with Warner Brothers. Creatively it makes sense. Organizationally it’s a nightmare. How do two massive organizations with different infrastructure, different security requirements, different IP policies actually move assets back and forth?</p><p>The current answer is expensive and manual. Legal reviews the contract. IT sets up VPN access. A new hire from the partner studio goes through background checks and onboarding. Confidentiality agreements. Access permissions. By the time the creative person can actually touch the asset, weeks have passed. The project momentum is gone.</p><p>This works when you’re doing three cross-enterprise collaborations per year. It doesn’t work when the MovieLabs vision materializes — when AI acceleration means you’re running 50 micro-projects with different partners, each needing rapid asset exchange.</p><p>Studios will try cloud solutions. But cloud-as-a-solution creates a different problem: if both studios dump their assets into the cloud, how do they maintain ownership? How does animation know which version of an asset was approved? How does Warner Brothers know Netflix didn’t accidentally (or intentionally) modify something? How do you trace which studio made which change, for legal purposes?</p><p>This directly conflicts with MovieLabs Principle 6: “Every individual on a project is identified and verified, and their access permissions are efficiently and consistently managed.” The principle works inside an organization. It breaks down across organizations. There’s no framework for cross-enterprise identity verification, no protocol for maintaining ownership and change history across organizational boundaries while still enabling fast collaboration.</p><p>The MovieLabs vision assumes the problem is solved. It isn’t.</p><p><strong>Why This Matters for AI Adoption</strong></p><p>Here’s the insight: AI only multiplies existing capacity. If you can’t currently search your asset library efficiently, AI won’t fix that — it will amplify it. If collaboration across enterprises is slow, faster generation speeds just mean you’re waiting longer for approvals.</p><p>The studios that will actually reach the MovieLabs 2030 Vision aren’t the ones with the best AI models. They’re the ones that solved the two problems nobody wants to talk about: finding data that’s scattered across legacy systems, and collaborating across organizational boundaries without sacrificing control or security.</p><p>These aren’t new problems. They’ve existed for a decade. But they’ve been painful enough to live with and expensive enough to ignore.</p><p>The MovieLabs commitment changes the equation. Suddenly, the cost of not solving these problems becomes the cost of not competing.</p><p><strong>What It Takes to Solve</strong></p><p>The first problem requires a new category of infrastructure: intelligent data layers that sit between legacy systems and modern applications. Not storage. A query layer that understands how to talk to old databases, normalize their output, and present complete data to modern tools. This enables the MovieLabs Principle 1 assumption that assets live in cloud — but only if you’ve created a unified view of data scattered across decades of infrastructure.</p><p>The second problem requires something different: an infrastructure layer that makes cross-organizational collaboration transparent and auditable. Not a shared cloud. A pipeline layer that moves assets between organizations while maintaining immutable records of ownership, access, and modification. This enables the MovieLabs Principle 6 assumption that permissions can be managed across participants — but only if you’ve built a system that maintains identity and ownership across organizational boundaries.</p><p>Both are unglamorous. Neither involves AI. Both are blocking issues that will define which studios actually deliver on the MovieLabs 2030 Vision.</p><p><strong>The Real Timeline</strong></p><p>Studios committed to the MovieLabs 2030 Vision in 2019. They’re now six years into a ten-year timeline. The studios that acknowledge these infrastructure problems early — in 2026–2027 — will have competitive advantage that no model, no matter how good, can match.</p><p>The technology to solve both exists. The blocker is organizational: nobody wants to admit they still have a data problem, and everybody assumes cloud will fix collaboration. But AI doesn’t care about assumptions. It just exposes existing inefficiencies at scale.</p><p>The studios that acknowledge these problems and build the infrastructure will reach the MovieLabs 2030 Vision. The ones that don’t will still be wrestling with the same data silos and collaboration bottlenecks they have today, except now with expectations that AI should have fixed it.</p><p>The vision is clear. The infrastructure to reach it is not. That gap is where the work actually happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5c729300bd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Built to Grow: How Virtual Communities Like Discord Become Irreplaceable]]></title>
            <link>https://medium.com/@marissacohen/built-to-grow-how-virtual-communities-like-discord-become-irreplaceable-1799e568a225?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1799e568a225</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[marketing-strategy-tips]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 02:23:38 GMT</pubDate>
            <atom:updated>2026-08-17T02:23:38.820Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Built to Grow: How Virtual Communities Become Irreplaceable</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lV4is4KctqVsMX42hEzyLA.jpeg" /></figure><p>Most product growth theory assumes that users choose products because they’re better. They compare options, find the one with the best features or easiest onboarding, and adopt it. Growth happens because word-of-mouth spreads about a superior solution.</p><p>This assumption breaks down completely for community platforms.</p><p>Discord didn’t grow because it was better than Skype or TeamSpeak. Slack didn’t dominate enterprise communication because email doesn’t work. Twitch isn’t the largest streaming platform because it has the best video codec. These platforms won and continue to dominate because they became structurally necessary for participation in communities people cared about. Once your friends are on Discord, you join Discord. Once your team uses Slack, you use Slack. Once the streamers you follow broadcast on Twitch, you go to Twitch.</p><p>This is structural lock-in, and it’s fundamentally different from the product-led growth everyone talks about.</p><p><strong>The Difference Between PLG and Network Lock-In</strong></p><p>Product-led growth (PLG) has become the default strategy in tech. Fifty-eight percent of companies now use a PLG model. The playbook is well-established: remove friction from onboarding, let users experience core value quickly, make the product so good that word-of-mouth spreads naturally. This works brilliantly for tools — Figma, GitHub, Stripe, Notion. Users sign up, experience value immediately, and decide to keep using it because it makes their work better.</p><p>But community platforms operate under completely different mechanics. A community platform’s value isn’t derived from any individual user’s experience with the product. It’s derived entirely from who else is there.</p><p>One person using Discord is nearly worthless. Discord alone doesn’t do anything for you. Discord with your gaming community in it is essential — you can’t participate without it. One person using Slack at a company where no one else is online is a waste of time. Slack at a company where 200 people are actively communicating becomes the nervous system of the organization. You can’t do your job without it.</p><p>This distinction matters because it changes everything about how these platforms grow. Traditional PLG assumes that each user adopts independently based on the product’s value. Network lock-in assumes that users adopt because not adopting means exclusion from a community they care about.</p><p>The implications are profound. When you understand structural lock-in, you stop measuring growth the way traditional SaaS companies do. You stop optimizing for DAU or conversion rates. You start optimizing for network density — how many communities exist, how engaged are they, how structurally necessary has your platform become for participation.</p><p><strong>How Discord Built Irreplaceability</strong></p><p>Discord launched in 2015 targeting gamers. The founding story matters less than what happened next: they watched where the growth actually came from.</p><p>Initially, Discord grew through word-of-mouth because it solved a real pain point. Gamers were hacking together screen sharing through Skype or Twitch — opening Twitch, muting it, talking on Discord instead. This was absurd. Discord’s founders noticed this behavior, built “Go Live” — a low-latency integrated screen share — and turned a janky multi-app workflow into one simple feature. They didn’t follow a growth playbook. They watched users, saw what they needed, and built it.</p><p>But something else was happening simultaneously that most growth analyses miss entirely: Discord made it trivially easy to create a community. Spinning up a server took seconds. Custom roles, permissions, bots — all available to anyone. This mattered more than the product being good.</p><p>Here’s why: as more communities launched on Discord, Discord stopped being “a voice app for gamers” and started being “where gaming communities live.” A new gaming community couldn’t choose between Discord and Slack or Telegram because their potential members were already in Discord communities. Those communities weren’t competing with each other — they were reinforcing each other. Each new server made Discord more valuable, not less.</p><p>This is network effects taken to their logical conclusion. In traditional software, network effects mean that more users make the product more useful for all users. In community platforms, network effects are compounded by the fact that each new community creates a new reason for new users to join.</p><p>By 2023, Discord had over 150 million monthly active users. But here’s the remarkable metric: Discord tracks concurrent active users as a key measure because their core interaction is groups chatting simultaneously. Discord’s record was 10.6 million concurrent active users. For comparison, Twitch — a platform built for broadcasting to massive audiences — averages 1.4 million concurrent viewers. Discord’s number is so high because it’s not built for broadcasting. It’s built for dozens of small, overlapping communities all talking at the same time. The concurrency is the point. It creates the feeling that Discord is alive, that something is always happening, that not being there means missing out.</p><p><strong>The Four Mechanisms of the Flywheel</strong></p><p>Discord’s growth wasn’t one thing. It was four interlocking mechanisms that fed each other.</p><p>First was ease of entry. Community creation was frictionless. This wasn’t just a product feature — it was the entire strategy. If creating a community required approval or took hours to set up, Discord would have remained a niche tool. Instead, the barrier was nonexistent. Any casual gaming group of five friends could start a server in seconds. This meant the number of communities on Discord exploded. And the more communities that existed, the stronger the second mechanism kicked in.</p><p>Second was exponential network growth. More communities meant more reasons for more people to join Discord. A person interested in League of Legends joined the League community. A person interested in anime joined the anime community. A person interested in book clubs joined the book club community. Each community was separate, but they all lived on Discord. The value of Discord wasn’t additive — it was exponential. Discord went from “a voice app” to “the place where your hobbies and friend groups congregate.” Each new community made Discord more essential, not just for its existing users, but for the next wave of new users.</p><p>Third was organic spreading. Discord prioritized features that facilitated word-of-mouth. But it wasn’t the features themselves that mattered. It was that being in a community on Discord created a genuine reason to invite others. A friend would say “I found this cool anime Discord server,” not because they were promoting Discord but because they wanted their friend in that community. Invitations were frictionless. Joining was frictionless. Discord just stayed out of the way and let communities spread through natural social behavior.</p><p>Fourth was structural necessity. And this is where the lock-in became irreversible. Once your friend group lived in a Discord server, you didn’t have a choice about using Discord. It wasn’t “I prefer Discord” — it was “my community is on Discord.” The platform became infrastructure, not a tool you evaluated against competitors.</p><p>Games amplified this dramatically. When Fortnite, Minecraft, and Apex Legends officially verified themselves on Discord and suggested users join Discord communities to find teammates and coordinate, Discord stopped being optional for serious players. It became required. You wanted to play competitively? Discord was where teams formed.</p><p><strong>How This Differs From Traditional Growth</strong></p><p>To understand why structural lock-in is so different, consider Figma. Figma has extraordinary network effects. More designers on Figma means more collaboration, more design systems, more reason for others to join. But here’s the crucial difference: one designer using Figma alone gets value. That designer can create, iterate, and ship designs in Figma without anyone else being on the platform.</p><p>Discord offers zero value to a solitary user. Discord is useful only insofar as other people are there. This completely changes the growth dynamic. Figma grows by each user independently recognizing value. Discord grows by communities recognizing that everyone else is already there, so joining becomes automatic.</p><p>This also explains why switching costs become infinite for community platforms in a way they don’t for tools. You can switch from Figma to another design tool by exporting files and rebuilding your design system. Switching from Discord means your entire community network disappears. It’s not that the data is hard to migrate — it’s that the community can’t be migrated. Communities exist on Discord because everyone is there. Move everyone to a competitor and the community ceases to exist. The lock-in isn’t technological; it’s social.</p><p><strong>The Slack Pattern: Lock-In Through Organizational Structure</strong></p><p>Discord pioneered this with gaming communities, but the same lock-in mechanism emerged in enterprise with Slack. Slack didn’t invent workplace chat — it just made it better. But “better” is the wrong frame for understanding Slack’s dominance.</p><p>Slack became essential to work because organizations adopted it. A software company might adopt Slack for a team. That team’s work history moves to Slack. Their processes, inside jokes, knowledge — everything gets embedded in Slack. Onboard a new person? They need to use Slack to get up to speed. Leave the company? Slack is the institutional memory.</p><p>What’s fascinating is that Slack charges premium pricing — thousands of dollars per year for large organizations — and companies rarely leave. Not because they love Slack, but because leaving means losing access to organizational knowledge and disrupting daily workflows. The lock-in is so strong that it survives ordinary complaints about the product.</p><p>This is structural lock-in at scale.</p><p><strong>The Twitch-Discord Symbiosis</strong></p><p>The real sophistication in modern platform strategy is understanding that different platforms can work together within this framework. Twitch and Discord don’t compete — they complement each other in a way that strengthens both.</p><p>Twitch solves discovery. A streamer broadcasts live, random viewers stumble in, some stick around. Twitch is the acquisition channel. But Twitch is bad at keeping communities engaged during offline hours. A streamer’s channel is dead when they’re not streaming.</p><p>Discord solves retention. A streamer invites followers to a Discord server. That server becomes the center of community. Memes, inside jokes, regular movie nights, game sessions — the actual relationship building happens in Discord. When the streamer goes live, Discord members get notified and immediately join. The Discord keeps them engaged in between streams.</p><p>The data bears this out: streamers who actively maintain Discord communities achieve 40–60% higher subscriber retention rates compared to those relying solely on Twitch. It’s not because Discord is better at streaming — it’s not. It’s because Discord solves the offline retention problem that Twitch can’t.</p><p>This is the future of platform strategy. Single platforms trying to do everything (be the discovery engine, the engagement tool, and the community hub) compete against platforms that specialize in one part of the flywheel and integrate with others that specialize in the rest.</p><p><strong>Why This Matters for Builders</strong></p><p>If you’re building a platform with community potential, structural lock-in should be your north star. Not user acquisition. Not DAU growth. Not even engagement metrics. Those are all trailing indicators.</p><p>What you should measure is network density and structural adhesion. How many communities are thriving on your platform? How hard would it be for a user to leave? Is your platform required for participation in communities people care about, or is it optional? Does each new user or community make the platform more valuable for everyone else exponentially, or does value plateau?</p><p>The platforms that will dominate the next decade won’t win because they have the best features or the fastest onboarding. They’ll win because they became the infrastructure that communities depend on for existence. Once you’re the platform where a community lives, the community can’t leave without ceasing to exist. That’s not abusive — it’s alignment. You’ve solved the problem so completely that the solution becomes indispensable.</p><p>Discord understood this early. Slack figured it out. Twitch benefited from it when gaming streamers made it essential. The pattern is consistent: enable easy community creation, facilitate network growth, make spreading organic, and let structural necessity do the lock-in work.</p><p>The irony is that this doesn’t require lock-in tactics. It requires the opposite: radical ease. Make community creation frictionless. Make joining effortless. Make leaving optional. And watch what happens when communities discover that everyone else is already there.</p><p>That’s structural lock-in, and it’s the most powerful growth engine in technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1799e568a225" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Happens When Developers Stop Coding and Start Directing?]]></title>
            <link>https://medium.com/@marissacohen/the-agency-gap-what-happens-when-developers-stop-coding-and-start-directing-928e86c01956?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/928e86c01956</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[developer-community]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[lovable]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Sat, 15 Aug 2026 23:04:52 GMT</pubDate>
            <atom:updated>2026-08-15T23:48:56.889Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fqyynnKm_RdY9He_93dJBA.avif" /></figure><p>Five years ago, there was a clear hierarchy in software development. Junior developers used low-code tools and templates. Senior developers wrote real code. The expectation was that as you leveled up, you’d move away from abstraction layers and into the actual craft of software engineering.</p><p>That hierarchy is evolving in ways we should celebrate.</p><p>Today, your most experienced engineers are opening Lovable. Not for prototypes. Not for side projects. For production systems. For payment processing. For critical paths. For work that used to consume the best developers on your team.</p><p>This isn’t because they’ve given up on engineering. It’s because AI coding agents got good enough that the smartest people in the room realized the constraint wasn’t writing code anymore — it was thinking through problems clearly enough to articulate them.</p><p>This shift represents an opportunity that software development has never had before: the chance to redirect human expertise toward the work that actually matters.</p><p><strong>The Inversion Unlocks New Possibilities</strong></p><p>When I started writing code, the progression was clear: you proved yourself by writing good code. You moved up by writing better code. You became senior by understanding systems deeply enough to architect them.</p><p>There was a cost to this. Fifty percent of your time went to boilerplate. Twenty percent went to debugging patterns you’d solved a hundred times before. Ten percent went to optimizations that made the code run faster but didn’t change what it did.</p><p>The stuff that made you feel like a real engineer — the craft, the elegant solutions, the deep system knowledge — was fragmented across all the other work.</p><p>Now that’s changing. And it’s changing in a way that liberates what engineering actually is.</p><p>Your senior engineer opens Lovable and asks the AI agent to build a payment processing system. Three minutes later, the agent returns with a working implementation. Your engineer reads the code, nods, and ships it.</p><p>This moment represents something profound: the engineer’s job has shifted from implementing solutions to architecting them. From writing code to specifying intent. From managing details to managing direction.</p><p>This isn’t a loss. This is what experienced engineers wanted all along.</p><p>For decades, software development was constrained by the fact that your best thinking had to be encoded into implementation details. You couldn’t separate the architectural insight from the code that expressed it.</p><p>Now you can. The architect speaks. The agent implements. The human reviews. This is how the work was always supposed to be divided.</p><p><strong>The Skills That Emerge</strong></p><p>When I look at how the best teams are using Lovable, I notice something exciting: they’re not replacing senior developers. They’re unleashing them.</p><p>The developers thriving in agent-based workflows are the ones who learned to:</p><p>Translate business intent into clear specifications that agents can execute. Read and validate agent-generated code quickly, understanding not just what it does but whether it solves the problem. Think architecturally about how pieces fit together without getting bogged down in implementation. Mentor teams on how to work with agents as collaborators, not tools. Focus their expertise on the decisions that actually matter: tradeoffs, patterns, consistency, design.</p><p>These are the skills that were always valuable but got buried under implementation work. Now they’re front and center.</p><p>And here’s what’s remarkable: these skills are learnable. They’re not exclusive to people who spent a decade writing code by hand. They’re teachable to anyone who understands systems thinking.</p><p>This means more people can contribute to building software. Not fewer.</p><p><strong>The Reorganization of Expertise</strong></p><p>Before AI coding agents, there was a clear skill pyramid. Junior developers wrote simple features. Mid-level developers built systems. Senior developers made architectural decisions. CTOs thought about the entire stack.</p><p>AI coding agents didn’t break this pyramid. They inverted it in a way that makes room for something better.</p><p>Now a junior developer working with a senior architect can direct an agent to build what used to require a mid-level developer alone. The senior architect provides the vision. The junior developer learns how to specify and validate. The agent does the implementation.</p><p>This creates something that’s been missing from software development: genuine mentorship at scale.</p><p>A senior developer can now mentor five juniors instead of one, because the constraint isn’t code review anymore — it’s architectural thinking. And architectural thinking scales.</p><p>The teams winning with AI coding aren’t smaller teams. They’re more effective teams. The same number of people shipping more, understanding systems better, and learning faster.</p><p><strong>What Gets More Valuable</strong></p><p>There’s a skill that’s always been important but often gets overshadowed: the ability to understand a system holistically.</p><p>When you hand-wrote code, this deep familiarity was expensive to build. You had to spend months in a codebase. You had to debug at 2 AM. You had to refactor and optimize and learn through pain.</p><p>Now the agent handles the implementation details. What remains is the opportunity to focus entirely on understanding how systems work together.</p><p>And that’s where the real value is. A person who deeply understands how payment processing connects to user workflows, how data flows through the system, how changes ripple across services — that person is invaluable. They’re not working on CRUD endpoints. They’re architecting the future.</p><p>AI coding agents are very good at writing isolated features. They’re perfect for implementation. But they’re completely dependent on humans who understand what needs to be implemented and why.</p><p>This isn’t a loss. This is what experienced engineers actually want: the freedom to focus on the thinking.</p><p><strong>The Organizational Opportunity</strong></p><p>Here’s what progressive CTOs are realizing: if agents can write most of the code, what do I need developers for? And the answer is beautiful.</p><p>You need people who can specify systems clearly and completely. You need people who can review code and catch logical errors before they reach users. You need people who understand the broader architecture and can ensure nothing is creating unnecessary technical debt. You need people who can mentor teams on how to work with agents effectively.</p><p>Some teams are responding by building flatter organizations: fewer developers, but each one more senior and more focused on high-impact work. Other teams are bringing product managers deeper into the engineering process, because they’re often the best people to specify what users need. Some teams are creating new roles — prompt engineers who specialize in translating business requirements into agent specifications, quality assurance specialists who understand how to validate agent-generated code, architects who focus entirely on system design.</p><p>These aren’t replacements for developers. They’re evolution of what development means.</p><p>And here’s the exciting part: these roles are often more fulfilling. They’re focused on judgment, creativity, and strategic thinking instead of implementation grind.</p><p><strong>The Craft Transforms</strong></p><p>Developers got into development because they loved solving problems. They loved the feeling of building something elegant that worked. They loved the aha moment when a complex system suddenly made sense.</p><p>That hasn’t changed. It’s just shifting focus.</p><p>Building a new feature used to mean wrestling with syntax and debugging and optimization. It meant managing cognitive load across implementation details. It meant the creative part was fractured across the mechanical part.</p><p>Now you describe what you want, and the agent builds it. If it works, great. If there’s a subtle issue, you direct the agent to fix it. You’re managing the architectural decisions, not managing the implementation details.</p><p>For many developers, this is liberation. This is what they wanted all along: the freedom to think about architecture without being constrained by implementation.</p><p>Yes, some people loved the craft of writing code by hand. But most people loved the craft of solving problems. And they still get to do that. They just get to do it at a higher level.</p><p><strong>The Teams That Are Winning</strong></p><p>The organizations getting the most value out of AI coding are the ones that leaned into this shift thoughtfully.</p><p>They invested in making specifications a first-class product. They recognized that clear requirements are the leverage point. They created processes where the best thinkers on the team focus on “what should we build?” instead of “how do we build it?”</p><p>They reorganized so that senior engineers spend more time mentoring and architecting and less time implementing. They created space for juniors to learn through working with agents and reviewing agent code, not by writing features from scratch.</p><p>They built internal processes around agent-generated code that make it easier to validate and maintain. They recognized that this code is different in important ways and designed review processes accordingly.</p><p>They committed to maintaining clear architecture as more code is generated. They understood that consistency and coherence become even more important when you’re not writing the code yourself.</p><p>These teams are shipping faster. More importantly, they’re shipping smarter. Their engineers are happier because they’re doing more interesting work. Their mentorship is better because experts have more bandwidth. Their code is better because it gets reviewed by people who understand the full context.</p><p><strong>The Future Is Collaborative</strong></p><p>We’re at the beginning of a professional evolution that will reshape software development in positive ways.</p><p>Developers are getting to do work that’s more meaningful. Implementation work that used to take weeks can now happen in hours, freeing up energy for the thinking that matters.</p><p>Teams are becoming more collaborative. Architects work more closely with implementers (agents and humans). Senior engineers mentor more effectively. Juniors learn faster because they’re exposed to high-quality code and clear architectural thinking.</p><p>Organizations are becoming more adaptive. When you can go from idea to implementation in days instead of months, you can respond to the market faster. You can experiment more. You can fail faster and learn more.</p><p>And maybe most importantly: the barrier to building software is lowering. More people can participate. More ideas can become real. More problems can get solved.</p><p>The code might be written by an agent, but the thinking behind it — the architectural vision, the specification, the validation, the judgment about what matters — that’s all human. That’s all irreplaceable.</p><p>The technology is enabling us to separate those things. And in that separation, we finally get to focus on what we should have been focusing on all along: the thinking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=928e86c01956" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Accountability Problem: Why Enterprises Are Winning by Solving for Auditability]]></title>
            <link>https://medium.com/@marissacohen/the-accountability-answer-why-enterprises-are-winning-by-solving-for-auditability-7a52ed5272f5?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a52ed5272f5</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[lovable]]></category>
            <category><![CDATA[vibe-coding-tools]]></category>
            <category><![CDATA[b2b-marketing]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Sat, 15 Aug 2026 23:04:42 GMT</pubDate>
            <atom:updated>2026-08-15T23:47:42.860Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDrBo4v4SsQ-l8ev9e5kBA.avif" /></figure><p>Lovable just raised $400 million at $13.3 billion valuation. Cursor is in every startup. GitHub Copilot is built into VS Code. AI coding adoption is accelerating everywhere.</p><p>But something interesting is happening in enterprise companies: the ones moving fastest aren’t the ones ignoring accountability. They’re the ones building it in from day one.</p><p>While startups race to velocity, enterprises are discovering an unexpected competitive advantage: they’re solving the auditability problem that everyone else is ignoring.</p><p>Your CTO approves Lovable for the engineering team. Three months later, you’ve shipped 40 features faster than ever. Code is solid. Users are happy. And when the CFO asks “If an AI wrote this code, who’s responsible if it breaks?” you have a clear, defensible answer.</p><p>This gap — between what the technology can do and what organizations need to do it responsibly — isn’t a barrier. It’s an opportunity. And the companies that solve it will own the enterprise market.</p><p><strong>The Accountability Question Is Your Competitive Advantage</strong></p><p>When you use an AI agent to write code, you’re forced to think about something most software organizations never properly address: how do we know this code is safe?</p><p>With human-written code, we pretend we know because the same person who wrote it reviewed it or we have a code review process. But we rarely ask the hard questions: Can we trace why each decision was made? Can we defend it to a regulator? Can we explain it to a customer?</p><p>AI-generated code forces this clarity. And that’s good.</p><p>An engineer can explain why they made a specific architectural choice. They can walk through their reasoning. They can defend the approach in an audit. But when you’re working with an AI agent, you can’t rely on that. You have to build systems where the intent is explicit, the decision process is documented, and the outcome is verifiable.</p><p>This sounds like overhead. It’s actually discipline.</p><p>The enterprises that embrace this are discovering something: clear specs, documented decisions, and verifiable outcomes make everything better. Not just for compliance. For everything.</p><p><strong>Building Trust Through Transparency</strong></p><p>The best enterprises aren’t hiding that they use AI for code. They’re making it a selling point.</p><p>They maintain detailed specs. They document why each requirement was specified that way. They create review checklists specific to agent-generated code. They maintain audit trails of every version, every change, every decision.</p><p>And here’s what happens: customers trust them more. Regulators trust them more. Their own teams trust the code more.</p><p>Why? Because they’ve solved something that most software organizations never do: they’ve made their decision-making transparent.</p><p>It’s easy to say “we have code reviews” and leave it vague. It’s harder to say “here’s exactly how this payment system was specified, here’s who reviewed it, here are the tests, here’s the audit trail.”</p><p>But when you can say that, you’ve moved from “we hope our code is good” to “we know our code is good because we can show you why.”</p><p>This isn’t bureaucracy. This is quality.</p><p><strong>The Spec Problem Becomes Your Strength</strong></p><p>Here’s where enterprises are winning: they’re realizing that AI-generated code is only as good as the spec that created it.</p><p>If you spec incompletely, the agent makes assumptions. If you spec unclearly, the agent fills gaps with defaults that might not match your requirements. If you spec poorly, you get working code that doesn’t do what you need.</p><p>Most organizations avoid this by having humans implement. Humans can ask questions. Humans can make judgment calls about ambiguity.</p><p>But when the agent is doing the implementation, you can’t rely on human judgment. You have to be precise.</p><p>And precision is a gift. When you’re forced to write complete, clear specifications, you discover that most software fails because requirements were never clear to begin with. Enforcing clarity upstream prevents bugs downstream.</p><p>The enterprises solving this are creating a new discipline: specification engineering. People whose job is writing complete, unambiguous requirements. Not vague product requirements. Detailed technical specifications that an agent can execute precisely.</p><p>And here’s the bonus: when you have precise specifications, you can trace any bug back to either a specification error or an agent error. This gives you the accountability that actually matters.</p><p><strong>The Auditability Becomes Your Moat</strong></p><p>The real competitive advantage isn’t velocity. It’s defensibility.</p><p>Enterprises need to explain their systems to regulators, auditors, customers, and lawyers. Most companies do this poorly. Most code is justified retrospectively: “this is how we built it” rather than “here’s why we built it this way.”</p><p>AI coding forces you to build this in from the start. You have to document your intent before the code exists. You have to specify your requirements before the agent implements them.</p><p>This creates a natural audit trail. Not because you’re trying to create one. Because you have to, to work with an agent.</p><p>The companies that lean into this are discovering they can answer regulatory questions faster. They can defend their code to customers with evidence, not just assertions. They can change code with confidence because they understand what it was supposed to do.</p><p>This is what enterprises actually want from their software development processes. They want clarity. They want defensibility. They want to be able to explain decisions.</p><p>AI coding is forcing this. And the organizations that embrace it will have competitive advantage for years.</p><p><strong>Why This Matters</strong></p><p>The companies that solve for auditability will own enterprise adoption. Not the ones with the fastest models or the best code quality, but the ones that make it easy to build responsibly.</p><p>This isn’t a burden. It’s a feature. It’s what enterprises are actually looking for.</p><p>Right now, most AI coding tools are playing to the startup market. They talk about building apps in 48 hours and shipping faster. These are real advantages for startups.</p><p>But enterprises want something different. They want to move faster without sacrificing the ability to manage risk. They want to use AI to amplify their teams without losing visibility or control.</p><p>The tools that win enterprise will be the ones that say: “We help you build faster AND give you complete visibility into what you’re building and why.”</p><p><strong>The Organizational Transformation</strong></p><p>The exciting part is what happens when enterprises solve this problem: their entire software development process improves.</p><p>When you’re forced to write clear specs, your requirements process gets better. When you maintain audit trails, your version control discipline improves. When you document decision-making, your architectural thinking becomes clearer. When you build processes to validate agent-generated code, your overall code quality goes up.</p><p>This isn’t overhead that slows you down. This is discipline that makes you faster and more confident.</p><p>The enterprises that embrace this are finding they can ship more frequently because they trust their code more. They can onboard new engineers faster because everything is documented. They can respond to regulatory changes faster because they understand their own systems.</p><p><strong>The Next Frontier</strong></p><p>The companies that crack enterprise adoption of AI coding won’t be the ones with the best models. They’ll be the ones that solve the accountability question beautifully.</p><p>This might mean building governance tools that make audit trails automatic. It might mean creating frameworks that make spec-to-code traceability effortless. It might mean building compliance scanners that understand your specific regulatory requirements.</p><p>But more importantly, it might mean changing how enterprises think about software development entirely. Moving from “we hope our code is good” to “we know our code is safe because we built it systematically.”</p><p>The technology is ready for enterprises. The organizations that build accountability into their process from day one will be the ones that win.</p><p>And they won’t win by being compliant. They’ll win by being faster, more confident, and more defensible.</p><p>The gap isn’t a problem to solve. It’s an opportunity to lead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a52ed5272f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Untapped Potential: How LGBTQ+ Dating Apps Are Redefining What Platform Success Means]]></title>
            <link>https://medium.com/@marissacohen/untapped-potential-how-lgbtq-dating-apps-are-redefining-what-platform-success-means-eb62959c748a?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb62959c748a</guid>
            <category><![CDATA[gay-dating-apps]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[gay-pride]]></category>
            <category><![CDATA[lgbtq]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 21:44:15 GMT</pubDate>
            <atom:updated>2026-08-14T21:44:15.628Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*YmriGqY8VuZoUs6_AcaTNQ.jpeg" /></figure><p>Every profile deleted from Grindr represents something worth celebrating: someone found love. Every person who leaves HER to build a life with their partner is a success story the app made possible. Every relationship that started on Taimi is proof that the platform worked exactly as it should.</p><p>This is the paradox that makes LGBTQ+ dating apps extraordinary: their success metric — users finding authentic connection and leaving to build relationships — is fundamentally different from how we typically measure platform growth. And that difference isn’t a weakness. It’s an opportunity to reimagine what scale, impact, and value actually mean in the social technology space.</p><p>For decades, LGBTQ+ people had nowhere to find each other safely. Grindr changed that. HER created the first dating space designed by and for queer women. Taimi built a platform that welcomed trans and non-binary users when mainstream apps were indifferent. These apps didn’t just solve dating problems. They enabled community, safety, and self-discovery for millions of people who had never had those experiences before.</p><p>The fact that they operate within a specific demographic isn’t a constraint. It’s their superpower.</p><p><strong>Reframing the Growth Ceiling</strong></p><p>Yes, LGBTQ+ dating apps have a finite addressable market. Compared to Tinder’s billions, queer demographics are smaller. But this creates something far more valuable than scale: it creates intimacy and accountability.</p><p>When Grindr serves 11 million users rather than 75 million, every decision the company makes has a clearer impact on actual human lives. When HER knows its users are part of a specific community with shared values, the app can be intentional about culture in ways Bumble can’t at scale.</p><p>This is the opportunity: build for depth instead of breadth. Create platforms so aligned with their communities that users don’t want to leave even after they find partners. Not because the app is addictive — but because the community is home.</p><p>This is already happening. Taimi users stay on the platform after finding relationships because they’ve built genuine friendships. Grindr has always been as much a social network as a dating app. HER hosts events that bring users together offline. The most successful LGBTQ+ apps are the ones treating their community as something to nurture, not extract value from.</p><p><strong>Four Paths to Meaningful Scale</strong></p><p><strong>Strategy 1: Community Capital as Currency</strong></p><p>Stop thinking of data as the monetization layer. Think of community as the asset.</p><p>LGBTQ+ users chose these apps because they felt safe and understood. That trust is invaluable. Rather than selling user data to advertising agencies, partner with brands and organizations that actually serve queer communities: health providers, LGBTQ nonprofits, affirming employers, queer-owned businesses.</p><p>Grindr could facilitate premium partnerships with PrEP programs, making health access frictionless within the app. HER could partner with queer-founded fashion brands, therapists, and legal services. Taimi could work with LGBTQ+ adoption agencies and fertility clinics.</p><p>This isn’t data extraction. It’s adding value to the community while creating revenue that actually improves users’ lives. Users pay because the marketplace inside the app makes their lives better. The platform grows because it becomes essential infrastructure, not just dating.</p><p><strong>Downsides:</strong> This requires deep partnerships and slower growth. But it builds something durable: a community that needs the platform because the platform serves them holistically.</p><p><strong>Strategy 2: Deepen the TAM Within the Community</strong></p><p>The most exciting users aren’t necessarily the ones looking for their first relationship. They’re the ones looking for the second, third, or tenth kind of connection.</p><p>Queer people navigate relationship structures mainstream dating apps don’t even recognize. Open relationships. Polyamory. Queer friendships that are as important as romantic partnerships. Co-parenting arrangements. Non-romantic life partnerships. These are thriving, authentic relationship models that deserve platforms built specifically for them.</p><p>Apps like Feeld proved there’s massive demand for relationship diversity. But Feeld isn’t queer-specific. Imagine a version of Taimi or HER that doesn’t just support these relationship structures — that celebrates them, makes them the default, and builds features specifically for them.</p><p>A person in an open marriage might use the same app for years. Someone seeking queer friendship stays engaged differently. A couple looking to foster or adopt could connect with others on the same journey. The churn profile transforms when success means many different things.</p><p>This expands the addressable market from “LGBTQ+ singles looking for a monogamous relationship” to “LGBTQ+ people looking for any form of authentic connection.” That’s a vastly larger cohort.</p><p><strong>Downsides:</strong> This requires evolving how the app understands itself. But it also positions the platform as ahead of mainstream apps in recognizing how people actually love.</p><p><strong>Strategy 3: Build the Integrated Queer Life Platform</strong></p><p>This is the most ambitious path, but also the most aligned with how LGBTQ+ communities actually need support.</p><p>Queer life involves decisions mainstream people take for granted. How do you find a therapist who gets your identity? Where do you access PrEP without judgment? How do you find other queer parents? Where do you discover your community when you move to a new city?</p><p>Imagine an app ecosystem where dating is one layer of a much larger platform. Layer in health services (PrEP coordination, STI testing, telehealth counseling). Layer in family planning (matching with co-parents, egg donors, surrogacy connections). Layer in community (events, meetups, interest-based groups). Layer in lifestyle services (affirming financial advisors, therapists, legal services).</p><p>This isn’t Grindr becoming a super-app. It’s recognizing that queer users need integrated support across life domains. Apps like Plume and OurFamily are proving there’s demand. What if those services lived inside the community platform users already trust?</p><p>A person might stay on the platform for five years — not because they’re dating, but because their entire support network is there. Churn becomes irrelevant when the platform is essential infrastructure.</p><p><strong>Downsides:</strong> This requires capital, expertise, and partnerships. It’s ambitious. But it’s also the vision that attracted many queer people to tech in the first place: building tools that serve communities that have been historically underserved.</p><p><strong>Strategy 4: Mainstream With Integrity</strong></p><p>Here’s the counterintuitive path: expand to mainstream audiences without losing your soul.</p><p>Bumble and Hinge have proven you can serve queer users at scale without diluting brand. The difference is that they started mainstream and added queer inclusivity as an afterthought. What if an LGBTQ-founded app did the reverse: stay rooted in queer community while deliberately expanding to straight users who share your values?</p><p>Position not as “a dating app for everyone” but as “a dating app for people who believe in love without limits.” Users of all orientations who care about authenticity, inclusion, and genuine connection. This attracts a specific straight demographic: younger, more progressive, values-aligned.</p><p>You’re not competing with Tinder on scale. You’re competing on meaning. The app’s identity becomes “this is where people go when they want dating that feels safe and intentional.”</p><p>Taimi is already positioned this way. It explicitly welcomes all orientations and positions itself around acceptance. HER has experimented with including non-binary and trans straight men. The brands that pull this off successfully aren’t positioning as “queer app trying to go mainstream” — they’re positioning as “values-based app that happens to be queer-founded.”</p><p>This actually leverages the queer foundation as differentiation rather than limitation. You grew up building for a community that taught you something about authentic connection that mainstream apps never learned.</p><p><strong>Downsides:</strong> This requires cultural confidence. You can’t water down what makes the app special. But done right, it’s not dilution — it’s scaling impact.</p><p><strong>The Real Opportunity</strong></p><p>Here’s what makes LGBTQ+ dating apps genuinely exciting in 2026: they’re positioned to redefine what platform success means.</p><p>For years, tech has measured success by growth at any cost. User acquisition. DAU. Retention at the expense of genuine value. The apps that obsess over scale often lose sight of why they existed.</p><p>LGBTQ+ dating apps have a built-in constraint that forces the opposite philosophy. You can’t grow infinitely, so you have to get really good at building things people actually need. You can’t rely on network effects alone, so you have to create genuine community. You can’t assume your users will stay forever, so you have to make the experience meaningful.</p><p>This is the opposite of a weakness. This is a masterclass in intentional platform design.</p><p><strong>A Different Kind of Scale</strong></p><p>Scale doesn’t have to mean billions of users. It can mean billions of lives improved. A platform that serves 11 million people exceptionally well — helping them find love, build community, access healthcare, start families — is scaling something real.</p><p>The most successful LGBTQ+ apps will be the ones that lean into this. That treat their bounded market not as a limitation but as an opportunity to build something so good, so aligned with community values, that users don’t want to leave because the app has become infrastructure. Home.</p><p>That’s not a growth ceiling. That’s a different kind of success entirely.</p><p>And honestly, it might be the most important thing platforms can build.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb62959c748a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring What Matters: How to Build Tangible Metrics of Success]]></title>
            <link>https://medium.com/@marissacohen/measuring-what-matters-how-to-build-tangible-success-metrics-a208e0286173?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a208e0286173</guid>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 21:44:07 GMT</pubDate>
            <atom:updated>2026-08-14T21:44:58.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*NwH7xsxKdwpAdBlK-GT09g.avif" /></figure><p>Your dashboard shows DAU is up 3% this quarter. Your community health score improved 12%. Off-platform relationship formation is at 18%. User lifetime value is $247.</p><p>But which number tells you the platform is actually working?</p><p>This is the measurement problem most community platforms never solve. They optimize for traditional SaaS metrics — DAU, MAU, growth rate — that fundamentally misrepresent how community platforms succeed. Then they make decisions based on that misrepresentation.</p><p>The solution isn’t to hide the hard metrics. It’s to build a measurement framework that tells the truth about what success actually looks like for communities. And then organize the entire product team around it.</p><p><strong>Why Traditional Metrics Lie About Community Platforms</strong></p><p>DAU (Daily Active Users) measures engagement, not value. A person opening Grindr for 30 seconds to check if their ex came back is a DAU. Someone in a committed relationship who opened the app once a week to stay connected with friends is also a DAU. They’re counted the same.</p><p>For dating apps, this is catastrophic. The metric treats churn from successful matches as failure. Every happy couple that stops using the app appears as decline. Every person who stayed 18 months in a dysfunctional pattern looking for The One appears as success.</p><p>MAU (Monthly Active Users) is worse. It measures whether someone opened the app once in 30 days. For a community platform where people find partners and leave, MAU is the opposite of what you want to optimize.</p><p>Growth rate assumes infinite expansion. This is fine for Slack, which expands vertically into enterprise. It’s fine for Spotify, which expands into new countries. It’s fundamentally wrong for platforms bounded by demography.</p><p>Here’s what makes this worse: because these metrics are standard, they drive behavior. You become what you measure. Optimize for DAU and you build push notifications that drive fake daily opens. Optimize for growth and you acquire low-quality users. The metrics become the strategy, regardless of whether they align with the actual mission.</p><p><strong>What to Measure Instead</strong></p><p>If traditional metrics mislead, what actually tells the story of a healthy community platform?</p><p><strong>1. Community Health Score (Composite Metric)</strong></p><p>This combines several signals into one number that represents whether your platform is thriving as a community.</p><p>Components:</p><ul><li><strong>Trust Verification Rate</strong> (% of active users with verified profiles): For dating apps, verification defeats catfishing and increases safety. Higher verification = stronger community. Target: 70%+</li><li><strong>Meaningful Connection Rate</strong> (% of new matches that result in 3+ messages exchanged): This separates genuine connections from swipes-and-ghosts. It’s a proxy for match quality. Target: 45%+</li><li><strong>Retention After Match</strong> (% of users who stay 30+ days after first meaningful match): This tells you whether people stay connected to community after finding partners. Target: 65%+</li><li><strong>Community Engagement Outside Dating</strong> (% of users participating in events, groups, forums, or friend connections): For apps with community features, this shows depth. Target: 35%+</li><li><strong>User-Generated Content</strong> (posts, photos, event listings per 1,000 users per month): Active communities create content. Passive communities consume. Target: 150+ per 1,000 users</li></ul><p><strong>Formula:</strong> Community Health Score = (Verification Rate × 0.25) + (Meaningful Connection Rate × 0.25) + (Post-Match Retention × 0.25) + (Community Engagement × 0.15) + (UGC per user × 0.10)</p><p>Weighted average of 0–100. This gives you a single number that combines safety, match quality, retention, and engagement.</p><p><strong>2. User Lifetime Value (ULV)</strong></p><p>This is straightforward but often calculated wrong for dating apps.</p><p>Traditional formula: (Average Revenue Per User × Gross Margin) × (Retention Rate / Churn Rate)</p><p>For a community platform, this needs to account for the fact that your “churn” includes successful outcomes.</p><p>Better formula: ULV = [(Subscription Revenue Per User + Partner Revenue Per User + Ad Revenue Per User) × Customer Lifespan] — Acquisition Cost</p><p>But refine the lifespan calculation. Don’t use traditional SaaS churn. Use “relationship formation age” instead.</p><p>For example: The average user stays 8 months. The average successful match happens at month 4. 60% of users who match stay another 4 months. So average lifespan = 8 months, not 24.</p><p>If you can track post-match behavior:</p><ul><li>Users who match and leave: 4 month average lifespan</li><li>Users who match and stay: 12 month average lifespan</li><li>Users who don’t match: 6 month average lifespan</li></ul><p>Weight by percentage: ULV = [(40% × 4 months) + (40% × 12 months) + (20% × 6 months)] × Revenue Per Month</p><p>This tells a completely different story. Yes, 40% of users churn after matching. But they’re churning because the product worked. And your 12-month cohort (users who stayed after matching) has significantly higher lifetime value.</p><p><strong>3. Off-Platform Relationship Formation Rate</strong></p><p>This is the business metric that’s hardest to track but most important to measure.</p><p>What percentage of your users form relationships and leave? How many of those relationships last? Are you actually solving the problem or just keeping people engaged?</p><p>Implementation:</p><p>Track users 6 months post-deletion via:</p><ul><li>Email survey: “Are you still in the relationship you met through [app]?”</li><li>Partner integrations: If users connect their Instagram or social profile, you can track relationship status</li><li>Optional exit surveys: “What would you rate your experience? Are you in a relationship?”</li><li>Second-order signals: If two users both delete within a week and their profile descriptions match, they probably matched</li></ul><p>You won’t get 100% response rate. Aim for 20–30% survey response among deleted users.</p><p><strong>Key metrics:</strong></p><ul><li>Relationship formation rate: % of users who match and remain in contact 6+ months post-deletion</li><li>Relationship longevity: % of those relationships still active 12+ months later</li><li>Relationship quality perception: Self-reported satisfaction (1–10 scale)</li></ul><p>This is the ultimate success metric. A 25% relationship formation rate with 70% longevity means you’re genuinely building lasting connections, not just engagement.</p><p><strong>4. Community Retention (Not User Retention)</strong></p><p>Traditional retention is a cohort metric: “What % of users from January are still active in February?”</p><p>For community platforms, this is wrong. You want to measure whether the community remains healthy after individual users leave.</p><p>Better approach: Cohort strength over time.</p><p>Track:</p><ul><li>New users added per month</li><li>Users who form meaningful connections per month</li><li>Users who exit per month (by outcome: in relationship, relocated, no matches, etc.)</li><li>New organic DAU (users who didn’t sign up this month but returned)</li><li>Community event attendance per month</li></ul><p>Then measure: Is the platform replacing churning users with new ones? Is the community self-sustaining?</p><p><strong>Formula:</strong> Community Retention Index = (Net New Verified Users + Organic Returns + Event Attendees) / (Users Who Left)</p><p>If this ratio is above 1.0, your community is growing or stable despite individual churn. If it’s below 0.8, you have a problem.</p><p>This separates two outcomes: (1) The app is dying because users are leaving; (2) The app is succeeding because users are leaving to form relationships and being replaced by new ones. The metric tells you which is actually happening.</p><p><strong>5. Trust and Safety Metrics</strong></p><p>For community platforms, safety isn’t a feature — it’s foundational.</p><p>Track:</p><ul><li><strong>Harassment reports per 1,000 users per month</strong>: Lower is better. Benchmark against your own history, not other apps.</li><li><strong>Report resolution time</strong>: Median hours from report to action taken.</li><li><strong>User confidence in safety</strong> (surveyed quarterly): “Do you feel safe on this app?” 1–10 scale. Target: 8+.</li><li><strong>False positive rate on automated moderation</strong>: % of actions taken that users appeal successfully. Aim for &lt;5%.</li><li><strong>Verification completion time</strong>: Days from account creation to verification. This is a retention blocker if it’s too long.</li></ul><p>Safety determines whether users stay. A platform with 50% DAU growth but declining safety scores is failing. Safety scores with stable DAU indicate a healthy platform.</p><p><strong>How to Track These (And Why They’re Harder to Game)</strong></p><p><strong>The infrastructure:</strong></p><p>You need event tracking architecture that captures behavior across the user lifecycle, not just login events.</p><p>Core events to instrument:</p><ul><li>Profile creation</li><li>Profile verification (upload photo, verify identity)</li><li>Profile completion (filled out all fields, added photos)</li><li>Swipe / Like / Match action</li><li>Message sent (first message, message count per conversation)</li><li>Conversation duration (time between first and last message)</li><li>Conversation outcome (still active, user deleted, unmatch)</li><li>Community feature engagement (attended event, posted, commented, joined group)</li><li>Account deletion (timestamp + exit survey reason)</li><li>Reactivation (deleted user who signs up again)</li></ul><p>You need a data warehouse (Snowflake, BigQuery, Redshift) to aggregate this at scale. And you need retention tracking to follow deleted users.</p><p><strong>Why these are harder to game:</strong></p><p>Traditional metrics (DAU, growth rate) are gamed constantly. Here’s how:</p><ul><li>Push notifications that drive fake daily opens</li><li>Artificial engagement loops that keep people in the app without value</li><li>Acquisition campaigns that target low-quality users</li><li>Retention hacks that increase time in app without increasing satisfaction</li></ul><p>These work because the metrics don’t measure real value. A 20% increase in DAU from push notification spam looks the same as a 20% increase from improved product.</p><p>Community health metrics are much harder to game because they require actual user behavior:</p><ul><li><strong>Verification rate:</strong> You can’t fake verified profiles without breaking safety, which tanks other metrics</li><li><strong>Meaningful connection rate:</strong> You can’t force matches to result in conversations. This requires actual attraction and compatibility</li><li><strong>Post-match retention:</strong> You can’t artificially keep people engaged after they find partners without destroying trust</li><li><strong>Off-platform relationship formation:</strong> You can’t fake this. Users either form relationships or they don’t</li><li><strong>Community engagement:</strong> You can create bot accounts to post, but verified user posting % still shows the truth</li></ul><p>The metrics are harder to hit, which makes them more credible. An increase in Community Health Score is real progress, not engagement hacking.</p><p><strong>What a Dashboard Looks Like</strong></p><p>Stop reporting like a SaaS company. Here’s what an actual community platform dashboard should look like:</p><p><strong>Tier 1: Executive Dashboard (Monthly Reporting)</strong></p><p>Single screen, 5 metrics:</p><ul><li><strong>Community Health Score:</strong> Current month vs. last quarter. Color-coded (green 70+, yellow 50–70, red &lt;50). Include trend line (3-month moving average).</li><li><strong>User Lifetime Value:</strong> Total and by cohort (match → stay vs. match → leave). Include churn-adjusted projection.</li><li><strong>Relationship Formation Rate:</strong> % of matched users forming 6+ month relationships (tracked via exit survey). Include 12-month longevity rate.</li><li><strong>Net Community Retention:</strong> (New Users + Organic Returns + Event Attendees) / Users Who Left. Target: &gt;1.0.</li><li><strong>Safety Confidence Score:</strong> User-reported safety (1–10 scale) averaged over quarter. Target: 8+.</li></ul><p>Below the fold: narrative explaining changes. “Community Health Score up 12% due to improved verification (now 73%) and post-match retention (now 68%). Off-platform relationship formation rate stable at 24%.”</p><p><strong>Tier 2: Product Dashboard (Weekly Reporting)</strong></p><p>For the product and operations team:</p><ul><li><strong>Funnel (weekly cohort):</strong> Sign-up → Verification → Profile Complete → First Match → Meaningful Conversation (3+ messages)</li><li><strong>Retention cohorts:</strong> Users matched vs. unmatched, segmented by relationship status on exit</li><li><strong>Engagement depth:</strong> % of users in each engagement tier (browsers, swipes, matchers, community participants)</li><li><strong>Event metrics:</strong> Events created, attendance, unique attendees, community lift (attendees who stay 30+ days)</li><li><strong>Safety incidents:</strong> Reports per 1,000 users, resolution time, user confidence by incident type (harassment, catfishing, safety concerns)</li></ul><p><strong>Tier 3: Financial Dashboard (Quarterly)</strong></p><ul><li><strong>Revenue per user:</strong> By cohort (acquisition month) and outcome (matched/unmatched)</li><li><strong>CAC vs. ULV:</strong> Customer acquisition cost vs. lifetime value. Include scenarios where users match early vs. late</li><li><strong>Unit economics:</strong> Revenue/Churn/Margin table broken by user outcome (in relationship, relocated, no matches, inactive)</li><li><strong>Partner revenue:</strong> By partner type (health, lifestyle, services) and user penetration</li></ul><p><strong>Example monthly report:</strong></p><p><strong>Community Platform Health Report — June 2026</strong></p><p><strong>Community Health Score: 68.5 (+2.1 vs. May)</strong></p><p>Component June Target Trend Verification Rate 73% 70% ↑ Meaningful Connection Rate 47% 45% ↑ Post-Match Retention 64% 65% → Community Engagement 38% 35% ↑ UGC per 1,000 users 162 150 ↑</p><p><strong>User Lifetime Value: $312</strong></p><ul><li>Users who match &amp; stay (40%): $410 avg</li><li>Users who match &amp; leave (40%): $186 avg</li><li>Users who don’t match (20%): $278 avg</li></ul><p><strong>Off-Platform Relationships Formed: 26% of matched users (6-month follow-up, n=4,200)</strong></p><ul><li>12-month longevity: 71% of 6-month relationships still active</li><li>User satisfaction with relationship: 8.2/10 avg</li></ul><p><strong>Net Community Retention: 1.12</strong></p><ul><li>New verified users: +3,400</li><li>Organic returns (users who deleted, then reinstalled): +420</li><li>Event attendees (new or repeat): +890</li><li>Users who deleted (matched or other): -3,600</li><li>Result: Community is self-sustaining; new users replacing churned users at 112% ratio</li></ul><p><strong>Safety Confidence: 8.1/10 (+0.2 vs. May)</strong></p><ul><li>Harassment reports: 2.1 per 1,000 users (target: &lt;2.5)</li><li>Resolution time: 18 hours median (target: &lt;24)</li><li>False positives on automated moderation: 3.2% (target: &lt;5%)</li></ul><p><strong>What Changed:</strong> Verification rate improved due to new one-tap verification option (reduced friction from 8 minutes to 2 minutes). Post-match retention held steady despite higher matching volume, indicating quality is consistent. Community engagement jumped due to first community event (Pride planning group) reaching 1,200 attendees.</p><p><strong>Building the Metrics Culture</strong></p><p>The hardest part isn’t the infrastructure. It’s getting your team to stop obsessing over DAU.</p><p>Weekly all-hands should feature:</p><ul><li>Community Health Score (trend and components)</li><li>User Lifetime Value (by cohort)</li><li>Relationship formation stories (qualitative signal of what’s actually happening)</li></ul><p>Engineers should be measured on their contribution to health metrics, not DAU. A feature that increases meaningful connections by 5% but decreases DAU by 2% is a win.</p><p>Product should run experiments that move health metrics, not engagement metrics. “Can we improve verification completion time without dropping completion rate?” is a better question than “Can we increase time in app?”</p><p>This is hard culture work. But it’s worth it because it aligns incentives with mission. You stop fighting your own strategy. The metrics become what you naturally optimize for because they reflect what actually matters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a208e0286173" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Family Plan Gold Mine: How Spotify Is Leaving CLV on the Table]]></title>
            <link>https://medium.com/@marissacohen/the-family-plan-gold-mine-how-spotify-is-leaving-clv-on-the-table-166d65c2ab48?source=rss-2164795c8ae7------2</link>
            <guid isPermaLink="false">https://medium.com/p/166d65c2ab48</guid>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[customer-lifetime-value]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[spotify-marketing]]></category>
            <category><![CDATA[saas-product-marketing]]></category>
            <dc:creator><![CDATA[Marissa Cohen]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 21:38:24 GMT</pubDate>
            <atom:updated>2026-08-13T21:38:24.110Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqr6X_CG_7PLl98POGFoSw.png" /></figure><p>There’s a customer segment Spotify isn’t optimizing for, and it’s hiding in plain sight: high-value family plan decision-makers who are willing to pay <em>more</em> for the right reasons.</p><p>Research reveals something that most churn models miss entirely. Spotify isn’t losing these customers because the product is bad. They’re losing them because Spotify has never given them a reason to feel like their subscription reflects their values. These are exactly the kind of customers who would spend more if it did.</p><h3>The CLV Opportunity Spotify Is Missing</h3><p>Let’s start with the math. A standard family plan subscription generates $20–25/month. That looks like $240–300 in annual recurring revenue per customer.</p><p>But here’s what Spotify’s current pricing misses:</p><p>High-value family plan decision-makers, if positioned correctly, might pay $35–45/month for a family plan that includes:</p><ul><li>Transparent artist payment data</li><li>Verified ethical guidelines on AI usage</li><li>Priority access to exclusive artist content</li><li>Direct artist support features</li></ul><p>That’s not a premium tier. That’s a <em>values-aligned</em> tier. And high-value customers don’t just accept it. They champion it.</p><p>The CLV shift: from $240–300/year to $420–540/year. A single family plan manager generating nearly double the revenue because their values are being honored.</p><p>Now multiply that across Spotify’s entire family plan base and segment by decision-maker profile. The untapped revenue is massive.</p><h3>Who Are High-CLV Family Plan Decision-Makers?</h3><p>Not all family plan managers are created equal. Some are passive administrators. Others are active curators and values-driven gatekeepers.</p><p>High-CLV family plan decision-makers share common characteristics:</p><ul><li><strong>10+ year tenure</strong> (highest lifetime value predictors)</li><li><strong>3–7 managed accounts</strong> (natural advocates with influence)</li><li><strong>Daily engagement</strong> (habit formation equals stickiness)</li><li><strong>Values-sensitive decision-making</strong> (willing to pay for alignment)</li><li><strong>Micro-influencer status</strong> (shapes family perception and external networks)</li><li><strong>High willingness to pay</strong> (for features that matter to them)</li></ul><p>These customers represent a disproportionate share of family plan CLV. Spotify’s current strategy treats them the same as casual managers paying for the convenience discount.</p><p>That’s leaving money on the table.</p><h3>The Retention Mechanism That Increases CLV</h3><p>Here’s the counterintuitive insight: the best way to increase family plan CLV isn’t to raise prices. It’s to deepen the relationship.</p><p>High-value family plan decision-makers will stay and spend more if Spotify makes them feel like stakeholders in the platform’s values and direction. This requires three things:</p><p><strong>1. Transparency Creates Stickiness</strong></p><p>These customers are concerned about artist payment and AI ethics. Right now, Spotify responds with silence or defensive positioning. Instead, build a “Family Plan Impact Dashboard” that shows:</p><ul><li>Real-time data on artist payouts from the family’s listening</li><li>Verified information on AI usage policies and artist consent frameworks</li><li>Breakdown of where subscription dollars flow (artist support, infrastructure, innovation)</li><li>Comparison metrics against competitors on ethical dimensions</li></ul><p>This transforms worried customers into informed stakeholders. Stickiness increases because transparency builds trust.</p><p><strong>2. Values Alignment Justifies Premium Pricing</strong></p><p>High-value decision-makers would pay more for a family plan that explicitly commits to artist-first positioning. Not as marketing spin. As measurable policy.</p><p>A “Spotify Family Artist Trust” tier could include:</p><ul><li>Guaranteed minimum artist payments (beyond Spotify’s current model)</li><li>Verified ethical AI usage</li><li>Direct revenue sharing with artists the family follows most</li><li>Quarterly transparency reports on ethical commitments</li></ul><p>Position this as a premium tier at $35–45/month. Market it to values-driven decision-makers. Conversion rates don’t hesitate.</p><p>The psychology: these customers aren’t paying for more music. They’re paying to feel like they’re part of the solution. That’s a more powerful CLV lever than any algorithmic recommendation.</p><p><strong>3. Expansion Revenue Within the Family Structure</strong></p><p>Current family plan monetization is flat. You pay for six accounts, period. But high-value decision-makers have expanded needs and willingness to pay:</p><ul><li><strong>Artist Direct Support Add-On</strong> ($5–10/month): Send a portion of your subscription directly to artists you designate</li><li><strong>Family Playlist Collaboration Tools</strong> ($3–5/month): Advanced sharing, discovery, and playlist management for the family unit</li><li><strong>Spotify Live Events Access</strong> ($2–3/month): Early access to artist performances, exclusive podcasts, or live sessions</li><li><strong>Ad-Free Podcast Discovery</strong> ($3–5/month): Premium podcast recommendations tailored to the family’s taste</li></ul><p>These aren’t premium tiers. They’re family-plan add-ons that high-value decision-makers will purchase to customize their experience. A $20/month family plan now generates $30–40/month in revenue.</p><h3>Segmentation Strategy for CLV Optimization</h3><p>Not every family plan manager needs the same treatment. Segment by decision-maker profile and tailor your expansion strategy:</p><p><strong>High-CLV Segment</strong></p><ul><li>Values-driven, tenure-based, influence within family networks</li><li>Strategy: Position as values-aligned stakeholder. Offer premium ethical positioning and transparency. Support with exclusive content and artist connection features.</li><li>Expected CLV increase: 50–100%</li></ul><p><strong>Convenience-Optimizers</strong></p><ul><li>Pragmatic decision-makers focused on price and ease</li><li>Strategy: Expand lock-in through social features and shared discovery. Simplify management. Avoid values-based messaging.</li><li>Expected CLV increase: 20–30% through add-ons and features</li></ul><p><strong>Growth-Focused Families</strong></p><ul><li>Younger households, expanding music taste, high engagement</li><li>Strategy: Offer discovery-focused add-ons, early access to new features, collaborative tools</li><li>Expected CLV increase: 30–50%</li></ul><h3>The Retention Math That Works</h3><p>Here’s why values-aligned positioning increases retention <em>and</em> CLV simultaneously:</p><p><strong>Current scenario:</strong> High-value decision-makers feel ethically conflicted. They stay because switching costs are high (family lock-in, playlists, habit). But they’re not happy. Retention is transactional. At the first major trigger (artist departure, price increase, competitor innovation), they leave.</p><p>CLV impact: $240–300/year, high churn risk</p><p><strong>Values-aligned scenario:</strong> These customers feel like stakeholders. They understand where their money goes. They see Spotify committing to artist support. They upgrade to the ethical tier and add artist direct support. They stay because the relationship is aligned with their values, not just convenient.</p><p>CLV impact: $420–540/year, significantly lower churn risk, organic advocacy</p><p>The insight: <strong>Retention driven by values alignment is stickier and more profitable than retention driven by convenience.</strong></p><h3>Why This Matters for Spotify’s Competitive Position</h3><p>Apple Music and YouTube Music are quietly building their own ethics narratives. They’re not talking about artist payment or AI ethics explicitly, but they’re positioning as “alternatives” to Spotify.</p><p>Spotify’s family plan could be a competitive advantage if positioned around values. Right now, it’s just a discount structure.</p><p>The company that builds a family plan experience around transparency, ethics, and values alignment wins the high-CLV segment. And that segment controls not just their own subscription, but their household’s perception of the brand.</p><h3>The Test You Should Run</h3><p>Offer a limited “Spotify Family Artist Trust” tier to high-value family plan decision-makers at $38/month (vs. current $20–25 family plan). Include:</p><ul><li>Transparent artist payment dashboard</li><li>Verified AI usage policies</li><li>Quarterly ethical impact reports</li><li>Early access to artist content and exclusive features</li></ul><p>Measure:</p><ul><li>Upgrade rate among high-tenure, high-engagement family plan managers</li><li>CLV increase vs. standard family plan</li><li>Churn rate for upgraded segment vs. control</li><li>Net Promoter Score and brand sentiment shifts</li></ul><p>If high-value decision-makers upgrade at 20%+ rates and CLV increases by 50%+, you’ve found an untapped revenue stream.</p><h3>The Bottom Line</h3><p>Spotify’s family plan was designed to democratize Premium subscriptions. But it can be so much more. High-value decision-makers aren’t just paying for music. They’re paying for alignment with their values.</p><p>The family plan that captures that demand doesn’t just retain customers. It transforms them into engaged advocates who spend more, stay longer, and influence their networks.</p><p>Right now, Spotify treats every family plan the same. The competitor that segments by decision-maker profile and builds differentiated value propositions around ethics and transparency will own the high-CLV family plan market.</p><p>For Spotify, the question isn’t how to prevent these customers from leaving. It’s how to make them want to spend more.</p><p><em>Are you a family plan decision-maker? What would make you willing to pay premium pricing for your streaming service? Share your answer in the comments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=166d65c2ab48" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>