Foundry Foundry

Marketing Copy Seeds

Drafted 2026-05-19. Raw material for the eventual landing-page sprint. These are positioning lines that emerged organically during architecture conversations and felt sharp enough to save. Refine before publishing — not all are tagline-ready.

This doc is intentionally messy. When the landing-page sprint runs (post-beta), pull from here, refine, A/B test.

Headlines / Taglines (raw material)

Existing brand line (from Claude Design):

  • "The document layer your work earns."

Strategic positioning lines (descriptive — refine into shorter taglines):

  • "Generic, inspectable, BYO-data KB that plugs into existing AI tools rather than competing with them."
  • "Inspectable knowledge bases that you BYO data to, integrated into the AI tools your users already approved."

Customer-quote-style hooks (sound like things buyers would say):

  • "We don't need to approve a new AI tool, just a new data source."
  • "Stop approving new AI tools. Start feeding the ones you have."

Internal strategic mantras (NOT for customer-facing copy, but useful for sales conversations + investor narrative):

  • "MCP is the product, not a feature."
  • "Web chat is the demo. MCP is where the product lives."
  • "Boring infrastructure is the high-leverage play right now. Everyone else is chasing capability gains; the gap is in the substrate underneath."

Positioning angles to lean on

Procurement-friction angle (the wedge): enterprise IT already approved Copilot / Claude Desktop / Cursor. We're not asking them to approve a new AI tool — just a new data source for the AI tool they already approved. Cuts deal cycles from quarters to weeks.

Inspectability angle (the original Autri wedge): every chunk anchored to its source page with a bounding-box overlay, every retrieval result tagged with the index that surfaced it (semantic / lexical / section), every document carries a confidence tier (green / yellow / red). Trust through legibility.

Multi-tool angle: not locked to one AI vendor. Plug Autri into Copilot today, Claude Desktop tomorrow, Cursor next week. The knowledge stays with you; the AI tools rotate.

Solo-author / team-author angle: Author tier for a single writer with one big body of work (mom's novel). Team tier for a small org (STEM Racing) with shared institutional knowledge.

Compounding angle (long-term): Autri's KB substrate is a platform other apps can build on. QuoteAI is the proof. Your knowledge becomes infrastructure.

What we're NOT

Anti-positions (clarify by negation — useful for sales conversations):

  • We are NOT another AI chatbot destination (Glean, Notion AI, ChatGPT Business).
  • We are NOT a DIY framework (Pinecone + LangChain).
  • We are NOT a single-vertical AI tool (legal AI, healthcare AI).
  • We are NOT a Microsoft replacement.
  • We are NOT trying to host the AI. We're trying to host your knowledge.

Audience-specific seeds

For prosumers / authors (Mom-tier):

  • "Your manuscript, queryable. From inside Claude. Or Cursor. Or whatever you write in."
  • "Your book becomes a thing you can ask questions to."

For small teams (STEM Racing-tier):

  • "Your team's institutional knowledge, pluggable into your team's AI tools."
  • "FIA Regulations + your team's internal wiki + your race strategy docs — all queryable from inside Copilot."

For enterprise (Brehob / Dan's day-job / future leads):

  • "BYO institutional knowledge to the AI tools your team already uses."
  • "We don't replace your AI. We feed it."

Sources / where this came from

  • 2026-05-19 strategic gut-check conversation between Dan + AI assistant during the locked-direction session
  • Dan flagged the descriptive lines as "the marketing plan" — saving verbatim as seed
  • Original "document layer your work earns" line is from Claude Design's brand work

Next steps

  • Refine into 3-5 actual tagline candidates (shorter, punchier) during the landing-page sprint
  • A/B test on beta users — which framings resonate?
  • Customer interviews during/after beta — capture the language real users use to describe Autri. That language goes on the landing page; ours doesn't.
  • Anti-positions are valuable for sales decks — keep these crisp.

Review

🔒

Enter your access token to view annotations