Every figure this model derived for STLY, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2024-12-31
cash
15,417,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
26,806,000
AssetsCurrent
2023-09-30
current liabilities
12,576,000
LiabilitiesCurrent
2023-09-30
equity
42,793,000
StockholdersEquity
2026-06-30
ocf
2,916,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
16,225,000
Revenues
2026-06-30
sbc
0
ShareBasedCompensation
2023-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
STLY on one particular measure came for.
Ratio
Value
cash operating margin
20.26
current ratio
2.13
current ratio reported
2.13
deferred revenue growth
-34.12
dilution pct
39.25
fcf margin
17.97
growth cv
1.7
operating margin
19.67
owner earnings margin
17.97
revenue growth
30.09
revenue growth per share
-6.58
roic
9.21
rule of 40
49.76
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about STLY's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2020-12-31, 2007 days before the revenue period (2026-06-30); dropped rather than divided by current revenue
no operating income tagged; derived as revenue minus OperatingExpenses
no current stock compensation tagged (last tagged 2023-12-31); treated as zero, so owner earnings are overstated
no current capital expenditure tagged (last tagged 2024-12-31); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
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 rests on 3 of 4 inputs; not tagged: contracted coverage