Revenue Experiment 3

BizDev Known Contacts Filter

Pending Discovery
Waiting on qualitative data

This experiment cannot be sized until we review three customer transcripts that Tukan is sending. The hypothesis is directionally sound — consultants prefer warm outreach — but we don’t yet know how many users have overlapping network contacts, or what current BizDev engagement looks like broken down by warm vs. cold signals. This card will be updated once the discovery is complete.

Draft Hypothesis

If we surface only warm contacts (companies where the user already knows someone) in the Growth Inbox, then we will increase BizDev engagement from TBD to TBD within the 14-day window.

Baseline and target cannot be confirmed until Tukan’s customer transcripts are reviewed and MongoDB engagement data is queried against warm vs. cold signal breakdowns.

Signal

From the March 16 check-in: Tukan described the Growth Inbox as underperforming because users don’t know whether a surfaced company is a warm connection or a cold match. The hypothesis is that the intent gap — knowing someone vs. not — drives the decision to engage. Tukan believes filtering to known contacts would give users a reason to act on the first view.

Quantitative baseline from MongoDB: the Growth Inbox has 54,371 total records with a 5% overall action rate and a 10% open rate. Ignore reasons are never captured (field exists, always null). None of this data is segmented by relationship warmth yet.

Belief

The team believes consultants use Gia as a warm-outreach accelerator, not a cold prospecting tool. If that’s true, a Growth Inbox full of cold ICP matches creates friction — not opportunity. Showing only companies where the user already has a relationship removes the “who is this?” question and makes the action obvious. The expected effect is higher engagement per impression, not just more impressions.

Readiness: Pending Discovery

This experiment is not ready to design, scope, or run. The following must be resolved first:

  • Blocker

    No baseline. We do not know current engagement rates segmented by warm vs. cold contacts. MongoDB has the data but the query requires defining “known contact” — which depends on what the discovery interviews reveal about how users think about their network.

  • Blocker

    Feature does not exist. Gia does not currently tag Growth Inbox records by relationship warmth. Building the filter requires scoping the data model, the matching logic, and the UI before any experiment can run.

  • Blocker

    Three customer transcripts pending. Tukan committed to sending three recorded customer calls that discuss BizDev usage. These transcripts will be used to validate whether the warm-contact hypothesis is something customers actually want, and to size the potential cohort.