Launch intelligence is in early access. Become a design partner

SolutionsProduct marketing

Know what engineering shippedbefore you write a word.

Engineering ships, and you find out from the changelog. Shots turns each release into a cited launch brief your whole team can trust. You approve a plan, and the visuals and posts are built to both.

Get startedRequest a demo
Launch briefv2 · draft

Problem

Finance teams rebuild the same invoice every month.S1

What changed

Invoices repeat on a schedule you set once.S2brief

Open question

How many beta teams used it? No source says.

Answer
Campaign planv1 · approved

Teaser

XLinkedIn

Launch day

XProduct HuntEmailChangelog

Follow-up

LinkedInInstagram

A1 hero 16:9 · /invoices/recurring · desktop

A2 feature shot 1:1 · schedule modal

Launch brief

One launch brief per release,with every claim tied to a source.

Every claim cites the pull request, the changelog, or the release. Gaps come back to you as questions. Approve one version and every visual and post is built to it.

  • messaging · pillars

    Positioning, written down

    Messaging pillars, positioning against alternatives, and calls to action live in the launch brief, where the whole team can read them.
  • v3 approved · v4 draft

    Every version kept

    Every AI draft, teammate edit, and applied revision is a new version. You always know which one the posts were written to.
  • beforeAfter · limitations

    Honest by structure

    Limitations have their own section in the launch brief, so the launch can't promise what the release doesn't do.

Team

Writers, approvers, and publisherseach get their own role.

Separate the people who write from the people who sign off and the people who press publish. Each role can read everything and change only its part.

Team roles
RoleWhoEdit draftsApproveSchedule
creatorProduct marketers who shape the posts
approverThe lead who signs off
publisherWhoever owns the calendar
viewerSales, support, and leadership

Quality

Your brand kit applies to every visual,and each review improves the next launch.

Nobody picks brand colors for each visual, so the brand stays consistent. Every note you leave teaches the next launch.

01

Brand applied automatically

The brand kit is applied to every visual the AI makes: the gradient, the accent, the text color, and the nearest font.
See the creative engine
Brand kit · Acmev3
HeadingGeist 500
Applied to4 visuals

02

Feedback that sticks

Approved posts teach it what good looks like. Posts you send back with a note teach it what to avoid. Revisions you apply teach it what you keep asking for.
How it learns
Review6 posts
  • X · TeaserREADY_FOR_REVIEW
  • LinkedIn · TeaserREADY_FOR_REVIEW
  • X · Launch dayREADY_FOR_REVIEW
  • Product Hunt · Launch dayREADY_FOR_REVIEW

- every cycle sends itself.

+ every cycle bills on time, by itself.

Approve all 6Apply revision

Questions

Anything else? Talk to us.

Can sales and support see the launch brief?
Yes. Give them the viewer role. They can read every launch brief, plan, and post, and change nothing.
Who approved what, and when?
Every decision is in the audit log with the teammate, the time, and how many posts it covered.
Does it replace our editorial calendar?
For launches, the plan and schedule cover it. A weekly calendar across launches is on the roadmap.

Related

Read how approval works,how a product launch is planned, and what Enterprise adds.

Invite your writers and approversand run your next launch in Shots.

Get startedRequest a demo