How marketing teams use Plane

Marketing work is rarely self-contained. Product changes a feature detail, Sales needs another deck, and the announcement blog takes longer than expected to clear review, while the video, email, and social posts still have to go out on schedule.

Keeping each deliverable tied to the messaging, decisions, and teams it depends on is the real challenge, and Plane keeps those connections next to the work itself. A launch is where most of them meet at once.

Plan and run product launches

A product launch brings content, creative, and campaign work together against a date that depends on Product and Engineering. In Plane, the brief lives in Wiki, the deliverables sit in a Module, and the team can follow dependencies, approvals, and progress as the release approaches.

Create launch briefs in Wiki

The plan starts as a Wiki page: the positioning, the dates, the channels, the messaging approved for external use, and the deliverables the launch will produce. Wiki holds knowledge that outlives any single work item, so this page stays the reference the execution links back to rather than something copied into each item.

Organize campaign deliverables in Modules

The execution lives in a Module, which groups the launch's work items inside the project that owns them. Each deliverable takes the Work item type that fits it, Blog, Video, Creative, or Social. The type classifies the deliverable and gives it the properties worth capturing, such as a target keyword on a blog or an edit stage on a video.

The workflow, meaning the states a deliverable moves through, is configured separately and can differ by type, so a video and a blog post advance through states that match how each is produced. A label such as a region or sub-brand cuts across the types when the team wants to slice the launch that way.

Plan campaigns with Claude and ChatGPT

A launch brief can become a structured set of deliverables without creating every work item by hand. With Plane MCP connected, a PMM can ask Claude or ChatGPT to work from the approved brief and the existing project context, then build the campaign in Plane.

For a product launch, the request might cover a feature page, announcement blog, customer email, demo video, social assets, and sales enablement. The assistant reads the relevant context through Plane MCP, works out the deliverables and their order, and creates the work items in the marketing project. It can add descriptions, assign owners and dates when those are provided, and link dependencies, such as the email and social assets waiting on the announcement copy to clear review.

The work is created in Plane rather than captured in a chat transcript, so the PMM can review the scope, adjust owners and dates, and check the dependencies before the campaign begins. What Claude or ChatGPT can read and change depends on the permissions and MCP tools available to the connected account.

Track campaign blockers with Dependencies

Some of the work is ordered. Video production depends on the social assets being approved first, so the Video work item takes a Blocked by relation to the Social asset item. The relation shows on both items and records that the video cannot proceed until the social work completes. It does not change the video's state on its own; the owner moves the work once the social asset is done.

Keep feedback and approvals in work items

Feedback and sign-off happen on the work item through comments and state changes, so the decision and the reason for it stay with the deliverable. When the conversation moves to Slack, the Slack integration keeps the two in step: a message can create or update the item, and thread activity syncs back, so the record does not fracture across channels. For how that connection works, see Slack x Plane.

Handle unplanned marketing requests

Not every marketing request arrives through the campaign plan. Sales may need a customer deck, Product may ask for an updated screenshot, or someone on the team floats a new idea. Adding every request straight to the team's planned work makes it harder to protect existing commitments.

Review and prioritize requests in Intake

A custom Intake form gives requesters a consistent way to submit marketing work. For a sales deck, the form can capture the audience, use case, required format, deadline, and a link to approved messaging, using the relevant Work item type and properties.

The marketing lead reviews submissions in Intake before adding anything to the team's planned workload. They can weigh the deadline against existing commitments, ask for missing context in comments, and decide whether to accept the request, revisit it later, or decline it. The discussion and the decision stay with the request.

Move approved requests into projects

Once accepted, a request becomes a work item with an assigned owner and due date. The original brief and the clarification comments carry over, so the designer or writer starts with the context they need.

Handle creative production end to end

A creative request that clears Intake becomes a deliverable a designer owns. In Plane, the brief, design files, feedback, and approval decisions stay on its work item rather than scattering across chat threads and shared drives.

Manage creative briefs with work items

