# DEC-51 web2app benchmark recommendations for Opal

Generated: 2026-05-06
Task: review the existing web-to-app benchmark breakdowns, keep the screenshots, and extract design recommendations for the Opal web funnel, especially landing page, reinforcement, social proof, plan/paywall, and checkout paths.

## Evidence used

Primary source:
- Figma board: `5 Web-to-App Examples`, file `trdPEQFNv7bfqCp0mO9GdQ`, last modified `2026-01-13T12:07:22Z`.
- Exported boards: Calm, Blinkist, PlantIn, YNAB, Photoroom.

Supplemental source:
- Existing DEC-51 Opal captures: 115 screenshots across `screentime`, `families`, and `2026` funnels.
- Existing full BetterMe and Headway captures: 87 screenshots.
- This run's live exploratory crawl for Noom, Simple, MadMuscles, FitMe, Nebula, Hint, Babbel, YNAB, Photoroom. These are useful directionally, but several flows hit repeated-state or bot-gate limits, so I did not over-weight them.

Artifacts:
- Persistent artifact directory: `/Users/m1/december/kanban-artifacts/DEC-51-web2app-benchmark-recs`
- Figma board screenshots: `figma-boards/`
- Selected evidence screenshots: `selected-screens/`
- Contact sheets: `figma-boards-contact-sheet.jpg`, `selected-screens-contact-sheet.jpg`
- Raw Figma outline and live crawl summary: `raw/`

## The core read

Opal already has the hard part: a long diagnostic sequence, emotional reframes, loaders, testimonials, plan reveal, paywall, and handoff. The gap is not that Opal needs more quiz screens. The gap is that the funnel still behaves like one canonical onboarding sequence instead of a set of acquisition paths that preserve user intent from the first click through the paywall and app handoff.

The strongest competitor pattern is not length. It is continuity.

Ad or SEO intent leads to a narrow promise. The landing page repeats that promise. The questions collect only data that changes the plan. Reinforcement appears immediately after shame-sensitive answers. Social proof matches the user's branch. The paywall repeats the generated plan. Checkout restates the exact subscription terms. The app handoff carries the plan into the installed product.

Opal should move from `quiz that persuades` to `plan builder that converts`.

## What each benchmark contributes

### Calm

Structure observed:
- Segment first: sleep, stress, focus, self-improvement.
- Ask broad emotional question, then cause, then symptom, then timing and content preference.
- Insert reassurance after vulnerable answers.
- Use contextual testimonials after pain disclosure.
- Ask for account late to save preferences.
- Use simple trial checkout with limited plan choice.
- Use exit discount after abandonment.

Useful for Opal:
- Branch by goal at the landing page: focus at work, studying, bedtime scrolling, less social media, presence with family, ADHD support.
- After a user admits loss of control, answer immediately: “That makes sense. These apps are designed to pull you back. Opal adds friction where willpower breaks.”
- Add a strictness or pace selector: gentle, balanced, strict, full reset.
- Use final proof immediately before account or paywall.

Avoid:
- Generic testimonials reused across branches.
- Discount popups that train users to abandon checkout.
- “Personalized plan” language without a visibly personalized plan.

### Blinkist

Structure observed:
- Paid ad uses a famous-person or cultural hook.
- Article landing page expands the ad topic before pitching the product.
- CTAs are contextual to the article.
- Account capture appears inside or after content interest.
- Mobile uses sticky app CTA.
- Pricing follows after account creation.

Useful for Opal:
- Build editorial or SEO acquisition surfaces, not only app landing pages.
- Examples: “I blocked TikTok before noon for 7 days”, “Why app limits fail”, “How to stop scrolling at night”, “Best app blocker for students”, “How to block Instagram on iPhone”.
- CTA should match the page: “Build my study focus schedule”, “Create my bedtime block”, “Calculate my distraction cost”.
- Mobile should keep one persistent app/action CTA, but not a noisy stack of CTAs.

Avoid:
- Fake endorsement by public figures.
- Clickbait content that does not naturally lead to Opal.
- Too many competing CTAs on the same page.

