STUD
← Plays

Calculate · Assess & Decide · Analysis & Finance

Partner-sourced vs influenced revenue and lift

Counts and won-revenue split partner-sourced / influenced / no-partner, with the comparative lift (close rate, deal size, days-to-close) of partner deals vs the rest.

You receive: A reviewed attribution calculator + the passing test report, run on your deal records.

Part of Grow Partnerships

Example

A sample of what this play produces. Your result is generated for your inputs.

Counts

Partner sourced
4
Partner influenced
3
No partner
5
Partner total
7
Rest total
5
Grand total
12

Revenue won

Partner sourced
1200
Partner influenced
340
No partner
440
Partner total
1540
Rest total
440

Comparative

Close rate
Partner
0.8333
Rest
0.6
Lift pct
38.89
Avg deal size
Partner
308
Rest
146.6667
Lift pct
110
Avg days to close
Partner
14.8
Rest
31
Lift pct
-52.26
Inputs
Deals
DealPartner roleStageAmountDays to close
Annual pack, 6,000 creditssourcedwon24014
Annual pack, 18,000 creditssourcedwon72021
Annual pack, 6,000 creditssourcedwon24018
Annual pack, 6,000 creditssourcedlost0
Annual pack, 6,000 creditsinfluencedwon24012
One-time pack, 2,500 creditsinfluencedwon1009
Annual pack, 6,000 creditsinfluencedevaluating240
One-time pack, 2,500 creditsnonewon10030
Annual pack, 6,000 creditsnonewon24028
One-time pack, 2,500 creditsnonelost0
One-time pack, 2,500 creditsnonelost0
One-time pack, 2,500 creditsnonewon10035
Dual tag precedence
sourced
Won stages
  • won
Lost stages
  • lost
Comparative metrics
  • close_rate
  • avg_deal_size
  • avg_days_to_close

Arithmetic recomputed against the tasks.py _attr_reference oracle (compute-partner-attribution), 2026-10-12, on an illustrative launch-quarter pipeline for STUD: 12 prepaid credit pack purchases tagged by whether a launch-community partner sourced or influenced the buyer (amounts are the published pack prices: the 6,000-credit annual pack at $240, the 18,000-credit annual pack at $720, and the 2,500-credit one-time pack at $100). Won revenue: sourced 240+720+240 = 1,200, influenced 240+100 = 340, no-partner 100+240+100 = 440, so the partner cohort carries 1,540 of 1,980 won dollars. Close rate: partner 5 won of 6 decided = 0.8333 vs rest 3 of 5 = 0.6, a 38.89 percent lift. Average deal size: 1540/5 = 308 vs 440/3 = 146.6667, a 110 percent lift. Average days to close: 74/5 = 14.8 vs 93/3 = 31.0, 52.26 percent faster. The open evaluating deal stays in the counts but is excluded from every won-only metric, per the play's convention. All deal records are illustrative; STUD is in a pre-revenue soft launch and the pipeline is a worked example, not reported pack sales.

Opens soon

Cost50 credits
ProtectionSpent when the run starts · returned only if STUD is at fault

STUD opens runs for everyone soon, on every play at once.

Scope of the check

What's verified: STUD verifies that your deal records are bucketed partner-sourced, partner-influenced, and no-partner exactly per your dual-tag precedence choice, that the counts and closed-won revenue per bucket are right, and that each requested lift metric (close rate over resolved deals, average won deal size, average won days-to-close) compares the partner cohort to the no-partner rest with lift_pct = (partner - rest) / rest x 100, null whenever the baseline is missing or zero. The arithmetic is checked against a hand-written reference on held-out datasets covering dual tags, open deals, missing amounts, custom stage labels, and empty cohorts. STUD does NOT verify that your partner tags are accurate in your CRM, that sourced or influenced was recorded correctly on any deal, or that the observed lift is causal rather than a selection effect.

Get early access to STUD the day it goes live.