Most marketing software is built around one of two assumptions: either campaigns are simple enough to manage with a list of tasks, or they're complex enough to need a full marketing automation platform. There's very little built for the space in between: teams running sophisticated, multi-channel campaigns that need to be produced, reviewed, and approved before they go anywhere near an email service provider.
That gap (the job of campaign approval software, and of the campaign journey design that comes before it) is what LaunchSign is built for.
The problem we started with
We spent time talking to marketing teams at agencies and in-house marketing departments.
The pain points were remarkably consistent:
Brief-to-launch is opaque. Once a campaign brief is written, there's no reliable way to see where everything stands at a glance. Status lives in heads, inboxes, and Slack threads. You find out something is blocked when the deadline is tomorrow, not three days ago when it first became an issue.
Approvals are document archaeology. When a client asks "what did we agree on for the email copy?", the answer involves searching email threads, finding the right PDF version, and hoping someone took notes. This takes time and produces uncertainty.
Channel dependencies are invisible. The landing page needs to be approved before the paid social campaign can finalize its call-to-action. The email can't be seeded until HTML production is complete. These dependencies exist in everyone's heads but nowhere in any system.
Client review creates coordination overhead. Sending content for client review (managing the sharing, tracking who reviewed what, following up on feedback, capturing the approval) takes a disproportionate amount of account manager time.
What Journey Builder does
Journey Builder is a visual canvas where you map out the full structure of a campaign (every piece of content, every channel, every dependency) before production starts.
Each node on the canvas represents a piece of content: an email, a landing page, a social post, a set of display ads. Connecting nodes shows relationships and dependencies. The canvas becomes the single source of truth for what the campaign contains and how the pieces fit together. If you would rather not start from a blank canvas, our journey blueprint library maps common campaigns (welcome, win-back, post-purchase and more) as blueprints you can adapt to your own ESP.
Inside each node is where production actually happens:
- Brief tab: the content brief for that specific piece, broken down by phase: creative, copy, production, QA
- Pipeline tab: phase-by-phase status tracking, with assignment and status per phase
- Assets tab: uploaded files with version history, organized by production phase
- Approval tab: formal approval workflow with guest links for client review (see our guide to defensible client approvals for what this needs to capture)
When you share a node with a client for review, they get a focused view of exactly what they need to see: the relevant version of the content, a simple interface for feedback and approval, no internal status information, no account creation required. Their approval is captured in context, versioned, and timestamped.
What we launched in v1
The initial release of LaunchSign covers the core production and approval workflow:
- Journey canvas with custom node types (email, landing page, paid social, SMS, push, custom)
- Full side panel per node: Brief, Pipeline, Assets, Comments, Approvals
- Guest link generation with expiration and revocation
- Multi-approver support per node: track "2 of 3 approvers have signed off"
- Campaign-level sign-off when all content nodes reach "done" status
- Workspace-level branding on guest views (logo, colors)
We also shipped canvas annotations in v1: free-form notes that live directly on the canvas, visible to the internal team by default, with the option to share specific annotations with guests. Useful for briefing context, decisions that didn't make it into the formal brief, or flagging open questions during production.
What's next
We have a full roadmap of features being developed, including:
- Visual proofing: pin-based feedback directly on creative assets (images, PDFs, rendered HTML)
- Email QA integration: HTML rendering tests across email clients, spam score, seed testing
- Translation management: per-node language variants with separate approval chains
- Journey versioning: save named snapshots of the full campaign structure, with comparison and rollback
- Segmentation tracking: audience segment status linked to campaign sign-off
For the fuller picture of how a campaign actually moves through the canvas, from brief to client sign-off, see managing a campaign from brief to sign-off.
We're currently in early access and working closely with a small group of agencies and in-house teams. If you're running complex campaigns and the production process is a bottleneck, we'd like to talk. We're particularly interested in hearing from teams running more than three simultaneous campaigns with external client approval requirements.
FAQ
Is Journey Builder available now?
Yes, it shipped in the LaunchSign v1 release and is in early access. It covers the journey canvas, per-node production, guest review, and campaign-level sign-off.
Does LaunchSign send my campaigns?
No. It sits between the brief and your ESP or marketing automation platform: production, review, and sign-off. Your existing platform still sends the campaign.
What channels does the canvas cover?
Email, landing pages, paid social, SMS, push, and custom node types, with the dependencies between them drawn on the canvas.
Do clients need an account to review?
No. Guest links give each reviewer a focused, login-free view of the relevant version, and their approval is captured in context, versioned and timestamped.
LaunchSign is a campaign production platform, not an ESP, not a MAP. It sits between brief and deployment, handling production, review, and sign-off. If you're looking to send campaigns, it works alongside your existing email or automation tools.
