---
title: Positioning and messaging — Born Free umbrella (April 2026)
date: 2026-04-29
project: born-free
tags: [strategy, positioning, messaging, born-free, store-free]
revision: 1
editor: marketing-editor
last_review: 2026-04-29
depends_on:
  - projects/store-free/research/public-sources-2026.md
  - projects/store-free/research/competitive-snapshot-2026-04-24.md
  - projects/born-free/style-guide/voice-and-boundaries.md
  - projects/store-free/style-guide/voice-and-boundaries.md
  - projects/knowtation/style-guide/voice-and-boundaries.md
  - projects/knowtation/research/public-sources-2026.md
  - projects/born-free/research/whitepaper.md
---

# Positioning and messaging — Born Free umbrella — 2026-04

## Changelog

- **2026-04-28** — Outline created **parallel to Store Free** (`projects/store-free/outlines/positioning-and-messaging-2026-04.md`). Same whitepaper and URL registry; **different lead story** (membership / Keys / experiences vs document custody). Web deploy source of truth for the technical doc remains **`bornfree-pwa/public/whitepaper.md`** ↔ **`bornfree-hub/docs/01-COMPREHENSIVE-WHITEPAPER.md`** ↔ Hub **`projects/born-free/research/whitepaper.md`** (vault import).
- **2026-04-29** — Split ICP vs evidence rules; triggers/objections as tables; Pillars 3–5 proof paths tightened; Pillar 4 (culture/creators) and Pillar 5 (email-first / onboarding) promoted to full pillars; `depends_on` expanded for agent discipline.
- **2026-04-29 (sync)** — **Path fixes:** `depends_on` whitepaper entry is **`projects/born-free/research/whitepaper.md`** (replaces obsolete `projects/bornfree/research/whitepaper.md`). **Knowtation** public URL registry added to `depends_on`. **Pillar 1** proof line updated to match. **Strategic choices** registry reference uses vault-relative path `projects/store-free/research/public-sources-2026.md` (no `vault/` prefix). Git-tracked copy added under `knowtation/vault/projects/born-free/outlines/` for parity with Hub.
- **2026-04-29 (merge)** — Folded durable items from `projects/born-free/outlines/positioning-umbrella-experiment-2026-04.md`: **Canonical live URLs** table (from public-sources registry), **public whitepaper URL** guardrail, **competitive snapshot** discipline note, **objection** row for docs-first entrants, **Forbidden claims** expansion (style-guide §5–6), **Open conflicts** note for Hub vs local whitepaper parity, **Pillar 1** headline guardrail and **Pillar 5** proof (§5.2 step 7), **Sibling products** table + Knowtation URL pointer, **Related** link to competitive snapshot. **Strategic choices #2** wording corrected so “utility-driven access” is the **category** for Keys, not labeled as the “anti-category.”
- **2026-04-29 (edit)** — Marketing-editor pass (hosted MCP): reinforced umbrella-first headline rule; tightened claims/registry and voice-§5 alignment (no new URLs; canonical table unchanged); softened wording that could read as hype or over-claim; added `revision` / `editor` / `last_review`.

## Situation (from research)

- **Umbrella first:** Born Free is how we communicate the **member-managed ecosystem**—places, experiences, Keys, credits, governance—not “storage SaaS” as the headline. **Store Free** is the document, signing, and provenance tool (standalone or inside the journey); keep that split explicit in external messaging.
- **Layered story:** When a page must mention documents, point to **Store Free** positioning and its instructional voice; do not collapse Born Free into storage slogans. (See competitive snapshot plus both Store Free and Born Free voice guides in `depends_on`.)
- **ICP / lead lanes:** Lead ICP for paid Keys / member growth: (1) People optimizing for recurring stays, predictable annual credits, and fair rotation of booking priority over years. (2) People who want collective stewardship, local creators and projects, and governance tied to place-based economics—not only personal nights.
- **Evidence discipline:** Strategy claims must cite `depends_on` paths or evidence recorded under `projects/store-free/research/public-sources-2026.md` (canonical URL registry for Born Free and Store Free app URLs). Use Knowtation product URLs and social handles only as listed in **`projects/knowtation/research/public-sources-2026.md`**. Competitive snapshot items may carry **[NEEDS CONFIRMATION]** until sourced.
- **Knowtation (sibling):** Use Knowtation in umbrella or ecosystem copy when the piece is explicitly **cross-product**; keep voice aligned with `projects/knowtation/style-guide/voice-and-boundaries.md` for product-specific pages (whitepaper §1.1 platform tools).
- **Competitive / matrix claims:** `projects/store-free/research/competitive-snapshot-2026-04-24.md` stresses layered Born Free vs Store Free messaging; **named competitors, pricing bands, and market sizing** stay **[NEEDS CONFIRMATION]** until backed by additional research or product sign-off—do not invent a competitor matrix from this outline alone.

## Strategic choices

