Weekly digest + pre-call brief, one signal chain.
HomeDrop tells a rep what changed across their book this week. Intel Chat tells them what to do about one account right now. The unified product closes the loop between them — every digest card is one click from a seeded chat, every chat reshapes next Monday's digest.
We shipped HomeDrop (the weekly Monday digest) and Intel Chat (pre-call prep, stateless) within a few weeks of each other. Same data sources, same users, same brand tokens. Different surfaces.
The failure mode was obvious from competitive research. It's what Gong, 6sense, and Demandbase all get wrong: two products sharing a skin, where reps eventually pick one and ignore the other because the tools don't know what each other did.
The best analog in the market is ZoomInfo Copilot's feed-with-inline-query pattern. Every passive signal card is one click from a scoped query surface. The framing to borrow from Clari: the active layer exists to explain the passive alert, not replace it.
One sentence for the team: HomeDrop tells you what changed across your book this week. Intel Chat tells you what to do about one account right now. The unified product makes each stronger by keeping context alive between them.
The active layer exists to explain the passive alert, not replace it.
Path-routed under a single subdomain via a thin Cloudflare Worker. One cookie jar. One access policy. Behind the routing: two existing deploys (the Python-generated digest and the Next.js chat) left intact. No Frankenstein rewrite.
The data flywheel is a single new table: signals_log(user_email, account_slug, signal_type, weight, occurred_at). Chat activity writes to it. The digest pipeline reads a 14-day rollup from it. Accounts a rep has been watching pin to the top of next Monday's digest, with framing that references the watching.
Before scaling past the pilot, the unification has to earn its keep. Five metrics, 12-week targets: