Marketplaces & analytics

Dataset Marketplace

A marketplace where domain experts publish curated, versioned datasets and buyers preview, license, and pull them via API or download.

Full planning bundle — BRAND, MRD, BRD, PRD, DESIGN
Branded styleguide — typography, color, components
4 previewable mockups

Cloning copies the full plan into a new project you own — edit it freely.

Inside the bundle

Styleguide and mockups

A look at the brand palette and screen-level mockups that ship with this plan. Cloning copies all of them into your project.

Mockups

Style guide

Styleguide

What this blueprint gives you

The “Shopify for datasets” model: publishers package CSV/Parquet files into versioned, subscription-priced products; buyers browse a catalog, inspect a schema and sample rows, license under clear terms, and pull fresh data through an API token or signed download URL.

Five planning documents (BRAND, MRD, BRD, PRD, DESIGN) at senior-team depth, covering schema previews, version pinning, license enforcement, metered API delivery, publisher payouts, and the trust layer that makes paid data feel safe to integrate.

Planning documents

Preview the plan

Each blueprint includes the senior-level planning files. These cards show the opening text before you clone the full bundle.

Brand Guidelines Document

BRAND.md

Preview

BRAND — Dataset Marketplace One line A catalog of trustworthy, versioned datasets you can preview before you pay and pull on a schedule after. Who it speaks to Data engineers, analysts, and ML teams who keep hitting the same wall: the data they need exists in someone's spreadsheet, scraper, or proprietary feed, and buying it is a procurement headache. On the other side: domain experts (ex operators, scrapers, niche analysts) who already maintain valuable datasets and want a clean way to sell acc

Design Specification Document

DESIGN.md

Preview

DESIGN — Dataset Marketplace Information architecture Public: home (catalog + verticals + featured), search results, dataset card (slug based URL), publisher profile, pricing/take rate explainer, license library, docs (API + SDK). Buyer app: Subscriptions, Tokens, Usage, Invoices, Pinned versions, Account. Publisher studio: Datasets (list), New dataset, Dataset detail (versions, subscribers, analytics), Payouts, Profile, Settings. Admin: Moderation queue, Publishers, Datasets, Disputes, Payouts.

Market Requirements Document

MRD.md

Preview

MRD — Dataset Marketplace The problem Buying useful data today is a mess. Niche datasets live in someone's S3 bucket, get emailed as zips, or sit behind sales calls. Buyers can't preview without signing an NDA, can't pin a version, and can't tell when the file last refreshed. Publishers who maintain real, valuable datasets either give them away on GitHub or build a half working Stripe + Dropbox pipeline themselves. The missing primitive is a marketplace where datasets are first class products: v

Business Requirements Document

BRD.md

Preview

BRD — Dataset Marketplace Business outcomes 1. GMV (gross marketplace volume). Total subscription + one time spend flowing through the platform; revenue is a take rate slice of GMV. 2. Take rate. Platform fee on every transaction (target: 12–18% depending on plan tier); covers infra, payouts, and dispute handling. 3. Activated supply. Number of publishers with ≥1 paying subscriber and a dataset refreshed in the last 30 days — the only supply that matters. 4. Buyer retention. Subscription renewal

Product Requirements Document

PRD.md

Preview

PRD — Dataset Marketplace Phase 0 — Foundations Auth + accounts: buyer , publisher , admin . A user can hold both buyer and publisher roles. Publisher onboarding: identity verification, payout account (Stripe Connect), tax forms. Billing primitives: card on file, subscriptions, one time charges, invoices, dunning. Storage: object store with per dataset prefixes, signed URLs, lifecycle rules for cold versions. Acceptance: a publisher completes KYC, connects a payout account, and is eligible to pu