Measure
Know which features actually create revenue.
Arkweaver tracks the meetings, reactivations, and expansion conversations a shipped feature produces, then attributes them back to that feature specifically, not to a company-wide average.
Illustrative Arkweaver revenue impact table showing shipped features ranked by the revenue attributed to them.
The problem
Most teams can name what shipped. Few can say what it earned.
A feature ships, gets a Slack announcement, and disappears into the release log. Whether it moved a single deal or opened a dozen conversations is not something anyone tracks, because the call data, the CRM, and the engineering tracker never get connected.
What it measures
Six numbers, tied to every feature you ship.
Prospect re-engagement
Closed-lost and stalled prospects who came back into active conversations after a blocker shipped.
Meetings booked
New meetings tied directly to a shipped feature reaching the account that asked for it.
Deals reactivated
Closed-lost opportunities reopened once the capability that killed them existed.
Upsell opportunities
Existing accounts who moved into an expansion conversation because of a specific release.
Cross-sell activity
Accounts introduced to a different part of the product because a shipped feature answered a need there.
Revenue influenced
Pipeline and closed revenue summed across every deal a feature touched, attributed feature by feature.
Ship to number
From shipped to attributed.
A feature ships
Arkweaver already knows which accounts and deals raised the problem it resolves.
Those accounts are watched
For 28 days, Arkweaver tracks new meetings, mentions, and CRM activity on the accounts tied to that feature.
Activity is attributed to the feature that caused it
A meeting or reactivation only counts toward a feature if it happened on an account that feature actually affected.
It rolls up to a number per feature
Pipeline influenced, deals reactivated, and meetings booked, visible on the feature itself.
The number at OhMD
OhMD tied 139 features to revenue.
Leadership at OhMD went from guessing which features mattered to seeing exactly which ones were creating commercial momentum, and where to double down.
Before you cite the number
Questions about how the attribution works.
How is revenue attributed to a specific feature?
Arkweaver matches deal and account activity to the blocker a feature resolved. Only accounts where that blocker was recorded count toward the feature, so the number reflects real cause, not a company-wide average.
What counts as an engagement?
A new meeting, a reopened deal, an upsell conversation, or a mention in a later call, all scoped to the accounts a feature affected. Configurable thresholds control how much activity counts as meaningful.
Can we see this broken down by rep or account?
Yes. The same attribution rolls up to the account and rep level, so you can see which reps are converting the revenue a feature makes available.
Does this work without a CRM?
Call and ticket data alone can show prospect re-engagement and mentions. Deal value, stage, and closed revenue require a connected CRM such as Salesforce or HubSpot.
The Revenue Platform for the AI Era
Use AI to turn every feature into more deals, more upsells, and more cross-sells.