### PlantIn

Structure observed:
- Paid ad leads to a dynamic bridge page.
- Mobile users are pushed toward app install.
- Desktop users land on a homepage with QR code, app badges, trust stats, feature modules, media logos, and SEO/database pages.
- Web account creation and web-discount paywall follow.
- Checkout appears as a modal with benefit recap.

Useful for Opal:
- Device-aware routing is mandatory: iPhone to App Store/deep link, desktop to QR/SMS/email plus web plan builder, Mac/Chrome to relevant platform route.
- Desktop landing should not be a dead end. It needs a QR code, SMS/email handoff, app badges, and a “continue on web” path.
- Build high-intent pages around specific jobs: block TikTok, block apps at night, focus app for ADHD, app blocker for students, reduce screen time, stop doomscrolling.
- If web pricing is cheaper, say why clearly: “Best price available on web” or “Save when you start on web.”

Avoid:
- Close buttons that redirect anyway.
- Sending paid traffic to a generic homepage when the ad promised a specific use case.
- Confusing duration-based plans like 7-day, 90-day, 365-day access unless there is a real strategy.

### YNAB

Structure observed:
- Free workshops and tailored landing pages create trust before monetization.
- Landing pages match specific anxieties, for example ADHD and money stress.
- Trial is low-friction: 34 days, no payment details.
- Onboarding starts with easy identity/context questions, then moves into personal topics.
- Debt or shame-sensitive answers trigger immediate reassurance.
- App mention comes later, after a multi-part setup creates motivation.
- Setup ends with progress and celebration.

Useful for Opal:
- Opal can use educational lead magnets: 5-day phone reset, focus audit, doomscrolling workshop, bedtime reset, ADHD focus setup.
- Start softer than “how addicted are you?” Use: name, main goal, when distraction hurts, which apps pull you in, what has failed before, desired strictness.
- Make every question operational. If it does not change the plan, proof, paywall, or app setup, do not ask it upfront.
- Consider a no-card activation path for some segments: plan first, install, first block, then paywall.

Avoid:
- Delaying app mention so long that the required install feels like a bait-and-switch.
- Asking many context questions that feel like company research rather than setup.

### Photoroom

Structure observed:
- Tool-first SEO entry, especially background remover.
- User receives free value before account creation.
- Account gate appears only when the user wants advanced editing.
- Onboarding segments by commercial intent: personal, business, clients, teams, product volume, ecommerce platform, brand import.
- Team invite is prioritized for business users.
- Paywall uses Pro trial, monthly/annual options, consistent benefit list.
- Checkout is excellent: due today, trial dates, future charge date, renewal amount.

Useful for Opal:
- Build a free utility before account or paywall: Focus Plan Builder, Distraction Cost Calculator, Bedtime Block Builder, App Block Schedule Builder.
- Let the user see a concrete output before gating.
- Segment by user type only where it changes the path: self, child/family, team, student, ADHD, work focus.
- Use accountability invite only when relevant: strict mode, family setup, team setup, or “I need stronger friction.”
- Copy Photoroom's checkout clarity directly.

Avoid:
- Asking “How did you hear about us?” early. That helps marketing, not the user.
- Fake personalization where the paywall ignores the user's answers.
- Business/team prompts shown to personal users.

## Recommendations for Opal

### 1. Landing page: stop treating every visitor as the same user

Current issue:
Opal's canonical funnel can work once the user is inside it, but the landing surface needs stronger message match. Competitors preserve intent from ad or SEO source into the first screen.

Recommended structure:
- One production funnel app with path-based variants, not one-off branches.
- Paths like `/bedtime`, `/students`, `/adhd`, `/deep-work`, `/social-media`, `/families`, `/founders`, `/block-tiktok`.
- Each path changes the hero promise, first question, proof, plan preview, paywall headline, and handoff copy.

Landing modules to add:
- Hero: one outcome, one action.
- Immediate proof line: App Store rating, users, hours saved, or focus sessions completed if verified.
- Device handoff: desktop QR plus SMS/email, mobile app deep link/app store, Chrome/Mac route where relevant.
- Interactive entry: “Build my Focus Plan” beats “Get started.”

Example hero directions:
- Bedtime: “Stop losing your nights to scrolling.” CTA: “Build my bedtime block.”
- Deep work: “Protect your first two hours from your phone.” CTA: “Create my focus schedule.”
- Students: “Study without TikTok negotiating with your brain.” CTA: “Build my study plan.”
- Social: “Block the apps you keep reopening.” CTA: “Find my distraction pattern.”

### 2. Reinforcement: turn repeated quiz screens into a visible state machine

Current issue:
The existing Opal capture shows 39 option-tile questionnaire instances and 12 agree/disagree check-ins. That is a lot of input. The next refinement is to make each answer visibly change the plan or the emotional frame.

Recommended changes:
- After every shame-sensitive answer, insert a short reframe, not a generic bridge.
- Show a persistent “plan being built” object or summary drawer: goal, apps, time window, strictness, expected benefit.
- Replace some generic questions with operational selectors: apps, time window, strictness, accountability, break policy.
- Keep a progress rhythm: Diagnose → Plan → Activate.

Strong reinforcement moments:
- After “I scroll in bed”: “Better sleep is the fastest win. We’ll protect the last hour first.”
- After “I override limits”: “Native limits are easy to bargain with. Opal works because it moves the decision out of the weak moment.”
- After high daily hours: “This is not a discipline failure. It is hostile design. We’ll add friction where the loop starts.”

### 3. Social proof: move proof into the moments where doubt appears

Current issue:
Opal already has trust and testimonial templates, but proof needs to become branch-specific and timed.

Recommended proof matrix:
- Work focus path: founder/operator/customer quote about deep work blocks.
- Student path: study/exam quote.
- Bedtime path: late-night scrolling and sleep quote.
- Social media path: Instagram/TikTok reduction quote.
- ADHD path: structure without relying on willpower.
- Family path: presence/child boundary quote.

Proof surfaces:
- Screen 2 or 3: broad credibility, only one line.
- After painful disclosure: matched testimonial.
- Before account gate: proof that people like the user succeeded.
- Before paywall: quantitative proof plus selected branch proof.
- Checkout: compact benefit recap, not a new testimonial wall.

Proof assets to prioritize:
- Verified App Store rating and review count.
- Hours saved by Opal members.
- Focus sessions completed.
- Before/after screen-time reductions.
- 3 to 5 short, branch-specific customer quotes.

Rule:
Do not use fake specificity. If the stat is not verified, do not invent it. Use qualitative proof until the metric is durable.

### 4. Plan preview: make the quiz output concrete before price

Current issue:
The current funnel has plan reveal and paywall screens, but the benchmarks show that the plan should be the central conversion object. It should look like the thing the user earned, not a generic transition to payment.

Recommended plan preview:
- Title: “Your 7-day Focus Plan” or branch-specific equivalent.
- Based on your answers line: goal, apps, time, strictness.
- Plan cards:
  1. Apps to protect against.
  2. First schedule or focus window.
  3. Strictness and bypass policy.
  4. Expected reclaimed time or qualitative outcome.
  5. First activation step.
- CTA: “Activate this plan in Opal.”

Example:
“Your bedtime reset is ready. You told us TikTok, Instagram, and YouTube pull you in after 10 PM. We’ll block them from 10:30 PM to 7:00 AM, start with balanced friction, and add a stricter mode if you override twice.”

This is the highest-leverage design recommendation. It makes every upstream screen justify itself and gives the paywall a reason to exist.

### 5. Paywall: personalize the offer, not just the quiz

Current issue:
Competitors often fake personalization at the paywall. Opal should not. The paywall should repeat the actual plan state.

Recommended paywall hierarchy:
- Personalized headline: “Protect your mornings from Instagram and YouTube” or “Start your 7-day bedtime reset.”
- One sentence tying back to user inputs.
- Plan benefits in outcome language:
  - Block your selected apps during your risk windows.
  - Use stricter blocking when willpower is not enough.
  - Keep recurring schedules automatic.
  - Track hours saved and streaks.
  - Sync across supported platforms where true.
