Shipping in December: how to plan a launch around the holidays

Every year someone asks whether to hold a launch until January. The honest answer depends on exactly one thing: does your launch require another human to make a decision?

If your launch needs a decision-maker

Enterprise sales, partnerships, press coverage, hiring, fundraising: hold. Budget cycles close, inboxes fill, and your best email lands under three hundred others. Aim for the second week of January.

If your launch is self-serve

Ship it. Consumer and prosumer tools frequently see above-average December signups because people have unstructured time and a new-year mindset already forming. A quiet launch week is also a gentle load test.

The plan that works

• Freeze scope on the first of the month. Whatever is not code-complete by then ships in January.
• Deploy no later than the third week. Never ship a migration on the day everyone leaves.
• Set an explicit support window and say it publicly. "Replies within 48h until the 24th, then the 2nd."
• Write January's follow-up in December. The re-launch email to a rested audience is often more valuable than the launch itself.

For freelancers specifically

December is the best month of the year for pipeline work: write case studies, fix your own site, publish the posts you have been putting off, and send a short year-end note to every client from the last two years. That note reliably produces January work.

The mistake is not launching in December. The mistake is launching in December on a schedule that assumes everyone is at their desk.