Running several titles from one account, without flattening their identity
A publishing group runs several sites. How to narrate them all from a single account while each title keeps its own voice, player and logo, without multiplying subscriptions.
A publisher with one site never has this problem. A group running four titles hits it on day one: open four accounts, with four subscriptions, four logins and no overall view? Or put everything on one setup, at the cost of each title's identity? Both answers are bad, and it is exactly the gap between them that multi-site mode is meant to close.
The real dilemma of multi-brand groups
Multiplying accounts looks simple at first. Each title gets its own, each does as it likes. Then billing scatters, nobody knows what the group spends in total, and you have to sign out of one workspace to sign into another every time you switch title. Pool everything under a single setup instead, and the accounting gets tidy but the thing that matters breaks: the regional daily's voice is not the culture magazine's, and one shared logo across two distinct brands is a mistake.
So the real need has two sides, and no single compromise satisfies it: central management for what belongs to the group, and a distinct identity for what belongs to the title. Multi-site is where that dividing line becomes concrete.
What stays specific to each site, and what is shared
The rule is explicit, and that is what makes it usable. Each site keeps its own voice, its own player template, font, reading speed and logo. Those are the five settings by which a listener recognises the title, by ear and on screen. Anything you do not set explicitly for a secondary site inherits from the account: you never enter twice what is already common.
What is shared, conversely, is what makes sense at group level: a single login, a character quota shared across every title, a common team whose members move from one site to another without changing account, and a single invoice. You see what the group consumes in total, while each newsroom works inside its own decor.
Adding a site takes two pieces of information: a name and a domain. The secondary site then exists, ready to receive its own configuration. The main site is still set through your Player, Voice and Settings pages, exactly as before: multi-site does not add a layer on top of what exists, it extends it.
A concrete example
Take a group running a regional daily, a culture magazine and a business site. The daily wants a measured voice and a plain player tuned to its blue palette. The magazine wants a warmer voice and a player that lets its long features breathe. The business site wants speed, with an audio summary at the top of each article for readers in a hurry.
Under a single account, these three configurations coexist without stepping on each other. The ad team selling audio inventory across all three titles works from the same workspace. The developer who wired the plugin into each site has one set of credentials to manage. And the publisher gets one invoice, not three, with total consumption in plain view. That is what we mean by the payoff of audio for a brand-owned media: cost is steered at group level, quality is tuned at title level.
What multi-site does not do
In fairness, let us say what this mode does not claim to solve. It does not merge your analytics into a single misleading number: each site keeps its own listens, because an average completion rate across three different titles means nothing. It does not automatically carry a paid voice from one site to another if your plan does not include it. And it does not replace a genuine legal separation if your titles belong to distinct entities: it is a management tool, not an accounting arrangement.
For a group that wants to narrate several brands without diluting any of them, this is the right level of pooling: neither the scatter of several accounts, nor the uniformity of a single setup.
Bring your titles under one account
The free plan lets you start with one site and add the others when you are ready: try it now.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo