Launch intelligence is in early access. Become a design partner
NewLaunch intelligence

Turn every releaseinto a launch.

Shots reads what you shipped, writes a cited launch brief, designs on-brand visuals from your real product, and drafts posts for every channel. Nothing goes out until you approve it.

Acme · Recurring invoicesexample launch
  1. Release

    Recurring invoices · PR #452

    Trigger
  2. Launch brief

    14 of 14 claims cited

    AI
  3. Campaign plan

    3 angles · 6 channels

    AI
  4. Visuals

    4 on-brand visuals · checks passed

    AI
  5. Posts

    X, LinkedIn, Instagram, Product Hunt, changelog, email

    AI
  6. Review

    Approve all 6 posts in one click

    Human
  7. Schedule

    Published once, with confirmation

    Scheduler

Takes releases from GitHub and GitLab. Drafts posts for the channels your users read.

  • GitHub
  • GitLab
  • X
  • LinkedIn
  • Instagram
  • Email

You ship every week. The launch post goes out when someone finds a free afternoon. Shots turns the release you already wrote into the launch you never had time to make.

sections in every launch brief
11
sections in every launch brief
channels drafted from one release
6
channels drafted from one release
posts published without a teammate's approval
0
posts published without a teammate's approval

The gap

Your release shipped.Most of your users haven't heard about it.

The feature is live, but the changelog is a commit message. The screenshot sits in Slack, and the post is a draft nobody approved. Work your users never hear about can't win you customers.

Every release, by hand

  • Crop the screenshot, again
  • Hunt for the brand hex code
  • Write five versions of one post
  • Paste each into a different tool
  • Chase a teammate for sign-off
  • Hope nothing claims what the product cannot do

Every release, with Shots

  • Describe the release once, or let GitHub send it
  • Check a launch brief where every claim cites a source
  • Approve a plan for every channel
  • Review real screenshots, framed on brand
  • Approve six posts in one click
  • Publish on schedule, with confirmation

Workflow

From release to scheduled postsin six steps you can check.

Shots works the way a good team would: understand the change, agree on a plan, make the visuals, check the work, then publish. You approve each stage.

  1. New releaseAcme Billing

    Release title

    Recurring invoices

    Why it matters

    Bill repeat customers without rebuilding the invoice.

    Source links

    github.com/acme/billing/pull/452

    acme.com/changelog/recurring-invoices

    github · release.published201 · signature ok

    01

    Start from what you shipped

    Give the release a title, a reason it matters, and up to twenty source links: the pull request, the changelog, the docs. Or let a signed GitHub, GitLab, or custom webhook send every release on its own.

  2. 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

    02

    Check the launch brief

    Launch intelligence writes a launch brief with 11 sections, from problem and audience to proof and limitations. Every claim cites your release or a source. A claim with no source is removed and becomes a question for you.

  3. 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

    03

    Approve the plan first

    Each channel gets a role and a cadence, and each angle maps to a messaging pillar. Every visual names the screen to capture, the device, and the focus. The timeline runs teaser, launch day, then follow-up.

  4. Asset boardBrand kit · Acme v3

    Invoices that send themselves

    Monthly
    Quarterly
    Monthly
    Yearly
    LegibleOn brandMatches brief

    04

    Get visuals from your real product

    The AI captures your product pages, frames them in the editor, and applies your brand kit. Each visual is checked for legibility, brand, and fit with the launch brief before it moves on.

  5. X · Launch day241 / 280
    Stop rebuilding the same invoice every month. Recurring invoices are live in Acme: set the schedule once and every cycle sends itself.
    capabilities.0whatChanged.1
    Within limitNo hypeKnown links

    05

    Get posts that cite their claims

    Posts written for X, LinkedIn, Instagram, Product Hunt, your changelog, and email. Each post lists the claims from the launch brief it relies on. A post that runs long, uses hype words, or links somewhere unknown fails the copy checks and is rewritten.

  6. 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

    06

    Approve in one click, or ask for changes

    Approve all six posts at once, or pick three. Ask for a revision on a post, a visual, the plan, or a section of the launch brief. You get a diff that shows what else it would update. Nothing changes until you apply it, and each decision teaches the next launch your taste.

Creative engine

Visuals made from your real productthat you can edit in the Shots editor.

Every visual the AI makes opens in the editor as layers. Move anything by hand and save it back to the workspace.

Browser frameSafari · dark

Invoices that send themselves

Monthly
Quarterly
Monthly
Yearly

Real screens, framed

Safari and Chrome mockups, Arc, macOS, and Windows frames, device shells, and 3D perspective. Shots captures your live product to fill them.

Brand kit · Acmev3
HeadingGeist 500
Applied to4 visuals

Your brand, applied

Every visual uses your kit: the background gradient, the accent, the text color, and the nearest font. Nobody picks a hex code twice.

