Frequently Asked Questions: An introduction to TeamOhana

About TeamOhana

  • TeamOhana is workforce management for human and digital workers. Finance and people teams use TeamOhana to plan headcount, manage positions, route headcount approvals and track AI spend against the same budget. TeamOhana connects to the company's HRIS, ATS and FP&A tools, so the approved workforce plan stays in sync across every system. TeamOhana was founded in 2022 and is based in San Francisco. The product description is a workforce planning and position management platform. Core modules: hiring plan, budget envelopes and variance tracking, scenario planning, position management, approvals, TeamOhana Computer (AI workforce agent) and AI Spend Management.

  • TeamOhana is used by CFOs and FP&A teams, CHROs and People Ops teams, talent acquisition leaders, and the department leaders who request and approve headcount. Customers include Scale AI, ElevenLabs, Decagon AI, Abridge AI, Reflection AI, Vanta, SeatGeek and EverPure. Above roughly 500 employees, people ops and TA ops teams run TeamOhana day to day and finance consumes the forecast. Department leaders and hiring managers get scoped access to request headcount and see their own plan. Most customers are high-growth technology and AI-native companies. TeamOhana also serves healthcare, biotech and financial services companies.

  • TeamOhana gives workforce decisions a governed home. Hiring, backfill and re-level decisions usually happen in spreadsheets and Slack threads before they reach the HRIS. TeamOhana replaces those spreadsheets with one workflow: request the role, approve it against budget, push it to the ATS and HRIS, and reconcile the hire back to the plan. Finance gets a live headcount forecast tied to a budget envelope. People and TA teams get one source of truth for approved roles. Leaders approve in Slack instead of chasing spreadsheet versions.

  • No. TeamOhana sits upstream of the HRIS and ATS. The HRIS stays the system of record for employees and the ATS stays the system of record for candidates. TeamOhana holds the approved workforce plan and pushes approved changes into HRIS positions and ATS jobs and openings. For Workday customers, TeamOhana creates and updates Workday positions after approval. Leaders who never log into the HRIS can request, approve and track headcount in TeamOhana or Slack.

  • No. TeamOhana is the execution layer for hiring managers, talent teams and HR, and FP&A tools model the full P&L. Most TeamOhana customers run both. TeamOhana feeds the line-by-line headcount forecast into Pigment and Workday Adaptive Planning, and into other FP&A tools by API or file export. TeamOhana covers total human-capital cost, not revenue or the P&L. Companies without an FP&A tool run scenario planning and budget envelopes natively in TeamOhana and export to spreadsheets.

  • TeamOhana supports companies from 150 to 10,000 employees and also helps very large enterprises. Pricing scales by employee count and every plan includes unlimited users.

