Every figure this model derived for ZEO, 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-06-30.
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
822,690
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
2,451,981
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
19,617,068
AssetsCurrent
2026-06-30
current liabilities
12,562,842
LiabilitiesCurrent
2026-06-30
equity
9,263,661
StockholdersEquity
2026-06-30
interest expense
198,484
InterestExpenseNonoperating
2026-06-30
ocf
-5,455,775
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
71,818,720
Revenues
2026-06-30
sbc
4,423,375
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
ZEO on one particular measure came for.
Ratio
Value
cash operating margin
-7.89
current ratio
1.59
current ratio reported
1.56
deferred revenue growth
19.31
fcf margin
-8.74
interest cover
-60.06
operating margin
-16.6
owner earnings margin
-14.9
revenue growth
10.17
revenue growth per share
10.17
roic
-54.92
rpo growth
-41.73
rule of 40
-6.43
sbc pct revenue
6.16
What to be careful about
What this model itself distrusts about ZEO'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 2025-03-31 (517 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
gross profit not tagged; rebuilt from Revenues - CostOfRevenue
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
durability DROPPED from the total: only 2 of 4 inputs could be computed (worst year, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 2 of 4 inputs could be computed (sustained growth, margin trend not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left