Skip to content
ale@portfolio:~/portfolio$ cat README.md

portfolio

Every case study here answers one question: measurable outcome.

revenue-partner-share-attribution.mdZapier

Revenue Partner Share Attribution

ShippedTeam: Data + Business
TL;DR

Built partner revenue attribution from scratch, becoming the base model for a later multi-touch attribution system.

Outcome

  • ↑ability to identify high-performing partners
  • →became the base model for a later multi-touch attribution system
Saw It
  • Partner contributions to signups and upgrades weren't being recognized or incentivized.
  • No existing attribution model connected partner activity to revenue outcomes, so partners had no visibility into their own impact.
↓
Figured It Out
  • Started from interviews with business owners, PMs, and POs rather than assuming which rules mattered.
  • Needed technical specs that both engineering and business stakeholders could align on before building.
  • Traded a broader attribution model upfront for a single-touch model that could be validated and extended later.
↓
Did It
  • Shipped a POC and validated it against expectations, with edge cases confirmed through audit.
  • No major miss flagged, this one landed clean and directly seeded the next project.

My Role

Owned the business rule translation into specs, the technical spec definition, and the ETL modeling and audit.

Full breakdown

Problem & Risk

Business Viability Risk

Partners driving signups and upgrades had no way to be recognized or incentivized, risking lower partner engagement over time.

Customer Discovery & Validation

Evidence

Interviews with business owners, PMs, and POs surfaced the actual patterns and edge cases used to define the spec, rather than guessing at rules.

Context

In order to increase signups and upgrades, we wanted to recognize and incentivize partner contributions.

Timeline

git log --oneline⏱ → multi-touch model
kickoff: partner contributions unrecognized, no attribution pathPhase 0
discovery: interviewed business owners, translated rules into specsPhase 1
ship v1: POC shipped, validated against expectationsPhase 2
feedback: audit surfaced edge cases and exceptionsPhase 2
next: became base model for multi-touch attributionNext

What We Did

  • Highlighted main usage patterns and documented edge cases
  • Translated business rules into specs and aligned across teams
  • Defined technical specs and tracking requirements
  • Shipped a POC, modeled the ETL, tested use cases through audit
~ rough sketch, not an actual screenshot ~

partner contributions invisible

interviews + spec

POC + audit

base model

for multi-touch

Who Benefits

Marketing improved its ability to identify high-performing partners, focusing effort where it mattered and driving more signups and upgrades.

Next Steps

Became the foundation for a later multi-touch attribution project.