Accounts
Every company with at least one mapped signup. Pick a row to see each signal and its points, the champion, and a draft first line.
Held for a person
These signups could belong to a company, but nothing in the product data says which one with confidence. Each has a reason code and a next step for whoever reviews it.
How signups roll up
Applied top to bottom. The first rule that fits a signup decides where it goes. Counts are from this export.
Assumptions
Scoring weights
All in one WEIGHTS object in rollup.mjs. They are starting guesses, meant to be argued with. Change any value and the whole page re-ranks. Reloading resets them.
| What it controls | Value |
|---|
Show the object as code
Plans, lists and definitions
What I'd need to run this on real data
- Product events with an organization or group ID, for example a PostHog export or a webhook, plus how each user signed up (dashboard or API), dashboard logins, inboxes, sends and webhooks.
- The CRM's account and contact fields, so a mapped company lands on the existing record instead of creating a duplicate, and the buyer can come from enrichment rather than a guess.
- Where the "Talk this week" list should land: a CRM view or a Slack channel, and who works the held list each week.
The rules and scoring would stay the same; only the loader that reads the export changes.
Questions I'd want answered first
- Do your product events carry an organization or group ID, or only the person who signed up?
- When an agent signs up on its own, what ties it back to a person or company today?
- Which event best predicts an upgrade for you: a verified domain, webhooks, or hitting the free-plan cap?
- At a company where developers are already active, who usually signs off on paying?