# Shoreline Brand Guide Research date: June 5, 2026 ## Strategic read Shoreline is an early-stage podcast about building with AI in real life. It does not feel like a polished corporate AI show, and that is a strength. The best version of the brand is a clear, useful, slightly intimate companion to long-form conversations about agents, workflows, knowledge systems, tool choice, and the taste required to make AI useful. The website should become the "company brain" for the podcast: every episode gets turned into searchable notes, resources, links, definitions, transcripts, and practical follow-up paths. ## Origin story Shoreline is named after the small house off Shoreline Boulevard in Mountain View where Enzo Sison and Will Meinhardt lived together near Google headquarters. The name should feel grounded in a real place, not like a generic coastal metaphor. It carries the show's useful tension: two friends and operators talking from lived experience, close to the center of the AI and technology world, but focused on practical work rather than spectacle. ## Brand role Shoreline sits at the edge between tools and judgment. It is not just a podcast archive. It is a field notebook for people trying to understand what AI is doing to work while they are actively using the tools themselves. ## One-line positioning Shoreline is a field conversation about building with AI where tools, taste, and real work meet. ## Alternate taglines - Conversations from the edge of AI-native work. - Where AI tools meet taste, workflow, and reality. - A working notebook for the company brain era. - Long-form conversations for people building with agents. - AI, workflows, and the human judgment between them. ## Brand promise Listen for the conversation. Visit the site for the working memory. Every episode should leave behind something useful: a map of ideas, a list of tools, a resource trail, and a clearer mental model than the listener had before. ## Audience Primary audience: - AI-native operators, founders, builders, and creative technologists. - People using Claude, Codex, Cursor, OpenAI, Notion, and automation tools in actual work. - Teams trying to build a company brain, internal agent workflows, or practical AI operating systems. - Curious listeners who want real examples instead of hype-cycle summaries. Secondary audience: - Sales and growth operators testing AI prospecting workflows. - Consultants and small agencies building repeatable AI services. - Technical generalists who want language for what is changing in work. ## Core themes - Company brain: memory, knowledge management, internal context, durable notes. - Agentic work: agents as collaborators, workers, coordinators, and interfaces. - Workflow automation: prospecting, productivity systems, routing, operations. - Tool ecosystems: Codex, Claude Code, Cursor, OpenAI, Notion, Anthropic, and adjacent products. - Token economics: token budgets, cost awareness, model routing, OpenRouter-like infrastructure, and when more context changes the answer. - Human judgment: taste, review loops, "slop detection", and knowing when AI is useful versus merely impressive. - The end of apps: work moving from fixed software surfaces into agent-driven interfaces. ## Voice The voice should feel like two sharp operators thinking out loud after actually using the tools. Use: - Clear, specific language. - Practical curiosity. - Concrete nouns: agents, memory, workflows, prompts, transcripts, tools, costs, tasks, notes. - First-principles explanations without sounding academic. - Occasional casual phrases when they carry real meaning. Avoid: - Generic AI hype. - Corporate futurism. - Empty words like "transform", "revolutionize", and "unlock" unless backed by a concrete example. - Overly poetic shoreline metaphors. - Pretending the show is bigger or more institutional than it is. ## Visual identity The current public artwork points to a simple, usable direction: - Logo: minimal horizon/sunset mark with thin black lines. - Wordmark: spaced "SHORELINE" lettering. - Banner: warm coastal walking image with surfers, sand, ocean, and a quiet sunset tone. - Episode thumbnails: mostly black backgrounds, white episode numbers, video call cutouts of the hosts, soft glow, and small Shoreline mark. - Episode 3 thumbnail: full coastal artwork with tool logos, implying the show can move between beach-like brand calm and very practical AI tooling. The site should preserve that contrast: calm coastal brand on the surface, dense practical AI notes underneath. ## Color system Use a restrained palette derived from the public artwork. Primary: - Ink: `#000000` - Off white: `#f6f6f6` - Interview charcoal: `#161517` Coastal accents: - Warm sand: `#e9bf92` - Sunset peach: `#ecb783` - Tide glass: `#8eafae` - Sea fog: `#9eb8b3` - Driftwood: `#6a6457` Guidance: - Let black, white, and off-white do most of the work. - Use warm sand and tide glass as quiet accents. - Avoid neon AI gradients, purple-blue SaaS palettes, and overly beachy blues. - Use the coastal colors to create atmosphere, not decoration. ## Typography direction Use typography that feels editorial and direct. Recommended direction: - A clean sans serif for UI, notes, and metadata. - A compact display style for episode numbers and page headlines. - Monospace only for tools, commands, timestamps, and model names when useful. Keep letter spacing normal in body text. The wordmark can be spaced, but site copy should stay easy to read. ## Imagery direction Use: - Real episode frames. - Host video-call imagery. - Tool screenshots or logos when tied to a specific episode. - The shoreline image as a calm brand anchor. - Simple annotated resource cards. Avoid: - Abstract AI stock art. - Pure gradient hero sections. - Generic beach photography with no connection to the show. - Decorative visuals that make the site feel less useful. ## Naming rules Show name: - Use `Shoreline` as the primary brand name. - Use `Shoreline Podcast` only when a platform field needs clarity. - Use `@ShorelinePod` for the YouTube/social handle. Episode titles: - Prefer searchable topic titles over generic numbering. - Format: `[Specific topic phrase] | Shoreline Ep. N` - Good example: `AI Agents and Knowledge Management: Building a Company Brain | Shoreline Ep. 1` - Good example: `Token Maxing and the Company Brain Era | Shoreline Ep. 3` Site navigation: - `Episodes` - `Topics` - `Resources` - `About` - `Listen` Avoid vague navigation like `Explore`, `Insights`, or `Learn More` unless the page content is extremely clear. ## Website principles The first screen should make the podcast useful immediately. Do not start with a marketing landing page. Recommended first impression: - Latest episode. - Search or topic filters. - Clear access to resources and notes. - YouTube/listen links. - A compact explanation of what Shoreline is. The site should feel like: - A searchable show notebook. - A resource companion for people who heard a tool, idea, or reference and want to find it again. - A calm, minimal interface with enough density to reward repeat visits. ## Editorial standards Every episode page should include: - Plain-language summary. - Topic hooks. - Timestamped chapters. - Tools mentioned. - Links and resources discussed. - Definitions of useful terms. - Transcript or transcript-derived notes. - Related episodes. Every resource should include: - Why it matters. - Which episode mentioned it. - Timestamp or context when available. - Link status. - Category: tool, article, company, concept, book, person, framework, or quote. ## About copy draft Shoreline is a podcast by Will Meinhardt and Enzo Sison about building with AI at the edge of real work. The name comes from the small house off Shoreline Boulevard in Mountain View where they lived together near Google headquarters. They talk through agents, company brains, automation, tool choices, and the human taste needed to make new systems useful. The website collects the notes behind the conversations: episode resources, timestamps, tools, definitions, and follow-up reading. ## Meta description draft Shoreline is a podcast about AI agents, company brains, workflow automation, and the practical judgment behind AI-native work. ## Site CTA language Use direct commands: - Watch episode - Listen now - Read notes - View resources - Search topics - Send a resource Avoid oversized promises like: - Transform your workflow - Unlock AI productivity - Discover the future ## Brand constraints - Keep the brand useful before making it flashy. - Keep AI topics concrete and searchable. - Preserve the early-show intimacy. - Build the website around episode memory, not promotion alone. - Let the shoreline metaphor stay quiet: edge, boundary, tide, signal, not constant beach language.