Appearance
Audience Research and Personas
You cannot write compelling copy or design an effective layout until you deeply understand who will land on your page and what they need.
Why This Matters
- 💻 Dev: Audience data determines personalization logic, dynamic content rules, and which integrations you need (CRM, analytics, A/B testing). Building without audience clarity means rebuilding later.
- 📋 PM: Personas are the foundation for prioritization. They tell you which features to highlight, which objections to address, and which traffic sources to invest in. Skip this step and every decision downstream is a guess.
- 🎨 Designer: The audience dictates tone, visual language, information density, and interaction patterns. A page designed for enterprise CTOs looks nothing like one designed for freelance designers.
The Concept (Simple)
Think about writing a letter. When you write to your boss, you are formal, structured, and concise. When you write to your best friend, you are casual, personal, and maybe a little funny. When you write to a stranger asking for a favor, you are polite, clear about what you want, and quick to explain why it benefits them.
You did not change who you are. You changed how you communicate because you understood your audience.
Landing pages work exactly the same way. The product stays the same, but the way you present it — the words, the visuals, the structure, the proof points — must shift depending on who is reading. A developer wants to see code samples and documentation links. A marketing director wants to see ROI numbers and case studies. A designer wants to see the interface and feel the craft.
Same product. Different letter. That is what audience research enables.
How It Works (Detailed)
Research Methods
You do not need a six-month ethnographic study. You need focused, practical research that gives you enough signal to make confident decisions. Here are the methods, ordered by effort:
Low Effort (start here):
- Analytics data: Look at who is already visiting. Google Analytics demographics, device data, geographic distribution, and behavior flow reveal patterns. Which pages do visitors come from? Where do they drop off?
- Search query analysis: Use Google Search Console to see what queries bring people to your site. The language visitors use in search reveals their mindset, awareness level, and intent.
- Support tickets and chat logs: Your support team talks to real users every day. Mine those conversations for recurring pain points, vocabulary, and objections.
Medium Effort:
- Customer surveys: Send a 5-question survey to recent signups or customers. Ask: What problem were you trying to solve? What almost stopped you from signing up? What would you tell a friend about us?
- Sales call recordings: Listen to 10-15 sales calls. Note the questions prospects ask, the objections they raise, and the language they use to describe their problems.
High Effort (do this once you have traction):
- User interviews: 30-minute conversations with 8-12 people from your target audience. Use open-ended questions. Listen more than you talk.
- On-site surveys: Tools like Hotjar or Qualaroo let you ask one question to visitors in the moment: "What brought you to this page today?"
Jobs-to-Be-Done for Landing Pages
Forget demographics for a moment. The Jobs-to-Be-Done (JTBD) framework asks one powerful question: What job is the visitor hiring this page to do?
A visitor landing on your page has a job in mind. They might be:
- Evaluating whether your product solves their problem
- Comparing you against a competitor they already know
- Looking for proof that your product works for someone like them
- Trying to justify the purchase to their boss or team
Each of these jobs requires a different page structure, different copy, and different proof points.
╔══════════════════════════════════════════════════════════════╗
║ JOBS-TO-BE-DONE FRAMEWORK ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Visitor arrives with a JOB in mind: ║
║ ║
║ ┌──────────────────┐ ┌──────────────────┐ ║
║ │ "Help me decide │ │ "Help me compare │ ║
║ │ if this solves │ │ this to what I │ ║
║ │ my problem" │ │ already use" │ ║
║ └────────┬─────────┘ └────────┬─────────┘ ║
║ │ │ ║
║ ▼ ▼ ║
║ Page needs: Page needs: ║
║ - Clear value prop - Feature comparison ║
║ - Use cases - Migration ease ║
║ - Social proof - Switching benefits ║
║ ║
║ ┌──────────────────┐ ┌──────────────────┐ ║
║ │ "Help me prove │ │ "Help me get │ ║
║ │ this to my boss"│ │ started fast" │ ║
║ └────────┬─────────┘ └────────┬─────────┘ ║
║ │ │ ║
║ ▼ ▼ ║
║ Page needs: Page needs: ║
║ - ROI calculator - Quick setup guide ║
║ - Case studies - Free trial CTA ║
║ - Enterprise logos - Time-to-value stats ║
║ ║
╚══════════════════════════════════════════════════════════════╝Creating Actionable Personas
Most personas are useless. They list demographics — "Sarah, 34, lives in Austin, likes hiking" — that tell you nothing about how to design a landing page. Actionable personas focus on four things that directly influence page decisions:
- Goals: What does this person want to achieve?
- Fears: What could go wrong? What are they afraid of?
- Objections: Why might they NOT convert today?
- Decision criteria: What information do they need to say yes?
Here is the persona card template:
┌────────────────────────────────────────────────────────────────┐
│ PERSONA CARD │
├────────────────────────────────────────────────────────────────┤
│ Name: [Role-based label, e.g. "The Technical Evaluator"] │
│ Role: [Job title / function] │
│ Context: [How they arrive — search, ad, referral] │
├────────────────────────────────────────────────────────────────┤
│ GOALS │
│ ───── │
│ • [What they want to accomplish] │
│ • [What success looks like for them] │
├────────────────────────────────────────────────────────────────┤
│ FEARS │
│ ───── │
│ • [What keeps them up at night] │
│ • [Past bad experiences with similar products] │
├────────────────────────────────────────────────────────────────┤
│ OBJECTIONS │
│ ────────── │
│ • [Why they might not convert today] │
│ • [What makes them hesitate] │
├────────────────────────────────────────────────────────────────┤
│ DECISION CRITERIA │
│ ───────────────── │
│ • [What information closes the deal] │
│ • [Proof they need to see] │
├────────────────────────────────────────────────────────────────┤
│ PAGE IMPLICATIONS │
│ ───────────────── │
│ • [What this means for copy, design, CTA] │
│ • [Which sections matter most to this persona] │
└────────────────────────────────────────────────────────────────┘Mapping Persona Attributes to Page Decisions
Every persona attribute should translate to a concrete design or copy decision. If an attribute does not change what you put on the page, it is decorative — remove it.
| Persona Attribute | Page Design Decision |
|---|---|
| Technical role | Show code snippets, API references, architecture docs |
| Non-technical decision maker | Show ROI, case studies, integration logos |
| Price-sensitive | Lead with free tier, show pricing transparency early |
| Risk-averse | Emphasize security, uptime SLAs, enterprise customers |
| Time-pressured | Short page, clear CTA above fold, minimal form fields |
| Comparison shopping | Feature comparison tables, "why us" section |
| First-time visitor | Explain the category, not just the product |
| Returning visitor | Skip the intro, go straight to CTA or deeper content |
| Arrives from paid search | Match headline to ad copy, high intent — short page |
| Arrives from social media | Lower awareness, longer page, more education needed |
In Practice
How Airbnb Researches Host vs Guest Motivations
Airbnb operates two fundamentally different landing pages because they serve two fundamentally different personas: hosts and guests.
Guest personas are motivated by unique experiences, trust, and price. Their landing pages feature stunning photography, verified reviews, and price transparency. The copy emphasizes discovery and belonging.
Host personas are motivated by income, flexibility, and safety. Their landing pages feature earning calculators ("Hosts in your area earn an average of $1,200/month"), insurance guarantees, and host community stories. The copy emphasizes financial opportunity and control.
Airbnb discovered these differences through extensive user research — interviews with thousands of hosts and guests across dozens of markets. They found that hosts needed reassurance about safety and liability above all else, while guests needed reassurance about quality and authenticity.
What you can steal from Airbnb:
- If you serve multiple personas, build separate landing pages for each
- Lead with the motivation that matters most to each persona (income for hosts, experience for guests)
- Use persona-specific proof points (host earnings data vs guest review scores)
How Notion Targets Developers vs Teams vs Personal Users
Notion maintains distinct landing pages for different audience segments, each with tailored messaging:
For developers: The page highlights wikis, API documentation, and integrations with tools like GitHub. The visual language is clean and technical. Code blocks appear in the examples.
For teams: The page emphasizes collaboration features, shared workspaces, and templates. Screenshots show team dashboards and project boards. Customer logos from known companies build credibility.
For personal users: The page is warmer, featuring use cases like note-taking, journaling, and personal project management. The tone is approachable rather than enterprise.
Notion built this segmentation through a combination of product analytics (observing how different user types actually used the product), search query analysis (understanding the different language each segment used), and user interviews.
What you can steal from Notion:
- Segment your landing pages by use case, not just by company size
- Match visual density to audience expectations (technical audiences tolerate more detail)
- Use the vocabulary your audience actually uses — mine search queries and support tickets for real language
Key Takeaways
- Audience research is not optional — it is the foundation for every copy, design, and technical decision on your landing page
- Start with low-effort methods (analytics, search queries, support tickets) before investing in interviews
- Use the Jobs-to-Be-Done framework to understand visitor intent, not just demographics
- Build actionable personas focused on goals, fears, objections, and decision criteria — skip the demographic fluff
- Every persona attribute must map to a concrete page decision or it is wasted information
- Different audiences need different pages — if you serve multiple personas, build multiple landing pages
- Mine real customer language from support tickets, sales calls, and search queries to write copy that resonates
Action Items
┌──────────┬──────────────────────────────────────────────────────┐
│ 💻 Dev │ ☐ Set up analytics segmentation to track behavior │
│ │ by traffic source, device, and referrer │
│ │ ☐ Build dynamic content blocks that can serve │
│ │ different copy/visuals per audience segment │
│ │ ☐ Implement URL parameter handling for persona- │
│ │ targeted ad campaigns (e.g., ?audience=developer) │
├──────────┼──────────────────────────────────────────────────────┤
│ 📋 PM │ ☐ Conduct 5 customer interviews focused on goals, │
│ │ fears, and objections — not demographics │
│ │ ☐ Create 2-3 actionable persona cards using the │
│ │ template in this chapter │
│ │ ☐ Map each persona to specific page design decisions │
│ │ using the attribute-to-decision table │
│ │ ☐ Review search query data monthly to track how │
│ │ audience language evolves │
├──────────┼──────────────────────────────────────────────────────┤
│ 🎨 Design│ ☐ Audit current pages: does the visual language │
│ │ match the primary persona's expectations? │
│ │ ☐ Create a mood board per persona that captures │
│ │ tone, density, and visual references │
│ │ ☐ Design at least one persona-specific page variant │
│ │ and test it against the generic version │
└──────────┴──────────────────────────────────────────────────────┘