Every CEO Dan Shipper presents a portion of the company's internal 2026 strategy, explaining how Every is becoming a fully AI-native platform: unifying its writing, apps, and training into a single subscription and shifting its software toward an agent-native model in which AI agents collaborate across products to do real work. # Channel Identity Observations: "Every" (AI-Native Company) ## Explicit Self-Description (Creator Claims) ### Subscription Business Model - The channel/company describes itself as a **bundled subscription**: *"Every is the only subscription that you need to stay at the edge of AI."* - Claimed three components: - **Ideas** — *"a daily newsletter about AI"* - **Apps** — four AI apps (writing, email, file organization, speech-to-text) - **Training** — *"camps and courses where we teach you about how to use these tools"* ### Named Products - **Kora** — *"an email agent"* - **Monologue** — *"a smart dictation app"* / speech-to-text - **Spiral** — *"our writing agent"* - Custom CMS, a consulting business, and a **Claude Code plugin** teaching "compound engineering" ### Claimed Positioning - Aspiration to be an **"archetypal AI native company"**: *"we figure out for ourselves how to build and work and live in this new future. And then we become an example for other people to follow."* - Reputation claim: *"people think of us and the vibe checks that we do... they think what is Every's take"* — day-of-release hands-on product evaluations. - Goal: *"be the number one place where people go to learn to code, write, and design with AI."* ### Claimed Traction (Unverified Creator Claims) - *"We hit 3 million in total revenue, which is 3x growth"* and *"two million in ARR"* for 2025 - Team size: *"we're a team of about 20 people"* running four software products - 2026 target: *"3x our revenue again"* to ~$6M ARR / $10M total, claimed *"purely organic"* growth ## Intended Audience - **AI-curious professionals** experiencing technology anxiety: people *"feeling like I can't keep up and I don't want to be left behind"* - **Hands-on learners** — training is described as *"really hands-on"* (e.g., Claude Code, "codecs") - **Enterprise clients** — *"we do big enterprise deals where we do trainings"* - Dual audience ambition: *"the audience is humans but it needs to be both humans and agents"* — writing intended to be consumed by AI agents as well as people ## Claimed Scope & Philosophy - **"AI first in every way"** internal culture — *"Writing code into a code editor you're weird"* - Operating loop: *"we live in the future... we write what we see... we go build that... we teach what works"* - Mission framing: helping people *"live and work with AI in a more flourishing, creative, better, more human way"* - Analogical positioning vs. model labs: *"asking an oven maker how to bake a soufflé"* — the channel claims authority as a practitioner, not a model builder - Explicit editorial value: *"we keep the human soul, the human storytelling as the core of Every"* ## Observable Presentation Patterns (Demonstrated) - **Transparency about internal operations**: the video presents an *"internal strategy presentation"* publicly, including quarterly milestones (Q1–Q4 2026 product roadmap) and revenue figures - **Thought-leadership vocabulary**: coins/promotes terms like *"agent native"* (*"apps that are cloud code in a trench coat"*), "compound engineering," "vibe checks" - **Narrative-driven founder voice**: personal storytelling about company history since 2020, wave-spotting instincts (*"I had that tingle feeling"*), positioned to model a philosophy for viewers - **Marketing-adjacent framing**: the strategy consistently maps company goals back to the subscription bundle (*"that maps very cleanly onto the bundle that we're building"*) ## Notes on Evidence Quality - All revenue, growth, and traction figures are **creator claims** with no external verification in the source material - No curated metadata was supplied; observations rest entirely on title and transcript - No private motivations were inferred beyond the creator's direct statements (e.g., *"really important to me"* regarding vibe checks) # Delivery Observation: "Our Full Strategy for Building a Truly AI-Native Company in 2026" ## Overall Tone - **Conversational, informal first-person presentation** — the speaker addresses the audience directly as if sharing an internal deck: *"All right, welcome to 2026. So, here's a section of our internal strategy presentation."* - **Enthusiastic and candid**, mixing strategy with self-deprecating humor: *"I actually did that whole background for the team too because after 10 days of vacation, who knows what I barely remember what we do."* - **Reflective confessional moments** about intuition and timing: *"I had that tingle feeling and that's one of the reasons why we really went all in."* ## Vocabulary & Signature Phrases - **"AI first" / "AI native" / "agent native"** used repeatedly as core framing terms: - *"It's AI first in every way."* - *"we're going to be fully agent native"* - *"I hope that we have an opportunity to be an archetypal AI native company."* - **A distinctive metaphor for the central concept:** *"apps that are cloud code in a trench coat"* — repeated with acknowledgment: *"I think that cloud code and trench code metaphor should tell you most of what you need to know."* (Note: "trench code" appears to be a transcript rendering of "trench coat.") - **Another vivid analogy** to dismiss a category of competitors: *"I think that's asking an oven maker how to bake a sule."* (likely "soufflé" in the audio.) - **Superlative intensifiers** appear throughout: *"crazy,"* *"ginormous,"* *"gigantic consequences,"* *"super proud,"* *"really cool."* ## Structural / Teaching Habits - **Enumerated roadmap structure** — the plan is delivered as quarter-by-quarter milestones, each introduced the same way: - *"One is by the end of Q1..."* - *"By the end of Q2, we're going to have..."* - *"By the end of Q3, what I want to do is..."* - *"by the end of Q4, I think you'll be able to see..."* - **Concrete product examples to explain interconnection**, with named apps and specific scenarios: - *"When Corora wants to compose an email, it can talk to Spiral, which is our writing agent."* - *"When Monologue, which is our smart dictation app... it'll be able to talk to Kora."* - **Number-heavy evidence delivery** for credibility: *"We hit 3 million in total revenue, which is 3x growth. We hit two million in AR which is again 3x growth"*; *"we're a team of about 20 people and we have four separate software products."* - **Loop framing** as an organizing teaching device: *"we live in the future. We write what we see... we teach what works."* ## Recurring Communication Patterns - **First-person conviction statements** anchoring priorities: *"It's very important to me that we keep the human soul, the human storytelling as the core"*; *"that's really exciting and I think also very important to me."* - **Hedged confidence** — strong claims softened with "I think," which appears very frequently: *"I think we're in a moment for that right now,"* *"I think that would be really cool,"* *"I think that's why we're here."* - **Short declarative verdicts** punctuating longer passages: *"Writing code into a code editor you're weird"* (apparently meaning manual coding is now unusual), *"That's crazy,"* *"That's what we're building."* - **Anticipating audience anxiety** as a rhetorical move: *"people feeling like I can't keep up and I don't want to be left behind... there's a real need for people to actually figure out how do you live a more creative more human future with this technology."* ## Stable Patterns vs. Isolated Moments - **Stable (repeated across the talk):** the "I think" hedge; quarter-based enumeration; naming specific products (Kora, Spiral, Monologue); enthusiasm markers ("really cool," "crazy"); first-person ownership of vision ("I want," "I hope"). - **Isolated:** the humor about post-vacation memory loss, the "oven maker" analogy, and the "tingle feeling" anecdote each appear once — memorable but not repeated habits. ## Uncertainty Notes - Punctuation and some word boundaries come from a rough transcript (e.g., "every" for the company name, "AR" for ARR, "su(le)" for soufflé, "trench code"), so exact phrasing beyond quoted spans carries some transcription uncertainty. - Tone judgments (enthusiasm, candor) are inferred from word choice and structure only; no audio cues are available in this source. # Position Record: "Our Full Strategy for Building a Truly AI-Native Company in 2026" ## Source - **Video ID:** 01a0f15a-b485-7e0f-89cb-b94a06c220a1 - **Speaker:** Unnamed presenter (identified as founder/leader of "Every," speaking from an internal strategy presentation) - **Format:** Excerpt of internal strategy deck, framed as public-facing narration --- ## Business Structure (as described) The speaker positions Every as "the only subscription that you need to stay at the edge of AI," built on three components: - **Ideas:** a daily AI newsletter - **Apps:** four AI apps — writing (Spiral), email (Kora), file organization, speech-to-text (Monologue) - **Training:** camps, courses, and enterprise deals teaching hands-on AI tool use (e.g., Claude Code, "codecs") The speaker frames the company as a **loop**: 1. **"Live in the future"** — everyone uses the tools daily; "AI first in every way" 2. **Write what we see** — "Writing I think is the soul of Every"; articulating the future "brings that future into being" 3. **Build what's missing** — apps emerge from internal needs 4. **Teach what works** --- ## Claims and Positions ### Performance claims (2025) - **$3M total revenue**, described as **3x growth** - **$2M ARR**, also described as 3x growth - Speaker notes tension with six years of running the business: "we finally hit it" - Believes Every "cemented our status" via **vibe checks** — day-of-release hands-on evaluations of new models/products - Team of ~20 people running **four software products**, a **custom CMS**, and a **consulting business** — called "crazy shape for a business to have" (acknowledged, not smoothed over) ### 2026 targets - Plan to **3x revenue again**: ~$6M ARR, ~$10M overall revenue - Speaker claims this is "really doable" — reasoning: last year's growth was "purely organic," so "a very good shot to do this or better" ### Unified platform and ecosystem - Current state: apps and content "live in separate silos" (admitted deficiency) - Plan: a platform layer where apps communicate, plus a **centralized model of user identity and interests** to improve apps and content ### Quarterly milestones (stated as "what it looks like if things are working") - **Q1:** products talk to each other (e.g., Kora asks Spiral for writing/style; Monologue pulls vocabulary from Kora for its custom dictionary) - **Q2:** central user-context concept built from "what you write, what you say to your computer, your emails, and your files" — portable to ChatGPT/Claude - **Q3:** personalized content; speaker insists on "keeping the human soul, the human storytelling as the core of Every" while arguing "it's weird for everyone to get the same newsletter every day" - **Q4:** ecosystem reframed as "an ecosystem of agents that all know about each other" ### Agent-native software (core thesis) - **Claim:** agent-native apps are "basically Claude Code in a trench coat" — instead of manually written code and UI, an agent "kicks off" to do the work - All Every software moving agent-native "over the next couple months" - **Claim:** Anthropic's bet — "if you make a great software agent, it becomes a really good general agent" — is true, evidenced by Claude Code and the Claude agent SDK - Stated consequences: "gigantic consequences for software, for writing, for design, for company building" ### Writing for humans *and* agents - Current writing audience is humans; the speaker argues it "needs to be both humans and agents" - Example given: articles on **compound engineering** (Every's engineering philosophy) paired with a Claude Code plugin teaching the agent that philosophy ### Organizational collaboration goals - Goal: everyone pushing to each other's apps; already happening but requiring repo setup and **merge etiquette** norms (how/when to submit features or fixes without burdening app GMs) - Next level: customers submitting PRs, detailed bug reports, or feature specs that Every can "oneshot with Claude" --- ## Reasoning Patterns - **Build-from-need logic:** Apps exist because writing about the future revealed gaps; "the tools that we sell are tools that we build for ourselves" - **Analogy defending the company's role:** Asked who should teach people to live with AI, the speaker says model builders are the wrong teachers — "That's asking an oven maker how to bake a souffle" — so it falls to "people on the edge doing work" - **Wave-detection pattern:** Speaker cites a personal "tingle feeling" at prior waves (creator economy 2020, GPT-3 2022, post-ChatGPT pivot) and claims the same feeling now about agent-native apps — presented as intuition, not evidence - **Aspiration:** Every as an "archetypal AI-native company" — figure it out internally, become an example others follow and subscribe to --- ## Qualifications and Unresolved Tensions (preserved as stated) - The speaker admits not remembering the business after 10 days of vacation ("who knows, I barely remember what we do") - Silos between apps are acknowledged as a current problem - Cross-app collaboration goals are explicitly incomplete: "there's a lot that needs to be done" - The Q3 goal contains an explicit tension: hyper-personalization vs. keeping "the human soul" as the core - Revenue targets are framed as the speaker's own belief ("I think that's really doable"), not settled fact - The "Claude Code in a trench coat" metaphor is offered as sufficient explanation, with detail deferred — a self-acknowledged simplification - Speaker acknowledges widespread **anxiety, FOMO, and fear of job change** created by agents, alongside the "good things" # Speaker Attribution Record ## Video **Title:** Our Full Strategy for Building a Truly AI-Native Company in 2026 **Video ID:** `01a0f15a-b485-7e0f-89cb-b94a06c220a1` ## Speakers & Roles ### Primary (sole) speaker - **Role:** Creator / company founder-presenter - **Evidence:** Opens with a section of an internal strategy presentation: *"here's a section of our internal strategy presentation"*; refers to running the business for six years, addressing the team, and owning the 2026 strategy. - **No other speakers** appear in the transcript. No guests, narrators, or third-party voices are present. ## Provenance Notes ### First-party claims (speaker's own business) - Company called **"Every"** — subscription bundling newsletter, four AI apps, and training (camps/courses, enterprise training). - Named in-house products: **Kora** (email agent), **Spiral** (writing agent), **Monologue** (speech-to-text app), plus a custom CMS. - Self-reported metrics: **$3M total revenue** (3x growth), **$2M ARR**, ~20-person team — **unverified, first-party claims**. - Cited tools used internally: **Claude Code**, **Codex**, **Claude Agent SDK** (Anthropic). ### Third-party references - **Anthropic** — described as betting that great software agents become general agents; source of Claude Code and agent SDK. - Historical references to **GPT-3** and **ChatGPT** as industry moments; no external sources, data, or citations provided for these claims. ### Promotional Segments — Flagged - The entire presentation is **self-promotional in nature**: it markets the Every subscription ("the only subscription that you need to stay at the edge of AI") and previews product plans for 2026. - No third-party advertising or sponsored segments are present in the transcript. ### Availability & Metadata Limits - **No curated metadata supplied** — speaker's personal name, channel identity, and publication details are **not established** by the source. - **Comment availability:** not indicated in the provided material. - **Timestamps:** none present in the transcript. All right, welcome to 2026. So, here's a section of our internal strategy presentation to talk to you about where we're going. Okay, every is the only subscription that you need to stay at the edge of AI. That's what we're building. We have three main components of the business. We do ideas, so that's a daily newsletter about AI. We've got apps. So, we have four different AI apps that help you write with AI, help you email with AI, help you organize your files with AI, do does speech to text with AI. Then we have training. So we do camps and courses where we teach you about how to use these tools like cloud code or codecs in a really hands-on way. We do that all under one subscription and we build things in this loop where at the start of the loop we live in the future. So we're all of us it's this really cool creative playground where all of us are using all these tools every day. It's AI first in every way. Writing code into a code editor you're weird. So we're living in the future. We write what we see. Writing I think is the soul of every and by articulating the future that you're living in, you bring that future into being because you can now talk about it with the people that you work with. And so we write in order to make that future visible to each other and to the people who read us and one of the consequences of that is it makes it really easy to tell what's missing and then we go build that and that becomes all the apps that we make. Kora which is an email agent or monologue which is speechto text app. These are all things that come from our own our own needs. And then we teach what works. So we take all that stuff and we teach it in camps and courses and we do big enterprise deals where we do trainings to teach people how to use AI. So that's like the quick background. I actually did that whole background for the team too because after 10 days of vacation, who knows what I barely remember what we do. This is such a cool time because 2025 was a huge breakout year for us. We hit 3 million in total revenue, which is 3x growth. We hit two million in AR which is again 3x growth. So that's amazing and it's just I've been running this business for six years so having a year like this is just we finally hit it. I also feel like we really cemented our status where people think of us and the vibe checks that we do. Whenever a new model comes out or new product comes out they think what is every's take which is really important to me and I think we've done a really good job of having these hands-on vibe checks on the day comes out that tells what you need to pay attention and what you don't. And we also have four products in market and that's crazy for we're a team of about 20 people and we have four separate software products that we run. We also have our own custom CMS that runs our website and we have a consulting business and that's just like crazy shape for a business to have. So I'm super proud of that and it sets us up for 2026 where I want to double down again. Our current plan is to 3x our revenue again. So that would take us to about 6 million in AR and to 10 million overall revenue which I think is really doable. The growth from last year was purely organic. So I think we have a very good shot to do this or better. The next thing that we're going to do is double down on a unified platform and ecosystem. So right now all the apps and the content, they all live in separate silos. And what we're doing in 2026 is we're going to build a unified platform layer where all the apps can talk to each other and we build a centralized idea of who you are and what you care about that makes all the apps better and also makes the content that we write better for you. And then we're going to be fully agent native. This is something I talk about a little bit more deeply later on. But I think being agent native is a new kind of software development where apps that are agent native are basically cloud code and it trying to all the UI all the buttons. It just kicks off an agent to do all the work instead of having code manually written that gets executed. And I really think we're in a moment for that right now and we're moving all of our software to be fully agent native over the next couple months. Here's what I told the team about what it looks like if things are working. One is by the end of Q1 if our products can talk to each other. So, we're going to have Kora talking to Spiral. When Corora wants to compose an email, it can talk to Spiral, which is our writing agent, and ask it to write something great or ask it for a writing style. When Monologue, which is our smart dictation app, when you're using it, it has a custom dictionary to know what to transcribe for hard to transcribe words. and it'll be able to talk to Kora to say, "Okay, what are the kinds of words that I should prefill in the custom dictionary?" So, we're going to have the ability for all of our products to talk to each other. By the end of Q2, we're going to have a central concept of who our users are and what they care about. So, we're going to basically gather all the context from what you write, what you say to your computer, your emails, and your files, and build a view for you of who you are, and what you care about that goes into all of our apps, goes into our content, and that you can take with you to Chachet to your cloud to enhance the context that they have about you. By the end of Q3, what I want to do is use all of this to make our content more personalized and better. It's very important to me that we keep the human soul, the human storytelling as the core of every. And I think it's clear that it's weird for everyone to get the same newsletter every day. And if we really want to keep you on the edge of AI, we need to know what you care about and then tailor what we tell you about to what you care about. And the last thing is by the end of Q4, I think you'll be able to see the ecosystem, not as an ecosystem of apps and content, but as an ecosystem of agents that all know about each other and all collaborate really well to help you get your work done. I think a couple other things that we really want to do. We really want to be the number one place where people go to learn to code, write, and design with AI. I think we're on our way there, but there's always more work to do. I really also think that the writing that we do right now the audience is humans but it needs to be both humans and agents. So a really good example is we write a lot about compound engineering which is our engineering philosophy. We have a cloud code plugin that teaches cloud code about compound engineering. That's an example of writing for both humans and for agents. I also want to be in a place where by the end of the year we're all pushing to each other's apps. And that's already happening. Everyone is committing code to everyone else's apps. But there's a lot that needs to be done. There's a lot of organizational stuff to make sure that everyone's repo is set up well to allow this kind of collaboration. There's also a lot of etiquette to be done about when you should submit a new feature or bug fix to an app and how to do it to take the pressure off or the work off of the app GM in order to allow them to merge it. So that's really interesting. And the next level of that once we figure that out is allowing customers to essentially write PRs that we can or really detailed bug reports or feature specs that we can then oneshot with cloud. And I think that would be really cool. So that's where we're trying to go. I want to talk for a little bit about why this is even important. Why are we doing this? The world just changed recently. Right now software agents are great. That's crazy. And the really interesting thing is a couple companies, Anthropic is a big one of them that made this bet that if you make a great software agent, it becomes a really good general agent. And I think that's true. And we're seeing that with cloud code and the cloud agent SDK. And this has gigantic consequences for software, for writing, for design, for company building, and for really how we see ourselves and our role in the future. And it is creating a tremendous amount of anxiety and FOMO and excitement and just people feeling like I can't keep up and I don't want to be left behind and I don't know how this is going to change my job and all that kind of stuff. And there's so many good things but there's a real need for people to actually figure out how do you live a more creative more human future with this technology. I think that's probably not the people building the underlying models. I think that's asking an oven maker how to bake a sule. It's people on the edge who are doing work that need to figure out how these tools fit into our lives. And I think that's why we're here. It's why we build this bundled subscription. If our goal is to help people learn to live and work with AI in a more flourishing, creative, better, more human way, that maps very cleanly onto the bundle that we're building. So, you need to spread the word. So, you need to tell stories about the future that we see that we live in. You need to build tools that they'll use. And the tools that we sell are tools that we build for ourselves. And then we need to teach them hands-on. And those are all the components of the company that we're building. And I hope that we have an opportunity to be an archetypal AI native company. And what that means to me is we figure out for ourselves how to build and work and live in this new future. And then we become an example for other people to follow. And in doing that, they subscribe to read our ideas and they use the tool set that we build and all that kind of stuff. And my hope then is that creates the way that people build and write and think in this new future. And that's really exciting and I think also very important to me. And I think we're in this moment that I want to talk about for one second. I've seen a lot of technology waves when every was first started in 2020. It was right before the creator economy wave and I was seeing our numbers just go up and I was like, "Okay, there's something really special here that's happening. We're growing super fast. I had that tingle feeling and that's one of the reasons why we really went all in on the company in 2022 when AI think going to be a wave. It was just GBT3 but I was like this is the next big thing and after chatbt we just really focused the whole company around AI and that has really paid off and I am getting that same feeling right now and that feeling is about what I call agent native apps which is basically apps that are cloud code in a trench coat. There's a lot more detail about what makes something agent native and how traditional software fits into that. I think that cloud code and trench code metaphor should tell you most of what you need to know and there's a ginormous number of implications for it. But we're going all in on that in 2026 and that means the content that we write, the stuff that we build, all that stuff is going to be really focused around this. And yeah, that's it. That's our 2026 strategy. Thanks for watching.