How can startups manage different vesting calendars across teams?

The right way to manage different vesting calendars across teams is grant-level scheduling: each grant has its own start date, cliff, and vesting schedule tied to when that person joined, not to a company-wide calendar or payroll cycle. That single structural decision is what keeps a 30-person cap table from becoming unmanageable.

To see why it matters, consider what typically happens around the fifteen-person mark. You have a founder grant from day one, a CTO hired six months later, three engineers who joined in the first year, a head of sales who came on board after your seed round, and a couple of contractors picking up specific projects. Each of them has equity. Each of them has different terms. And somehow you are expected to track all of it.

At five people, a spreadsheet can handle this. At fifteen, it cannot. The dates are different, the cliff periods vary, some grants have acceleration clauses, and refresh grants are starting to layer on top of everything else. This is the point where founders either get it right by design or spend the next two years correcting errors.

Why forcing one vesting schedule breaks

The instinct to standardise is understandable. One cliff period, one vesting length, one set of terms for everyone. It feels cleaner.

The problem is that equity serves different purposes for different roles. When you force one template onto all of these situations, you either over-reward short-tenure hires or under-reward the people who took the most risk. Neither outcome builds the culture you want.

Grant-level scheduling: vesting tied to start date, not payroll cycle

The first structural fix is simple but important: vesting should start from a clearly defined date, typically the employee's start date of employment, not from the nearest payroll cycle or calendar quarter. The grant date and the vesting start date are often the same, but not always: the grant might be issued a few weeks after someone joins, while vesting is backdated to their first day.

Some early-stage companies, often because of how their payroll software works, inadvertently delay the effective start of a grant by a few weeks or even months. Over a four-year schedule, that drift is mostly cosmetic. But it creates inaccuracies in your cap table and, more importantly, it erodes trust when an employee checks their vesting and the numbers do not match their offer letter.

Grant-level scheduling means each grant has its own start date, its own cliff, and its own schedule that runs independently of everything else. When you hire someone on March 15, their grant starts March 15. When they hit their cliff, it is exactly twelve months later. No rounding, no batch processing.

The equity tier model: five tiers, different terms

The most practical framework for growing startups is to define equity tiers before you need them. These are not rigid rules but reference points that make grant decisions faster and more consistent.

Founders. Standard four-year vesting with a one-year cliff, often with a portion vesting immediately or on a compressed schedule to reflect pre-incorporation work. Double-trigger acceleration is common for founder grants, particularly in VC-backed companies.

Executive hires (VP level and above). Four-year vesting with a one-year cliff is still typical, but the grant size and any acceleration provisions are usually negotiated. Some executives, particularly those joining at a late seed or Series A stage, will ask for a shorter cliff or partial acceleration on a single trigger. That is a negotiation, not a standard.

Early hires (the first 10 to 20 employees). Four-year vesting with a one-year cliff. These are the people who took a risk on you when the company was unproven. The terms are the same as founders and executives, but grant sizes reflect their role and the stage at which they joined. Some companies add a small accelerator for employees who hit a multi-year tenure milestone.

Later hires (post-seed and beyond). Still typically four years with a one-year cliff, but grant sizes reflect the lower risk profile of joining a company with traction. The equity conversation is different here: it is less about sweat equity and more about competitive compensation.

Contractors and advisors. This tier is where the most variation exists and where most mistakes happen. A long-term contractor doing ongoing work might be on a two or three-year monthly vesting schedule with no cliff. An advisor who gives two hours a month probably warrants a one or two-year schedule with a short cliff. A project contractor with a defined scope should get a fixed grant that vests on delivery or over a short fixed period, not a standard four-year schedule.

Having these tiers documented means that when a new hire negotiates equity, you are comparing against a framework rather than improvising.

Managing overlapping refresh grants

Refresh grants, additional equity awarded to retain employees who are approaching the end of their initial vesting schedule, are where complexity really compounds.

The key principle is to treat every refresh grant as its own independent grant. It has its own start date, its own cliff, and its own vesting schedule, separate from the original grant. Some platforms try to merge or roll grants together, which creates a confusing hybrid schedule that is hard to explain to employees and hard to audit for investors.

The practical consequence of keeping grants separate is that an employee might have three or four grants running simultaneously at any given time, each at a different point in its vesting schedule. That sounds complicated, but it is actually easier to manage than merged grants, because each line item is clean and traceable back to a signed document.

When you are communicating equity to employees, aggregate the numbers into a simple statement of total vested and unvested shares across all grants.

Centralising tracking in Cake: what that looks like in practice

The manual version of all of the above is a set of spreadsheets that someone has to remember to update after every payroll cycle. That works until it does not, and the consequences of an error on your cap table range from uncomfortable employee conversations to problems at your next funding round.

On Cake, each grant is entered once with its own start date, cliff, and vesting schedule. From that point, vesting is automated. New vest events appear in the cap table automatically, employees can see their own vesting schedule in the stakeholder portal (and only their own holdings, not anyone else's), and you have a live, fully diluted view of ownership at any point in time.

When you add a refresh grant, it sits alongside the original in the same employee record, tracked separately but aggregated in the ownership summary. You do not need to manually reconcile anything.

The equity tier model is easy to implement with vesting schedule templates, which let you define standard terms for each tier once and apply them consistently to new grants. That removes the risk of a typo changing a cliff period or a schedule length in a way that creates a disparity between what someone was promised and what they actually receive.

For startups heading into a Series A, this level of organisation is not optional. Investors will want to see a clean cap table and a clear record of every grant. Having it all in one place, tracked at grant level, means that due diligence becomes a report rather than an audit.

Equity management that scales with your team

Vesting complexity compounds as your team grows. The founders who build grant-level scheduling into their process from the start spend less time on equity administration and more time on the work that actually moves the company forward.