All posts

Positioning6 min read

The operator playbook: running many brands on one flat-rate scheduler

Why per-account pricing gets expensive when one person runs many brands, what Postcrow does instead, and what a flat rate works out to per brand.

Most social media schedulers price per social account or per seat. That model fits a team of marketers running a single brand. It scales poorly when a single person runs many brands: indie hackers, portfolio operators, holding companies, small studios.

Postcrow is designed for that profile. This article explains the design choices: why we chose flat-rate pricing, how the product reflects multi-project use from the ground up, and which workflows it's optimised for.

The pricing problem

Per-account pricing scales linearly with account count. For a team managing one brand, the cost is bounded and predictable. For an operator managing ten brands, the same pricing structure means ten times the cost, even though their support burden and usage pattern haven't scaled the same way.

Postcrow uses flat-rate pricing instead. $79/month for the Agency plan covers unlimited projects, unlimited social accounts, and unlimited scheduled posts. The marginal cost of an additional project in our system is small enough that we can absorb it without changing the price.

BrandsPostcrow AgencyPer brand / month
1$79$79
10$79$7.90
50$79$1.58
100$79$0.79

For comparison points, public pricing pages of Buffer, Hootsuite, and Later are easy to find. The point isn't that they are wrong for their market: they're built around different assumptions. The point is that a portfolio operator's usage doesn't fit those assumptions cleanly.

What the product reflects

Flat pricing is necessary but not sufficient. Running 50 projects in a tool that wasn't designed for it is its own kind of slow. Four product primitives matter:

1. Project switching

At 50 projects, a dropdown is the slowest part of the workflow. Postcrow has a Cmd+K command palette that fuzzy-finds any project in under a second. You can use it from any page in the app, including the keyboard shortcut equivalents on Linux and Windows.

2. Brand voice per project

With many brands, you can't remember each brand's tone when you draft a post. Postcrow lets each project store a trained brand voice, a paragraph distilled from 3 to 10 sample posts, that is added to any AI compose call for that project. The details are covered in Brand voice training.

3. Bulk operations

Some workflows scale better as batches than as single-post UIs. Postcrow ships a CSV importer (up to 1000 rows per import), project cloning (timezone + brand voice copied in one click), and bulk scheduling through the API. Bulk operations covers each in detail.

4. A terminal interface

Many portfolio operators are technical and spend their day in an editor or terminal. A Model Context Protocol server that exposes Postcrow to Claude Code and other MCP clients is written and tested, but its npm package is not published yet, so it cannot be installed today. Until it is, everything goes through the web app or the HTTP API.

What Postcrow is not

Postcrow is not built for large teams running a single brand. Team approval flows, role-based permissions, and internal review queues aren't in scope today. If your bottleneck is internal coordination on one brand, established tools serve that case well.

We focus on a different bottleneck: the moment one person tries to run more brands than the per-account economics of those tools allow.

How to start

Sign up, create one project per brand or clone an existing one, connect at least one social account, train each project's voice, and either compose manually or enable auto-recycle (Agency and Platform plans) so the queue stays alive without daily attention.

The 14-day trial is free and does not ask for a card. Agency is $79/month, flat.