Every figure this model derived for SNYR, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2018-12-31
cash
292,115
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
6,344,924
AssetsCurrent
2026-03-31
current liabilities
6,848,786
LiabilitiesCurrent
2026-03-31
equity
-25,405,250
StockholdersEquity
2026-03-31
interest expense
6,850,754
InterestExpenseNonoperating
2026-03-31
ocf
-3,806,919
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
27,702,980
Revenues
2026-03-31
sbc
252,555
AllocatedShareBasedCompensationExpense
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
SNYR on one particular measure came for.
Ratio
Value
cash operating margin
-38.22
current ratio
0.93
current ratio reported
0.93
deferred revenue growth
-93.71
dilution pct
27.44
fcf margin
-13.74
interest cover
-1.6
operating margin
-39.61
owner earnings margin
-14.65
revenue growth
-17.53
revenue growth per share
-35.29
roic
-422.54
rule of 40
-57.14
sbc pct revenue
0.91
What to be careful about
What this model itself distrusts about SNYR's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2018-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
share count is from 2026-05-11 (111 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.
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