high high likelihood
R-001: Opaque financial statements and unit economics
Public sources do not disclose audited financials, current ARR, margins, burn, cash, backlog or AR aging.
Diligence request: Request audited/management financials, KPI definitions, revenue waterfall, cash runway, debt, backlog and AR aging.
high medium likelihood
R-004: Security, privacy and compliance exposure
Remote access products handle privileged access and telemetry; public compliance claims require NDA evidence testing.
Diligence request: Review SOC 2, ISO scope, pen tests, incidents, DPAs, subprocessors and security roadmap.
high unknown likelihood
R-002: Unknown customer concentration and retention
Logos and aggregate user claims do not reveal revenue concentration, active contract status, churn or expansion quality.
Diligence request: Request top-customer revenue, cohorts, NRR/GRR, contracts, renewal pipeline and references.
high unknown likelihood
R-007: Cap table, preference stack and debt opacity
A long financing history and unicorn round are public, but ownership, preference stack, options, warrants, debt and rights are not.
Diligence request: Request charter, cap table, stock ledger, option ledger, debt schedule, side letters and board minutes.
medium high likelihood
R-003: Competitive pricing and substitution pressure
Splashtop positions on price/value against TeamViewer/LogMeIn/AnyDesk and competes with VPN/RDP/VDI substitutes.
Diligence request: Review win/loss, discounting, churn reasons, sales productivity and competitor quotes.
medium high likelihood
R-010: Stale public growth metrics
The strongest operating metrics are from 2020/2021 and may not describe current post-pandemic demand or margins.
Diligence request: Obtain quarterly KPI trend through current month, cohort retention, bookings, pipeline and segment growth.
medium medium likelihood
R-005: Product expansion and integration execution risk
AEM, Foxpass, Secure Workspace, endpoint security and legacy lines broaden platform scope without public adoption/economics.
Diligence request: Request SKU adoption, roadmap, integration plans, support tickets, defect backlog and product margin.
medium medium likelihood
R-006: Cloud and third-party dependency concentration
AWS and integrations/providers are important to delivery; spend, commitments, redundancy and incidents are not public.
Diligence request: Request vendor contracts, subprocessor list, architecture/resilience evidence, SLAs and cost sensitivity.