Skip to content

Mission, Vision & Values

Phase: 5 — Brand Project: likeness Date: 2026-05-09 Confidence: Medium-High — these are crafted to serve the strategy, but mission/vision is finally a founder choice; pick one or remix.

How to read this document

Three options for mission and three for vision are presented below. They are not all the same — they differ in tone, scope, and where they sit on the spectrum from defensive (protect creators) to expansive (build new infrastructure). After the options, a single recommended values set is presented because values benefit less from variation: the strategy already constrains what they should be.

The skill expects mission/vision to be founder-authored. The job here is to present credible drafts the founder can pick from, edit, or reject.

Mission

A mission says what the company is doing now, in present tense, action-oriented. Three drafts:

We give adult creators the infrastructure to license their own AI likeness on their own terms — and revoke it whenever they choose.

  • Strengths: leads with the worker; uses "license" and "revoke" specifically (the load-bearing words from 01-discovery/target-audience.md's language map); sounds like a tool the creator uses, not a service the platform provides them.
  • Weaknesses: doesn't explicitly name the alternative (gray-market deepfakes); creators reading it cold may not understand the urgency.

Option M2 — Defensive frame

We replace the gray market for AI-generated adult content with a platform where the creator owns the license, sets the rules, and earns the revenue.

  • Strengths: names the enemy (gray market); makes the "supply side, not victim side" framing from the founder brief explicit; suitable for press and investor materials.
  • Weaknesses: contains the word "gray market" which is jargon to people new to the space; longer.

We build consent infrastructure for AI-generated likeness, starting where the unauthorized-use problem is loudest.

  • Strengths: positions as infrastructure, which is the correct frame for capital and partnerships; "starting where" admits the platform's narrow MVP scope without selling it short; lines up with the regulatory tailwind.
  • Weaknesses: less emotionally direct; a creator hearing this on a sales call wouldn't immediately know what it means for them.
  • Creator-facing site copy and outreach: M1
  • Investor deck and pitch: M3
  • Press positioning and policy conversations: M2 or M3

The fact that audiences have different missions is not unusual — Stripe, Linear, and Notion all do this. The mission behind the mission (what the company is actually doing) is constant; the framing adapts to who's reading.

Vision

A vision says the world the company is building toward. Aspirational but credible. Three drafts:

Option V1 — Worker rights extended into AI

A future where every person whose face, body, or voice is used in AI-generated content does so by their own consent, on their own terms, with the right to revoke.

  • Strengths: extends naturally from M1 / M2; aligns with the active labor-movement framing in docs/founder-brief.md; aspirational in the right direction.
  • Weaknesses: describes a state of the world, not a state of the company. Investors typically want a more company-shaped vision.

Option V2 — The legitimate alternative becomes the standard

A creator economy where consent is the default, provenance is verifiable, and licensed AI is a normal revenue line — not a gray-market threat.

  • Strengths: paints a credible 5-10 year future; lines up with regulatory direction (TAKE IT DOWN, NO FAKES, EU AI Act); investor-shaped.
  • Weaknesses: starts to sound conventional; "creator economy" is the kind of language CLAUDE.md flags as marketing-speak. Could be tightened.

A future where adult creators are the default authors of AI versions of themselves — and the gray-market industry that grew around them without consent stops being economically viable.

  • Strengths: specific to Likeness's beachhead, not pretending to be a generic AI infrastructure company; names the displacement explicitly; sharper than V2.
  • Weaknesses: pins the company to a vertical that may or may not be the long-term scope. (Counter: vertical-specific vision serves the company well at pre-seed stage; expansion can update the vision later — Stripe started as "payments for developers," Linear as "issue tracking for design-led teams.")

V3 is the recommended primary vision for fundraising and external positioning at pre-seed. V1 is the right vision for creator-facing materials, where worker-rights framing is most resonant. V2 is acceptable but less sharp.

Values

A single recommended set of five values, with concrete what-this-means-in-practice statements. Values that don't help make decisions are worthless; each of these is designed to be invoked when a real decision is contested.

When a feature, partnership, or shortcut would speed something up but compromise consent infrastructure, we don't ship it.

In practice: - We say no to model export even when a fan or partner asks for it. - We say no to processor diligence shortcuts that ask us to weaken license rules for category breadth. - We say no to creators asking us to disable the audit log on their own model "for performance" — the log is the consent record.

2. Plain talk

We don't soften the hard parts. We tell creators what we can and can't do, in adult-to-adult language, and we expect the same from each other internally.

In practice: - The line "anyone selling perfect rights management on the internet is lying" stays in our materials. - We name when something doesn't work yet rather than dressing it up as "in beta." - Internal disagreement is communicated directly. No politicking, no triangulating through Slack DMs.

3. The creator is the customer

Our customer is the creator. Not the studio, not the agency, not the processor, not the investor. When their interests conflict with ours, we update our interests.

In practice: - Pricing decisions resolve in favor of creators when there's a tradeoff. - The Creator Ops cofounder has unilateral veto on creator-impacting product decisions where there's clear creator-side concern. - We don't run features past creators after-the-fact; we co-design them upfront.

4. Architecture as policy

What the architecture cannot do is what we promise will not happen. We don't write policies that depend on people behaving well; we build systems where the bad behavior is impossible.

In practice: - Models never leave the platform — not because we promise, but because there's no export path in the code. - License-gating runs before model loading — not as a check we could disable, but as a structural requirement. - Per-creator isolation is enforced at the inference layer, not as a guideline.

5. Compounded compliance

We treat compliance like compound interest: invest above the floor early, and the returns compound. We don't catch up to regulation; we run ahead of it.

In practice: - We adopt C2PA from day 1, not when forced. - We treat AI of real performers as 2257-covered before 2257 is forced to clarify it. - We build for the regulatory floor of 2027, not 2026.

If forced to a single combination:

Mission: M1 (creator-facing) + M3 (investor/policy) — kept as parallel framings, both authored by the company, used per audience.

Vision: V3 (primary, fundraising and external positioning).

Values: All five as above. Each was crafted to address a specific decision-making moment that the strategy and research surfaced — pulling any of them weakens the whole.

Strategic Connections

  • The values directly reflect the architectural commitments in 01-discovery/raw/'s ML brief and the regulatory analysis. They are not generic cultural statements — they are operationalizations of the company's design.
  • M1's worker-controlled framing connects to the labor-movement context in docs/founder-brief.md and the language map in 01-discovery/target-audience.md.
  • M3's infrastructure framing connects to the funding comparables in 01-discovery/raw/trends.md (Loti / Vermillio as mainstream consent infrastructure).

Flags

Red Flags: - None.

Yellow Flags: - The mission options assume an outside-in technical founder and an upcoming Creator Ops cofounder. If the Creator Ops hire pulls the company in a different cultural direction (warmer, more service-oriented, more agency-like), the founder should expect to revise the M1 framing in particular. Review with Creator Ops cofounder once hired. - Values 3 and 4 are operational commitments that have to be defended under pressure. If the company can't actually live them when investors or partners push, they should be removed, not weakened. Empty values are worse than fewer values.

Sources

  • 02-strategy/lean-canvas.md — strategic anchor
  • 01-discovery/target-audience.md — language map (informs M1)
  • 01-discovery/industry-trends.md — regulatory direction (informs Value 5)
  • docs/founder-brief.md — labor-movement context (informs V1, V3)