The accepted work item carries the format, channel, dimensions, and deadline in its properties. The description holds the requirements, with approved messaging and brand references linked through Pages.

The designer attaches the working asset or adds a link to the design file and moves the item through states such as In design, In review, Changes requested, and Approved. The current state makes it clear where production stands, while the work item keeps the original brief.

Track creative decisions and revisions in the Activity log

Consider a launch carousel submitted for review. The designer has prepared widescreen slides, but the brief specifies a square format. A reviewer flags the mismatch in a comment and points to the dimensions recorded on the work item.

The designer corrects the asset, attaches the revised export, and moves the item back for review. The Activity log records the updates to the work item, including its state changes, while comments and attachments hold the feedback and the revised files.

Manage content production and publishing

Editorial teams can set up a repeatable process in Plane, with consistent properties, review stages, and handoffs across articles.

Set up editorial workflows with Work item types

A Blog post Work item type carries the properties an editorial team reviews on every piece, target keyword, format, distribution channel, product area, and reviewer, and its workflow moves through states such as Briefing, Drafting, Editorial review, Ready to publish, and Published.

Assign content reviewers with Automations

An automation drives the handoff into review: when a piece enters editorial review, a property-update rule assigns the managing editor, using a state-change trigger and an assignee action. The editor opens the item, checks the linked draft, and flags a product statistic the draft states without a source. The comment stays on the work item, the writer adds the citation and moves it back for approval, and the exchange remains the record of why the number changed.

Generate campaign copy with Plane Agents

A product launch needs copy for announcement emails, social posts, newsletters, and other channels. Instead of drafting each separately, a marketer can assign a work item to a Plane Agent with access to the approved campaign brief and relevant project context.

With instructions or a Skill defining the brand voice, audience, and channel requirements, the agent generates the copy in a Plane Page and shares the Page link in a comment on the assigned work item. The marketer can then review the drafts, refine the messaging, verify product claims, and approve the copy before publishing.

For a reusable starting point, see Essential agents and skills.

Coordinate publishing with Calendar views

An announcement article usually ships with multi-channel distribution. Its social carousel, newsletter mention, and community post each have their own work items, owners, and publishing dates. When these assets depend on the article clearing editorial review, the team can mark them as Blocked by the article work item. If approval slips, the content lead can see which distribution items are waiting on it. A saved Calendar view shows the scheduled dates across channels, so the lead can decide what to move or hold. Plane records the dependencies and dates but does not reschedule the work.

Create visibility across marketing campaigns

The Module overview covers an individual launch. To review marketing execution across campaigns, Dashboards chart work item data from selected projects, and saved Views organize specific workstreams for regular check-ins.

Track campaign execution with Dashboards

A marketing Dashboard shows configurable charts, metrics, and tables built from work item data in the Growth, Content, Creative, and Product Marketing projects. Widgets can break deliverables down by state, compare work across assignees, and show due dates. Each widget can use its own filters and grouping to cover a different part of campaign execution.

Organize upcoming campaign work with Views

Views keep the filters, layout, and grouping for a recurring set of work. A saved View of upcoming marketing deliverables can use PQL, stateGroup IN openStates() AND dueDate BETWEEN (today(), daysFromNow(7)), to show open work due within the next seven days, grouped by assignee. Another View can focus on editorial reviews or launch assets without rebuilding the filters each time.

Dashboards chart work item metrics across projects, and Views give a consistent way to work through the deliverables underneath them. Both track delivery, not marketing outcomes such as attribution, conversions, or pipeline contribution.

Run your next marketing campaign in Plane

A deliverable rarely goes wrong on its own. What trips a campaign is a lot more such as the messaging that governs an asset, the review that signed it off, the scope decision that changed it, and the team it waits on. Plane keeps those connections on the work. A dependency shows on the work item, the approval sits in it too, and the revision a change calls for traces back to the assets and owners it touches. The team still does the work. Plane takes away the guessing about what the change reached.

Choose the campaign your team is planning next. Build the plan in Plane, assign its deliverables, and set the dependencies and reviews before work begins. Start planning your next campaign in Plane.