Running several Projects

What changes when a workspace holds more than one Project: billing, discounts, switching and usage.

A workspace can run many Projects on one subscription, each priced on its own.

The active Project#

Most of the workspace shows one Project at a time. The switcher at the top changes which one, and it changes what every page below it is about: posts, topics, settings, analytics and usage all follow the active Project.

Billing across Projects#

One subscription, one payment method, one invoice. Each Project contributes its own plan price as a line on that subscription.

Running several Projects earns a multi Project discount, and it is worked out per Project rather than across the subscription. Each Project takes the band its own position earns: the first pays full price, positions 2 to 4 take 10 percent off, 5 to 10 take 15 percent and 11 to 20 take 20 percent, each against that Project's own plan price.

Adding a Project therefore does not re-price the Projects you already run. The new one joins at the next free position and takes that position's band. Positions are recomputed oldest first, so nothing is grandfathered: if an earlier Project leaves, the ones behind it move up and their discounts change with them. See discounts for how this combines with promotion codes.

Usage is never shared#

There is no workspace wide post allowance to run down. Each Project has its own counters, sized by its own plan, and a workspace running one small Project and one large one has two separate allowances with no single pair of numbers that describes both.

The counters need not even share a cadence. A paid Project's counters reset with its billing period, while a Free Project holds a one-time lifetime grant that never resets.

Limits#

A workspace can hold up to a fixed ceiling of Projects. If you need more than that, the constraint is worth a conversation rather than a workaround: write to hello@blogged.dev.