Timeline00:08
MP4WebMGIF

Motion when it matters

43 animation presets on a keyframe timeline, exported as MP4, WebM, or GIF in the browser.

  • 250+ backgrounds
  • Export up to 5x
  • Annotations and blur
  • App Store screenshots
  • Templates with your media
  • Apache 2.0 licensed

Approval

Nothing publishesuntil a teammate approves it.

Approval is enforced on the server, so the same rules apply in the browser, the API, and the AI. An API key can create a release. It cannot approve a post.

Every decision is on the record. The audit log saves who approved what together with the change itself.

owner
Billing, SSO, roles, everything
admin
Teammates, brand, channels, releases
creator
Create releases, edit drafts, submit
approver
Approve, reject, request changes
publisher
Schedule and cancel approved posts
viewer
Read everything, change nothing
The AI suggests what to do. Shots decides how it runs safely.
Our principles

Publishing

Each approved post goes out once,and the network confirms it.

When a post is due, Shots checks its approval, visual, workspace, and destination again. It counts as published only when the network confirms it. If delivery is uncertain, a teammate decides what happens next.

  • Scheduled

    X

  • Scheduled

    LinkedIn

  • Scheduled

    Instagram

  • Sent

    Email

  • Drafted

    Product Hunt

  • Drafted

    Changelog

Delivery logTemporal
  • post_8f2aSCHEDULED → PROCESSING → PUBLISHED
  • post_91c4retry 429 → PUBLISHED, once
  • post_a07eUNKNOWN_DELIVERY → held for a teammate

Channel connections are set up with you during early access. Release emails go only to subscribers who consented, with one-click unsubscribe and exactly one delivery per address.

Guardrails

Release notes and web pages can't steer the AI.Text that reads like orders is flagged for you.

Release notes, pull requests, and web pages can hide instructions aimed at an AI. Shots cleans and labels every source before the AI reads it, and checks every output before it is saved.

  • <source id="S2" trust="untrusted">

    Prompt-injection defense

    Scripts, hidden text, and zero-width characters are stripped. Text that reads like orders to an AI is flagged and shown to the reviewer.

  • redirect hop → resolve → public? yes

    Public pages only

    Source links can reach public web addresses only. Every address and redirect is checked, and every response is capped in size and time.

  • proofPoints.2 → openQuestions.0

    Citations enforced

    A claim that cites nothing, or a source that does not exist, is removed and turned into an open question.

  • x: 291 > 280 · rewrite

    Copy checks

    A post fails if it runs over the channel limit or uses hype words, your banned terms, unknown links, or uncited claims. The AI gets the reason and fixes the post.

  • tools: [] · workspace: session

    Readers can't act

    Steps that read sources can't take actions. Your login decides the workspace, and nothing the AI writes or a page says can change it.

  • launch.spec · model · tokens

    Metered and audited

    Each AI call is charged credits at cost, rate-limited per workspace, and logged with the model and usage.

Developers

Send a release from your pipeline.Retries are safe with an idempotency key.

Post a release from CI or a deploy script, or point a signed webhook at Shots. The release waits in your workspace, ready to become a launch.

curl https://shots.playbookmedia.io/api/v1/releases \
  -H "x-api-key: $SCREENSHOT_STUDIO_API_KEY" \
  -H "Idempotency-Key: release-v2.4.0" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Recurring invoices",
    "benefitStatement": "Bill repeat customers without rebuilding the invoice.",
    "sourceUrls": [
      "https://github.com/acme/billing/pull/452",
      "https://acme.com/changelog/recurring-invoices"
    ]
  }'
201 Created
{
  "created": true,
  "release": { "id": "cm…", "status": "DRAFT", "title": "Recurring invoices" }
}

Security

SSO, six roles, and an append-only audit log,ready for your security review.

Every request goes through the same permission checks. Each control below is documented in the open-source repository, down to the database role.

  • SSO and SCIM

    SAML and OIDC single sign-on, plus SCIM user provisioning and deprovisioning.

  • Six fixed roles

    Owner, admin, creator, approver, publisher, viewer. Least privilege by default.

  • Append-only audit log

    The app can add and read audit rows but cannot edit or delete them. IPs are hashed.

  • Audit log export

    Signed CloudEvents to your security log tool (SIEM), with presets for Splunk and Datadog.

  • Retention and legal hold

    Ninety days by default. Longer retention and legal hold on Enterprise.

  • Private storage

    Files are kept separate per workspace. Signed links expire in two minutes. Uploads can't be overwritten.

  • Two-factor

    TOTP, required to connect social channels and to configure SSO.

  • Workspace isolation

    Your login decides which workspace you see. IDs from another workspace return 404, and a test with two workspaces proves it.

  • Self-hosting

    Docker images and a Helm chart in the open-source repository.

