How ZOZOFIT launched mobile subscriptions on a tight timeline
ZOZOFIT is an at-home body-management app that builds a detailed 3D body rendering, measures more than 12 body locations, charts change over time, and estimates body-fat percentage.
This page explains the launch decision, the build-versus-buy trade-off, and the growth and support work planned after launch, in a form the owner can verify before publication.
What ZOZOFIT does
The app's core promise is measurement without a store visit: a phone-based 3D model, measurements across more than 12 locations, trend graphs, and an estimated body-fat percentage. That framing matters for subscriptions because the value is ongoing tracking and comparison, not a one-time scan. Before writing subscription copy, confirm the current feature set, the paywalled versus free boundary, and the exact measurement claims with {{OWNER_CONFIRM_FEATURES_AND_CLAIMS}}.
The launch constraint: first subscription, short deadline
ZOZO, Inc. — described in the captured material as the operator of Japan's fashion shopping site ZOZOTOWN, with the app provided by ZOZO Apparel USA, Inc. — was entering mobile subscriptions for the first time. The team had months, not years, to ship. No one in the company had previously worked on subscriptions, and the team expected edge cases around administration, refunds, and store-specific behaviour to create ongoing headaches if built internally. The practical lesson is to audit internal subscription experience before estimating an in-house build: missing experience is a schedule risk, not just a staffing gap.
How the platform decision was made
The team compared options on three criteria: reputation in the subscription space, demonstrated expertise, and ease of implementation. Clear documentation and responsive support were treated as evidence of expertise, not as extras. Weekly calls and a shared messaging channel were used during implementation, and the lead iOS developer reported the documentation was easy to follow in practice. Use this as a vendor checklist: ask for documentation quality, named support responsiveness, and a reference implementation timeline before committing.
After launch: acquisition, paywalls, and support
The app launched in January 2024. After launch, the planned growth work falls into three buckets. First, attribution integrations with Adjust and Facebook to connect subscription events such as trial starts, subscriptions, and cancellations with media source, campaign, and keyword data for reporting, supporting KPIs like downloads and trial starts. Second, paywall work: remotely configurable templates, audience-based targeting with dynamic pricing and packaging, and A/B experiments with full-funnel analytics. Third, support: a customer-level view combining cross-platform usage and a purchase timeline so support can diagnose what happened before replying, including granting promotional subscriptions where appropriate.
Decision checklist for a first subscription launch
Use this checklist to decide whether a first-time subscription team should build or buy: 1) Is anyone on the team experienced with store subscription edge cases? 2) Is the launch window measured in months? 3) Can the vendor show clear documentation and a support channel with timely replies? 4) Can subscription events flow to attribution and analytics without custom plumbing? 5) Can paywalls be targeted and tested without an app release for every change? 6) Can support see a unified purchase timeline across platforms? If most answers are no, an external platform reduces schedule and maintenance risk.
| Decision area | What to check | Why it mattered here |
|---|---|---|
| Internal experience | Has anyone shipped subscriptions before? | No prior subscription experience was reported, raising in-house risk. |
| Timeline | Can the team ship in months? | A short launch window favoured an existing platform. |
| Documentation and support | Is guidance clear and are questions answered promptly? | Documentation clarity and timely replies built developer confidence. |
| Attribution | Do trial, subscription, and cancellation events reach marketing tools? | Planned integrations with Adjust and Facebook were intended to support downloads and trial-start KPIs. |
| Paywall testing | Can pricing, packaging, and placement vary by audience and be A/B tested? | Targeting and experiments were planned for paywall optimisation. |
| Support visibility | Can support see cross-platform usage and purchase history together? | A customer-level timeline was planned to speed diagnosis. |
Captured account evidence; owner confirmation required before publication.