What it does

Every part of the brief, automated.

SendBriefs is six things, working together. The brief editor, branding, approvals, schedules, integrations, and engagement analytics. Each one does its job; together they make reporting a system instead of a Thursday-night chore.

What it looks like

The brief is the product. Everything else is plumbing.

Below is a stylized preview of a real SendBriefs delivery — branded for the client, packed with live data, approved in two clicks, opened on a Monday morning.

Reserve my spot
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg read
Approved · Apr 30, 14:32 UTC
v7 · audit log

The six

All six features, at a glance.

Tap any tile to jump to its deep dive below.

01Editor

Block-based brief editor

Build the brief once with live data blocks pulled from your stack. No copy-paste from spreadsheets, no stale screenshots.

02Branding

Per-client white-label

Each client sees their logo, their typography, their colors, on their domain. Your brand stays invisible unless they ask for it.

03Approvals

Two-click sign-off + audit log

Private review link, inline comments, structured change requests. Every action timestamped. Sign-off becomes data, not email.

06Engagement

Brief analytics

Who opened, when, how long, which sections. Bring the data back into your next brief's narrative.

Every feature exists to remove one thing your team is currently doing manually. If we can’t point at the manual step we replace, we shouldn’t ship the feature.

01 / Editor

Block-based brief editor

Build the brief once with live data blocks pulled from your stack. No copy-paste from spreadsheets, no stale screenshots.

  • Live data tokens — type {{revenue.mom}} and the number renders fresh every period.
  • Narrative blocks, data blocks, and image blocks composable into any layout.
  • Templates per client, per cadence, or per practice area — inherit and override.
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Block-based editor + live data tokens
Sends 1st of every month3 inline comments68% opened · 4m avg read
Approved · Apr 30, 14:32 UTC
v7 · audit log

02 / Branding

Per-client white-label

Each client sees their logo, their typography, their colors, on their domain. Your brand stays invisible unless they ask for it.

  • Custom subdomain per client (briefs.theirdomain.com via DNS).
  • Theme tokens — color palette, fonts, header marks — set once, applied everywhere.
  • Per-section branding on Enterprise (practice-area templates for big agencies).
Northway · Q2 brief
April 2026Per-client branding

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg read
Approved · Apr 30, 14:32 UTC
v7 · audit log

03 / Approvals

Two-click sign-off + audit log

Private review link, inline comments, structured change requests. Every action timestamped. Sign-off becomes data, not email.

  • Inline comments anchored to specific blocks — no email-tag.
  • Structured "request change" flow with assignee + due-date.
  • Immutable audit log — every approval, comment, and send recorded with timestamp + IP.
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg read
Approved · Apr 30, 14:32 UTC
v7 · audit logTwo-click sign-off + audit log

04 / Schedules

Triggered + scheduled delivery

Send weekly, monthly, quarterly, or on data-change. Time-based or event-based. You set the rule once.

  • Cron-style schedules: "1st of month, 9am client tz" or "every other Friday".
  • Event triggers: send when revenue crosses a threshold or a campaign ends.
  • Pause + resume per client, per template — never accidentally send during an MSA dispute.
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg readScheduled delivery
Approved · Apr 30, 14:32 UTC
v7 · audit log

05 / Integrations

Connect what you already use

HubSpot, Stripe, GA4, GSC, Linear, Meta Ads, Google Ads. Plus webhook for anything else.

  • OAuth where available, scoped API keys where not. No password-storage anti-patterns.
  • Cached at the workspace level — one fetch covers all briefs that reference the same source.
  • Webhook fallback accepts any JSON payload — Zapier, Make, custom scripts, all work.
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

Live data from your stack

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg read
Approved · Apr 30, 14:32 UTC
v7 · audit log

06 / Engagement

Brief analytics

Who opened, when, how long, which sections. Bring the data back into your next brief's narrative.

  • Per-brief open rate, time-on-page, scroll depth, click-throughs.
  • Section-level engagement — see which blocks actually got read.
  • Aggregate trends per client — Q2 engagement was 38% better than Q1, here's why.
Northway · Q2 brief
April 2026

Revenue

$ —

↑ 18.4%

Retention

$ —

↑ 4.2pp

CAC

$ —

↓ 11%

What we did this month

Plan for May

Sends 1st of every month3 inline comments68% opened · 4m avg readBrief engagement analytics
Approved · Apr 30, 14:32 UTC
v7 · audit log