Negotiating Equity Refreshers: What Actually Moves the Number

Refreshers are not automatic, and the process is more mechanical than it looks

Engineers who joined a company with a large initial equity grant sometimes assume additional equity will simply continue flowing at a similar pace indefinitely. In reality, refresher grants at most large tech employers are tied to a formal, periodic process — typically annual or tied to the performance-review cycle — that weighs performance rating, retention risk, leveling, and overall equity budget for your team or organization that cycle. Understanding this process, rather than treating refreshers as passive and automatic, is what allows an engineer to actually influence the outcome.

What actually drives refresher size

• Performance rating. Most refresh processes explicitly tie grant size to your most recent performance rating — a strong rating is usually a prerequisite for a meaningful refresh, not just a nice-to-have.
• Perceived retention risk. Managers and compensation committees frequently have some discretion to allocate additional refresh budget toward employees they specifically want to retain — which means visibly signaling market alternatives (without threatening) or having a documented competing offer can shift outcomes, though how much varies significantly by company culture and manager.
• Vesting cliff timing of existing grants. Engineers approaching the end of their initial grant's vesting schedule, where remaining unvested value is dropping toward zero, are natural candidates for refresh conversations, since a "cliff" in total unvested value is itself a retention risk the company has an interest in addressing.
• Team and organizational equity budget. Refresh pools are typically allocated top-down to organizations and then distributed by managers — meaning the same performance and retention profile can yield different refresh outcomes in a well-funded year versus a constrained one, a factor largely outside an individual engineer's control.

Building a case, concretely

Rather than a vague request for "more equity," a more effective approach documents specific, factual inputs: your current unvested equity value and its vesting timeline (showing where the cliff in remaining value actually falls), your recent performance ratings and any specific accomplishments tied to them, and, where relevant and honestly presented, market compensation data for your level and role from public compensation-data sources. Framing the conversation around your documented value and retention timeline, raised proactively with your manager before a review cycle rather than reactively during it, tends to be more effective than raising it only when frustrated about a specific outcome.

Competing offers: a real lever, used carefully

A documented competing offer is one of the more concrete inputs a manager can use to justify an off-cycle retention grant, since it gives them a specific number and urgency to bring to whoever controls refresh budget approval. This lever carries real risk if used insincerely or repeatedly — companies generally do not appreciate being treated as a negotiating tool against an offer you never intended to accept, and overusing this approach can damage trust with a manager over time. Used honestly, when you do have a genuine competing opportunity, it remains one of the more reliable ways to trigger an off-cycle refresh conversation.

What to do if the answer is no, or smaller than expected

• Ask directly what specific factors (rating, budget, level) constrained the outcome, so you understand what to address before the next cycle rather than repeating the same ask unchanged.
• Confirm the timing of the next refresh opportunity explicitly, rather than assuming it follows the same cadence as your initial grant.
• Factor the actual outcome into your broader financial plan — if your remaining unvested equity value is genuinely declining toward a cliff with no confirmed refresh in sight, that changes your near-term liquidity and retention-risk planning regardless of what you would prefer the outcome to be.

Timing the ask around the review calendar, not around personal frustration

Refresh conversations raised reactively — immediately after a disappointing bonus or in the heat of frustration about a missed promotion — tend to land less effectively than the same substantive case raised proactively, several weeks before the formal review or budget-planning cycle actually begins. Most managers have limited ability to influence refresh outcomes once budget allocations for the cycle are already set, which means the highest-leverage moment to raise a documented case is typically earlier than most engineers instinctively choose to raise it — closer to when planning begins than to when results are announced.

This same logic applies to manager transitions: an engineer who signals interest in a larger scope of work well before the formal cycle gives their manager more runway to build a supporting case internally than one who raises the same interest only once results have already been decided for the period.

Keep a running, dated log of specific accomplishments and their business impact throughout the year, rather than trying to reconstruct it from memory in the days before a review. A concrete, contemporaneous record is both easier to write persuasively and harder for a reviewer to discount than a retrospective summary assembled under time pressure right before the conversation actually happens.

This habit also pays off beyond any single refresh cycle: a well-maintained accomplishment log is equally useful when interviewing externally, when writing a self-review, or when a genuine competing offer materializes and you need to articulate your value case quickly and specifically rather than in general terms.

The takeaway

Equity refreshers are governed by a real, largely mechanical internal process — tied to performance rating, retention considerations, remaining vesting cliff, and organizational budget — not an informal continuation of your initial grant. Build a specific, documented case ahead of the review cycle rather than a vague request, and treat a genuine competing offer as a legitimate, if carefully used, input into that process.