Multi-brand portfolios don't have a PR problem. They have a fragmentation problem.

If you run more than one brand, you don't have a PR problem. You have a fragmentation problem.

The PR problem is the obvious one — three hundred journalist queries a week, five worth answering, the deadline is in two hours, the draft sounds like a B2B SaaS brochure. We've written about that before. PRAPI was built to fix exactly that workflow, and PR-Pitch (the live module today) does fix it.

But the PR problem is one face of the bigger thing. The bigger thing is: every multi-brand operator runs each brand on a different stack, and each stack charges per seat per brand. The math breaks before you ever get to the question of whether the tools are any good.

That's the problem we're really solving. Today we shipped the marketing rewrite that says so out loud: PRAPI is the GTM platform for multi-brand portfolios. PR, editorial, outbound, and brand assets — one workspace, one bill, one voice rule per brand. PR-Pitch is the first GA module. Editorial Calendar, Outbound, and Asset Management ship Q3 2026. Source Directory ships Q4. All of them included at every tier.

This post explains why the pivot, what changes for you, and what doesn't.

The fragmentation tax

Imagine you run six brands. (One of us does. Hi.) Here is what your stack looks like in a year that costs you nothing to track:

• A PR tool. Per seat per brand. $150/mo × 6 = $900/mo.
• A content calendar tool. Per brand workspace. $50/mo × 6 = $300/mo.
• A cold-outbound platform. Per seat per brand. $80/mo × 6 = $480/mo.
• A brand-asset DAM. Per workspace per brand. $25/mo × 6 = $150/mo.
• A press-kit generator. One-time fee per brand. $99 × 6 = $594.

That's $1,830/mo before you've used any of it. Eleven separate logins, six copies of every brand voice rule pasted into six different "voice" fields, six headshot folders, six audience-segment lists, six positioning statements you've forgotten to update on three of the six.

You aren't paying for tools. You're paying for context-switching tax, and the SaaS vendors are pricing it as if you were six different customers.

The deeper problem isn't the cash. It's that no two of those tools talk to each other. The voice rule you nailed in the PR tool isn't readable by the content calendar. The audience definition in the outbound platform isn't readable by the asset DAM. Every brand context lives in a proprietary database, behind a login, in a format only that vendor can parse.

When you cancel the PR tool because you're consolidating, you don't move the brand context to the next tool — you re-enter it from screenshots.

Why "multi-brand mode" in single-brand tools is a band-aid

The standard answer to multi-brand operators is "use our agency tier, you can manage multiple brands." Some of these are decent. None of them are designed for a portfolio operator who's also the founder of every brand.

The agency frame assumes:

• Each brand has a separate team.
• Each brand has its own voice manager who sets up that brand's settings.
• Brand context is brand-private — not portable across brands you also operate.
• Pricing scales linearly with brand count because that's how agencies charge clients.

The portfolio frame is different:

• One person operates all the brands.
• One person sets up all the voice rules, audiences, asset libraries.
• Brand context overlaps massively (your founder credentials, your operator-level voice rules, your shared methodology) — duplicating it across six brand setups is busywork.
• The brand count is incidental to the unit of value. The unit of value is the portfolio.

PRAPI prices per portfolio. Up to 10 brands at one bill on Intel ($249/mo). Compare to $1,830/mo for the fragmented stack above and the math works at brand count two, gets ridiculous by brand count five.

But the deeper change is structural. Same brief.md file per brand drives every module. Author it once. PR-Pitch reads it for voice and outlet preferences. Editorial Calendar reads it for content cadence and tone. Outbound reads it for cold-email personalization. Asset Management reads it to label and version your headshots and press kits. One file, every module.

That's the fragmentation problem solved at the substrate, not at the workspace level.

The six modules

Here's what's shipping and when.

PR-Pitch · LIVE. The thing that's already running. Eight inbound source-request feeds (HARO, Featured, B2B Writer, PressRanger, SourceBottle email-forwarded; Substack, X, LinkedIn poll-driven). Each query forwarded into one inbox, scored against your brand brief, drafted in your voice. Voice validator runs on every draft. Outlet diligence flags pay-to-play and templated-content placements. Auto-escalates outlet classifications when multiple operators report the same problem.

Editorial Calendar · Q3 2026. Cross-brand content cadence. One grid showing every brand's content slots — blog, LinkedIn, social — across the next month, drafted from the same brief.md. Topic fanouts: pick one theme, fan it across six brands' voices automatically. The thing you've been doing with a Notion master sheet and seven brand sub-pages, except the voice doesn't drift because the brief is canonical.

Outbound · Q3 2026. Multi-brand cold email plus LinkedIn paste-and-validate. Per-brand sequences in per-brand voice, single inbox for all replies. Hard cap at 50 sends per brand per day. Pause-forever-on-reply: if a target replies once, the sequence dies for them across every brand you operate, permanently. Linear sequences, JIT generation against the latest brief.

Asset Management · Q3 2026. Versioned brand assets. Logos, headshots, press kits — non-destructive history per brand. Public press-kit ZIP endpoint that PR-Pitch and Outbound link to from drafts. Feeds the Q4 source directory.

Source Directory · Q4 2026. Public dual-surface source directory. A human UI at prapi.dev/sources for journalists and operators to browse who's available to comment on what. A REST API plus MCP for AI agents to query the same thing. JWS-signed brief.md from V1, so a journalist or AI agent can verify a brand's claimed credentials cryptographically.

