Blog: Never Evaluate the Same Product Twice — Introducing Status Lifecycle
Never Evaluate the Same Product Twice
Introducing Product Status Lifecycle in v0.1.59
As the crawler runs more scans and the product database grows, a new problem emerges: how does the team track what it's already looked at?
Without a shared record, two things happen. First, team members re-read dossiers they've already assessed. Second, genuinely interesting products get buried under new discoveries and never actioned. Both are a waste of time.
v0.1.59 solves this with a simple but complete status lifecycle.
Five Statuses, One Clear Pipeline
Every product in the system can now carry one of five statuses: new, reviewed, shortlisted, building, or archived.
They map directly to the real stages of how the team evaluates an opportunity:
new— the crawler found it, nobody's looked yet.reviewed— someone has read the dossier and formed a view.shortlisted— strong candidate; deserves a second look before committing.building— we've started replicating it on the platform.archived— not worth pursuing right now; cleared from active consideration.
There's no rigid sequence. Move products forward, pull them back, or skip steps — the lifecycle follows your process, not the other way around.
Filter the Dashboard, Not Your Memory
The ranked dashboard now has a status filter. Instead of mentally tracking what you've seen, you can simply hide archived products, or show only shortlisted ones.
The filter state lives in the URL, so you can bookmark a view and share it with the rest of the team without having to explain the context.
The Watchlist
The most useful addition is the Watchlist — a dedicated view that automatically collects every product marked shortlisted.
Think of it as the team's shared second-stage pipeline. Products arrive there because someone already vetted them and thought they were worth serious consideration. When you sit down to plan the next build, the Watchlist is your starting point.
Why This Matters
The core loop of this platform is: discover → evaluate → build. Status lifecycle closes the gap between evaluate and build. It turns a stream of crawled products into a managed, queryable pipeline — one where the team's collective judgment is recorded and reusable.
Available now in v0.1.59.