One URL, eleven teams
Every team adds their slice to the same canvas. The board is the meeting; cross-team status updates happen inline.
Use case · Launches
Run a launch from one canvas.
Zero status meetings.
Cross-functional launches turn into coordination tax fast. A single BookSlash board — brief, calendar, assets, dashboards, retro — replaces the slide deck, the Slack channel, and the weekly status call. Everyone on the same canvas, every team in sync.
The shape of the work
Three steps to a calmer launch.
Launches fail quietly between teams. The fix is not more meetings; it is one shared canvas where every team’s status updates inline.
- 1
Stand up the board
b/launch-q4. Brief at the top, calendar in the middle, kanban below, retro template at the bottom. Two hours of setup; the board is the meeting from there.
- 2
Every team adds their slice
Sales pins enablement decks. Marketing pins the channel calendar. Engineering pins deploy slugs. Comms pins the press list. Updates happen on the canvas, not in chat.
- 3
Retro on the same surface
Day-of metrics flow in via embedded charts. The retro template lives at the bottom of the board. Lessons are searchable for the next launch — same URL.
Launch board template
b/launch-q4 — the eight blocks that matter.
Most launch artefacts live as separate documents. This template puts them on one canvas, so the question "where is the [thing]?" stops happening.
b/launch-q4
8 nodes- Brief
Two-paragraph note at the top: audience, message, success metric. Pinned, not buried in a doc.
- Channel calendar
Timeline node — every channel, every send, every owner. Drag to re-sequence.
- Sprint kanban
Engineering tickets in flight. Click a card to advance the column. Live, not a screenshot.
- Asset embeds
Live Figma frames for the launch creative; Loom recordings for the keynote rehearsal.
- Press + influencer list
Table node with names, outlets, status. Owners check rows as outreach lands.
- Live metrics chart
Embedded chart from the analytics warehouse. Updates as launch day unfolds — no screenshots in Slack.
- Launch countdown
Timer node. The whole company sees the same number.
- Retro template
Three columns: keep, change, kill. Filled in the week after launch — same board, longer life.
Why this works
Six things a slide deck cannot do.
Live charts, not screenshots
Embed the warehouse dashboard directly. Launch-day metrics update in place — no "let me take a screenshot" Slack dance.
A shared countdown
A timer node visible to the whole company removes "is launch tomorrow or Friday?" The number is on the board.
Live Figma + Loom
Asset frames update automatically. Reviewers see the current creative, not last Tuesday’s screenshot.
A retro that ships
Same board, scrolled to the bottom. Lessons live where the work happened — searchable for the next launch.
Slug-fast handoff
Sales rep onboarding for the launch? Send b/launch-q4. Done in 90 seconds.
We ran our biggest launch out of one b/launch board. Sales, comms, and product stayed in sync without a single status meeting.
TS
Theo Saar-Lindgren
Head of Marketing · Cinder & Lake
Frequently asked
Questions, answered.
For internal coordination, yes. Most teams keep an external-facing deck for press and partners and pin a slug to it on the board (b/launch-deck). The board does the cross-functional work; the deck does the sales pitch.
Comments. Leaders drop questions on the relevant section as comments; the team responds inline. Decision logs and approvals stay attached to the artwork or section they are about, not to a Slack channel three days behind.
Yes. Boards inherit workspace roles (Owner, Admin, Member, Guest) and can be restricted further with per-board permissions. Guest links work for external partners (PR firm, retail partner) without burning a paid seat.
One board per launch, with a top-level dashboard board (b/launches) that links to all of them. Most marketing teams settle on this pattern after their second launch.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial