Hedgehog

INTRO

Overview

Before a product ships, it needs validation. Hedgehog's landing page was not just a marketing asset, it was the first real test of whether the product concept could communicate itself clearly enough to convert strangers into committed early adopters.

The design challenge was specific: present an unreleased, technically complex Web3 prediction market to a professional and institutional audience, and convince them to join a waitlist before they'd seen a single screen of the actual product.

This case documents the conversion architecture behind the page: The research that informed it, the structural decisions made at each section, the alternatives that were discarded, and what the results told us about product-market fit before launch.

ACTUAL SCENARIO

A new Web3 product needs early adopters. The product doesn't exist yet.

Hedgehog was pre-launch. There were no product screenshots, no live demos, no user testimonials, and no track record. The only assets available were: a compelling concept, a credible team, and a clear problem worth solving.

The standard approach, feature lists, product screenshots, social proof, wasn't available. The page had to do something harder: make people believe in what the product would be, based entirely on how clearly and credibly it communicated the problem and the promise.

The conversion context:

Target audience: institutional users and experienced DeFi participants, skeptical by nature, high bar for credibility.
Product stage: pre-launch, no live product, no existing user base
Channel: organic only, Discord communities, Twitter/X, Web3 developer networks, no paid traffic
Conversion goal: waitlist sign-up as the single measurable action
Validation goal: test product positioning and messaging before committing to full build

THE PROBLEM

How do you convert a skeptical, institutional audience on a product they can't see yet?

This was the core design problem, and it's fundamentally different from a standard landing page brief. Most conversion design works by showing the product. Here, the design had to do the persuasion work that the product itself couldn't yet do.

"In institutional and professional contexts, users convert best when trust, context and clarity are established before asking for contact or commitment."

Specific challenges:

Communicating professionalism for a product not yet publicly released, without overpromising
Institutional users expect precision and context before engaging, consumer conversion patterns don't apply
The product concept (on-chain prediction markets) requires explanation before it creates desire, it's not a self-evident value proposition
Driving high-intent waitlist sign-ups, not casual email captures, quality of conversion mattered as much as volume

RESEARCH & BENCHMARKING

Researchs

The research focused on understanding how comparable products in institutional and Web3 contexts build trust and drive conversion before launch. Three reference categories were analyzed:

Category 1 — Institutional SaaS / FinTech launch pages

Studied: Brex, Ramp, Mercury (early launch pages), Stripe (initial launch)
Pattern identified: trust hierarchy before conversion, these pages establish credibility (team, backers, problem framing) in the first two sections before showing any product or CTA
Applied: Hedgehog's page was structured to earn credibility before asking for the email

Category 2 — Web3 / DeFi product launches

Studied: Polymarket launch, Aave early site, Uniswap v3 announcement, Blur NFT marketplace
Pattern identified: on-chain credibility signals matter more than traditional social proof, the community wants to know the team is technical and the mechanics are sound
Applied: the copy explicitly addressed on-chain mechanics, governance, and system integrity, not just the user benefit

Category 3 — Waitlist-driven acquisition funnels

Studied: Linear (product launch), Superhuman (invitation-only model), Notion (early waitlist), Phantom wallet launch.
Pattern identified: exclusivity framing + benefit clarity = highest conversion in professional waitlists. Users need to understand what they're getting early access to before they value the exclusivity.
Applied: the waitlist CTA was framed around early access benefit, not just 'sign up'

Key insight driving the architecture:

In professional contexts, the conversion funnel is: Understand → Believe → Trust → Act. Most landing pages skip to 'Act' too early. This one was structured to earn each stage before advancing to the next.

SOLUTION

Solution Finds

Stage 1 — Hero: Value Signal + Immediate Action

The hero had one job: make the right person immediately understand what Hedgehog is and why it matters to them. Not everyone, just the right person. Institutional clarity was more valuable than broad appeal.

Clear articulation of Hedgehog's core value proposition in one sentence
Institutional tone, no hype, no crypto slang, no promises of returns
Primary CTA (Join Waitlist) placed above the fold, for users who already understand the space and don't need convincing
No product screenshots, intentional. A placeholder image or mockup of an unreleased product signals 'not ready.' We showed concept, not UI.

Hero decision: 'Show concept, not UI'
Considered & discarded: Including early-stage UI mockups to give users a sense of the product.
Choosen direction: Showing visual metaphors and brand language only, no product screens.
Why: In usability review, placeholder UI created skepticism ('is this real?') rather than confidence. Institutional users are trained to read unfinished UI as 'not ready.' Concept visuals with strong copy outperformed UI mockups in the scroll depth data, users who saw no UI stayed longer and converted more.

Stage 2 — Trust & Context: Credibility Layer

After the hero, the user's implicit question is: 'Why should I believe this?' This section answered that question before it became a reason to leave.

Problem framing aligned with the user's reality, not the product's perspective
Differentiation through on-chain focus, signaling technical credibility to a technical audience
Sections addressing reliability, governance, and system integrity, the concerns institutional users have that consumer products ignore

Stage 3 — System Explanation: Make the Mechanics Clear

Before a professional user converts on an unfamiliar product, they need to understand how it works. Not every detail, but enough to believe it's real and sound.

This section explained the prediction mechanics (time-based rounds, pool system, on-chain resolution) in language that was technically accurate but not overwhelming. The goal was informed consent, not feature education.

Hero decision: how much is enough?
Considered & discarded: A full mechanics explanation with diagrams and on-chain flow documentation, similar to a whitepaper section.
Choosen direction: A simplified 3-step explanation with emphasis on what the user does, not how the system works internally.
Why: User research on comparable DeFi products showed that explanation sections longer than 200 words before conversion had diminishing returns, users skimmed or left. The goal was enough to believe, not enough to audit. Technical depth was linked to a documentation page for users who wanted it.

Stage 4 — Action Reinforcement: Conversion Loops

By Stage 4, users who are still reading have already formed intent. The design task here was to remove every remaining reason not to convert.

Repeated CTAs with evolving microcopy, the language shifts from awareness ('Learn more') to intent ('Get early access') to commitment ('Join the waitlist')
Social proof and performance signals, community size, early participant signals, ecosystem credibility
Secondary CTA in footer for late-stage conversion, captures users who read the entire page before deciding
Short, frictionless waitlist form, email only, no additional fields

Hero decision: how many?
Considered & discarded: Name + Email + 'How did you hear about us?', standard waitlist form for segmentation.
Choosen direction: Email only
Why: Every additional field reduces conversion rate. For a product validation goal, email volume and conversion rate matter more than segmentation data at this stage. Segmentation was deferred to the onboarding email sequence, where response rates are higher and context is clearer.

VISUAL DESIGN DECISIONS

Design

The visual language was designed as a direct extension of the conversion strategy, every aesthetic choice had a functional rationale.

Institutional typography for clarity and authority

The typeface and sizing choices were deliberately serious, no playful display fonts, no crypto-aesthetic gradients. Institutional users pattern-match credibility from visual signals before reading a word. The typography needed to pass a one-second credibility test.

Restrained color palette

The palette used dark backgrounds with high-contrast highlights, consistent with professional financial tools and institutional Web3 products. The goal was to feel like a tool, not a consumer app. Color was reserved for CTAs and system states, not decoration

Information hierarchy with clear section anchors

Each section had a single dominant message and a clear visual hierarchy from heading to supporting copy to CTA. This supported scan-driven behavior, institutional users read in F-patterns, and the layout was designed around that reality.

Spacing as a trust signal

Generous whitespace was a deliberate choice. Dense layouts signal rushed execution. In institutional contexts, restraint and breathing room communicate confidence, the product doesn't need to oversell itself by filling every pixel.

RESULTS

Results finds

The page was distributed organically through Discord communities, Twitter/X, and Web3 developer networks, zero paid traffic.

Conversion performance:

