Travel Journal App | 12-Month Subscription Forecast

Travel_Journal_App_Subscription_Forecast_12M.xlsx — four editable sheets, all formulas live, every sheet labelled "Simulated data · Not real operations" (header badge, footers and chart titles).

Sheet guide

• Detail — shared drivers (monthly visits, sign-up rate, price, opening subscriptions) plus three full monthly blocks (Low / Baseline / High): visits → sign-ups → new paid subscriptions → opening → cancellations → ending subscriptions → monthly revenue, with an FY/Dec column and calculation-order footnotes.
• Definitions — the editable scenario table (paid conversion rate + monthly cancellation rate per scenario), shared drivers pulled from Detail, 14 metric definitions with their formulas, modelling conventions/limits and a cell legend (yellow = input).
• Summary — annual results by scenario (new subs, cancellations, ending subs, annual revenue, ARPU, net growth, revenue per visit), monthly ending-subscriptions and revenue matrices, and six model checks — all currently PASS.
• Dashboard — four baseline KPI cards, a scenario comparison table, and three trend charts: ending subscriptions by month, monthly revenue by scenario, and annual revenue by scenario (labelled axes, USD formats, data labels).

Baseline results (simulated): ending subscriptions 2,232 at Dec 2027 (Low 1,800 / High 2,664), annual revenue $152,331 (Low $134,441 / High $170,221). Only the paid conversion rate differs between scenarios (2.5% / 4.0% / 5.5%); cancellation is shared at 5.0%/month, so the comparison isolates conversion.

Verification performed: reopened the saved file — sheet roster, formulas, validations, freeze panes and 3 charts intact; 0 mismatches for 493 formula cells against an independent formula engine reading the file, and 0 mismatches against a separate recomputation from the raw assumptions; no #-error tokens; deterministic width/content audit shows no clipped or overlapped labels. Limit: no spreadsheet renderer (e.g. LibreOffice) exists in this Computer, so I could not produce pixel-level renders of the sheets — layout was verified by the deterministic width/content audit instead, not by visual rendering.