Use case
Building a course while everything else keeps running
Module recording, the workbook, launch emails, and social all point at one date. Put them in one grid, link what moves together, and drag launch week onto a calendar.
Last updated: 28 July 2026
A launch is not one task list
You record modules. You write the workbook. You draft a launch sequence. You post about it. Each of those runs on its own rhythm, and all of them point at one date. The course is also not the only thing you are doing — client work, your channel, and everything else keep their own deadlines that week.
Split across a doc, a task app, and a calendar, the dependencies live in your head. You find out the workbook is late on the morning the email that links to it was supposed to go out.
Start with the matrix
Projects run down one axis, channels across the other. Put the course on one row and the rest of your work on the rows beneath it, so you are looking at the launch and your client deadlines in the same grid.
Channels are the columns. YouTube, Instagram, Facebook, Pinterest, and Website are there by default. Email is not, so add it as a custom channel — that column holds the launch sequence. Free includes two custom channels, which is enough for email plus one more.
Every cell is one project meeting one channel. The course row under the email column is the whole sequence in one place, and the row across all columns is the launch.
Link the batches that move together
Module three does not ship alone. The recording, the workbook pages that go with it, the email that announces it, and the post that points at the email are one unit of work. Link them and they become a batch.
When the recording slips a week, the batch moves with it. The email stops being scheduled to announce something that does not exist yet, and you find out about the collision when you move the task rather than on the day.
Do this per module and the launch becomes a handful of batches instead of forty loose tasks you have to hold in order.
Schedule launch week
Drag a batch onto a day and it lands on the calendar next to the rest of that week — client calls included. Launch week stops being a countdown and becomes a set of days with a visible load.
If Wednesday is already full, move the batch to Thursday. Everything linked to it moves too, so the sequence stays in order without a manual pass over every date.
Three readings of the same launch
- Overview — the matrix, every project and channel at once. Use it when you want to see whether the course is crowding out the rest of the month.
- Flow — one project at a time: channel, then tasks, then links. Use it when you are working the course and nothing else.
- Graph — a connection map of projects, channels, tasks, and their links. Use it to check that every module actually has an email and a post attached.
What you get on Free
Two projects, the default channels plus two custom ones, calendar scheduling, and task linking. That is enough to run one course launch alongside one other pursuit, on one device.
Free has no cloud sync and no calendar export. Your plan lives in the browser you built it in.
When Solo starts to matter
A launch usually outgrows two projects. Solo is $19/mo (₹499/mo incl. GST) or $180/yr and gives you unlimited projects and channels, so the course, the client work, and the next course can each be their own row. It adds cloud sync across devices, so the plan you make at your desk is on your laptop at a shoot, and .ics export, so launch week can land in the calendar you already live in.
There is a 14-day trial, a 14-day money-back guarantee, and you can cancel any time. Full plan details are on the pricing page.
What Polylane will not do for your launch
Studio ($39/mo) is the shared workspace for up to five people, and it is not available yet. If you are launching with an editor and a VA, Polylane today plans your side of it, not theirs. Studio is founding waitlist only.
Calendar sync to Google is one-way: Polylane pushes to Google, and nothing comes back. A meeting booked in Google will not appear here, so keep Google as the place you check for other people's time.
There is no mobile app, so scheduling happens at a desk. There is nothing to import from — no connections to your email tool, your course platform, or your task app — so the matrix is something you build rather than something you sync. And there are no AI features: Polylane does not write your launch emails or guess your dates.
Try it on the next module
The fastest test is one module. Put the course in the matrix, link a recording to its workbook page, its email, and its post, then drag the batch onto a day and move it once. If moving four things by moving one feels right, the rest of the launch works the same way.
Start free — no credit card required.