Headcount planning and budgeting

  • In TeamOhana every planned role is a headcount record with a unique headcount ID. The ID is assigned when the request is drafted and locked at approval. The record carries department, level, location, target start date and budgeted compensation. After approval the headcount ID becomes the ATS opening ID and later links to the employee ID, which gives a three-way reconciliation of plan, ATS and HRIS. Hiring managers request new roles and backfills from a form or from Slack. Approved roles move into the hiring tracker for recruiting. Mismatches between plan, ATS and HRIS surface in a Needs Attention queue.

  • A budget envelope in TeamOhana is a top-down, not-to-exceed limit in dollars and heads that finance sets by company, division or department. Bottom-up headcount requests show their impact against the envelope, and the variance tracker compares budget, forecast and actuals. Toggle between fiscal-year impact and annualized impact so hire-date timing does not mask run rate. Use multiple budget envelopes for mid-year refreshes and compare the forecast against each. Separate envelopes work for contractors or other worker types. Budget envelopes are included in the platform fee.

  • TeamOhana applies configurable load factors to base and variable compensation. Load factors are set by division, department, location, category or employee type, so benefits, payroll taxes and social contributions can differ by jurisdiction. Base and variable pay sit in separate buckets, so commissions can carry their own load. Load factors are not set per individual employee today. Detailed general ledger splits such as EOR fees stay in the FP&A tool.

  • No. TeamOhana calculates the forecast line by line from annualized compensation, start dates, termination dates and load factors. It does not ingest payroll runs. Payroll forecasting and payroll-to-budget reconciliation stay in the FP&A or payroll system.

  • TeamOhana recommends a target start date for each open role using historical time-to-fill for similar roles and locations from the ATS. The recommender needs about three months of history or three similar roles, and defaults to 90 days without it. Users can override the date, and the offer start date replaces the target once an offer is made. Pushing a start date out can skip re-approval. Pulling a start date in requires a change request. TeamOhana Computer can bulk-update dates and flag roles at risk of missing their target.

  • In TeamOhana a backfill is created from the departing employee's record, before or after the departure date, and pre-populates role, level and compensation. The headcount ledger links each backfill to the person who left and the person who filled the seat. A terminated role can be marked ineligible for backfill with a note explaining why. Multiple backfills per departure are supported, for example splitting one role into two. Until the termination is recorded in the HRIS or TeamOhana, the forecast counts both the incumbent and the backfill. Backfills can follow a lighter approval policy than new roles.

  • Yes. TeamOhana supports custom employee types with hours per week, hourly, monthly or annual pay, and end dates. Each employee type can have its own budget envelope and its own approval flow. Interns convert to full-time employees through the internal transfer workflow. Per diem, locum and shift workers are configured the same way. Contractor planning is view-only on the vendor side. TeamOhana does not write requests into a VMS such as SAP Fieldglass or Beeline.

  • Yes. TeamOhana stores compensation in local currency and converts to USD using daily spot rates or rates the customer supplies. When a role's location changes, compensation and currency update automatically from the job catalog.

  • Yes. TeamOhana tracks equity per employee and per headcount in shares, units or dollars. Bonus percentage is part of the job catalog and recalculates when a role is re-leveled. Commission sits in the variable compensation bucket. Involuntary terminations can carry a severance amount, and backfill overlap cost is tracked.

  • No. TeamOhana works with job titles alone. Load pay bands where they exist and leave other roles blank. Requests for unbanded roles route to a compensation approver. Once a job catalog of role, level and location is loaded, TeamOhana fills compensation on every request automatically. Job levels can vary by team and can be renamed. Compensation data comes from the customer's own sources, such as Radford or Pave exports.

  • No. TeamOhana uses the customer's own job catalog and pay bands. Customers load benchmark data from providers such as Radford or Pave by file, and TeamOhana flags requests that fall outside band.

  • TeamOhana includes a predictive attrition and backfill-rate model for annual planning. Known departures are logged as future-dated terminations so the forecast reflects them on the exit date. A reconcile alert flags pending terminations that never happened. Notice periods are handled by entering a future-dated termination and creating the backfill early.

  • Yes. TeamOhana supports multiple hiring plans, and most customers start a new plan once a year. To move unstarted roles into a new plan, open a scenario, select the roles, move them and merge. An active plan is never locked. Changes run through a scenario and an approval.

Position management

  • Yes. TeamOhana has native position management. A position is a budgeted seat with its own ID and history, and a headcount request either fills an existing position or creates a new one. The position ID stays constant through backfills, so finance keeps one record of every seat over time. Position management is hybrid. Teams can track by seat or plan without positions. A position supports an end date and a next start date, so incumbent and backfill overlap reconciles automatically. For Workday customers, TeamOhana positions map one to one to Workday positions and TeamOhana writes approved changes back.

  • Yes. TeamOhana position management works with any connected HRIS. Finance loads position IDs, talent teams hire against open positions, and the HRIS sync marks positions filled. With Rippling and Ashby, TeamOhana owns the position ID and pushes it to Ashby as a custom field. ADP position IDs are visible in TeamOhana.

  • Yes, optionally. TeamOhana lets finance budget one full-time position that several shift or part-time workers fill. Companies that want strict one-to-one position control, as in Workday, can run it that way.

  • Yes. TeamOhana imports historical position IDs through a template. Teams can also start clean with active employees only and track positions going forward.

  • Most HiBob customers turn off HiBob position management after adopting TeamOhana. The TeamOhana headcount ledger tracks positions, backfills and roles marked ineligible for backfill. A position integration with HiBob is optional.

