Internal · 16 variants

Pricing page exploration

16 directions for vanio.ai/pricing. Same chrome, same data, same below-the-fold — different ways to make subscription + per-reservation legible above the fold.

Live page ↗·Built Jun 28, 2026

Slider hero

Drag a slider, see your price.

Pattern: OwnerRez per-property pattern

Best for: Visitors who want their answer in 3 seconds, no reading.

Two-line price

$8/listing — line break — + $5 per reservation. Two parts. That's it.

Pattern: Restraint / clarity through omission

Best for: Scanners. Emphasizes simplicity by hiding everything else.

Receipt hero

Your hero is a literal monthly invoice — line items add up to a total.

Pattern: Transparency through itemization

Best for: Math-comfortable buyers who reward total honesty.

Wallet frame

Two visual panels: subscription (recurring) and prepaid wallet (drawn down).

Pattern: Make the credit mechanism literal

Best for: Visitors confused by 'what is a credit?' — shows the metaphor.

Tiered packs

Three packaged tiers, each bundles a starter wallet. One number per tier.

Pattern: Anthropic-style tiers + included usage allowance

Best for: Buyers who want predictable monthly spend.

Compare to manual

Lead with $5/reservation vs $30/reservation human VA. Savings is the headline.

Pattern: Value-anchor / ROI framing

Best for: Skeptical operators focused on total cost-to-serve.

Dual-product split

Bold left/right: Vanio OS (no AI) vs Vanio AI. Each side stands alone.

Pattern: Force a single decision between two products

Best for: When OS deserves equal billing and shouldn't be buried.

Quiz first

One field — 'How many listings?' — reveals a personalized recommendation.

Pattern: Anthropic-style quiz / interactive disclosure

Best for: Audiences with high variance in scale (1 listing vs 200).

Animated stack

Watch the price assemble: $0 → +$8/listing → +$5/reservation → total.

Pattern: Motion clarifies the stacking model

Best for: Visitors who'd benefit from seeing the model build itself.

Plain English

One short paragraph. No cards above the fold. Conversational tone.

Pattern: Anti-design / trust through restraint

Best for: AI-skeptical operators tired of slick pricing pages.

Split + plain prose

Dual-product split followed by a conversational explanation of how the wallet works.

Pattern: Visual decision first, prose for the curious

Best for: Visitors who pick the product fast but want the model explained without scrolling to FAQ.

AI primary + OS strip

Vanio AI gets the entire hero. A thin contextual strip below offers OS for hands-on operators.

Pattern: Single-product hero + downsell band

Best for: When AI is the message but OS revenue still matters. OS is acknowledged, not promoted.

AI with on-ramp

AI hero with a footnote framing OS as the on-ramp: 'start with OS, upgrade when ready.'

Pattern: Trust ladder / training wheels framing

Best for: AI-skeptical buyers who need permission to start small without losing the upgrade path.

AI with reveal toggle

Above the fold: only AI. A small 'Just need a PMS?' button reveals OS on demand.

Pattern: Progressive disclosure / opt-in to see alternatives

Best for: Maximum AI focus — most visitors never see OS, only the ones who explicitly opt in do.

Asymmetric split

Two cards in one row, but visually weighted ~75/25 toward Vanio AI.

Pattern: Familiar split layout with deliberate visual hierarchy

Best for: When you want both products visible but the eye must land on AI first.

AI hero, OS later

AI dominates the hero. OS appears later as a single compact card with the 'not ready?' framing.

Pattern: Single-product hero, secondary product deferred

Best for: AI-first positioning with no risk of confused above-the-fold messaging. OS for visitors who keep scrolling.

What changes

Hero + plan presentation only. The first viewport is the variant axis.

What stays

Calculator, add-ons table, FAQ. Everything that already works on the live page.

How to evaluate

Show someone the first viewport for 5 seconds. Ask: “What does this cost for 10 listings, 50 reservations/mo?”

Open variant 1 →