1. **Primary ICP (umbrella)** — Anchor on what §1.1–1.3 of the whitepaper states: people who want collective paths to real property, community-aligned access, and legible on-chain rules for booking, credits, and governance—not generic “crypto investors.” The whitepaper contrasts that audience with traditional timeshares, high capital and operations barriers, illiquidity, and weak member governance. Born Free is a member-managed network for real-place experiences—Experience Keys tie stays, renewable credits, and community governance to on-chain rules you can read, not a hidden back office.
2. **Category frame** — Name the problem in membership, access, and governance terms, not storage. The whitepaper’s own frame: community-building network around collective property and Experience Keys as “Digital Keys to Real Experiences,” tying property access to DAO governance through on-chain rules. **Position as utility-driven access and governance** (membership), **not** fractional real-estate speculation or opaque “ownership” claims—Experience Keys deliver access and utility, **not direct property ownership** (§1.3).
3. **Proof we will lead with** — Restrict to shipped or documented-in-whitepaper facts—for example Avalanche deployment, contract and test counts, launch timestamp, and architecture stack as listed in §1.4—plus live URLs only after verification and only as written in `projects/store-free/research/public-sources-2026.md` (Born Free rows). Do not describe availability, financial outcomes, or booking results as guaranteed (voice guide §5). Do not treat internal funnel or unapproved docs (for example `bornfree-pwa/docs/TOP-FOLD-QUICK-REFERENCE.md`) as **compliance-approved** proof until product and legal align those steps and numbers with the live funnel.

### Triggers (why now)