Headcount requests and approvals

  • TeamOhana routes every headcount request through an approval policy set by request type: new hire, backfill or change request. Conditions can use division, department, location, level, employee type, custom fields and percentage over pay band. Chains run sequentially, in parallel or as any-of, with unlimited approvers and notifiers. Example: route the CEO or CFO in only when compensation is more than 20% above band. Admins configure policies in Settings. Admin overrides are logged in the audit trail. Approvers can edit a request while it is in review.

  • Yes. The TeamOhana Slack app lets approvers approve, deny or comment on a headcount request directly in Slack. Comments sync back to the headcount record, so the paper trail stays complete. Email notifications are also available. Install the TeamOhana Slack app from the Slack Marketplace.

  • TeamOhana does not offer a Microsoft Teams app today. Approvals and notifications run through the TeamOhana Slack app, email and the web app.

  • Yes. TeamOhana auto-approval rules can approve a request when compensation falls within the pay band minimum and maximum, when it matches a specific location, or when it lands at specific job levels. Change requests below a set threshold, such as under 10%, can skip approval. Auto-approval on relative level changes, such as plus or minus one level, is not supported today.

  • Yes. With the budget-impact setting on, TeamOhana shows forecast and budget impact on new hire and backfill requests, including the approver's remaining budget. One-off change requests show the changed fields. Scenarios show the total impact of many changes at once.

  • TeamOhana private headcount hides a confidential role from everyone without explicit access. For those users the role does not appear anywhere in the platform. Access is limited to the requester, approvers in the private chain, collaborators, the reporting manager and recruiters linked after approval. Private headcount shows a padlock icon for users with access. Variance tracker totals can differ between users because private roles count only for users with access. The role stays private until the hire's start date. Private headcount passes to Greenhouse and Ashby as confidential.

  • Yes. Admins add custom fields, dropdowns and help text to the TeamOhana request form from Settings, and can make custom fields mandatory. Job titles can be restricted to the job catalog. Fields are the same across request types, and only the approval chain differs by type. Nested conditional questions are not supported. Use a naming convention with an N/A option instead.

  • Not automatically. TeamOhana admins can approve on behalf of another approver and can set a temporary approval policy for the absence.

  • Yes. TeamOhana sends automated approver reminders and configurable notifications by Slack and email. TeamOhana Computer can build a bottleneck report that shows which approvers hold the most pending requests.

  • Yes. TeamOhana keeps a full audit trail on every headcount record and every approval, including prior values, who changed them and when. History and comments stay on the record when a role is re-hired.

  • Yes. TeamOhana runs new role, change and backfill approvals, then writes approved changes to Workday positions. Workday business processes are mapped during implementation. Leaders approve in TeamOhana or Slack instead of logging into Workday.

Scenario planning and org design

  • A TeamOhana scenario is a sandbox copy of the live hiring plan. Leaders add roles, push dates out, pull them in, eliminate open roles, re-level roles and model terminations, and see the budget impact against the baseline and the budget envelope. Approval triggers when the scenario is merged into the live plan, not while leaders explore. Share a scenario with department leaders as limited editors to collect their needs. A master scenario rolls up every leader's plan and exposes duplicate requests. Approved scenario roles flow into the hiring tracker automatically.

  • Partly. TeamOhana scenarios model terminations and reporting manager changes for current employees, plus every change to open roles. Raises made in the HRIS flow into the forecast automatically. Moving existing employees between departments inside a scenario is on the roadmap.

  • Yes, through TeamOhana Computer. Upload ramp, quota or ratio assumptions and Computer builds a capacity model against live headcount and time-to-fill data. Examples include sales capacity, recruiter capacity, support staffing per customer and engineering ratios. Results can be sent to a scenario.

  • Yes. The TeamOhana org chart shows current employees plus future hires and terminations. In a scenario, leaders add roles, change managers and drag to reorganize. A team or pod view shows people who share a team but report differently, and the chart can be colored by employee type, department, tenure or compensation. Missing managers are flagged, never deleted. Monthly snapshots support historical and forecast org charts, for example for audit requests.

  • TeamOhana compares each scenario against the published baseline plan or the budget envelope. Direct scenario-to-scenario comparison is not available today.

  • In TeamOhana, keep contingent roles in tagged scenarios with future start dates and release them when the trigger happens. Positions are created only when the roles are released, so the live plan stays clean.

Reporting, forecasting and analytics

  • TeamOhana includes effective headcount reports for heads and cost by month or quarter, ending headcount variance, hiring burndown, gap analysis, recruiter progress, a change report and a variance tracker against budget. Every report exports. TeamOhana Computer adds reusable report recipes and custom dashboards. The variance tracker splits variance into hiring timing, pay differences and non-budgeted roles. The change report captures up-levels, department changes and compensation changes for any period.

  • Yes. TeamOhana sends scheduled reports as spreadsheet files by email. TeamOhana Computer can also refresh an interactive dashboard on a schedule and share it as a link.

  • TeamOhana exports any report to CSV or Excel, and the TeamOhana API feeds data warehouses such as Snowflake and BigQuery and BI tools such as Tableau. Live sync to Google Sheets is not available today.

  • Yes. TeamOhana keeps monthly snapshots of the plan, which support historical views and plan-versus-actual comparisons. The change report lists every change in a chosen period.

