The problem this solves
Referrals already happen, but nobody asks for them systematically. Happy customers finish onboarding, renew twice, and are never once invited to refer, review, or speak. When a referral does arrive there is no record of who sent it, so nobody thanks them and the behaviour is never reinforced. Case studies and reviews get chased ad hoc when a deal needs proof, always from the same two customers someone happens to remember.
How we work
Design comes first: who qualifies as an advocate, based on signals you already have, customer success input, survey scores, usage and tenure; what they get asked for, referrals, reviews, case studies, reference calls, intros; and what they receive in return, which in B2B is usually recognition, access, and genuine reciprocity rather than cash. The mechanics get written down as program rules, so the program survives the person who launched it.
Then the build in HubSpot: enrollment lists and workflows that identify and invite advocates, a referral capture flow that links the referrer to the referred contact and deal, tracking properties so referral-sourced pipeline is visible in reporting, and thank-you and reward automation so no advocate is ever left hanging. A program dashboard shows enrollment, asks, responses, and referral pipeline in one place.
Launch itself runs deliberately small: an initial cohort of well-chosen advocates rather than a mass blast, so the asks, the tone, and the mechanics get tested on people who like you before the program scales.
Deliverables
- Program design: advocate criteria, asks, rewards, and written rules
- HubSpot build: enrollment lists, workflows, referral capture, tracking properties
- Referral attribution linking referrer to referred contact and deal
- Invitation and program assets
- Launch with an initial advocate cohort
- Program dashboard: enrollment, asks, responses, referral pipeline