Upcoming
On demand

How Vercel and Greenhouse Cut Headcount Reconciliation Time by 92%

Greenhouse cut headcount reconciliation time by 92%. Vercel took theirs from 30+ hours a month to almost none.

Headcount reconciliation is manual by default. Finance tracks FTEs, HR tracks individuals, Recruiting tracks requisitions, and none of the three numbers match. At Greenhouse the number lived across five systems: Workday, Adaptive, Monday.com, Greenhouse Recruiting, and a stack of spreadsheets. Moving one person from the US to EMEA meant updating three systems by hand. Finance and Talent burned 60 hours a month reconciling a single number.

In this product webinar, Virginia Hyland, Director of Solutions Engineering at TeamOhana, walks a real account live and shows the three features that take a company from a headcount number nobody trusts to one Finance can plan against:

What we'll show:

  • Headcount Reconciliation: A headcount change gets made once, in one place, instead of copied across every system that tracks it. Greenhouse went from 60 hours a month to 1-2 hours a week.
  • Auto-Approval Workflows: Greenhouse retired the two-executive bottleneck where every request ran through the CFO and CPO. Department leaders now authorize their own headcount with Finance and People on the chain, and approval lands in three business days instead of two weeks. At Vercel, hiring managers submit a backfill in under two minutes.
  • Total Budget Envelope: Once the number is reconciled, Finance can plan against it, not just clean it up after the fact. Every approved change ties to budget in real time, so spend can't drift past plan unnoticed.

If you've spent the week before a board meeting reconciling instead of preparing, this is that problem.

Key Highlights

The Human API problem is a single point of failure
One person in rec ops, people ops, or FP&A ends up manually stitching together the ATS, HRIS, and FP&A tool every month. They're good at it, but the entire headcount plan depends on one person. If they take vacation or leave, the reconciliation process starts over from scratch.
Jump to
03:55
60 hours a month reconciling one number nobody trusts
Greenhouse spent roughly 60 hours a month getting Finance, HR, and TA to agree on a single headcount number. Vercel spent 30+. Both replaced weeks of pre-board-meeting reconciliation with a forecast leaders can walk into any meeting and defend.
Jump to
00:56
Approvals only get faster after the forecast is trusted
Greenhouse routed every single request through their CFO and CPO on purpose, because they couldn't trust their own numbers. Once the forecast is reconciled, control can safely push down to business leaders through auto-approval rules and budget envelopes without losing governance.
Jump to
05:50

Most companies are making multi-million dollar workforce decisions on a headcount number three teams cannot agree on. Finance tracks dollars in the FP&A tool. HR tracks employees in the HRIS. Recruiting tracks reqs in the ATS. The result is a plan held together by one person, hundreds of spreadsheets, and a week of reconciliation before every board meeting. This session walks through how Greenhouse and Vercel used TeamOhana to eliminate that work, cutting reconciliation time by 92% at Greenhouse and near-zero at Vercel, and how they used the trusted forecast to safely push approval authority down to business leaders.

What You'll Learn

  • Why headcount reconciliation is a systems problem, not a discipline problem, and why cleaner spreadsheets will not fix it
  • How Greenhouse cut reconciliation from 60 hours a month to one or two hours a week
  • How to build a single forecasted headcount number that Finance can plan against and TA can recruit against
  • How to sequence auto-approvals and budget envelopes so control moves to business leaders without losing governance
  • How the ledger keeps Greenhouse, Ashby, Workday, and Adaptive or Pigment in sync when a single change would otherwise require updates across three systems and a stack of spreadsheets

Takeaway 1: Reconciliation is a systems problem, not a discipline problem

Companies do not burn 60 hours a month reconciling headcount because their teams are disorganized. They burn it because Finance, HR, and Recruiting each track a different object in a different system of record: dollars in the FP&A tool, employees in the HRIS, requisitions in the ATS. Even a simple change like moving one role from the US to EMEA requires updates in three systems plus a handful of spreadsheets. No amount of Excel discipline closes that gap.

Takeaway 2: A trusted forecast is the prerequisite for faster approvals

Greenhouse routed every hiring request through their CFO and CPO on purpose. It was a deliberate choice to protect the business, because their data lived across disparate systems and they had no way to see how they were performing against the plan. High-friction approvals were the price of low-trust data. The cost showed up as slower time-to-hire, especially on revenue-generating roles where a delayed sales backfill directly impacts pipeline and quota attainment.

Takeaway 3: Push authority to business leaders without losing control

Once the forecast is trusted, the approval layer can do real work. Sales IC backfills can auto-approve. A backfill that up-levels the role or raises pay by more than 10% can route into a full approval flow. Approvers get the request in Slack, approve in one click, and the change pushes back through to Greenhouse or Ashby automatically. Business leaders get speed on the decisions that do not need scrutiny, and Finance keeps scrutiny on the ones that do.

Takeaway 4: Budget envelopes turn headcount into a live financial conversation

A trusted forecast unlocks a real budget conversation. Finance sets a budget envelope at the beginning of the year, broken down by division or department, with an optional not-to-exceed headcount count. Business leaders see their forecast against their envelope in real time, in both fiscal year and annualized views. The difference matters. Fiscal year variance can look like savings from delayed hiring, while the annualized view can reveal roles being offered at a much higher run rate than planned. Leaders stop asking "how many heads am I over" and start asking "what does that mean for spend."

"If you've ever had a conversation where finance, HR, and TA each had a different headcount number and you had to spend a week before your next board meeting reconciling that number instead of preparing what you wanna say, that's the problem that TeamOhana helps solve."— Virginia Hyland, Head of Solutions Engineering, TeamOhana

Frequently asked questions

How much reconciliation time can we realistically save?

Greenhouse cut headcount reconciliation time by 92%, going from roughly 60 hours a month down to one or two hours a week. Vercel went from 30+ hours a month to near zero, with a fully reconciled headcount view available at any time. Actual savings depend on team size and current process, but the pattern is consistent: the work that used to happen right before a board meeting disappears.

We already have an ATS, an HRIS, and an FP&A tool. Isn't this what integrations are for?

Integrations move data. They do not reconcile it. Departments in your ATS may not map to your HRIS. Locations created in one tool may not exist in another. Candidates rescind and re-accept offers. TeamOhana sits on top of those systems, surfaces the mismatches in a Needs Attention view, and enforces one reconciled number that pushes back to the source systems. Integrations are the starting point, not the answer.

Which systems does TeamOhana integrate with?

TeamOhana works with the systems Finance, HR, and Recruiting already use, including BambooHR, UKG, Workday and other HRIS platforms, Greenhouse, Ashby, and SmartRecruiters on the ATS side, and Adaptive, Pigment, and other FP&A tools. Data syncs from the HRIS every four hours, and approved changes push back to the ATS and downstream systems automatically.

Won't automated approvals cause us to lose control over hiring?

The opposite. Approval automation is conditional. You decide which scenarios auto-approve, for example one-for-one sales IC backfills, and which scenarios route into full approval, for example any backfill that raises comp by more than 10% or up-levels the role. Business leaders move faster on routine decisions. Finance and People keep scrutiny on the decisions that actually need it.

What is a budget envelope and how is it different from what our FP&A tool already does?

A budget envelope is the pool of money Finance allocates for headcount, set at the start of the year and broken down by division or department, with an optional not-to-exceed headcount count. It differs from the FP&A tool in one important way: it is tied to a live, reconciled headcount forecast, and every approval decision updates the variance in real time. Business leaders can self-serve their view of forecast against budget in both fiscal year and annualized terms, so a headcount decision is always a spend decision.