What should happen?
Or type your own.
Seven steps. No dashboard.
Boomship recommends the strategy. You can expand it, steer it, or let it run.
Why this plan?
- The positioning decision (speed, not price) was confirmed twice in memory, so the story comes before the page.
- Customers struggle with first configuration, so the product update sits inside the launch, not after it.
- Nov 18 is a Linear issue with an owner; the plan keeps it and Measure begins the Friday after.
- 01Understand the marketa research memo
- 02Define the storythe launch narrative
- 03Create the launch systempage, deck, brief
- 04Update the producta verified change
- 05Reach the audiencea campaign brief
- 06LaunchNov 18
- 07Measurea Friday Mission
Research mode. Evidence, then a memo.
- competitor pages
9 sites · pricing, positioning, onboarding9 kept - customer notes
14 interviews · Drive14 kept - analytics
activation funnel · 90 days4 kept - past experiments
3 pricing tests · Notion4 kept
Boomship made something. Not another dashboard.
The market doesn’t need another feature. It needs a clearer reason to switch.
Seven of nine competitors lead with feature counts; none says how long the first order takes.[1]
Eleven of fourteen interviewed teams chose their current supplier for setup speed, then stayed out of habit.[2]
Activation drops 38% between account creation and the first configured catalogue.[3]
The 2024 pricing tests moved nothing; the 2025 onboarding test moved activation 9 points.[4]
Change the product by touching it.
Northstar v4
Everything you order, in one platform.
Request a demoClick Improve.
Boomship points at the pricing hero. The change happens in the rendered page first.
Ask for work. Get work.
The market doesn’t need another feature. It needs a clearer reason to switch.
Seven of nine competitors lead with feature counts; none says how long the first order takes.[1]
Eleven of fourteen interviewed teams chose their current supplier for setup speed, then stayed out of habit.[2]
Your first order in nine minutes.
- Audience: operations leads at 20–200 person suppliers
- Promise: your first order in nine minutes
- Proof: the onboarding test, +9 activation
- Channels: email to the waitlist, two partner newsletters, retargeting
- No gradients. No feature lists.
Your first order in nine minutes.
Northstar v4 sets up your catalogue from last month’s invoices.
Start with an invoiceArtifacts are live objects, not attachments. Open one, point at a part of it, say what is wrong.
How artifacts workClose the laptop. The Mission doesn’t disappear.
It runs on the server, not in your tab. Open the same Mission from any screen, send it a line while it works, and come back to what is ready.
Launch our new product.
You start it, and leave.
Launch our new product.
- Research memo4 claims
- The storydrafted
- Launch page19 of 27
- Board decknext
One line from the train. It changes course.
Northstar v4 is ready.
- Launch page27 / 27 tests
- Board deck12 slides · PDF
- Research memo4 claims · cited
Back at the desk: what is ready.
runs on the serverthe same Mission on any screena line you send is a step on the run’s own ledgerno notification, no approval · it finishes, and the receipt says what it did
Tell it once. It holds when it should.
Every Friday, give me launch performance and flag anything unusual.
- Collect launch metrics
- Compare against plan
- Explain material changes
- Prepare the update
- Hold if a check fails
- Deliver
Next Friday17:00 · the Mission wakes
- Collect launch metricsdone
- Compare against plandone
- Prepare the updatetests · 24 of 27
- Delivernext
One check failed. What depends on it waits.
The update changed the launch page’s number. Nothing goes out until a person looks.
heldthe launch pagethe Friday update
No recommendation · the receipt records which you chose
Done is a claim.
Prove it.
- Project Brain
- Files
- Connections
- Memory
- Browser
- Computer
- Automations
- Artifacts
- Receipts
Models change. Your Boomship doesn’t start over.
Keep your models. Upgrade everything around them.
Questions people ask first.
Is Boomship only for code?
No. A Mission can build or fix software, make a deck or a document, answer a question from your project’s sources with every claim cited, verify a pull request, or run on a schedule. It does not make phone calls, send email or messages, or generate images in this release.
How is this different from Cursor or an IDE agent?
An IDE agent writes code where you are typing. Boomship is the loop around a change: it reads the repository through the Brain, edits in a sandboxed runner, runs your tests, opens the result in a real browser and tries to break it, and ends with a Work Receipt that says which checks passed, failed or did not run. Many people use both.
Which models does it use?
Yours. Add Anthropic, OpenAI, Google or OpenRouter keys; they are stored encrypted and only the last four characters are ever shown again. Auto picks a model within a tier and the receipt says why. Where a deployment has managed keys, Auto can use those too.
Does Boomship upload my code somewhere?
Runs happen on the Boomship worker in an isolated runner with a private git mirror; your GitHub token never enters the sandbox. The Brain indexes a repository into rows that belong to your project. Nothing is sent to a model beyond the compiled context for the run, which the Context card shows you.
What can the Brain see?
What you give it: a connected repository, files and notes you drop in, pages, and the connectors you turn on (Notion, Linear, Slack, Airtable, with Gmail and Google Drive where the host has OAuth configured). Each source shows when it was last read and whether it is in sync.
Can it run on its own?
Automate chains runs and schedules them; a run that did not pass blocks everything behind it until a person looks. Signed webhooks can start a chain. One switch pauses everything automatic.
Can I try it without connecting GitHub?
Yes. Drop files into the Brain, or work in the Playground project. Connecting a repository is one token away when you want it.
What does "verified" mean on a receipt?
That an independent stage, not the builder, collected the diff, re-ran the tests and typecheck, had a different model review the change, scanned the added lines for secrets, and, where a page was involved, compared before and after in the browser. A check that could not run is listed as not run; confidence is rated from what actually ran.
What does it cost?
A monthly plan for everything around the model: the runner, verification and receipts, the Brain and Automate. Inference is billed by your provider on your keys. Current plans are on the pricing page.