An agency producing a nine-message lifecycle programme for a client has a coordination problem that neither of the obvious tools models. Most marketing software assumes campaigns are either simple enough for a list of tasks or complex enough for a full marketing automation platform. There is very little built for the space in between: multi-channel campaigns that have to be produced, proofed with the client, and approved before they go anywhere near the platform that sends them.
That gap starts with campaign journey design, runs through campaign production management, and ends in client proofing and campaign approval. It is what LaunchSign is built for.
The problem we started with
We spent time talking to account managers, campaign producers and CRM leads at marketing agencies.
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 work to the client (managing the sharing, tracking who reviewed what, chasing feedback, and then separately getting somebody to actually decide) takes a disproportionate amount of account manager time. Those last two are different jobs: proofing collects the changes, approval records the decision.
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 whichever platform the client sends from.
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 the canvas connects to
The canvas is the plan. What makes it useful is that the plan and the work are the same object, so each node carries its production stage, the client's comments on the version they saw, and the decision recorded against it.
Pin-based feedback on the work itself and inbox previews across 100+ email environments both ship today, which means the two things a client campaign most often gets stuck on, "what does the client want changed" and "does this render", happen on the canvas rather than in an attachment.
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.
If you are running complex client campaigns and production is the bottleneck, we would like to talk. We are particularly interested in hearing from agencies running more than three simultaneous client campaigns with external approval requirements.
FAQ
Is Journey Builder available now?
Yes. It covers the journey canvas, per-node production, client review by link, and campaign-level sign-off.
Does LaunchSign send the campaigns?
No. It sits between the brief and the platform the client already uses to build and send campaigns: production, proofing, and sign-off. That platform still sends the campaign, and LaunchSign does not connect to it.
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 campaign production, client proofing and approval software for marketing agencies. It is not a sending platform and not a marketing automation platform. It sits between brief and deployment, and the client's own email or automation tools still send the campaign.
