The lane map
One document, built before any post is drafted, that assigns every account a topic territory and a point of view. It is the single artifact that prevents round-robin distribution.
What a lane is
A lane has three parts, and all three are required:
Territory. The subject matter this account covers. Narrow enough that a reader can state it after seeing three posts.
Point of view. The position this person holds inside that territory. Two people can both cover pricing; one thinks usage-based billing is inevitable and the other thinks it destroys forecastability. That disagreement is the asset.
Standing. Why this person specifically can say it. Their role, their scars, the thing they shipped. A lane without standing produces posts that anyone could have written, which is the failure the fleet exists to avoid.
Territory alone is not a lane. Two accounts assigned "demand gen" and "content" will converge within a month, because the territories overlap and nothing distinguishes the takes.
Building it
Inventory the people. Real role, tenure, what they actually do in a week, what they argue about internally. Internal arguments are the richest source of points of view, because they are positions the person already holds and can defend.
Draw territories from the work, not the market map. Assigning lanes by keyword coverage produces accounts writing outside their competence, and readers detect it immediately. Start from what each person genuinely does, then check the coverage gaps.
Force the disagreements. Where two lanes touch, name the tension explicitly. A fleet where the VP Sales and the Head of Product publicly disagree about discounting is more credible than one where every account agrees, and it gives both accounts recurring material.
Mark the deliberate overlaps. Launch weeks, a shared customer story, a company milestone. These are scheduled, named, and given a per-account angle in advance. Unplanned overlap is the failure mode; planned overlap is a campaign.
Record the exclusions. What each account does not post about, including topics that belong to someone else's lane. Exclusions do more work than inclusions, because the pressure in a fleet is always toward everyone covering the hot topic.
Worked example: a five-account fleet
| Account | Territory | Point of view | Standing |
|---|---|---|---|
| Founder | Category and market direction | The category is consolidating faster than analysts think | Runs the roadmap, talks to acquirers |
| VP Sales | Enterprise deal mechanics | Discounting is a symptom of weak qualification | Closed the last 40 enterprise deals |
| Head of Product | Build tradeoffs and roadmap | Most feature requests are workflow problems | Owns what ships and what does not |
| Head of Demand | Channel economics | Paid social is mispriced for B2B right now | Owns the budget and the CAC number |
| Senior CSM | Post-sale reality | Churn is decided in week two, not month eleven | Sits with customers daily |
Where they touch, on purpose: the VP Sales and Head of Demand disagree publicly about lead quality. The Founder and Head of Product both cover roadmap during launch weeks, from strategy and from tradeoffs.
Where they must not touch: only the Senior CSM posts customer stories in the CSM's own accounts. Only the Head of Demand posts channel numbers.
Review cadence
Revisit quarterly, and immediately when someone changes role. A lane tied to a job the person no longer does produces posts with no standing behind them, and standing is the part readers actually respond to.
When two accounts start drifting into the same territory, the fix is a lane adjustment, not a content note. Content notes decay within two cycles.