
Mission 6 of 6
Ship your data product, ready for launch day.
You have a clean, labelled, refreshed dataset. Pick the product shape from the buyer's words, build a searchable site, price it, write the terms and keep it fresh with a cron.
What you'll do
Choose site, CSV, API or newsletter from what the buyer says, then serve your SQLite with Datasette.
Price from the hour you save the buyer, then draft terms that cover licence, accuracy and personal data.
Run a cron that rebuilds the database and refuses to swap in a broken one.
- Work through a launch checklist before you go live
- Email the buyers who already described the problem
- A labelled SQLite or CSV from mission 3, refreshed by a scheduled script from mission 4 or 5
- Docker (Docker without fear) on the machine that will serve it; a VPS for the real thing (self-host on a VPS gets you one with HTTPS)
- A Stripe account for payment (take payments with Stripe)
- BRIEF.md with its
## Legaland## Qualitysections filled in
Your progress0/6
- 01Pick the shape from the buyer's words8 min
- 02The searchable site: Datasette on your SQLite20 min
- 03Price it from the hour you save10 min
- 04Terms, attribution and the accuracy line10 min
- 05Keep it fresh: the nightly refresh that refuses to ship a broken build12 min
- 06Launch: the first ten customers and what you're handing over15 min
Pick the shape from the buyer's words
Before you build anything, decide what you're building. The buyer tells you the product shape in one sentence, if you listen for it.
There are four common shapes for a data product. The table shows what the buyer says for each, how much it takes to build, and when it fits best.
Read through the table of the four shapes.
The four shapesSHAPE BUYER SAYS BUILD EFFORT PRICE SHAPE BEST WHEN Searchable site "I look things up" low monthly, per seat many small lookups, SEO brings buyers CSV subscription "I load it into my own system" lowest monthly or annual buyers have analysts or a CRM API "my software needs it" medium per call or tier buyers are developers or SaaS Newsletter "tell me what changed" low monthly the delta matters more than the table
Find the buyer's sentence
Go back to the buyer interviews or forum threads from mission 1 and find the sentence. 'I'd look up each one' is a searchable site. 'I'd pull it into our CRM' is a CSV or an API. 'Just tell me when something changes' is a newsletter or alert.
Most data products end up as a site with a CSV download, because that covers the first two sentences, and a weekly email of the delta, because that's the retention engine. Start with the site.
The shapes built in other missions
The three shapes this mission doesn't build in full already have missions.
- API: sell API access to data covers keys, metering and per-call pricing.
- Newsletter: build a paid newsletter, with mission 4's digest script as the content engine.
- The full SaaS on open data with accounts and plans: micro-SaaS on open data.
If your buyer's sentence points at one of those, do this mission's steps 3 to 6 (pricing, terms, refresh, launch) and that mission's build steps.