TeamOhana Computer, the AI workforce agent

  • TeamOhana Computer is an AI workforce agent that works on a company's reconciled HRIS, ATS and budget data inside TeamOhana. It answers workforce questions, builds reports and interactive dashboards, runs capacity and ratio models, and takes permitted actions on headcount records. TeamOhana Computer follows the same access controls as the TeamOhana platform. Example questions: how big will the sales org be in six months, which roles will miss their target start date, which hiring managers have unapproved requests. Saved prompts and skills make analyses reusable, and every user sees the same answer filtered by their access. Outputs include HTML dashboards, spreadsheets and slides that can refresh on a schedule.

  • TeamOhana Computer runs on Anthropic Claude models inside a TeamOhana harness that understands headcount data, approvals and access controls.

  • No. TeamOhana does not train models on customer data. Customer data stays in TeamOhana, prompts are processed and not retained for training, and AI use is covered by the customer's data processing agreement.

  • Yes. TeamOhana Computer uses the same role-based and attribute-based permissions as the TeamOhana platform, so each user sees only data they can already see. Artifacts follow the creator's access and are shared only explicitly.

  • TeamOhana Computer runs in Slack and in the TeamOhana web app. Hiring managers get permission-scoped access in the company's own Slack workspace.

  • TeamOhana Computer takes permitted actions. Approvals already work in Slack, and Computer can bulk-update target start dates and assign recruiters. Computer confirms before acting and logs each action in the record history as performed by TeamOhana Computer.

  • TeamOhana Computer is built for workforce planning. It already holds normalized HRIS, ATS and budget data, knows the org structure, approval chains and permissions, and can act on headcount records. General-purpose assistants need MCP connectors stitched together, have no headcount access controls, and can return different answers to the same question. Customers own the outputs Computer produces.

  • Yes. TeamOhana offers an MCP server that inherits TeamOhana permissions, so a company's own AI assistant sees only data the user can see.

  • TeamOhana Computer is an optional per-seat add-on. Tokens are included with no usage limits, and Computer does not use the customer's own Claude or OpenAI subscription. People who view a shared Computer report do not need a seat. Admins manage seats in Seat Management, with a licensed pool and an uncapped limited-trial pool. A paused seat keeps its history for 30 days.

AI Spend Management and digital workers

  • TeamOhana AI Spend Management shows a company's AI spend in one place and attributes it to employees, agents and departments. It connects to AI providers through read-only billing and usage APIs and tracks spend against a forecast. Because TeamOhana already holds employee and department data, AI spend can be measured alongside payroll. Spend is auto-claimed by matching employee names or emails. The rest is assigned to an employee or agent in the AI Spend Classifier. TeamOhana does not show employee compensation in AI Spend Management. Existing compensation permissions still apply.

  • TeamOhana AI Spend Management connects to Anthropic, OpenAI and Cursor. Any other provider or AI gateway can be added as a custom provider with a CSV template. Connecting a gateway alongside the provider it routes to can double-count spend. Custom provider files need periodic re-upload because they do not sync automatically.

  • No. The OpenAI and Anthropic admin APIs work on team plans, and spend from any plan can be uploaded by CSV.

  • No. TeamOhana AI Spend Management uses read-only credentials and reads billing and usage data only. It never reads prompts, completions, conversations or code.

  • No. TeamOhana AI Spend Management operates under the customer's existing TeamOhana data processing agreement and TeamOhana's SOC 2 Type II certification.

  • Each AI provider takes about 20 minutes to connect. An IT admin goes to Settings, then Integrations, and adds a read-only billing API key. Data appears once at least one provider or custom spend file is connected.

  • Admin and IT Admin roles see AI spend by default. Other roles get one of four view tiers: View Own, View Reporting Line, View All and View All (Unrestricted). The first three respect attribute-based access controls. Managing providers and classifying spend are separate permissions.

  • No. AI Spend Management is included for TeamOhana customers at no additional cost.

  • TeamOhana ties AI spend to the people and departments it belongs to. TeamOhana already holds employee, department, cost center and compensation data, so it reports AI spend as a percentage of payroll per employee, department and cost center. A spend tool sees the invoice but not the org chart behind it.

  • A digital worker in TeamOhana is budgeted AI capacity that does work that would otherwise be a role. A digital worker can span several agents and API keys. Companies budget a digital worker the same way they budget a human worker: define the work, set the spend, get it approved, and TeamOhana tracks actuals from every API key and gateway. Copilot seats and developer tooling stay software spend. Spend becomes a digital worker when it is budgeted against work that would otherwise be a role. Adjusted FTE in TeamOhana is a cost-side capacity measure, not a productivity claim.