Waitlist conversion rate: 37.5%, the average for B2B/Web3 waitlist pages is 2–8% for cold traffic. 37.5% from organic, community-sourced traffic indicates strong message-market fit.
CTA engagement: consistent interaction across hero (above-the-fold) and footer CTAs, confirming the two-CTA architecture was effective for both fast-deciders and thorough readers
Scroll depth: high retention through the trust and mechanics sections, users weren't bouncing at the explanation layer, validating the decision to include system transparency

Product validation signals:

Engagement patterns indicated qualified interest, not casual curiosity. Users who signed up had spent meaningful time on the page before converting.
The waitlist served as the acquisition layer for the product beta, users who signed up were segmented by engagement level and onboarded in priority order
Conversion data directly informed product communication decisions, the sections with highest engagement shaped the onboarding copy and product UI microcopy

The landing page wasn't just a marketing asset, it was the first usability test of the product's value proposition. The 37.5% conversion rate was the earliest product-market fit signal the team had.

LANDING TO PRODUCT

Looping

The relationship between the landing page and the product was intentional and designed from the start, not treated as two separate projects.

The copy and framing on the landing page directly shaped the onboarding language in the product, ensuring continuity between the promise and the experience.
The 3-step mechanics explanation on the landing page was the basis for the in-product onboarding tooltip sequence.
Conversion signals from the landing (which sections had highest engagement) were used as research input for the product's information hierarchy, confirming that users cared most about the pool mechanics and on-chain resolution.
Waitlist users served as the first cohort for usability testing, because they had already demonstrated comprehension of the product concept, their feedback on the product was significantly more actionable than cold user recruitment would have been.

LESSONS

Lessons Learned

Institutional audiences respond to clarity, not flash.

Every time we added a visual element to 'make the page more exciting,' we were actually eroding the trust signal. The highest-converting version of the page was also the most restrained one. The benchmark, financial and institutional SaaS products, is deliberately austere. We learned to treat visual restraint as a deliberate product choice, not a failure of creativity.

Conversion in professional pages requires trust signals before CTAs.

The first version of the page placed the primary CTA in the hero with minimal context. Conversion rate was significantly lower. Adding a credibility and context layer before the CTA, and moving the CTA to repeat at the end of that layer, was the single highest-impact structural change. Users needed to believe before they would act.

Explaining the mechanics is a conversion feature, not a liability.

The initial hypothesis was that a long mechanics explanation would increase drop-off. The data showed the opposite: users who reached the mechanics section had higher conversion rates than those who bounced earlier. Understanding the system reduced anxiety and increased commitment. For technical products, clarity about how something works is a trust signal, not a hurdle.

The landing page is a research artifact.

The most valuable outcome of the landing page wasn't the waitlist emails, it was the behavioral data. Which sections held attention, which CTAs got clicked, which copy drove the most engagement. This data was treated as primary research input for the product design process. Building the landing page before the product was one of the best research investments the team made.

NEXT STEPS

Next Steps

A/B test headline microcopy variations

The hero headline was not tested, it was the team's best first hypothesis. With a validated conversion rate baseline, the next step is testing alternative framings of the core value proposition. Even a 5-point improvement in the headline conversion rate would compound significantly at scale.

Segment waitlist users for tailored onboarding flows

The current waitlist is unsegmented. Based on behavioral signals from the page (which sections users engaged with longest), users can be segmented into: institutional/professional (high scroll depth on mechanics sections) vs. consumer/enthusiast (high engagement with product concept sections). Each segment warrants a different onboarding sequence.

Integrate early user feedback into landing copy refinement

The first cohort of beta users, recruited through the waitlist, now has direct product experience. Their feedback on the gap between what the landing page promised and what the product delivered is the highest-quality input available for a second iteration of the page.

Add tracking to measure engagement path and drop-offs

Current data covers macro metrics (conversion rate, scroll depth). Heatmap and session recording data would identify the specific micro-drop-off points within sections, enabling surgical copy and layout improvements rather than broad structural changes.