Campaign Room.
Get the next launch over the line.

Bring the campaign brief to its reviewer

Campaign Room is for marketing coordinators assembling launch plans and reviewers deciding whether a brief is ready. Its supplied queue covers customer-story content, a product webinar, a partner email needing a revised call to action and an approved newsletter. Those different examples help a team agree what a decision note should contain before adding a larger content calendar.

Every campaign has a title, campaign owner, budget amount, status and note explaining the proposed work. Review counts summarize the queue and status filtering narrows the list to the next set of decisions. Search by title or owner to locate a campaign. Opening a row exposes the editable fields and a short activity list that reflects the review actions taken in this preview.

Try revising a partner email plan

Open the partner-email record and read the request to update its call to action. Rewrite the decision note to describe the proposed change, save it back for review and inspect the resulting activity. Approve the plan after checking the revised explanation. Add another campaign with its own budget and verify that the waiting-for-review count updates when it is saved.

All people and records are fictional. The example stores edits in your current browser and simulates campaign review; it does not publish content, schedule an email or spend advertising budget. Reset restores the starting briefs. A real marketing workspace needs shared persistence and authorization that separates proposing, reviewing and executing a campaign.

Keep campaign context and publication rights distinct

An adapted version could read a reviewed list of campaign identifiers, approved asset references or aggregated performance measures from company sources. Connect only the context the reviewer needs. Audience contact lists and advertising credentials are broader permissions than the ability to read a campaign budget, and should not arrive in a browser just because a brief mentions an email channel.

Ask marketing to define brand review, budget review and the person responsible for publication. Add the required business checks to the application and preserve the decision associated with each version of a brief. SpringRoll's deployment workflow reviews the application release separately. Test a coordinator, a reviewer and an unrelated employee before making the tool part of a launch process.

Three ways to extend the source in Claude Code

Use these prompts to make the starter match your campaign planning process. Keep fictional campaigns during development and check each new permission before connecting an external marketing service.

1. Add launch date, channel and asset-reference fields to campaign briefs. Validate dates and make the reviewer see which material changed since the previous review.
2. Replace local edits with shared campaign records and enforce separate coordinator and reviewer roles on the server. Require another review after a material budget change.
3. Read approved campaign performance totals through SpringRoll without exposing recipient-level data. Handle a denied or revoked data grant without losing the draft brief.

Take the next step

Use the first adapted campaign to agree who signs off the brief and who is accountable for the eventual publication.

Start with Campaign Room

Download the source