Clarity over features
Every screen answers the question in front of the user. A manager submitting a requisition should not need training. A finance lead pulling a cost report should not need an analyst sitting next to them.
About FTE Tree
Almost every organization has an HRIS and a general ledger. Almost none have a single source of truth for their positions. FTE Tree fills that gap.
The problem we saw
We kept watching capable organizations lose hours and real dollars to the same pattern: position data scattered across HR, Finance, and department managers, each with a private spreadsheet and a private definition of what counted.
Vacancies disappeared the moment a row was deleted. Approval chains lived in email threads nobody could audit. Forecasts drifted from reality because reality had too many authors. A simple question, how many funded positions do we have and what will they cost next quarter, routinely took a week to answer, and the answer routinely changed.
A position is a concrete thing: a funded slot with an FTE, a wage, and a home in the org. Treat it as a first-class record and the hard questions answer themselves.
FTE Tree exists because that work should not be hard. Give every stakeholder the same view, attach the rules your organization already runs on, and the scattered spreadsheets quietly go away.
What we believe
Every screen answers the question in front of the user. A manager submitting a requisition should not need training. A finance lead pulling a cost report should not need an analyst sitting next to them.
Your approval chain already exists. Software should trace it, not replace it with a generic workflow. We model thresholds, delegation, and escalation because you already do.
Position control should not require a seven-figure implementation. We charge per position, not per seat, so every stakeholder who needs the truth can log in and see it.
The team
FTE Tree is built by people who have run these processes inside schools, municipalities, and growing companies. We stay small on purpose, so the person who writes the code is the person who answers the phone.