Roadmap

Today you send Shots a release.Next, paste a URL and get a first week of posts.

We built the manual tools first, then step-by-step workflows, then the AI. More automation comes last, and only as far as your approval rules allow.

  1. ShippedLaunch intelligenceRelease, cited launch brief, plan, visuals and posts, review and revise.
  2. ShippedWorkspace and assetsSave visuals to the workspace, reopen them in the editor, and save again.
  3. ShippedRelease intake APIREST, scoped keys, idempotency, and signed GitHub and GitLab webhooks.
  4. ShippedScreenshots after every deployA successful production deploy on GitHub captures fresh screenshots of your product pages.
  5. NextPaste a URL, get a week of postsA product profile to review in seconds, then a first week of posts in minutes.
  6. PlannedMerged PR to suggested launchA pull request worth announcing becomes a suggested launch for you to review.
  7. PlannedDemo videosShort, captioned demos rendered from captured product flows.
  8. PlannedThe weekly planEvery Monday, one plan for the week that you approve in one step.
  9. PlannedCopilot and AutopilotSuggestions first. Later, automatic publishing within approval rules you switch on.

Pricing

Three plans.Pro is $199 a month for teams that ship every week.

Every plan includes the editor, release intake, and the API. Higher plans raise every limit, and Enterprise adds the controls a security review asks for.

Pro

Popular

For teams that ship every week

$199

per month, or $169 billed annually

Seats
5
Social channels
3
AI credits per month
3,600
Scheduled posts per month
120
Release emails per month
5,000
API writes per minute
300
Concurrent jobs
5
Asset storage
25 GB
  • Editor, image tools, and video export
  • Six roles and approval on every post
  • Append-only audit log, 90 days
  • Release intake: form, API, webhooks
  • Save visuals to the workspace
  • Edit and delete saved visuals

Business

For larger teams posting to many channels

$699

per month, or $594 billed annually

Seats
20
Social channels
15
AI credits per month
13,200
Scheduled posts per month
480
Release emails per month
25,000
API writes per minute
1,500
Concurrent jobs
25
Asset storage
250 GB

Everything in Pro, plus

  • Higher limits on every quota

Enterprise

For security reviews and scale

From $3,000

per month, billed annually

Contact sales
Seats
Unlimited
Social channels
Unlimited
AI credits per month
54,000
Scheduled posts per month
2,400
Release emails per month
100,000
API writes per minute
10,000
Concurrent jobs
250
Asset storage
5 TB

Everything in Business, plus

  • SAML and OIDC single sign-on
  • SCIM user provisioning
  • Signed audit log export to your SIEM
  • Longer audit retention
  • Legal hold

Plans renew automatically each month or year at the price shown, plus any tax, until you cancel. Cancel any time in Settings → Billing; access continues to the end of the paid period. By subscribing you agree to the Terms.

Extra launch $29

500 AI credits, about one launch, for any subscribed workspace. They are spent after the monthly allowance and do not expire.

Launch intelligence is in early access for design partners on any plan. One credit is one cent of AI cost. A launch uses about 430 credits ($4.30). At zero, Shots stops before the next AI call.

Questions

Anything else? Talk to us.

What is Shots?
A launch platform for software teams. You describe a release, or send it from GitHub. Shots writes a launch brief where every claim cites a source, plans the launch, designs visuals from your real product, and drafts posts for each channel. You approve before anything goes out. The open-source screenshot editor underneath is included in every plan.
Will it ever post without me?
No. Approval is enforced on the server. The AI and API keys can create drafts. Only signed-in teammates can submit posts for review. Only teammates with approval rights can approve, and only approved posts can be scheduled.
Where do the screenshots come from?
Your live product. Shots captures your product URL and the release's source links, then lays them out in the editor with your brand kit. Pages behind a login are not supported yet.
How does it avoid making things up?
Every claim in the 11-section launch brief cites your release or a source. A claim with no source is removed and becomes an open question for you. Posts may only use claims the launch brief contains, and a post that breaks that rule fails the copy checks.
Which channels does it cover?
Posts for all 6 channels: X, LinkedIn, Instagram, Product Hunt, your changelog, and email. Scheduled publishing to X, LinkedIn, and Instagram is in early access, and we set up channel connections with you.
Can I edit what it makes?
Yes. Edit copy inline, open any visual in the full editor, or ask for a revision and apply it from a diff. Approved posts stay exactly as you approved them.
Do you train models on my content?
No. Each time Shots writes, it looks up your own workspace history: approved posts, rejected posts with notes, and applied revisions. Nothing is shared across workspaces.
Is the editor still open source?
Yes. The editor is Apache 2.0 licensed, included in every plan, and exports carry no watermark.

Shipping something this week?Have its launch ready for review the same day.