Product
Everything between the mergeand the post.
Send Shots a release. You get a cited launch brief, a plan, on-brand visuals, and posts for six channels, ready for your approval. Six parts do the work, and each one also works on its own.
- Trigger
Release
Recurring invoices · PR #452
- AI
Launch brief
14 of 14 claims cited
- AI
Campaign plan
3 angles · 6 channels
- AI
Visuals
4 on-brand visuals · checks passed
- AI
Posts
X, LinkedIn, Instagram, Product Hunt, changelog, email
- Human
Review
Approve all 6 posts in one click
- Scheduler
Schedule
Published once, with confirmation
The parts
Start with the part you needand add the rest when you are ready.
Release intake brings the work in. Launch intelligence writes the launch brief and the drafts. The creative engine makes the visuals, and approvals keep a teammate in charge. Publishing delivers the posts, and guardrails keep the AI to what your sources say.
What is saved
Every launch is saved as records,so you can change one piece at a time.
Change one hook, regenerate one image, or approve three posts without starting over. Every generated piece records the versions it came from.
Title, why it matters, audience, and source links.
Audit entryCited. Every draft or edit is a new version.
Audit entryChannels, angles, assets, and the timeline.
Audit entryCopy, channel, and the claims it relies on.
Written frombrief v2plan v1Audit entryEditable in the Shots editor, with its variant and critique.
Audit entryDestination, time, and the confirmation once it posts.
Audit entry| Record | What it holds | Who changes it |
|---|---|---|
| Release | What you send: title, why it matters, description, audience, and up to twenty source links. | Creators, API keys, webhooks |
| Launch brief | The cited launch brief. Every AI draft, teammate edit, or applied revision saves a new version. | The AI drafts. Teammates edit and approve one version |
| Plan | Channels, angles, visuals with capture hints, and the timeline. Versioned like the launch brief. | The AI drafts. Teammates approve |
| Post | Copy, channel, the claims it relies on, and the launch brief and plan versions it was written against. | The AI drafts, creators edit, approvers decide |
| Visual | An editor file with its place in the plan, a variant label, and its check results. | The AI, or anyone in the editor |
| Scheduled post | Destination, time, delivery state, and the confirmation from the network. | Publishers, then the scheduler |
| Audit log | Every decision with its teammate, request ID, and outcome. | Append-only. Nobody edits it |
Build order
We built the manual tools first,then step-by-step workflows, then the AI.
Every feature works without the AI. When a step fails, it tells you which step. The AI then chooses from features that already work.
1 · manual toolsManual tools
The editor, brand kits, product pages, and launch records work on their own, in the app and through the API.2 · workflowsStep-by-step workflows
Each workflow runs fixed steps. The AI fills in text at set points, the output is checked, and any step can be retried.3 · the AIThe AI on top
The AI picks what to do. Shots decides how it runs safely: inside one workspace, with no approval rights.
Where to next
See Shots on a real launch,or read the page for your team.
Launch intelligence is in early access for design partners.