Drip scheduling for creators who don't like cron

Cron syntax is one of those things that seems simple until you need to express 'every other Tuesday except in August'. Content drip scheduling has the same complexity problem, but your users are course creators and musicians — not sysadmins.

The schedule types that cover 95% of use cases

After analyzing how our first 500 merchants actually used drip scheduling, we found four patterns that covered nearly all real-world needs. Everything else was edge cases that merchants eventually simplified away.

1. Fixed interval — release a piece every N days from subscription start
2. Calendar day — release on a specific day of the week or month
3. Manual batch — curator releases a set of content at a specific date
4. Milestone — unlock content after subscriber reaches a threshold (30 days active, 3 orders, etc.)

Fixed interval is simpler than you think

The most popular approach is fixed interval starting from subscription date. Subscribe on the 14th, get Day 1 content immediately, Day 2 content the next day (or week, or month — depending on cadence), and so on. This is the Netflix model: your access level is a function of how long you've been a subscriber.

The implementation challenge with fixed interval is handling subscription pauses, plan changes, and refunds. We treat all of these as 'subscription age adjustments' — pausing for 7 days simply adds 7 days to every future release date.

Calendar day releases for cohort content

Some content works better when all subscribers get it at the same time — a live cohort course, a weekly newsletter with time-sensitive market commentary, a monthly photo pack. For this, calendar day scheduling is the right tool.

The tricky part here is what happens to subscribers who join mid-cycle. We default to giving them immediate access to the current period's content plus all past content. You can override this in settings to gate past content for new subscribers.

Setting it up

In Content Vault, drip scheduling is configured per subscription product, not per content item. You define the schedule once, then tag content items with the release slot they belong to. This lets you update the content library without touching the schedule logic.

“The best drip schedule is the one your subscribers barely notice because the content just shows up when they expect it.”