HRIS integrations

  • TeamOhana integrates with Workday, Rippling, HiBob, BambooHR, ADP Workforce Now, UKG Pro, SAP SuccessFactors, Oracle HCM, Namely, Deel, Justworks and Personio. HRIS platforms without a standard connector connect through SFTP flat files or the TeamOhana API. A single HRIS has no connector fee. Switching HRIS later carries a small one-time implementation fee.

  • TeamOhana connects to Workday through an Integration System User with domain security permissions. TeamOhana reads workers, organizations and positions, and writes approved changes back to Workday positions. A RaaS report gives the customer control over position columns and filters. Workday Recruiting works with either positions or requisitions. No Workday consulting resources are required. Implementation and sandbox Workday tenants sync more slowly than production.

  • TeamOhana syncs Workday changes every few hours, and approved TeamOhana changes write back to Workday positions.

  • Rippling does not offer a write API, so TeamOhana uses a report-based integration. Rippling Workflow Studio sends an employee roster report and a change history report to a secure TeamOhana inbox on a schedule, and TeamOhana validates and ingests them automatically. Employee ID is the primary key. The integration is one-way from Rippling to TeamOhana. Mismatches such as a promotion not yet entered in Rippling are flagged for reconciliation.

  • TeamOhana reads employee, organization and compensation data from HiBob every few hours. Setup takes about 45 minutes in a connect-and-map session. The integration is read-only, and HiBob stays the system of record for employees.

  • Yes. TeamOhana has a native ADP Workforce Now integration and is listed in the ADP Marketplace. ADP does not charge customers for the integration. TeamOhana also supports a daily ADP SFTP sync.

  • TeamOhana writes approved position changes back to Workday. For Rippling, HiBob, BambooHR and UKG, TeamOhana reads from the HRIS and the HRIS stays the system of record. Hires flow into the HRIS through the ATS or the HRIS's own process.

  • Yes. Subsidiaries not yet in the main HRIS load into TeamOhana by scheduled file. A second HRIS dataset uses a custom connector, which carries a one-time fee.

ATS integrations

  • TeamOhana integrates with Greenhouse, Ashby, Lever, iCIMS and SmartRecruiters. Greenhouse and Ashby integrations create jobs and openings from approved headcount and sync offers back to TeamOhana.

  • TeamOhana creates Greenhouse jobs and openings from approved headcount, and the TeamOhana headcount ID becomes the Greenhouse opening ID. Offer data syncs back to TeamOhana about every 30 minutes, so finance sees offer-level variance. Private headcount passes to Greenhouse as confidential. One job can hold multiple openings, each linked to its own headcount. Level and compensation changes should start in TeamOhana and flow to Greenhouse.

  • TeamOhana creates Ashby jobs and openings from approved headcount and maps role, level, compensation and custom fields. Offers sync back to TeamOhana about every 30 minutes. Recruiter changes and closed roles in TeamOhana update the Ashby opening. Openings are created as drafts by default. Ashby was TeamOhana's first ATS integration partner. Comp changes made directly in Ashby do not trigger TeamOhana approvals, so make them in TeamOhana.

  • Yes, with manual linking. The iCIMS API is limited, so recruiters link iCIMS jobs and offers to TeamOhana headcount. Some customers automate the step with the TeamOhana API.

  • Yes. TeamOhana creates one headcount per opening, so four approved heads under one job description become four openings on the same ATS job. Evergreen and pipeline jobs are supported.

