Sprint 1 in progress

Evidence-backed SaaS pricing intelligence

Compare SaaS pricing tiers, team cost, and price changes without guessing.

tiers.fyi starts narrow on purpose: public-priced B2B SaaS, verified source evidence, immutable price snapshots, and comparisons that admit when something is hard to compare.

Initial wedge
5 categories

Public-priced, mostly seat-based collaboration and workflow tools.

Seeded catalog
10 products

Official pricing URLs are in the database and ready for capture or review.

Evidence stored
0 artifacts

The first capture run is the next gate before broader extraction work.

Current execution

Foundation before growth

Why this is credible

Plan tightened around credibility

The strategy now prioritizes narrow scope, provenance, and realistic scaling instead of broad AI-generated volume.

Published

App scaffolded for Vercel

Next.js App Router, route structure, and deploy-ready scripts are in place, and the project is live on Vercel.

Published

Database contract defined

Drizzle schema groundwork is ready for provenance, price snapshots, change events, and manual overrides.

Published

Wave-one catalog seeded

10 products are seeded with official pricing URLs in the launch catalog.

Published

First live capture recorded

The browser capture path is wired, but no successful source runs have landed yet.

Candidate

Trust pillars

The site has to earn belief.

Agents are there to move faster on capture and structure. The user should still be able to inspect what was sourced, when it was verified, and what caveats remain.

Source trail

Official links visible

Every future pricing claim is expected to point back to an official vendor source and a captured run.

History

Immutable snapshots

The model is built around append-only price snapshots so charts and change logs are more than marketing copy.

Review

Human gates remain

New products, material diffs, and low-confidence extracts stay in review instead of silently shipping.

Honesty

Caveats stay public

If a pricing page is messy, the page should say it is messy rather than pretend the comparison is exact.