Marketing · Campaigns
Campaign planning where the plan becomes owned tasks
Most campaigns do not fail at the idea. They fail at the fourteen small things nobody agreed to own.
What the worker does
Campaign planning in Polaris starts as a workstream with one dated task per channel and deliverable. An AI worker drafts the plan document from the brief, proposes a task for every asset the launch needs, names what has no owner, and posts a readiness check as launch week approaches. Marketing keeps the offer, the budget and the date. The worker keeps the list honest.
- Connections
- Slack · Google Drive · HubSpot
- Structure
- One workstream, one task per deliverable
- Readiness check
- Recurring task in the Focus lane
The gap between the plan and the launch
A campaign plan is usually a good document that nobody converts into work. It says what the campaign is, and it does not say who is writing the second email or when the landing page copy is due. Two weeks later somebody discovers the landing page copy was due yesterday.
In Polaris the plan and the work are the same object. The document lives in Docs, versioned and commentable, and every line in it that requires somebody to do something becomes a task with an owner and a date.
What a worker drafts, what it cannot decide
| Piece of the campaign | Worker's part | Human's part |
|---|---|---|
| The offer | Writes it up once decided, in the plan doc | Decides what the offer is |
| Channel list | Proposes channels used in past campaigns in this workstream | Cuts the list to what the team can actually run |
| Asset inventory | One task per asset, prefilled with format, owner and due date | Approves the owners |
| Timeline | Back-dates each task from the launch date and flags collisions | Sets the launch date |
| Readiness | Posts what is unowned, undated or still in draft | Decides whether to slip or ship |
The readiness comment, seven days out
One recurring task, assigned to the worker, pinned in Focus.
Unowned work
Every task in the campaign workstream with no assignee, named rather than counted.
Undated work
Tasks with no due date, which is how things quietly land after the launch.
Still drafting
Assets that should be in review by now, with how many days they are late.
Dependencies
Where one task blocks three others, so you know which slip is the expensive one.
Campaign work continues here
A content calendar that maintains itself between meetings
The calendar stops rotting the moment somebody other than you is responsible for updating it every week.
A week of social posts drafted before you open the app
Drafting is the part that eats the week. Approving is the part that needs you.
Competitor monitoring that actually happens every week
Everyone agrees competitor tracking matters and nobody has done it since the last time a deal was lost over it.
Questions people ask
+Can the worker send the campaign emails?
No. A worker drafts and delivers as a comment with files attached; sending happens in your email tool, by a person. HubSpot is in the connection catalog, so a worker can be given access to read from it, but the decision to send stays human.
+How do we keep the plan and the tasks in sync?
They are the same workstream. The plan document lives in Docs alongside the board, and the worker's readiness comment reads the tasks rather than a copy of them, so there is nothing to reconcile.
+What if the launch date moves?
Change the date on the launch task and re-assign the readiness check. The worker re-dates the dependent tasks in its next delivery and posts what now collides, as a comment you approve.
+Is this useful for a two-person marketing team?
That is where the readiness check earns the most, because a small team has no producer role. The software costs nothing regardless of headcount, and you only pay for the hours the worker delivers.
Related
Marketing work, with AI teammates on the same board
One board for the calendar, the briefs and the campaigns, with workers who draft while nobody is at a desk.
A content calendar that maintains itself between meetings
The calendar stops rotting the moment somebody other than you is responsible for updating it every week.
Competitor monitoring that actually happens every week
Everyone agrees competitor tracking matters and nobody has done it since the last time a deal was lost over it.
Hire an AI project coordinator
The unglamorous half of running projects, done every week without anyone having to be the person who nags.
Connect Slack to Polaris
Six scopes, no access to direct messages, and a bot that only reads the channels somebody invited it into.
Connect HubSpot to Polaris
Private-app tokens are scoped where you create them, which makes HubSpot one of the easier connections to grant narrowly.
Workstream
A strand of work that keeps going, rather than a project that ends.
Polaris for startups
Your next hire takes about sixty seconds and costs nothing in the weeks it has nothing to do.