Building a course while everything else keeps running

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 — project 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.

Projects are columns and channels are rows. Put the course in one column and the rest of your work in the columns beside it, so you are looking at the launch and your project deadlines in the same grid.

Channels are the rows. YouTube, Instagram, Facebook, Pinterest, and Website are there by default. Email is not, so add it as a custom channel — that row 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 column at the email row holds the whole sequence, and reading down the course column shows the launch across all channels.

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.

Drag a batch onto a day and it lands on the calendar next to the rest of that week — project 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.

• 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.
• Timeline — upcoming work across every project, day by day. Open the course to read its agenda and find work that still needs a slot.
• 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.

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.

A launch usually outgrows two projects. Solo is $180/yr, paid annually; monthly billing in India is ₹499/mo incl. GST. You get unlimited projects and channels, so the course, the project work, and the next course can each be their own column. 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.

If you are launching with an editor and a VA, that is Studio ($120/seat/yr, paid annually) — one shared matrix and calendar, from 2 seats up to 20, priced and sold per seat on the pricing page. Solo plans your own side of the launch only; it has no shared workspace.

Calendar sync is not two-way. Once your Google Calendar or Outlook is connected, a meeting booked there shows here as busy time, and on a paid plan the blocks you schedule can be sent to your calendar, but changes made to them there do not come back.

There is no native app yet; Polylane runs in the browser and installs to your home screen. There are no connections to your email tool, your course platform, or your task app — work comes in by hand or as a CSV import — so the matrix is something you build rather than something you sync. And there is no AI of our own: Brain dump turns pasted notes into tasks with your own Claude, OpenAI or Gemini key, but Polylane does not write your launch emails or guess your dates.

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.