Trigger the Ask at the Win

Ask for the share right when the product just proved itself.

Most referral prompts fire at the worst possible moment, the day you sign up, before you have any reason to vouch for anything. Tesla waits. The referral link sits in your account the whole time, but the reward attached to it stays frozen until your friend's car is actually sitting in their driveway, not the day they typed a card number into an order form. That single design choice ties the whole loop to the one moment a car buyer is most likely to tell everyone they know: delivery day.

What to do: Find the exact moment inside your product where a user just watched it work, the export finished, the deal closed, the report rendered, and put the share prompt there instead of on the signup screen or in a weekly digest email. If a reward is attached, hold the payout until the person your user brought in reaches that same proof moment themselves. An order, a signup, a click on "invite a friend" does not count on its own.

Why it works: A user who just watched your product deliver is the most convincing salesperson you will have for the next ten minutes, and a reward that only fires on someone else's real result keeps the whole loop honest instead of paying out on hope.

Example: Tesla's referral program will not pay you for a friend who merely places an order. The moment they order using your link, your reward appears inside the Tesla app already, marked pending, and it stays pending, earning you nothing, until what Tesla calls the Grant Date, the day your friend's car is actually delivered. Order and never take delivery, and the pending reward just expires unpaid.

Walk it through

I tried to pull a screenshot of Tesla's referral page in July 2026. Here is what actually happened.

1. The live page blocks scripted requests outright.

curl -s -o /dev/null -w "%{http_code}\n" https://www.tesla.com/support/refer-and-earn

Output: 403. Pointing headless Chrome at the same URL renders an Akamai "Access Denied" page, reference number and all, never the support article itself. Tesla's edge network only serves this page to a browser carrying a real session, so there is no honest screenshot to take here.

2. The Wayback Machine already has a clean copy.

curl -s "http://archive.org/wayback/available?url=tesla.com/support/refer-and-earn"

That returns a stored snapshot, crawled before whatever rule now blocks outside requests. Pull that URL instead and the whole page comes back as plain, readable HTML.

3. Grep the archived HTML for the actual policy.

grep -i "grant date" tesla-refer-and-earn.html

Real output, Tesla's own words, not a summary of them:

After your friend places an order, your benefit will appear as
'pending' in the Tesla app until the Grant Date. Each referrer
benefit expires 12 months after the Grant Date.

Pending starts at order. The reward itself starts at delivery. The gap between those two dates is exactly what this chapter is about.

4. Work the actual timeline.

Say a friend orders a Model Y on July 1 and takes delivery six weeks later, on August 15. Your reward sits pending in the Tesla app that whole six weeks, worth nothing yet, then converts to spendable Tesla Credit on August 15, the real Grant Date. From that same date, not from July 1, you have 12 months to spend it before it expires, and Tesla emails you 30 days out to remind you it is about to.

The read

Pending is a leash, not a receipt. Showing the reward as pending the moment a friend orders keeps the referrer checking back and rooting for the delivery to happen, instead of collecting a payout and forgetting the whole program exists.
The trigger is delivery, never the order. Crediting at the order would make the referral count look better on a dashboard that same week, but it would pay out on people who might still cancel. Delivery is the only event Tesla is willing to call real.
Expiration counts down from the same real event. Twelve months runs from the Grant Date, not from the day the invite was sent, so a reward can't dangle half-earned forever, and it can't expire before the win it depends on has even happened.

Steal it

Find your own product's version of delivery, the moment a user has undeniable proof the thing works, and put the ask there instead of on the welcome screen or in a trial-start email. If you already run a referral flow, audit where the prompt currently fires. If it is at signup or trial start, that is the equivalent of Tesla crediting you at reservation. Move it to right after the first real result, and if a reward is attached, split it into two events the way Tesla does, show pending status the moment the referred person takes the small step, order, signup, first click, but only release real value once they reach their own delivery, a first paid invoice, a completed project, a real outcome.

Defend the mechanic by refusing to compress those two events into one for the sake of a better-looking weekly number. It will always be tempting to credit at the earlier, cheaper-to-hit event because the referral count looks bigger sooner. Resist it the way Tesla resists crediting at order instead of delivery. A reward tied to a reversible action is a liability you will eventually have to claw back, and clawing back a reward someone already believes they earned costs more goodwill than the delayed version would ever have cost you.

Gotchas

A long gap between order and delivery can cool a referral off entirely. If your version of "delivery" takes months, an enterprise contract, a slow onboarding, the referrer may have moved on emotionally before the reward ever posts. Pair the delayed real reward with a small immediate acknowledgment, a thank-you, a status update, so the loop stays warm in between.
A deadline you don't enforce is not a deadline. Tesla emails you 30 days before credits expire and then actually lets them expire. If your reward has a stated cutoff but you quietly extend it for anyone who complains, you are running a discount code with extra steps, not a time-bound incentive.
Honest caution: the stricter trigger has a real cost, not just a fraud benefit. Timing the ask to a genuine win is close to free to test. Timing the payout to a stricter event is not. Some referrers simply will not bother sharing if the payoff feels distant or uncertain, so check whether the higher-quality referrals you get from waiting actually beat the raw volume a faster, cheaper reward would have brought in before you assume delayed is always the right call.