Role: CEO and co-founder, Every (every.to). Former founder of Firefly (acquired). Y Combinator alum. 15-person team running a bundled media + software + consulting company — self-described “AI-native startup” with 100% AI-written code.
Platforms:
- Every.to — bundled subscription platform. 100,000+ subscribers (“trusted by 100,000 builders” per homepage). $30/month or $288/year.
- Substack (every.substack.com) — distribution mirror for the newsletter.
- LinkedIn — active posting, moderate engagement relative to Mollick/Miller.
- Podcast (“AI & I”) — weekly conversations with operators and AI builders. Available on Apple, Spotify.
- X/Twitter (@danshipper) — frequent short takes on AI product development.
- Lenny’s Podcast guest — high-visibility appearance (2025) positioning Every as the “AI-native startup” case study.
Cadence: Daily newsletter (multiple columns by different writers). Dan’s personal column “Chain of Thought” publishes ~weekly.
Format Specs
- Length: 1,500–3,000 words per essay. Shorter than Mollick. More narrative, less academic.
- Visual grammar: Text-first with occasional product screenshots. No custom data visualizations, no kinetic typography, no video briefings. Product demos embedded when promoting Every’s own tools.
- Tone: Builder-practitioner. First-person (“I built this,” “we shipped this”). Optimistic about AI without hedging. Less academic rigor than Mollick, more operational detail than Miller. Comfortable making bold claims from n=1 experience.
- Distribution: Every.to email → Substack mirror → LinkedIn amplification → podcast cross-promotion → consulting pipeline.
Recurring Topics + Implicit Thesis
Core thesis: The future belongs to small teams that use AI as a force multiplier. A 15-person company can ship five products, a daily newsletter, a podcast, and a consulting arm — because AI replaces headcount in writing, coding, and operations. The “AI-native organization” is not a Fortune 500 with an AI strategy; it is a small, fast team that treats AI as infrastructure from day one.
Recurring topics (from archive and podcast analysis, 2025–2026):
- AI-native company building — how Every itself operates with AI agents
- AI product development — shipping tools (Spiral, Cora, Sparkle, Monologue, Proof, Plus One)
- Personal productivity with AI — individual workflows, writing assistance, email management
- AI and creativity — how AI changes the writing process, not replaces it
- Agent-native product design — building products around AI agents rather than retrofitting
- The “AI operations lead” role — organizational design for AI-first teams
- Generalists thriving in AI era — “rigid job titles blur and everyone becomes a manager of AI tools”
What he consistently covers well:
- Practitioner credibility — he runs an AI-native company and shows the receipts
- Bundling model innovation — content + software + consulting in one subscription
- Speed of iteration — ships products fast, writes about what works and what doesn’t
- Builder audience engagement — attracts people who want to make things, not just read about them
What he does NOT cover:
- Enterprise deployment at scale (200+ employees, cross-functional rollout)
- Procurement, contracting, vendor security, compliance
- ROI measurement and CFO-facing business cases
- Change management and adoption resistance
- Industry-specific regulatory requirements
- Workforce anxiety, reskilling, or labor displacement evidence
- Independent research synthesis — cites his own experience, not RCTs or institutional studies
Audience Overlap with Brandon (Estimate: 15–25%)
Overlap zone: Tech-forward leaders interested in AI as a business tool, not just a technology. People who want practical “how to use AI” guidance backed by real operational experience.
Divergence: Shipper’s core audience is (a) founders and indie builders running sub-50-person companies, (b) product managers and engineers at tech companies, © “creator economy” professionals — writers, podcasters, newsletter operators. Brandon’s audience is (a) C-suite at mid-market companies ($50M–$2B revenue), (b) people managing 200–5,000 employees through an AI transition, © people buying enterprise software, not building it.
Shipper writes for “how do I build an AI-native company from scratch?” Brandon writes for “how do I transform an existing 500-person organization that has legacy systems, change-resistant teams, and a procurement process?”
The overlap is thin because the organizational contexts are fundamentally different. A 15-person AI-native startup has no change management problem, no procurement council, no SOC 2 vendor review, no union considerations, no board reporting requirements. The lessons transfer at the individual-productivity level but break down at the organizational level.
Revenue Model / Funnel
Every’s monetization is direct and multi-stream — notably different from Mollick (institutional capture) or Miller (personal brand → corporate keynotes):
- Paid subscription ($30/month, $288/year) — content + software bundle. At 100K subscribers, even a 5% paid conversion rate implies ~$1.4M ARR. Reported at $1.2M ARR growing 15% month-over-month (Lenny’s Podcast, 2025).
- Software products — Spiral (writing), Cora (email, $15/month standalone), Sparkle (file organization), Monologue (dictation), Proof (collaborative editing), Plus One (Slack agent). Bundled into subscription but some available standalone.
- Consulting arm — seven-figure revenue reported. Advises companies on AI adoption and implementation.
- Entrepreneurs in Residence program (Every Studio) — incubates AI productivity tools, likely equity/rev-share model.
- Podcast sponsorships — standard podcast monetization on “AI & I.”
Key insight: Every is the only adjacent voice running a genuine bundle model — content creates demand for software, software increases subscription stickiness, consulting monetizes the highest-intent readers. This is a more sophisticated business than a newsletter with a paywall. The risk: breadth dilutes depth. Shipping six products with 15 people means none gets the investment a focused competitor would apply.
Gap Brandon Can Own
What Shipper consistently does NOT cover — and mid-market CIOs care deeply about:
-
Scale. Shipper’s frame is the small team (5–50 people). He has no frameworks, data, or experience for deploying AI across 500 people in a regulated mid-market company. The organizational complexity gap between 15 and 500 is not linear — it is categorical. Brandon’s entire corpus addresses this layer.
-
Evidence base. Shipper cites his own experience (n=1) and occasional anecdotes. He does not synthesize institutional research (Stanford HAI, MIT CISR, BCG, METR RCTs, NBER studies). Brandon’s credibility comes from triangulating 300+ sourced documents. A CFO trusts an evidence base, not a founder’s war stories.
-
The reluctant adopter. Shipper’s audience self-selects for AI enthusiasm. He never addresses adoption resistance, workforce anxiety, the “Endangered” archetype (25% of workforce per BCG), or how to bring skeptical middle managers along. Brandon’s workshop content is built around this problem.
-
Procurement and compliance. Zero coverage of MSA timelines, DPA friction, SOC 2 requirements, BAA for healthcare, SR 11-7 for banking, indemnity ceilings. These are the actual blockers for mid-market AI deployment. Brandon’s Pillar 16 is defensible ground Shipper will never enter.
-
ROI rigor. Shipper’s implicit ROI argument is “we ship more with fewer people.” That is compelling for a startup founder. A CFO at a 300-person company needs TCO per seat, training investment per employee, payback period modeling, and independent benchmarks. Brandon’s CFO-facing tools occupy this space.
-
Industry specificity. Every covers AI generically. A healthcare system, a regional bank, a manufacturing company, and a law firm all face different regulatory, workforce, and integration constraints. Brandon’s industry-segmented research (legal, healthcare, financial services, manufacturing) addresses contexts Shipper’s content ignores.
Anything Worth Borrowing
-
The bundle model as concept. Content + tools + consulting in one subscription is a more defensible business than content alone. Brandon’s eventual productization (assessment tools, workshop templates, diagnostic frameworks) could borrow from this architecture — though the audience and price point differ substantially.
-
“AI operations lead” framing. Shipper’s articulation of a dedicated role for making teams productive with AI maps to what Brandon’s corpus calls the “AI Center of Excellence” or “AI champion” role. The simpler label may resonate better with mid-market CHROs who don’t want another committee.
-
Practitioner credibility through transparency. Shipper’s willingness to show how Every itself runs on AI (agents named “Friday” and “Charlie,” parallel AI tool usage, 100% AI-written code) builds trust through specificity. Brandon’s workshop format already does this live; the written content could reference more anonymized client implementation details.
-
Speed of iteration as proof. Every ships products weekly and writes about the process. The implicit argument — “if a 15-person team can do this, imagine what your 500-person company could do with the right approach” — is a useful bridge from Shipper’s world to Brandon’s audience. Worth referencing (with attribution) when making the case for organizational AI adoption speed.