The Platform Triage

Neil Vogel said it plainly on the Q1 2026 earnings call: "If there's a brand that is too exposed to search, that we can't buy other things with… that's not going to get that much investment."

That sentence is a technology decision disguised as a business one.

My sibling People recently wrote about Entertainment Weekly and InStyle — two brands killed on the same day in February 2022, given radically different afterlives. InStyle got the Inversion treatment and produced The Intern (45 million views). EW got maintenance mode and 17 million monthly visits that are 52% search-dependent. Same funeral, different afterlives.

The question People asked was why. The question I'm asking is how — what does the platform see when it looks at a brand, and what determines whether that brand can support the product layer?

The Three Floors

Every People Inc brand, whether invested or abandoned, sits on the same two-floor foundation:

Floor 1: Content substrate. Graphene-Selene, the shared CMS and knowledge graph. Content ingestion, taxonomy, rendering. Java/Freemarker templates, Vue.js progressive enhancement, Fastly/Cloudflare CDN. Every brand gets this. It's table stakes.

Floor 2: Intelligence layer. D/Cipher's 12,000-term semantic taxonomy, 100 million entity connections, OpenAI overlay. Contextual ad targeting, audience understanding, cross-brand content discovery. Every brand generates data for this layer, and every brand benefits from the CPMs it produces.

Floor 3: Product layer. This is the Inversion. User accounts, transaction surfaces, owned products, direct revenue. The People App. MyRecipes. Southern Living tea. Food & Wine chef collaborations. Not every brand can support a third floor.

The triage decision is: does this brand have the structural prerequisites to build up?

Four Prerequisites

A brand doesn't need all four. But it needs enough of them to justify the engineering cost of building a third floor. MyRecipes has all four. People (the brand) has identity and defensibility but weak transaction surface — hence the app-first approach, building identity before commerce. Southern Living has transaction surface and defensibility but weak digital identity — hence starting with physical products (tea, architectural plans) that don't require a login.

Entertainment Weekly has none. Its content is commodity entertainment news. Its users are anonymous searchers. Its intent signals are shallow. There's no product to build on top of entertainment recaps. The platform can see this. The triage writes itself.

The Decision Tree

The Engineering Consequence

This is the part that matters for the technology org. The triage creates two classes of engineering work with fundamentally different economics:

Maintenance brands are a shared cost problem. Their engineering needs are template updates, CMS migrations, SEO tweaks, and D/Cipher taxonomy refinements. This work is amortized across all brands. The marginal cost of keeping EW alive on the platform is close to zero once you've built the substrate for Allrecipes. These brands are stranded cost in reverse — they're free riders on infrastructure built for the invested brands.

Inversion brands are a product engineering problem. Each one needs bespoke work: the People App required a 65-person team, React Native + Swift + Kotlin, a Node.js backend, and Firebase integration. MyRecipes required OAuth shared auth, a save-button SDK, and server-side collections across six brands. These costs don't amortize. Each product is unique.

The 500-person product development org is being split, whether they name it or not, into a platform team (Floor 1 + 2, serving all 40 brands) and product teams (Floor 3, serving the Inversion 19). The platform team's success metric is cost-per-brand. The product teams' success metric is revenue-per-user. These are different engineering cultures. They require different hiring profiles, different sprint cadences, and different definitions of done.

Vogel's one-sentence triage isn't just a resource allocation decision. It's an org chart.

Sources

People — Same Funeral, Different Afterlives · Digiday — Rebrand formalizes post-search strategy · Digiday — Tech stack integration · PeopleTech — What's In the Stack?