The master synthesis. Pulls together findings across all workstreams — positioning, segments, competitive landscape, pricing, founder dynamics, culture model, product concept and the conceptual flip — into a single hierarchical reference document.
1.1 Executive Summary
1.1.1 FC is building a creative OS for early-stage concepting: reduces context fragmentation and tool friction while preserving taste and judgement.
1.1.2 The wedge is agency pitching — most acute pain (fragile, high-stakes, up to £200k per pitch), messiest workflow (tool switching, lost references), clearest ROI (speed, win-rate, cost reduction).
1.1.3 The deeper moat is a creative memory and context engine: persistent, structured context across project, user and agency, plus governance and audit trails.
1.1.4 Core brand paradox: structured context under the hood, freedom on the surface. Playground where the tools disappear.
1.2 Key Themes
1.2.1 Context fragmentation is the core pain. The problem is not "make content" but "maintain context" — brief constraints, brand constraints, references, decisions, rationale, prior learnings, digital fingerprint.
1.2.2 Taste is the scarce resource. "All that's left is taste." Human selects among machine suggestions. Overemphasising AI outputs triggers "slop" narrative. Emphasising taste leverage aligns with founders' worldview.
1.2.3 Freedom vs structure. Sell creative freedom, build structured systems. Solve it = differentiation. Fail = rigid enterprise tool (rejected by creatives) or chaotic sandbox (fails in teams).
1.2.4 Pitching as wedge. Agencies spend up to £200k per pitch. Measurable ROI: time saved, win-rate lift, cost avoided.
1.2.5 Governance and audit as real wedge. Audit trails of prompts, models, assets for legal/brand risk. Frame as "provenance" and "receipts" — powerful enterprise-tier driver.
1.2.6 Founding team as a system. Conor (vision) → Polina (product direction) → Marin (reality). Remove one and it breaks. Strength and scaling risk — imbalance is the failure mode.
1.3 Jobs To Be Done
1.3.1 Primary: vague → sharp → pitchable, without losing context.
- 1.3.1.1 Expand and refine directions from a seed idea
- 1.3.1.2 Stay brief-aligned and brand-aligned while exploring
- 1.3.1.3 Gather and curate references (visual, tonal, cultural)
- 1.3.1.4 Produce pitch-ready artefacts: decks, scripts, frames, concept film
- 1.3.1.5 Preserve provenance and decisions for team continuity
1.3.2 Secondary: reduce tool-proficiency barriers, keep creators in flow. Remove switching friction; let creators work their way while the system structures and exports.
1.3.3 Emerging: creative memory that compounds. Reuse past learnings, constraints, preferences. Stop re-asking "why did we decide that?"
1.4 Core Tensions
1.4.1 Freedom vs structure. Creatives resent tools that feel like timesheets. Teams need traceability. UX must feel expressive; backend must be strict.
1.4.2 Speed to pilots vs building moat. Pitch urgency demands fast pilot-win loop. Memory/context engine needs protected investment. Next steps and planning addresses this.
1.4.3 Seat-based vs usage-based pricing. Current: £50/seat/month. AI costs are usage-driven. Hybrid (seats + usage quotas + overages) likely, needs crisp packaging.
1.4.4 AI scepticism vs curious leading edge. 90%+ creatives already using AI weekly. Target the curious. Narrative should not trigger sceptics.
1.4.5 Clean code vs ruthless shipping. Codebase deliberately imperfect during PMF pursuit. Needs explicit "pay down debt" milestone gate.
1.5 Founder Motivations
1.5.1 Conor — momentum, cultural proximity, relationship-led GTM. Wants to be in rooms where culture is shaped. Not money-motivated.
1.5.2 Polina — meaning, identity, empowering creatives. Conviction about synergistic AI-human collaboration shapes the product's soul.
1.5.3 Marin — first-principles builder. Wants something people use daily and love. Irrelevant until people pay. Pragmatic to the core.
1.6 Positioning Signals
1.6.1 Recurring frames across all materials:
- 1.6.1.1 AI-native workspace (not a chatbot) for creative teams
- 1.6.1.2 Taste-first, judgement-first (anti-slop)
- 1.6.1.3 Context engine and creative memory as compounding advantage
- 1.6.1.4 Playground + structure: UI feels like freedom, backend keeps receipts
1.7 Questions for the Team
1.7.1 Product clarity:
- 1.7.1.1 What is the pitch-concepting workflow in 3-5 steps? Must-have output artefacts?
- 1.7.1.2 What does "70% faster" mean? Faster vs what baseline?
- 1.7.1.3 Minimum viable "single source of truth" — what must be captured?
1.7.2 Differentiation:
- 1.7.2.1 Non-negotiable differentiator: browser extension, creative memory, governance trail, or concepting-loop UX?
- 1.7.2.2 Where does "creative DNA" land in the roadmap?
1.7.3 Commercial:
- 1.7.3.1 Who is the initial economic buyer? CD, strategy lead, ops, agency leadership?
- 1.7.3.2 What packaging drives easiest pilot-to-paid: seats, usage, or pitch packs?
1.7.4 Brand:
- 1.7.4.1 How to articulate "tools disappear, context remains" in creative-native language?
- 1.7.4.2 Tone: iconoclastic rule-breaker vs professional reliability? Can the brand hold both?
1.7.5 Scaling:
- 1.7.5.1 What rituals prevent imbalance across speed, meaning and execution?
- 1.7.5.2 Is "creator fingerprint" something FC will build? If yes, what privacy/IP model?