Every figure this model derived for HURN, the value it took, and
the element in the company's own XBRL it was read from — so any of it can be checked
against the filing rather than taken on trust.
As at 2026-03-31.
The figures, and where each came from
This is the part no other screener shows. Each figure below names the XBRL element it
was read from, so it can be checked against the filing itself.
Figure
Value
XBRL tag
As at
capex
14,267,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
26,459,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
514,742,000
AssetsCurrent
2026-03-31
current liabilities
232,174,000
LiabilitiesCurrent
2026-03-31
equity
397,440,000
StockholdersEquity
2026-03-31
interest expense
34,300,000
InterestPaidNet
2025-12-31
ocf
138,053,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
1,746,769,000
Revenues
2026-03-31
sbc
46,847,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HURN on one particular measure came for.
Ratio
Value
cash operating margin
15.14
current ratio
2.57
current ratio reported
2.22
deferred revenue growth
12.66
dilution pct
-3.34
ebit cagr
20.43
ebit yoy
0.44
fcf margin
7.09
growth cv
0.49
interest cover
5.32
net debt ebitda
3.81
operating margin
10.44
owner earnings margin
4.4
revenue growth
11.79
revenue growth per share
15.66
roic
11.76
rpo growth
43.48
rule of 40
22.23
sbc pct revenue
2.68
What to be careful about
What this model itself distrusts about HURN's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-28 (124 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
gross profit not tagged since 2020-12-31; rebuilt from Revenues - CostOfGoodsAndServiceExcludingDepreciationDepletionAndAmortization - dep_amort
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions