mdcraft.ai Phase 5 — Monetization Surfaces and Upgrade UX#

Objective#

Convert activated free users into paid users through value-timed upgrade moments, without harming trust or first-success speed.

Strategic alignment#

This phase follows the locked direction:

• premium markdown finishing layer
• quality-first Markdown -> PDF experience
• honest PDF -> Markdown beta framing

It also aligns with the freemium model plus one public Pro plan in the foundation.

Monetization principles#

1. Value before ask
   • no hard paywall before a user reaches first successful export
2. Contextual upsell
   • upgrade prompts should appear where premium value is naturally understood
3. Benefit-first copy
   • explain what outcome improves, not just what feature unlocks
4. Low-friction path
   • upgrade CTA should not interrupt active editing flow
5. Trust-safe gating
   • no manipulative countdowns or dark patterns

Package architecture (design-facing)#

Free#

• limited daily studio runs
• core studio workflows
• account-backed profile defaults
• single-account focus

Pro#

• $8/month
• unlimited studio runs
• saved defaults across sessions
• markdown to pdf plus pdf to markdown beta
• billed monthly, cancel anytime

Enterprise later#

• keep this contact-led, not self-serve
• bring it forward only when procurement or API needs are real

Monetization surface map#

Homepage#

• pricing section with Free and one paid Pro offer
• one clear CTA to start free or upgrade
• short ROI copy: time saved + quality consistency

Workbench (primary)#

• usage messaging in the studio access surface
• upgrade prompts around free-tier limits and account state
• post-export success panel with upgrade suggestion

Pricing page/section#

• concise Free vs Pro comparison
• use-case-first guidance:
  • “best for individuals”
  • “best for frequent professional exports”

Trigger strategy (when to ask)#

Trigger A: Usage threshold#

When free usage is nearly exhausted:

• soft warning at ~80%
• stronger prompt at limit hit

Trigger B: Billing-controlled feature intent (future iteration)#

When the product later exposes a billing-controlled capability:

• in-context lock card with immediate upgrade action

Trigger C: Post-value moment#

Immediately after a successful export:

• compact panel showing unlocked benefits with Pro

UX patterns for upgrade prompts#

Pattern 1: Inline lock card#

• location: next to locked setting
• copy: “Unlock brand-ready exports”
• actions: Upgrade + Not now

Pattern 2: Toast/banner reminder#

• location: top-right toast or top bar
• use: approaching limits
• actions: View plans

Pattern 3: Success-state panel#

• location: export success panel
• use: repeated exports on free plan
• actions: Upgrade to Pro

Messaging guidelines#

Good:

• “Remove daily caps for repeat export work.”
• “Keep the studio available whenever you need it.”

Avoid:

• “You must pay now to continue.”
• “Limited-time pressure” without real basis

Paywall behavior model#

Soft gates (preferred default)#

• allow viewing controls
• block final premium action only
• show clear unlock rationale

Hard gates (use sparingly)#

• only when limit is fully exhausted
• always present clear fallback options

Plan-to-feature mapping reference#

• limited daily studio runs -> Free
• unlimited studio runs -> Pro+
• enterprise billing/procurement support -> contact-led later
• API and automation rollout -> contact-led later

Accessibility and trust requirements#

• all lock states and limits readable by screen readers
• no essential information hidden by color alone
• prompts dismissible and non-blocking during editing

Monetization KPIs#

• free -> pro conversion rate
• free -> paid upgrade click-through
• upgrade prompt view -> upgrade start rate
• export completion rate (must remain stable or improve)
• churn signals after upgrade prompt exposure

Acceptance criteria#

1. Upgrade moments occur after value signals, not before.
2. Users always understand why a feature is gated.
3. Monetization prompts do not reduce first-export completion.
4. Plan differentiation is clear and tied to outcomes.

Implementation status#

Iteration update (2026-03-10)#

• studio now surfaces a free-vs-pro access banner
• free plan messaging communicates daily run limits and Pro upgrade path
• hooks for plan-aware behavior are now present in studio UX