Mechanical January-to-July change from endpoint values; not independently audited here.
Public-source data-product sample • captured 18 July 2026 AEST
Do not turn open metrics into a directory. Turn them into an auditable change ledger.
A founder-readable LaunchReady sample showing how to preserve raw values, mark missing fields, explain derived changes, and avoid implying that a public company is for sale.
One official endpoint, seven observed rows
Source: https://ente.com/api/open-data. Captured 2026-07-18 20:31 AEST. The API returned monthly dates, registered accounts, paid accounts, and MRR from January through July 2026.
Observed endpoint values with a derived percentage.
A derived ratio only. Do not relabel it ARPU, price, margin, or customer quality without a published definition.
Field completeness is part of the product
Observed values
metric_date, registered_accounts, paid_accounts, mrr.
Definition metadata
Currency/unit, exact metric definitions, restatement/version flag, and schema version.
Business-quality fields
Costs, profit, churn, retention, CAC, acquisition status, and seller intent.
“Missing in payload” means only that the captured API response did not contain the field. It does not claim the company has never published the information elsewhere.
The founder-readable five-bullet review
1
Preserve source truth before analysis
Store the source URL, capture timestamp, reporting date, raw value, and extraction status. Keep raw rows separate from derived percentages and editorial labels.
2
Make missingness explicit
Do not model-estimate currency, definitions, profit, retention, or acquisition intent. Use missing, link any separate source, and let buyers see the evidence gap.
3
Separate momentum from availability
A changing public metric can justify a watch item. It does not show that the company is for sale, welcomes contact, or meets an acquisition criterion.
4
Version the comparison rules
Show source cadence, rounding, period selection, schema changes, and corrections. Alert readers when a definition or publication pattern changes instead of presenting a false continuous series.
5
Sell verification and change detection
The paid wedge is a source ledger, completeness score, material-change alert, and custom watchlist—not another startup directory, valuation model, or “hidden deal” claim.
A$149–299 Public-source Data Product Readiness Review
One landing page plus one sample ledger or alert, returned in 48–72 hours with a source schema, missing-field policy, change-card template, claims edits, pricing/CTA teardown, and next-distribution queue.
One landing page plus one sample ledger or alert, returned in 48–72 hours with a source schema, missing-field policy, change-card template, claims edits, pricing/CTA teardown, and next-distribution queue.
Build a free three-observation requestSee request → delivery exampleView the broader signal-product sample
Boundary: public or explicitly supplied redacted evidence only. No valuation, investment recommendation, acquisition advice, company-contact automation, source-accuracy certification, private-data access, or guarantee of a deal, reply, return, or complete market coverage.