| Trigger | Whitepaper |
|--------|------------|
| Distrust of opaque membership (timeshare-style extraction, no real governance) | §1.2 Property Access |
| Desire for legible rules (booking, credits, votes on-chain vs black box) | §1.1, §1.3 |
| Reservation season / cycle awareness (tier priority, June 1–30 window, annual credit renewal, §1.5.9 “ALL RR#s are valuable”) | §1.3, §1.5 |
| Starting without a wallet; optional later custody | §1.1, §1.3, §5.2 |
| Interest in trading credits or Keys inside member surfaces | §1.3; §6.1 Marketplace |

### Objections (internal scripts)

| Objection | Answer anchor |
|-----------|----------------|
| “Is this an investment / real estate play?” | Experience Keys deliver access and utility, not direct property ownership (§1.3). Do not promise investment returns (voice §5). |
| “Will I definitely get the stays I want?” | Describe rotating priority, windows, and credits ≈ nights (~550 credits/night in §6.1 worked example) as documented mechanics, not guaranteed outcomes (voice §5; no guaranteed booking). |
| “Crypto is too hard / I don’t want a wallet.” | Email-first onboarding; path can extend to wallet and custody later (§1.3, §1.1, §5.2). |
| “Who pays gas / what costs money?” | Avalanche on-chain actions involve user-paid network gas like other C-Chain dapps; session and off-chain work do not (§1.3). |
| “What if I don’t care about documents?” | Umbrella story stays Keys, place, and governance; documents are Store Free (§1.1 platform tools; §6.1 Strategic fit). |
| “I only care about documents, not stays.” | Lead with **Store Free** positioning and **`https://app.bornfree.io/storefree`** (public-sources table); umbrella copy still names Born Free as family without making storage the headline. |
| “Sounds like hype / scam culture.” | Voice §1–2: calm specifics, no WAGMI-style copy; cite shipped stack from §1.4 only when you need credibility, not speculation. |

## Canonical live URLs (Born Free + Store Free in-app)

From **`projects/store-free/research/public-sources-2026.md`** (Born Free — marketing and app):

| What | URL |
|------|-----|
| Marketing / main site | `https://bornfree.io` |
| Marketing (alternate) | `https://www.bornfree.io` — registry notes confirming which is primary for campaigns. |
| Web app (signed-in experience) | `https://app.bornfree.io` |
| Store Free (in-app area) | `https://app.bornfree.io/storefree` |
| PWA / debug (ops) | `https://app.bornfree.io/pwa-debug.html` |

**Last checked in registry:** 2026-04-26 (re-verify before major launch).

Public white paper URL in that registry remains **`[ADD public PDF or landing URL]`** — do not invent a hosted-PDF link in external copy until the registry row is updated.

## For / Who / Unlike / We (skeleton)

| Block | Draft |
|--------|--------|
| **For** | People who want real-place experiences and community with clear rules (stays, credits, governance)—including paths that start email-first and can move toward self-custody (§1.1, §1.3 “Multi-Campaign Coordination”). |
| **Who** | Are blocked or burned by timeshare-style extraction, opaque back-office rules, illiquid “ownership” stories, or governance theater (§1.2 Property Access). |
| **Our product** | Born Free — Experience Keys, stay credits, reservations, member marketplace and trading surfaces, DAO participation, and **place-linked culture and creator programs** as described in §1.1–1.3 (keep Store Free and Knowtation as siblings only). |
| **Unlike** | Traditional timeshares, high-friction sole ownership, and platforms where booking rights and votes live in a black box—describe capabilities and transparency, not competitor trash talk (Born Free voice §3–4, §5). |
| **We** | Verifiable utility: access, renewal, rotation, and governance documented on-chain; stay calm about tradeoffs (custody, gas, no guaranteed outcomes per voice §5). Hook proof to §1.4 metrics + registry URLs after verification. |

## Message hierarchy

**External headline rule:** Lead with Keys, place, credits, and member governance; when the reader's job is documents, hand off to Store Free without making storage the umbrella headline.

- **Pillar 1** — Digital Keys to Real Experiences  
  Experience Keys bundle stay utility, rotating priority, and governance participation with rules on the ledger, not in a hidden admin layer.  
  **Headline guardrail:** Umbrella copy leads with **Keys, place, credits, governance**—not storage.  
  **Proof:** `bornfree-pwa/public/whitepaper.md` §1.1–1.3; Hub mirror: **`projects/born-free/research/whitepaper.md`** (see `projects/store-free/research/public-sources-2026.md`).

- **Pillar 2** — Fair, explicit access over the long cycle  
  8-year tier round-robin, June booking windows, annual credit replenishment (mechanics in §1.3 and §1.5).  
  **Proof:** same whitepaper sections; messaging guardrails in §1.5.9 (“ALL RR#s are valuable”).

- **Pillar 3** — Community stewardship of place  
  Collective purchase, local projects and creators, DAO proposals and voting; surplus from real-world stays, events, and on-property offerings—after operating costs and agreed reserves—can flow into community-aligned economics (treasury and governance outcomes), alongside credits and marketplace activity, as described in the whitepaper sections cited below.  
  **Proof:** `bornfree-pwa/public/whitepaper.md` §1.1; **`### 6.1 Revenue Streams` → `#### 3. Property Profits`**; marketplace context in §6.1 **2. Marketplace Fees** where relevant.

- **Pillar 4** — Culture and creative work, grounded in place  
  The network exists to **establish place and community**: collective stewardship of real property, local projects and creators, and experiences where culture and shared governance reinforce each other—not a disconnected “audience platform.”  
  **Proof:** `bornfree-pwa/public/whitepaper.md` §1.1; `projects/born-free/style-guide/voice-and-boundaries.md` §1 (who we help); optional economics hook: §6.1 **3. Property Profits**.

- **Pillar 5** — Join on your terms  
  Email-first onboarding; optional wallet and self-custody when members are ready; honest framing of on-chain costs where applicable—supports the umbrella story without making document custody the headline (hand off document detail to Store Free when needed).  
  **Proof:** §1.3 Shared Platform; §5.2 User Journey (including optional Store Free / Knowtation depth per step 7); §1.1 platform tools list; §6.1 **Strategic fit** (Store Free as gateway, without collapsing Born Free into storage).

## Sibling products (short pointers — do not duplicate full positioning)

| Sibling | Role in umbrella copy | Where full positioning / URLs |
|--------|------------------------|----------------------------------|
| **Store Free** | Documents, signing, custody, DocNFT; gateway for email and card users (§6.1 Strategic fit). Instructional, limits-forward voice. | `projects/store-free/outlines/positioning-and-messaging-2026-04.md`; in-app **`https://app.bornfree.io/storefree`** per public-sources. |
| **Knowtation** | Open knowledge vault and agents; ecosystem depth—not the Born Free headline. | URLs: **`projects/knowtation/research/public-sources-2026.md`**; voice: **`projects/knowtation/style-guide/voice-and-boundaries.md`**. |

## Forbidden claims

- Nothing here is approved for external use until checked against the whitepaper and live product.
- Born Free does **not** promise **investment returns**, **guaranteed booking** or other **guaranteed outcomes**, or **legal, tax, or medical** results—see `projects/born-free/style-guide/voice-and-boundaries.md` §5. For law, tax, or securities-sensitive topics, point readers to qualified professionals rather than improvising authority (same section).
- Do not invent **metrics**, **testimonials**, or **case study numbers**; cite whitepaper or registry paths, or label projections explicitly.
- No **competitor or individual trash talk**; compare **capabilities and tradeoffs** only.
- Avoid **hype vocabulary** the style guides call out (for example WAGMI, “moon,” guaranteed life-change copy).
- **Urgency:** only **real** dates, **real** capacity, **honest** deadlines (voice §6).

## Open conflicts

- None recorded for product vs research yet; add rows when they disagree.
- **Imports:** Hosted Hub may hold **`projects/born-free/research/whitepaper.md`** while a local Git vault lacks that file—use Hub path in `depends_on`; reconcile body text with **`bornfree-pwa/public/whitepaper.md`** / **`bornfree-hub/docs/01-COMPREHENSIVE-WHITEPAPER.md`** per registry changelog when diff matters.

## Related

- Parallel outline (tool track): `projects/store-free/outlines/positioning-and-messaging-2026-04.md`
- Canonical Born Free / Store Free URLs: `projects/store-free/research/public-sources-2026.md`
- Knowtation public URLs (when ecosystem copy references the product): `projects/knowtation/research/public-sources-2026.md`
- Competitive guardrails (thin evidence; **[NEEDS CONFIRMATION]** on matrix depth): `projects/store-free/research/competitive-snapshot-2026-04-24.md`