Upcoming
On demand
30 minutes

Gatekeeper to Partner: A Better Way for Finance to Support the Business

Business leaders need Finance. But not the version that says no, asks for a form, and comes back three days later with a number.

They need the version that says "here's what that hire costs, here's how it compares to plan, and here's what happens if we wait a quarter." That's the Finance team that gets pulled into decisions early. That's the one that shapes strategy instead of just scoring it after the fact.

The problem is most Finance teams are still playing defense. A department head wants to add a role. They ask Finance. Finance pulls the budget, checks the plan, and gets back to them two days later. By then, the hiring manager already got a verbal yes from their VP and Finance finds out when the offer letter hits their inbox.

It's not a people problem. It's a visibility problem. Business leaders work around Finance because they don't have live access to their own data. And Finance spends more time reconciling than advising.

This session is for Finance leaders who want to change that dynamic.

In this TeamOhana demo, we'll walk through:

  • Live Budget and Headcount Visibility: Department heads get a real-time view into approved headcount, open roles, and where they stand against budget. They stop asking Finance for status updates. Finance stops answering them.
  • Self-Serve Scenario Planning: Business leaders can model headcount changes themselves and see the budget impact before they ask for approval. Finance reviews and advises instead of building every scenario from scratch.
  • Approval Workflows: Every headcount decision goes through a structured process. Finance stays in control without being the only one doing the work.
  • Variance Tracker: When actuals drift from plan, you can see exactly why and walk into any business review with a clear story instead of a reconciliation exercise.

Key Highlights

One headcount, six systems, dozens of handoffs
Virginia walks through the lifecycle of a single hire, from the leader's decision to the HRIS update. Every headcount touches Slack approvals, an annual plan spreadsheet, an FP&A tool, the ATS, and the HRIS. Multiply that by hundreds of hires per year and finance becomes a bottleneck instead of a partner.
Jump to
2:18
Give the business self-serve visibility into budget, forecast, and variance
The variance tracker gives business leaders their own view of budget, forecast, and what's driving the gap. Leaders can see whether early hiring, higher pay, or unplanned hires pushed them over budget before they ask finance for anything. Finance stops answering the same Slack questions and starts reviewing decisions instead.
Jump to
14:35
Scenario planning and TeamOhana Computer put decisions in the leader's hands
Business leaders can model changes to their own plan, uplevel roles, shift locations, and see the forecast impact in real time. With TeamOhana Computer in Slack, a head of engineering can ask "do I have room to offer 10K more for this role" and submit a change request without leaving the channel. Finance stays in the approval loop with a full audit trail.
Jump to
19:10

What You'll Learn

  • Why headcount planning breaks down when the workflow lives across Slack, spreadsheets, FP&A tools, the ATS, and the HRIS
  • How to give business leaders visibility into their approved hiring plan without giving up finance control
  • How the variance tracker exposes what's actually driving budget overruns: early hiring, higher pay, unplanned hires, or location changes
  • How scenario planning lets leaders model uplevels, location changes, and budget-neutral trades before they ever come to finance
  • How TeamOhana Computer lets leaders query headcount data and submit change requests directly from Slack, with finance approval and audit trails preserved

Takeaway 1: Finance is stuck in the middle because the workflow is stuck across six systems

Every headcount decision touches Slack, spreadsheets, an FP&A tool, the ATS, and the HRIS. Finance owns reconciling all of it. That's why finance business partners spend their time answering questions instead of guiding decisions. The problem isn't finance capacity. It's that the workflow forces finance to sit in the middle of every question the business could answer themselves if they had the right view.

Takeaway 2: Self-serve visibility for the business is the biggest unlock for finance

Business leaders don't want to Slack their finance partner every time they need to check plan progress or budget. When they have their own view of approved headcount, forecast, and variance, they can answer their own questions and come to finance already knowing whether they have room for the request. Finance moves from reactive support to strategic partnership.

Takeaway 3: Variance analysis only matters if the business can see it

Finance already tracks variance in their FP&A tool. The problem is that no one else can see it, so leaders make requests without knowing whether they have budget. When variance is exposed to the business, broken down by early hiring, higher pay, unplanned hires, and location changes, leaders start making tradeoffs before asking for more.

Takeaway 4: Scenarios and TeamOhana Computer move decisions upstream, with governance intact

Uplevels, location changes, and offer adjustments used to require a spreadsheet rebuild and a Slack thread with finance. Scenarios let leaders model the changes themselves and see forecast impact in real time. TeamOhana Computer takes it further: leaders can ask questions and submit change requests directly from Slack. Every change still flows through finance approval with a versioned audit trail.

"TeamOhana is a tool for finance, but really it's a tool for finance to give this type of visibility to their business partners."— Virginia Hyland, Head of Solutions Engineering, TeamOhana

Frequently asked questions

How is TeamOhana different from our FP&A tool?

Your FP&A tool is where finance builds the forecast. It isn't designed for business leaders to log into and understand their plan, budget, or variance. TeamOhana sits at the decision layer: it gives leaders self-serve visibility into their approved headcount, forecast, and variance, and routes every change back through finance approval. Finance keeps the forecast in FP&A. TeamOhana connects to it and gives the business a view they can actually use.

Does giving business leaders self-serve access mean finance loses control?

No. TeamOhana is access controlled, so the head of engineering only sees engineering headcount, and every change request routes through configurable approval workflows. Finance stays in the loop on every decision. The difference is that leaders come to finance already knowing whether they have budget, instead of asking finance to build them a spreadsheet to find out.

How does TeamOhana keep data in sync across the ATS, HRIS, and spreadsheets we use today?

TeamOhana has bidirectional sync with your systems of record, including Workday and Greenhouse. When a headcount is approved, the position is created in Workday and the job opening is created in Greenhouse. Offer details flow back from the ATS. That's how we replace the reconciliation spreadsheet with a single source of truth.

What is TeamOhana Computer and how does finance stay in control?

TeamOhana Computer is the decision layer that runs in Slack on top of your governed, unified headcount data. Any user can ask questions like "do I have room in my engineering budget for a 10K bump" or submit a change request without leaving Slack. It respects user permissions through ABAC, so leaders only see and act on roles they have access to. Every change still routes through your finance approval workflow and lands in a versioned audit trail.

Who owns TeamOhana internally: finance, HR, or talent?

All three. Finance uses it to manage budget, forecast, and variance. HR uses it for governance and policy on the approved plan. Talent uses it for prioritization, ready-to-hire flags, and ATS execution. That's the point: headcount decisions span all three functions, and TeamOhana is the shared workflow where they meet.