FP&A, finance and data integrations

  • Yes. TeamOhana pushes the headcount forecast to Pigment through a connector and a scenario API that sends one transaction list per scenario. The TeamOhana headcount ID is the join key. The integration is one-way, so edits happen in TeamOhana. Do not pull ATS data into Pigment separately. Use TeamOhana as the single source.

  • Yes. TeamOhana pushes forecast data to Adaptive Planning through an API push, SFTP or CSV. TeamOhana sends compensation components such as base, bonus, commission and equity, and Adaptive applies its own load logic. Budget targets can flow from Adaptive into TeamOhana at department level.

  • TeamOhana feeds Anaplan, NetSuite Planning and Budgeting and Oracle EPM through the TeamOhana API or a scheduled flat file over SFTP. The file is a clean roster of current, departing and to-be-hired people with the fields the model needs.

  • Yes. The TeamOhana API exposes historical, current and future headcount data, forecast data and scenario data, scoped to the integration user's permissions and including custom fields. SCIM handles user provisioning. API documentation lives at api.teamohana.us.

Slack, SSO and user provisioning

  • Yes. Microsoft Entra ID and Google Workspace sign-in work out of the box. Okta SAML, Okta OIDC and Azure identity providers are supported and set up with the customer's IT team.

  • Yes. TeamOhana supports SCIM through Okta. Assigning the TeamOhana app to a user provisions them, and unassigning deprovisions them. A TeamOhana Role attribute in Okta sets the user's role, such as hiring manager.

  • No. Leaders can request, approve and comment on headcount from Slack, and TeamOhana Computer seat holders can ask workforce questions there too. Core TeamOhana pricing is not seat-based, so every leader can be a user at no extra cost.

Security, privacy and compliance

  • Yes. TeamOhana is SOC 2 Type II certified and ISO 27001 certified. TeamOhana shares SOC 2 and ISO reports, a security one-pager and an AI fact sheet during security review, and signs a data processing agreement with every customer.

  • TeamOhana hosts customer data in the United States on AWS.

  • TeamOhana combines role-based access with attribute-based access by department, location, level and job category. Compensation and equity visibility are separate permissions, and users without comp access see only rolled-up totals. Sensitive fields can be hidden down to the column level. Leaders automatically see everyone in their reporting line, for example through the Workday supervisory org. Recruiters can see budget without seeing employee compensation.

  • Yes. TeamOhana admins can impersonate a user to troubleshoot visibility. Impersonation is view-only and times out after 10 minutes.

Implementation and support

  • Most TeamOhana implementations take 4 to 6 weeks. ElevenLabs went live in 4 weeks. Workday customers adding position management typically take 8 to 12 weeks because of Workday write access and position mapping. A typical 4-week plan: week 1 maps the HRIS and ATS, weeks 2 and 3 configure permissions and approvals, weeks 3 and 4 cover testing and change management. TeamOhana can start mid-planning-cycle by loading the existing spreadsheet plan.

  • TeamOhana does not offer a self-serve sandbox, because a sandbox without the customer's data shows little. Instead, a TeamOhana solutions consultant runs a guided demo on the customer's use cases, and TeamOhana Computer offers pilot seats.

  • Every TeamOhana customer gets a dedicated customer success manager, an implementation team and a shared Slack channel with the TeamOhana team, plus ticketed support and quarterly business reviews.

  • No. TeamOhana roles are preconfigured, users provision through SSO and SCIM, and custom fields are self-service. People Ops usually administers TeamOhana, and finance holds admin access.

Pricing and packaging

  • TeamOhana is priced per employee per month based on company headcount, billed annually with a true-up. Every plan includes unlimited users with no seat licenses for the core platform. A one-time implementation fee covers setup. TeamOhana Computer is an optional per-seat add-on with tokens included. AI Spend Management is included. The compensation cycle module is a separate add-on. Multi-year agreements are available, and TeamOhana can be purchased through the ADP Marketplace.

  • Yes. Contractors and freelancers tracked in TeamOhana count as employees for pricing. Large worker populations that TeamOhana does not plan, such as hourly field staff, can be excluded.