- Target plan architecture: annual or 3-month preselected if billing supports it, monthly as anchor, clear trial terms.
- Risk reversal: trial length, cancellation, renewal date.

Do not copy:
- Scratch-card discounts.
- Cheap countdowns.
- Odd duration plans.
- Fake savings badges.

A premium Opal downsell should be softer:
- “Save this plan and come back later.”
- “Start monthly instead.”
- “Try a 3-day focus challenge first.”
- “What is stopping you?” then answer price, trust, timing, or install friction.

### 6. Checkout: use Photoroom-level clarity

Current issue:
Checkout is where trust is either preserved or burned. The strongest benchmark is Photoroom's split summary with exact trial and renewal disclosure.

Recommended checkout requirements:
- Due today: `$0` or the actual amount.
- Trial ends: exact date.
- First charge: exact amount and exact date.
- Plan name and billing period.
- What is included, using the same benefit language as paywall.
- Apple Pay or express wallet first on mobile.
- Card fields secondary.
- Clear “Change plan” and “Cancel before [date]” language.

Do not change the promise between paywall and checkout. If paywall says “Deep Focus, recurring schedules, time saved insights,” checkout repeats those exact items.

### 7. Web-to-app handoff: make activation explicit

Current issue:
A web subscription without a clean app activation path creates refunds and abandoned installs. Every benchmark either routes hard to app, captures identity, or uses QR/email bridges.

Recommended handoff:
- Mobile: “Open Opal to activate your plan” with app deep link or App Store fallback.
- Desktop: QR code, SMS/email link, copy link.
- Account continuity: “We saved your plan to this account.”
- App first screen should show the same plan state: apps, schedule, strictness, branch goal.

If using RevenueCat Web Billing:
- Redemption link should be created after purchase.
- Magic link should be emailed.
- Desktop should show QR of redemption/install path.
- Handoff state should survive failed install.

## Priority design moves

1. Build the plan preview as the central object.
Everything else depends on it. Without it, the quiz feels like persuasion. With it, the quiz becomes setup.

2. Create three acquisition variants before expanding.
Do not boil the ocean. Start with bedtime scrolling, deep work, and social media reduction. These are distinct enough to prove whether branch-specific landing, proof, plan, and paywall improve quality.

3. Add a real proof matrix.
Collect or select 3 to 5 testimonials and verified metrics. Place them by branch and moment of doubt.

4. Redesign checkout disclosure.
Even if pricing remains the same, make the checkout summary explicit: due today, trial end, charge date, plan, benefits.

5. Add desktop handoff components.
QR, SMS/email, and “saved plan” continuity should be part of the funnel, not a postscript.

## What not to do

Do not make the funnel longer for its own sake. BetterMe and Headway work by manufacturing commitment, but Opal has brand risk if it becomes manipulative.

Do not ask marketing questions early. “How did you hear about us?” belongs after activation or in analytics, not before value.

Do not use fake personalization. If the answer does not change the plan, testimonial, paywall, or handoff, cut or move the question.

Do not use cheap discount theater. If discounting is necessary, make it a reasoned objection response, not a casino moment.

Do not force app redirects from close buttons. Opal sells agency. The funnel cannot violate it.

## Suggested first implementation slice

A shippable first design slice:

Path: `/bedtime`

Flow:
1. Landing hero: “Stop losing your nights to scrolling.”
2. Question: “Which apps pull you in after 10 PM?”
3. Question: “When do you want your phone to quiet down?”
4. Reframe: “This is not a discipline failure. These loops are designed.”
5. Strictness selector: gentle, balanced, strict.
6. Branch-specific testimonial.
7. Plan preview: selected apps, bedtime block, strictness, expected outcome.
8. Account/save gate.
9. Paywall: “Start your 7-day bedtime reset.”
10. Checkout with explicit trial and renewal terms.
11. Handoff: QR/deep link to activate the bedtime block in Opal.

This slice tests the whole benchmark thesis without redesigning every Opal funnel at once.