In private beta · Waitlist open

A living card for every feature you ship.

Rico connects to your tools, builds a card for each feature, and flags when what's being built has drifted from what was intended.

No login · No signup · Waitlist only

Card · Checkout flowLive
Feature · CHK-12Drift detected

Checkout flow

Owned by @anshika · Spec v3.2 · Last shipped 3h ago

Context · Gathered automatically

  • NSpec · Checkout v3.2MON
  • FFlow updated by @mayaTUE
  • LRIC-204 · Promo codeWED
  • ##checkout · scope threadWED
  • GHPR #482 merged to mainTHU
  • ▲Deploy · main@a91f2c3H

Build drifted from spec v3.2

Tax scope narrowed (EU + US → US only) · decided in #checkout

The Problem

Features drift.
Nobody catches it.

You write a spec. Engineering starts building. Within days, a decision gets made in Slack that never makes it back to the doc. An edge case gets missed. A scope change happens in a standup.

Six months later, nobody can tell you why the feature was built the way it was — or whether it matches what was originally intended.

How Rico works
Step 01read-only

Connect your tools.

Rico connects to where your intent lives — and where your code lives.

Intent

NNotionGGoogle DocsFFigma#Slack

Build

GHGitHubLLinear▲VercelSSentry
Step 02builds itself

Every feature gets a card.

Rico creates a card for each feature and fills it with everything relevant — the spec, Slack threads, tickets, commits, decisions. You don't maintain it.

Checkout flowCHK-12
File uploadsUPL-04
Magic-link authAUT-21
Step 03live

Drift gets flagged.

When what's being built diverges from what was intended, the card lights up. You choose: alert the team, or update the spec. The card stays current either way.

Alert engineering⌘ E
Update the spec⌘ U
The card remembers

Six months later, you still know why.

Every decision, every Slack thread, every change — attached to the feature it belongs to. When someone new joins, when ownership transfers, when you revisit a feature you haven't touched in months — the card has the full story.

Not just what was built. Why.

Card · UPL-04 · File uploads4 months ago

  1. Apr 12 · @raj · Slack #uploads

    Flagged perf hit for files >50MB on mobile.

  2. Apr 14 · @anshika · Linear RIC-118

    Decision: drop the file size limit from the v2 scope.

  3. Apr 16 · @maya · GitHub PR #311

    Removed the limit input + validation. Spec doc updated.

  4. Today · Asked by new hire

    "Why is there no file size limit?" — answered from the card.

Ask Rico

Ask Rico anything about your features.

Not a separate product — just how you talk to a card. Rico answers from real data across your connected tools, and cites the commit, ticket, doc or thread it came from.

  • › Does the current deploy match what we scoped?
  • › What changed on checkout since Monday?
  • › Why did we decide to drop the file limit?
Ask RicoContext: 4 tools
Does the current deploy match what we scoped on the checkout card?

Mostly. Tax is currently US-only — spec v3.2 says EU + US. Change traces back to a #checkout thread on Wed and PR #482.

Card: checkout · GitHub · Slack

Why did we decide to drop the file limit?

Decided 4 months ago. @raj raised perf concerns in #uploads, you signed off in Linear RIC-118, then it was removed in PR #311. Full thread on the Uploads card.

Card: uploads · Slack · Linear · GitHub

›Ask anything about your stack
Built with the people who feel it

Built with PMs who feel this pain every day.

17+ discovery sessions with product managers at YC-backed startups, unicorn companies, and growth-stage teams. Three design partners are actively shaping what Rico becomes.

17 PM interviews · 3 design partners · Shipping Q3

Early access

Give every feature a memory.

Join the waitlist — we're onboarding a small group of product teams every week.

No spam · One update when you're in