Comparisons and alternatives

  • Workday is a system of record: stable, auditable and slow to change. Headcount decisions need to be fast and iterative. Workday can build headcount approvals through its business process framework, but customers pay consultants to build them, HRIS teams to maintain them, and managers still route around them in Slack. TeamOhana runs the decision workflow and writes approved changes into Workday positions.

  • Most TeamOhana customers on Pigment run both. Pigment models the financial plan. TeamOhana runs the headcount workflow that feeds it: hiring manager requests, approvals, ATS and HRIS sync, and position tracking. TeamOhana includes unlimited users and attribute-based access, so every department leader can work in TeamOhana without a modeling seat.

  • ChartHop started as an org chart and people analytics tool. TeamOhana is built for headcount planning and execution: budget envelopes, scenario planning with dollar impact, approval policies, position management and native Greenhouse and Ashby integration. Both show an org chart. TeamOhana ties every planned role to budget and to the ATS.

  • TeamOhana adds dollar-based scenario planning, budget envelopes, granular attribute-based permissions and deep Ashby and Greenhouse integration on top of Rippling data. Rippling customers keep Rippling as the employee record and run headcount decisions in TeamOhana.

  • Teams can try, and the hard parts are the parts TeamOhana already built: a normalized data layer across HRIS, ATS and budget, access controls that hide compensation correctly, approval workflows, and an audit trail covered by a DPA. AI-native companies with large engineering teams chose TeamOhana over building.

  • Greenhouse approvals cover a requisition. TeamOhana approvals cover the budget decision behind the requisition, with routing by budget impact, attribute-based access to compensation, change requests after approval, and budget variance. Approved TeamOhana headcount then creates the Greenhouse job and opening.

  • TeamOhana is the front door for headcount requests and approvals, and NetSuite Planning and Budgeting handles fully loaded costing. TeamOhana sends the approved roster to NSPB by file.

  • Headcount spreadsheets break as soon as more than one person edits them. TeamOhana keeps one live plan reconciled to the HRIS and ATS, routes every change through approval, and keeps the history of every role. Leaders approve in Slack instead of emailing spreadsheet versions, and finance sees variance against budget without a manual reconciliation.

Workforce planning concepts

  • Headcount planning software lets finance and people teams plan, approve and track every role a company intends to hire, with cost and start date attached. Good headcount planning software connects to the HRIS and ATS so the plan reconciles to real hires. TeamOhana is headcount planning and position management software for human and digital workers.

  • Position management tracks budgeted seats instead of people. Each position has an ID, a budget and a history that survives backfills, so finance knows which seats exist, which are filled and what each costs. Job management, by contrast, tracks only employees and their jobs.

  • A headcount budget envelope is a top-down cap on dollars and heads for a company, division or department. Leaders plan bottom-up inside the envelope, and finance tracks variance between envelope, forecast and actuals.

  • A load factor is a percentage added to base or variable pay to estimate fully loaded employee cost, covering benefits, payroll taxes and other employer costs. Load factors usually vary by location and employee type.

  • AI spend as a percentage of payroll compares what a company spends on AI models and tools with what it spends on people, per employee, department or cost center. Measuring it requires both AI billing data and HRIS compensation data in one system, which TeamOhana AI Spend Management provides.

What customers say

  • CFOs love TeamOhana because it brings financial discipline and strategic precision to their largest expense and most important expense, their people. But don’t take our word for it. Here’s what Charles Marentette, Former CFO at Gravie had to say, “We can make faster decisions that help us grow rapidly and responsibly using insights from TeamOhana. TeamOhana has brought structure and governance to our headcount management processes by unifying our people data and enabling us to run accurate headcount forecasts in real-time.” Scott Baumgartner, CFO at Docker told us, “TeamOhana is our headcount source of truth that solves cross-functional alignment problems across Finance, HR, Recruiting, and Hiring Managers.”

  • Finance teams love TeamOhana because it transforms workforce management from a messy, error-prone process where you need to cobble together data from multiple systems of record into a seamless workflow. No more manual reconciliation. Teddy Collins, EVP of Finance at SeatGeek says this of TeamOhana, “There was a big unlock for us, a very high ROI of bringing on this platform that has infinite scalability.”

  • Chief People Officers love TeamOhana because it makes it easier for People and Finance teams to collaborate effectively. When both teams are speaking the same language, headcount decisions and hiring plans can be easily aligned with budgets, so everyone can meet their strategic goals. As Tracie Akers, CPO at Metronet explains, “TeamOhana has made us much more budget-conscious as we grow. We’re adding hundreds of employees every year, but now we’re finding ways to do it responsibly and strategically.”

  • HR, Talent, and People teams love TeamOhana because it was purpose-built for cross-team collaboration. When everyone can collaborate in a single platform protected with access controls so employee data is accessible only to those who need it, everyone can focus more on strategy instead of wasting time reconciling data and wrangling spreadsheets. As Emily Sung-Simon, Senior Recruiting Operations Manager at Postman says, “With TeamOhana, TA teams can now participate in strategic conversations and organizational mapping.”

Maximize every dollar spent managing headcount

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.