Backlinks · ROLLING. Backlink targeting for brands actively running outbound. Reuses the voice validator plus outlet diligence plus a DataforSEO scorer to prioritize high-fit backlink opportunities — not a separate workflow, just a scoring layer that surfaces backlink-rich queries higher in the inbox when relevant.

The order isn't accidental. Each module reuses what the previous modules built. Editorial Calendar reuses PR-Pitch's voice validator. Outbound reuses PR-Pitch's outlet diligence and Editorial's drafting layer. Assets feeds both. Directory aggregates from all of them. Backlinks reuses everything.

This is what "platform" means structurally. Not "we have several products." It means each module's substrate is built so the next module gets to skip 70% of the work.

What doesn't change

The pivot doesn't change the things that made PRAPI useful in the first place.

brief.md is still your portable brand context. Stewarded by The Integrity Framework as an open spec, separate from PRAPI. If we shut down tomorrow, your brief.md keeps working with the next tool that implements the spec. Memory of why this is non-negotiable: see PRAPI is a Tool, brief.md is the Substrate. The platform pivot doesn't change this — it amplifies it. More modules reading the same brief makes the substrate-not-database commitment more load-bearing, not less.

Voice-strict, diligence-first. The voice validator runs on every draft, every module. Outlet diligence runs on every pitch. The platform expansion doesn't compromise quality discipline; if anything, the same gates run wider.

We draft, you send. No outbound automation that bypasses your review. Every channel — PR, content, cold outbound — produces drafts you approve. The thing that ruined HARO was automation without review. We're not making that mistake at six modules either.

API, CLI, MCP first-class. Every module ships with a REST API plus a CLI plus an MCP server alongside the dashboard. AI agents (yours or ours) can drive any module. "API parity later" isn't an acceptable scope cut — it's V1 scope, in the same PR.

14-day trial, no card up front. Same on every plan.

The pricing tradeoff we're making

There's a tension at the heart of "all modules at every tier" that's worth naming.

Every traditional SaaS pricing playbook says: tier the modules. Charge $49/mo for Solo with PR only, $149 for Operator with PR plus Editorial, $249 for Intel with everything. That's how you upsell. That's how you protect ARPU as the platform expands.

We're not doing that. Solo at $49/mo gets every module the same as Intel at $249/mo. The only thing that scales is brand count.

Why: portfolio operators are not the customers who care about module count. They care about brand count. A Solo customer with one brand using all six modules is a happy power user. An Operator customer with five brands using only PR-Pitch is the operational baseline. A fractional CMO with three clients spread across PR-Pitch and Outbound is exactly the segment we're built for.

Tiering by module would force us to draw lines between "PR person" and "GTM person" and "agency person." Those lines don't match how multi-brand operators actually work. Most of them oscillate between modes weekly.

The risk we're taking: ARPU per customer is lower than it could be. The bet: we capture more customers, retain them longer because the platform is genuinely sticky once you've authored briefs across modules, and the brand-count axis pulls customers up the price ladder organically as their portfolio grows.

If we're wrong about that, we'll find out in 18 months and adjust. Better to test the cleaner pricing model on a small audience than to launch with module tiers we'd regret.

What this means if you signed up before today

Nothing breaks. Your existing PR-Pitch workspace, your brief.md files, your forwarding addresses, your drafts, your billing — all stay exactly as they were. The only change is that the modules you didn't have access to before will start showing up in your sidebar as they ship Q3 and Q4. You don't pay extra for them.

If you signed up on a Solo plan and your portfolio has grown beyond one brand, the brand-count upgrade path stays the same: Solo → Operator → Intel as you scale brand count. Nothing about the module access changes.

If you bought the AppSumo lifetime deal during launch, you lock in your brand-count tier across every module that ships during the lifetime. Five brands, every module, lifetime — that's the deal we already promised, just with more in the box than we communicated.

What this means if you haven't signed up

The pitch is simpler now. PR-Pitch alone costs the same as PR-Pitch plus four more modules that ship later this year. If you're starting today, you're getting in on the platform price before the platform fully exists. If you wait until all six modules are GA, the price might be higher. (We aren't committing to a price hike either way — but we're not committing not to one.)

The 14-day trial covers the live module fully. Editorial / Outbound / Assets ship Q3 and unlock automatically when they're GA — you don't get charged extra, you don't have to upgrade, you just get the new modules.

Where to start

If you operate multiple brands and the fragmentation problem in this post sounds familiar: sign up, author a brand brief or generate one from your homepage URL at /brief-generator, and connect PR-Pitch to your inboxes. The first module's worth of value lands within an afternoon.

If you operate one brand and the platform framing sounds like overkill: it isn't. Solo at $49/mo runs the live module for a single-brand operator just fine. The other modules show up as they ship and don't cost you anything extra. You're paying for what's GA today plus an option on what's coming.

If you're a fractional CMO or indie agency operator: this is built for you. The portfolio-pricing model is the wedge. Three to five brands across two or three Intel-tier accounts (one per client portfolio you manage) gets you a per-portfolio bill that matches how you actually do the work.

The roadmap is published at /roadmap. Status by module, ingestion source, surface, feature, and protocol layer. Updated as the launch sequence ships.

We're a long way from done. PR-Pitch is one module of six. The platform pivot is the marketing surface catching up to what we've been building underneath. The next nine months are about closing the gap between what's promised and what's GA.

If you've been running a multi-brand portfolio on a fragmented stack and this is the framing you've been waiting for: welcome. Read your inbox, hit send, and we'll keep shipping.