Episode of AI & I in which four of Every's builders — COO Brandon Gell, head of marketing Douglas Brundage, growth engineer Yash Poojary, and head of growth Austin Tedesco — break down how they use AI in their work, sharing their personal AI stacks, workflows, and building strategies. Topics include Every's All Access membership and Builder Pack, how a Codex-built email campaign generated over $25,000 in revenue within hours, automating testing pipelines, the idea-to-execution loop, the "AI sandwich" workflow, making AI tools accessible to solo builders, AI in brand and design, and deciding what to build first. Timestamps: 0:00 Intro 0:35 All Access Explained 3:01 Yash's Tech Stack and How He's Automating Testing Pipelines 8:02 The Idea to Execution Loop 10:25 How an Agent Turned an Idea into $25K 17:50 The AI Sandwich Workflow 22:03 Making AI Tools Accessible to Solo Builders 28:50 Douglas on Brand and Design 34:51 Tips on What to Build First 43:46 What's Next for All Access # Channel Identity Observations ## Source - **Video:** "Behind Our Largest Subscription Revenue Increase" - **Channel context:** Every (a media/company hybrid); the show is **AI and I**, hosted by Dan Shipper. ## Self-Described Identity & Scope **Every positions itself as a subscription media company and AI-building community.** - Claims a product business, not just content: *"We generated the largest subscription revenue increase in every's history last week... by launching this thing called the builder pack."* - Describes a paid tier: *"All access is a new tier. Um, at every it's a $625 annual plan"* that bundles *"10 benefits, exclusive benefits from um all AI companies,"* plus *"office hours"* and *"unlimited use of Kora and Spiral."* - Multiple in-house products referenced as identity markers: *"I run one of the products at every called Sparkle"* (Yash), the AI writing app **Spiral**, and a **"compound engineering plugin"** — evidence Every sells both software and content. - Self-description as a learning destination: *"Go build, go build. It's the best time in the world to build... you should subscribe to every. We will teach you how."* ## Intended Audience Explicitly addressed in the video itself: - **Builders and AI practitioners**: *"This is for people that are really ready to start experimenting with with all of these tools"* (Douglas on the builder pack branding). - **Creative/knowledge professionals, not only engineers**: recommendations aimed at *"marketers, writers, designers, creative technologists, uh product designers."* - **Individuals priced out of AI tools**: an anecdote about an engineer who *"visually like gulp[ed]"* at spending figures — framing the product as solving *"how am I going to discover this technology when it's like prohibitively expensive as an individual."* - The hosts say they are *"speaking directly to people who either like just got access to the tools in the builder pack or like thinking about it."* ## Demonstrated Presentation Patterns - **Practitioner-casework format**: the episode brings internal team members on air to explain a launch *"from conception all the way to the full execution launch"* — the channel demonstrates its methodology through its own operations. - **Concrete, metric-backed storytelling**: claims like *"those emails alone had driven more than $25,000 in revenue"* anchor the teaching in real outcomes. - **Named tool fluency**: dense, specific references (Claude, Codex, Cursor, PostHog, Notion, Framer, Flora, Descript, Render, Kit, "Fable," "GPT-5.6") signal an audience assumed to be tool-literate or aspiring to be. - **Sponsored ad read** (Attio CRM) integrated with *"We use it internally at every, and we love it"* — monetization via sponsorship layered on subscriptions. - **Playful, informal register**: banter (*"Who are who am I? Wow"*), an AI-generated comedic outro *"smash that like button"*, and casual Slack-lore storytelling. ## Distinguishing Claims vs. Demonstrations - **Claims:** the revenue record, the value of the builder pack ("thousands of dollars" of benefits), future roadmap ("a lot more perks coming"). - **Demonstrated:** the working style itself — agent loops, MCP integrations, delegating email campaigns to Codex — shown through detailed first-person narratives rather than tutorials alone. # Delivery Observation: "Behind Our Largest Subscription Revenue Increase" ## Overall Format & Framing - **Panel-style podcast.** The host frames the episode as a team debrief: *"we've got myself, Yash, Austin, and Douglas here and we're missing Daniel"* and sets an outcome expectation for listeners: *"hopefully by the end of this, uh, there'll be like one nugget that you can take out of this."* - **Concrete-number anchoring.** Claims are repeatedly backed with specific figures: *"$625 annual plan," "$1,000 in Codex credits," "rebuilt sparkle 15 times," "$25,000 in revenue," "more than $25,000."* ## Recurring Teaching Habits - **Metaphor-heavy explanation.** Multiple extended analogies structure the teaching: - NBA general manager framing: *"just keep trading for future draft picks... we're on an eight-year time horizon for contention."* - The **"AI sandwich"** (attributed to colleague Kieran): *"you're at the top and bottom of the AI sandwich. You decide what the problem is... then you review the work."* - **Orchestra/conductor metaphor** from Douglas: *"we can all take a step back... we can conduct it"* and *"moving from playing the instrument to orchestrating."* - **Question-prompt as a teaching device.** The host models turning confusion into a prompt: *"Well, how do I use it?" It's like, "Well, what are you trying to accomplish?"... "Great, just say that again."* This is echoed by another speaker: a good self-prompt is *"What would you be the most excited to text someone like, 'Hey, I made this'?"* - **Narrative storytelling with a full arc.** Austin tells a complete incident with setup, action, and payoff: screenshotting Slack, running `/LFG`, going to the gym, returning to find *"four different... targeted cohorts in kit"* and eventual *"$25,000 in revenue."* Self-deprecating asides punctuate it: *"I'm still a control freak who doesn't want to turn over every single thing to AI."* - **Actionable prescription sections.** The episode ends with a structured "what would you do first" round: *"dupe something," "rebuild your portfolio," "use cursor cloud agents and use different models."* ## Vocabulary & Recurring Phrases - **"Builder" as identity language**, repeated throughout: *"be the builder you want to be," "be the builder that you want to be," "all of us are builders."* - **"Compound / compounding"** appears frequently: *"compound engineering," "the results keep compounding," "you can start this compounding flow right now," "you can then compound on that."* - **"Stack"** as a core noun: *"that's my stack," "the stack that you use... it's very expensive," "this stack is that for working with AI."* - **"Underrated"** as an intensifier: *"the Cloud Max subscription is really underrated," "cloud agents are a very underrated way."* - **"Loop"** as a working concept: *"that claude code and post hog loop," "Fable is just running in a loop," "always on like loop and architecture based automations."* - **"V1/V2" iteration language:** *"I've learned from seeing the V1 chip that the agent comes up with... let me figure out how to get it to a V2."* ## Communication Patterns - **Casual, conversational fillers and interjections** throughout: *"uh," "like," "yeah," "Mhm,"* plus playful banter — *"Who are who am I? Wow. I ask that ask myself that every day."* and *"Anthropic. I hope no one from Anthropic is blocking this."* - **Collaborative co-narration.** Speakers finish and riff on each other's points: *"so what's interesting to you is less actually the work... It's actually — what should I test?... And then did it work? Great. Implement it."* - **Product names used as shorthand** without re-explanation among panelists (Codex, Claude, Cursor, PostHog, Kit, Spiral, Flora, Fable, Descript, Underlord, Render, Notion), with brief glosses added for the audience when needed. - **Honesty about friction.** Even in a promotional context, speakers admit limits: *"doesn't happen every time you do slfg," "by no means has Fable and Descript created a video that is publishable, but it has gotten me like 70% of the way there."* - **Humorous scripted outro** (attribution unclear from transcript): exaggerated hype voice — *"smash that like button," "a roller coaster of emotions," "Dan, I'm absolutely hopelessly in love with you"* — a sharp tonal shift from the panel discussion. ## Stable Patterns vs. Isolated Moments - **Stable-looking:** metaphor-based explanation, "builder/stack/compounding" vocabulary, concrete-number evidence, prescriptive recommendations — each appears across multiple speakers and sections. - **Isolated or uncertain:** the orchestra metaphor appears only from Douglas; the NBA analogy only once from the host; the humorous outro occurs once with unclear speaker attribution. The promotional framing (explicit sales pitch: *"get the deal, guys. Get the builder pack"*) is present but interleaved with genuine teaching, so its balance relative to other episodes cannot be assessed from a single video. # Observation Record: "Behind Our Largest Subscription Revenue Increase" ## Speakers Identified Names are established only through in-transcript dialogue (no curated speaker metadata supplied): - **Host/interviewer** — referred to as "Brandon" by other speakers ("use the MCP as Brandon does"; "to Brandon's point"); self-identifies as running the growth team at Every - **Yash** — introduced himself as running the product Sparkle and working on the growth team - **Austin** — identified contextually; describes building a movie app and working with Codex - **Douglas** — identified as the "creative director behind this launch" by the host - **Dan** — absent from the recording; credited with the original email idea and a pre-recorded outro --- ## The Product Launch **Claim (host, opening segment):** Every generated the largest subscription revenue increase in the company's history "last week" via the **Builder Pack** launch. **Claim (host, launch details):** - **All Access** launched Tuesday the 14th; a **$625 annual plan** - Includes the **Builder Pack** — described as "10 soon to be more exclusive benefits" from AI companies (e.g., $1,000 in Codex credits, 12 months free Cursor access) - Also includes All Access–only office hours and unlimited use of **Cora and Spiral** - Described as "early access exclusive access to the Every stack" --- ## Position: Automate "Fake Work" to Focus on Interesting Problems (Yash) - Built Sparkle, rebuilding it "15 times" using Claude and PostHog; describes himself as "still very Claude[d]" despite company Codex preference - Finds manual AB-test setup (audience sizing, cohort ramp decisions) to be **"a lot of fake work"** he wants fully automated: > "Why should I be doing that manually?... I should be working on interesting more interesting problems." - His preferred work is deciding **what to test** (e.g., homepage takeovers, paywall timing), which he frames as "more human psychology" - Claims Every's culture is unusual: "everyone is very secure in what they do and so we are okay with automating our jobs," contrasting this with other organizations where he'd "stretch this out for like a year" - Daily stack: **Cursor** (cloud agents, Kimi/Kimmy composer model), **Framer** (MCP support), **Claude Max** — which he calls underrated: "I'd pay way more for it" --- ## Position: Idea-to-Execution Loops and the $25K Email Story (Host/Brandon) - Frames Yash's mode via an NBA GM analogy: using automation to "operate at the same level in like a set it and forget it mode" while freeing creative, competitive work - Claims the Builder Pack serves two types: experts like Yash who defer work to agents, and non-technical "ideas people" like himself who "give the model and the SAS tools... my outcomes and ideas and then just like let it run" - **Recounted story (his own account):** after the team (crediting Dan for the original idea) suggested targeting checkout-intent users with urgency emails, he screenshotted the Slack thread, dropped it into a Codex thread using "5.6 on medium," ran `/LFG` (described as their compound engineering harness: brainstorm, plan, work, review, compound loop), and went to the gym - **Outcome claims (self-reported):** the agent created four audience cohorts in Kit, drafted emails run through Spiral's MCP for style, analyzed past sends for style and click/open drivers, embedded a proven image, scheduled sends, and posted to an "all emails" Slack review channel; the emails generated **more than $25,000 in revenue** within hours the next morning - **Qualification he volunteered:** the agent finished quickly ("probably finished by the time that I like changed into my workout clothes"), he made light tweaks for ~10 minutes ("I'm still a control freak who doesn't want to turn over every single thing to AI"), and he acknowledged: "that doesn't happen every time you do slfg" - Notes his reaction was not amazement but "That's basically what it should do" --- ## Position: Tools Now Interoperate; Maintenance Is Delegated (Host/Brandon) - Cites colleague **Kieran's** framing: "you're at the top and bottom of the AI sandwich" — you frame the problem and review the work - Claims models now "speak together really, really well" via MCPs - **Notion reversal:** he "hated Notion for years" because of organizational maintenance burden; now maintenance is pushed to Codex/Cloud Code ("Once a week I just ask Codex... 'can you reorganize our growth hub?'") - Describes running Fable in a loop with the Descript MCP to rough out video edits (~"70% of the way there"), while explicitly noting the output is not publishable without his finishing work --- ## Position: Cost as a Barrier; Value Justification (Douglas) - Recounted anecdote: an unemployed engineer friend at an Every event "visually like gulp[ed]" upon hearing an engineer spent $30K/month on AI — the friend couldn't afford to discover the technology as an individual - Argues the Builder Pack addresses this: the OpenAI/Codex benefit (one month free plus three months of Codex credits — note he corrected himself mid-speech from "three months free" to "one month offering") plus $1,000 overage credits represent thousands of dollars of embedded value - Claims these are valuable specifically because they come from "model companies" --- ## Position: Orchestration Metaphor and Creative Strategy (Douglas) - Observes AI naming is literary (Codex, Haiku, Sonnet, Fable) but agent work is described as **orchestration** — "it feels a lot more like music to me" - Core metaphor: everyone can now "conduct" the orchestra without playing every instrument, and eventually "conduct a lot of different orchestras at the same time" - On the green branding: partly because Every hadn't used green much, and because Builder Pack targets Every's "most explicitly technical... audience," feeling "more matrixy and digital" than Every's usual "Greco-Roman and heritage driven" elements - Uses **Flora** most deeply (via MCP), plus marketing skills with compound engineering; claims competitive auditing that "used to be a several week long process" now takes "hours or less" - **Qualification:** "Do I think that the tools come up with the insight particularly well? Not always. Sometimes they do, but you can then give it the insight and say, prove this out." - Frames the workflow as the "sandwich": heavy upfront metacognition ("what is my process?"), then tools run with it --- ## Position: Trust in SaaS via Agents; Compounding (Host/Brandon) - Notes a January–March moment of building everything in-house ("We're building our own CRM") that ended with "man this sucks"; now trusts PostHog, Notion, etc. as agent-accessible sources of truth - Attributes this to the leap from "5.5 to 5.6" models finding and maintaining context - Describes his own prompts as looking like he "doesn't know what the hell he's doing" — minimal prompting, reliance on pre-built harnesses - **Qualification and advice:** setup isn't instant; "we've done it incrementally"; he's tried automating marketing email sends "for months and it keeps getting a little bit better"; "the best time to start... was a year ago. The second best time is right now" --- ## Recommendations for New Builders (Closing Segment) - **Host/Brandon:** dupe a product you love as a simplified MVP, deliberately using as many Builder Pack tools as possible (Render, PostHog, Anthropic, Codex, Cursor, Flora); claims duping quickly becomes inspiration for your own thing - **Austin:** pick the idea you're most excited about — his test: *"What would you be the most excited to text someone like, 'Hey, I made this'?"* — his indie-movie "Fandango" app is live and used by friends weekly; describes the process as "like playing a video game"; admits the V1 "design looks like ass" and iterates - **Douglas:** for marketers/writers/designers — rebuild your portfolio site with the stack, which "also kind of proves out that you're AI native" - **Yash:** use Cursor cloud agents with different models (including open-source Kimi K25) deployed via Render to discover your personal model taste: "You need to have your personal taste in terms of what you like" --- ## What's Next for All Access (Host/Brandon) - Two more partner benefits "in the next few days, week" - Plans to pair each benefit with a plug-in guide for agents - **Qualification/humor:** "I've never read one of our guides. I dropped the guide into Codex and I say use this to help build the next thing" --- ## Advertisement Segment - A mid-episode ad for **Attio** ("the CRM for the agent native world"), stating Every uses it internally, with a 15%-off offer at attio.com/every — promotional content, not speaker-position material ## Unresolved / Structural Notes - The **$25,000 revenue figure** and the "largest subscription revenue increase in Every's history" are speaker claims from the participants, not independently verified in the transcript - Douglas self-describes as relatively new ("my short few months I've been here at Every") and as learning the tooling alongside others — his position is framed as a perspective in progress, not expertise - The closing is a pre-recorded comedic outro attributed to Dan (unavailable for the discussion), including a scripted endorsement of the show # Speaker & Provenance Record ## Video Overview - **Title:** *Behind Our Largest Subscription Revenue Increase* - **Show:** "AI and I" podcast (mentioned in-transcript) - **Format:** Panel/roundtable episode with intro and pre-recorded outro ## Identified Speakers & Roles | Speaker | Role (as stated in transcript) | Notes | |---|---|---| | **Dan Shipper** | Host / Editor-in-chief context (named in outro: "Dan Shipper as the captain of the spaceship") | Missing from live panel; outro attributed to "Dan's outro" — likely pre-recorded or AI-generated voice | | **Brandon** | Every team member; runs **compound engineering** workflows; Codex/GPT-5.6 user | Not introduced by name in transcript, but referenced by others as "Brandon" ("as Brandon does", "Brandon's duping strategy") | | **Yash** | Product lead for **Sparkle** at Every; also on **growth team**; Claude/Claude Max user | Introduced by himself: "I'm Yash... I run one of the products at every called Sparkle" | | **Austin** | Runs **growth team** at Every; built indie movie app; Codex/GPT-5.6 user | Referenced by name by other speakers | | **Douglas** | **Creative director** at Every; new-ish ("short few months"); Flora/brand strategy lead | Asked about the green branding | - **Mentioned but absent:** **Daniel/Dan** ("we're missing Daniel") — likely the same Dan Shipper of the outro. ## Source / Provenance Facts ### First-party claims - Launch of **All Access** tier on **Tuesday the 14th**; **$625/year** annual plan. - **Builder Pack** = 10 exclusive AI-tool benefits (Codex credits, Cursor access, Claude, PostHog, Notion, Framer, Render, Flora, Gemini, Spiral, Kora, etc.). - Claimed revenue outcomes: **$25,000+** in revenue from four automated email sends; described as the largest subscription revenue increase in Every's history. - Builder Pack details: "$1,000 in Codex credits," "three months free" of OpenAI/Codex (later corrected by speakers to one month — noted with explicit self-correction in transcript). ### Third-party references - **Anthropic, OpenAI, Cursor, PostHog, Notion, Framer, Render, Flora, Descript, Kit, Spiral, Kora, Fable, Underlord** — tools/partners discussed. - **Google OAuth**, **Kimi K25 / "Kimmy composer"** open-source models — mentioned. - Anecdote: "a single engineer spent 30 grand last month" on AI (unverified third-party claim from an unnamed event attendee). ### ⚠️ Promotional segments 1. **Adio (Attio/Adio) ad break** — mid-episode sponsored ad for "Adio, the Agentic CRM" with affiliate link `adio.com/every` and **15% off first year** offer. Claims: used by Granola, Modal, WhisperFlow, Every. Explicitly flagged as advertisement ("Adio runs the work behind Every Win"). 2. **Self-promotion:** Whole episode promotes Every's **All Access / Builder Pack** subscription tier. 3. **Outro CTA:** Pre-recorded outro urging viewers to "smash that like button and subscribe" — stylized, hyperbolic promotional language. ### Comment availability - No information in the transcript about comments being enabled, disabled, or read. ## Attribution Boundaries - Opening monologue (single voice, unnamed but likely host) describes the launch and introduces the panel. - The **email-automation case study** ($25K revenue) is told by **Brandon**, with Yash credited as relaying Dan's original idea. - **Douglas** provides creative/branding perspective (green branding, orchestration metaphor, Flora use). - Recommendations segment: each panelist (Brandon, Austin, Douglas, Yash) gives individual advice — attributed sequentially in transcript order. - The outro voice names Dan Shipper but is tonally distinct (comedic/hyperbolic); provenance (human vs. AI-generated) is **not stated** in the transcript. We generated the largest subscription revenue increase in every's history last week. We did it by launching this thing called the builder pack. Basically, we partnered with a bunch of the AI tools we use every day. And subscribers to the builder pack get discounts and credits to those tools. So, $1,000 in Codex credits, 12 months of free cursor access, all that kind of stuff. The code pack's awesome, but I think the actual story behind it, like how we did it, why we did it, how it generated so much revenue is really interesting. For this episode, I had the team who worked on the builder pack. everything from conception all the way to the full execution launch. Come to the show to share how we did it and what we learned. I hope you like it. \>\> Hello everyone and welcome to AI and I. Uh this is a slightly different version of the pod today where we've got uh myself, Yash, Austin, and Douglas here and we're missing Daniel. Uh we're going to be taking you on a journey today introducing you to all access uh in the builder pack and this is a new uh tier at every that we decided to launch recently and we would just want to talk about why we decided to build it, why it's important, um how we use it and what it means to be a builder today. All of which all of us are are are builders and use these tools every day. So, um, yeah, hopefully by the end of this, uh, there'll be like one nugget that you can take out of this and and and use in your everyday. So, I guess like to introduce us, okay, \>\> uh, or to introduce this this pod, first I'm going to introduce All Access, we launched it Tuesday um, on the 14th. It was a big launch for us, big endeavor across the whole company. All access is a new tier. Um, at every it's a $625 annual plan that uh gives you access to the builder pack, which is 10 benefits, exclusive benefits from um all AI companies that you know and love that enable you to go build um and adopt some of these tools in ways that you may not have been able to before. And all access includes a couple other things. It includes access to office hours that we're hosting um that are that are exclusive to all access members, uh unlimited use of Kora and Spiral, and we have a couple other uh things up our sleeve that we're going to be launching in the next few months as well. Um but we really want to talk about the builder pack because that's like probably the meat of of of all access. And uh the builder pack is 10 soon to be more exclusive benefits to AI tools that the every team uses every day so that you can get access to these tools and use them uh you know for free for a while and and get comfortable with using them in your stack. It's it's it's it's early access exclusive access to um the every stack. This is the team that that brought it to life. All right, Yash, how do you use the builder pack? \>\> Yeah. Uh, context. I'm Yash. I run one of the like I'm just Yeah. \>\> Who are you? \>\> Who are who am I? Wow. I ask that ask myself that every day. But I run one of the products at every called Sparkle and I also work on the growth team. Now a large part of my work is using claude. Uh I know at every we are like codec stands but I'm still very clouded. I've been using cloud for the last one year and this involves like I I built out the entire product like I think 15 rebuilt sparkle 15 times using cloud uh and post hog. So those are the tools I reach out for the most. And recently I joined the growth team at every and growth meant a lot of AB testing a lot of segmentation and other stuff and again uh I started optimizing postto but I find it really annoying to open like dashboards and set a lot of these things up and that's where my setup with cloud helps a lot where I have like custom skills built out and essentially my plan is in the next few weeks to automate the entire AB testing pipeline. Like a lot of the work that I spent doing for the first one month at the growth team, I'm like this is very boring because it's it's very straightforward. Like I should be working on interesting more interesting problems and I should not be clicking buttons uh and figuring out what's the right audience size and stuff like that. Like Claude is so much better at that. I have to prompt it. I have to figure out okay what's the right audience size? when should an experiment go from a 10% AB testing cohort to 50%. Like why should I be doing that manually? It's I I feel it's a lot of fake work. Uh and we like to spend a lot of time observing these things like setting up setting up an experiment every time felt so boring to me. I'm like the only way I can set up do more experiments is automating the entire pipeline. So I spend a lot of time. So, so what's what's interesting to you is less actually the work. The work is no longer setting up the pipeline to be able to do it. It's actually \>\> what should I test? Yeah. \>\> And then did it work? Great. Implement it. What's the next test? \>\> Yeah. I should be like I'm more interested in the ideas like oh should we do a homepage takeover? Yeah. \>\> Uh who should we show that homepage takeover to versus actually setting that up uh is not that interesting. uh like we have so many experiments live right now uh which is like when should we cut off uh the pay wall, when should we show the pay wall, those are way more interesting and those are also like more human psychology and I can I I have more fun doing that. \>\> Mhm. \>\> And and I personally feel like a large part of our work at every is like everyone is very secure in what they do and so we are okay with automating our jobs. like I spent one months doing these things and I'm like okay I'm done \>\> like I want to do other things now and if it was some other organization I'm going to try to stretch this out for like a year like what what I did \>\> you want you want to move on to the next thing that you tackle yeah because that's fun and that's why we are always at the edge of AI right like we like yeah this is done guys like what's next like what's more interesting okay is there a better model for this \>\> u \>\> so so what in the builder pack do you use every day. \>\> Every day it's cursor. I use cursor because they have cloud agents which are really good. Um we did a lot a bunch of uh fable five optimizations because I was working on some other task. I did not want to mess with my setup. So cloud agents just spin off a cloud server and run there and give get me the results back. and they have a really good open source model which is really cheap like Kimmy composer \>\> uh which I love. So that's something I use. Uh I used framer a lot as well while I was building this the sparkle side. Um it it has a it it has good MCB support. So I could change the change the headline see like experiment more directly without actually going into framework and setting like every time. It's very annoying to me like I'm setting a lot of these things up the right font size for mobile and stuff like that. This is how you like \>\> like I used to do this like 20 years back like today I should not be spending my time on these things \>\> and I would say Claude Max is my go-to. I like I I feel \>\> it's insane. Yeah, that's my stack. And it's and post talk. Yeah, I use a lot of these products, but it's so cheap. Like I feel that the Cloud Max subscription is really underrated. Like I'd pay way more for it, \>\> right? \>\> I couldn't work without it. \>\> Right. Anthropic. I hope no one from Anthropic is blocking this. \>\> Yeah, get the deal, guys. Get get the builder pack. Um \>\> I I like the way Yash is describing uh one potential approach to work, which is like uh there there's this there's this approach to being a general manager in the NBA, which is like just keep trading for future draft picks to be like we're on an eight-year time horizon for contention. And there is for someone as like skilled as Yosh at engineering, go to market engineering growth, you can use these tools um this stack that he has to to like operate at the same level in like a set it and forget it mode and kind of I would be like well like I I run the growth team. I look at what Yash is doing. I'd be like Yash another experiment and it like moved the needle by 2%. I guess he's on it and like he knows how to set up that that claude code and post hog loop. But the way that he works instead, which is exciting, is that after he does that, he looks at how can we win right now? How can I be creative and competitive to find the next thing? And how can I use these always on like loop and architecture based automations to make it so that Yosh can do the thing that like lights them up which is I can see Yosh and Slack being like oh what if we like made a threehour time constrained discount specifically targeted to these users using this video building this thing in framer and that's this kind of stuff has always been the case right like that work is the most fun way to work. It's how smart creative people are able to differentiate themselves. But I think that the builder pack allows is that it allows someone like Yosh to automate and uh defer a lot of the work to cloud agents he would have otherwise had to manually click in post hog or manually code himself and then he can go be creative um on the space where he is an expertise. And then it also allows someone like me who doesn't know what the any of that stuff is, but kind of is naturally more of an ideas person to give the model and the SAS tools in the builder pack my outcomes and ideas and then just like let it run, which is like the craziest part for me. Like I I let go Oh yeah. \>\> Can you tell that story of uh you had an idea for something, you went to bed, you woke up, you had four emails? \>\> Yeah. So it wasn't even my idea. Like we were um we did the we did the builder pack launch on Tuesday. It was going really well. Um I'm on the west coast. Most of the team is on the east coast. as they were like getting ready to go to bed, uh Yash dropped a note in Slack saying, "Hey, we should send uh emails in the morning um to a group of users who have shown some sort of checkout intent but not converted um because we were running a early bird discount for the first 24 hours of launch. So, it's like we should probably hit them again with some sort of urgencybacked approach." And then Yash said, "This isn't actually my idea. It's Dan's idea, but I'm sharing it." And then they all signed off. And I think it was maybe like 700 p.m. here. I uh had been in front of my computer all day and I really wanted to go to the gym. And so I uh I took a screenshot of the Slack because it was like a bunch of different Slack messages. Usually I would just like copy paste the link to the Slack message and send it to Codex. I took a screenshot of the Slack. Um, I uh dropped it in a codeex thread using 56 on medium. It's like usually what I operate in. And I said, uh, can you do this? And then I did slash LFG, which is the harness in our compound engineering plugin to tell an agent to take itself through a brainstorm, plan, work, review, compound loop, which is like to me the ideal way to work with with agents. And then I went to the gym and I came back from the gym and uh what I saw in codeex was it worked for honestly not that long. like it it probably finished by the time that I like changed into my workout clothes at the gym because it like didn't actually need to to do that much. And it had created four different um audience-based uh uh cohorts like targeted cohorts in kit based on like these people got to the checkout page. These are um these people visited the visited the builder pack website but didn't check out. Um these are our highest engaged free users. There's like four different types. It drafted specific emails for each of those audience types. It ran the text for the emails through um the MCP for our AI based writing um app called Spiral. So, it's using a writing style that we've approved. It looked through all of our previous sends in Kit both for our language style as well as what had driven clickthroughs, what had driven opens. Um, it grabbed a social share image that had driven clickthroughs in a previous send and embedded it and it had scheduled it for the next morning. And it's crazy cuz I wasn't like, "Holy that's so cool." I was like, "That's basically what it should do." Like, my brain is so cooked on this stuff now that I'm like, "This is literally exactly what I expected." \>\> I think it did something. I think it then posted it in all emails. Yeah, I have I have an automation in there that it like so we have um we have a Slack channel called All Emails. Uh if you're a subscriber to every uh I'm sorry we send you a lot of emails. I swear we're working on it. Uh, one one step one step towards working on it is having a channel where um, one we we build all of our email sends through codeex or cloud code and can have the agent push a slack message um, saying here's what here's what's going to be sent to whom and why. And um, then they can get a review of, you know, should we actually send this to this audience at this time? So it sends that as well and the team can review it and know and know what's up. Um, I but I I pulled up I pulled up these four I pulled up these four email sends and I made very light tweaks. Um, partially because I was like, "Oh, I think I can write like a slightly better headline." And also partially because I'm still a control freak who doesn't want to turn over every single thing to AI. I was like, "Let me, you know, let me like put a little bit of spice on this." But I I maybe spent 10 minutes of extra work on it when I came back from the gym. Um, and then we we scheduled them and we we let it rip. And in in a couple hours the next morning, those emails alone had driven more than $25,000 in revenue. Um, it had driven like multiple conversions. It suggested things we could do to retarget the audience that didn't convert. Um, and like two nice things happened. Like one, I got to go to the gym, which is great because otherwise I would have sat there building these these emails. Um, and two, like at the gym, not looking at my phone, not looking at Slack, I had other ideas for stuff we could do the next day, right? like disconnected from being in the weeds. I'm like working out and I'm like, "Oh yeah, we should like we should do this experiment and that experiment because I don't have to use my brain and my fingers to like uh click around in Postto, which I which I love using, but I don't have to click around in Postto like find the exact right audience segment to to target." So that that's it's just so crazy like to go from here's an idea to go do this idea using slfg to actually like executing on what it created in this case sending these emails to generating $25,000 in revenue which doesn't happen every time you do slfg but like that is you know sort of a possibility to then compounding what you learned and also it recommending like what to do next. It's just like remarkable that you know like 5.6 soul is expensive but like relative to the value that you got out of that it's like nothing and best of all you went to the gym and like took care of yourself and that's it's just like remarkable that you can do that. You can if you are really harnessing these tools well for work and for life. I use it as my trainer at the gym. It's um it can be very fulfilling and and uh and like so effective. \>\> Yeah. Uh I feel it allows you to be get better at things you want to really get better at. Uh it it it frees up more time. uh like to give an example like uh when like Austin I like people are always pitching growth ideas to us like hey do this do this and to be really honest those are good ideas but I don't want to spend take away time from doing my main thing and spend time on that and that entire thing should be automated because a the idea is good we should not hire an engineer just to implement that particular idea so I feel we have these tool sets like if I have a workflow set up hey let's try this particular uh headline on our website. It should be like you should be that should be automated \>\> and I feel we can that's the goal like I have more time to do like deep work \>\> and or and be in my flow state and without really compromising these things like building that loop is me being in the flow state. \>\> Yeah. \>\> Versus like hey try this try this try this. And I think the thing we're we're like um circling around is like uh this is the best way to to build right now which is to um you know Kieran uh our colleague has described it this way of you're at the top and bottom of the AI sandwich. You you you decide what the problem is. You frame the idea and then you review the work. That's been the case for a while. But the exciting thing about this moment, the exciting thing about being able to use the tools in the builder pack is that you can go from idea to execution um quickly, easily, reliably, and at like a very high level by being able to just like um type or with Monologue any speech to text tool like we use just to be able to say the idea um and have it come out. And the the thing that I really like about this, the way I like working is that um whether you're, you know, primarily a Claude user like Yosh or a Codeex user like me, the tools all now speak together really, really well and connect to each other really well. Um Notion is is a great example of this. I have hated notion for years because my brain doesn't work in that way of like I'm gonna like organize this database and I'm going to make sure that like the growth hub makes sense to other people. \>\> Yeah. Yeah. Like uh I think up until a year ago, Notion was had had too much of a like um of a barrier to entry on like organization and m and maintenance that anytime I try to use Notion with a with a team, we've churned because no one's around to maintain it. And all of that maintenance has now been pushed off to Codex and Cloud Code. Once a week I just ask Codeex and I'm like, "Hey, can you like reorganize our growth hub?" And it does it perfectly. It's like amazing. Or it's like, "Hey, make sure this database is is set up well." Um, my favorite example of this is while I was doing the um this kind of like in the weeds codeex work, like when I work with Codeex, I'm like steering it and going back and forth with it. um Claude in in Cloud Code in the desktop app using Fable. Uh, I had the videos we're releasing attached to this launch all connected through Descript and the Descript MCP and Fable is just running in a loop building out the edits for all of those videos and reviewing its work and and interacting with Underlord, the Descript AI tool, because I'm not a video editor. like I'm actually really bad at it, but uh like sometimes that falls under my responsibilities and that can run in a loop so that when I go to edit the video by no means has has Fable and Descript created a video that is publishable, but it has gotten me like 70% of the way there while I'm steering codeex cloud code and Fable and and Descript have gotten it there so that I can go and I'm like, "Oh, I know what to do now." Like I see the pieces. It like it does this crazy stuff where it takes the transcript, makes a storyboard, makes a script itself, and then like pieces the video together. So I just have to do like a few tiny things to get us to a final product. You already know how AI is changing how everyday work gets done. \[music\] How much ground you can cover and how fast a team can scale. To stay ahead, you need tools that give you a competitive advantage built for this new era. Adio is the CRM for the agent native world. \>\> \[music\] \>\> It meets you where you work, compounds every customer signal into context, and then acts on it across your pipeline to let you move at unmatched speed \[music\] and scale with agents and automations for every job. Adio orchestrates your work around the clock. We use it internally at every, and we love it. It's built to handle the scale of your workloads. It's extensible with an API and MCP access and is built with infrastructure to keep up with your most ambitious agents. It's loved by high growth startups like Granola, Modal, Whisper Flow, and EveryY. Adio runs the work behind Every Win. That's Adio, the Agentic CRM. Go to adio.com/every and \[music\] get 15% off your first year. That's adio.com/every. And \[music\] now back to the episode. \>\> I think the thing that I love about the builder pack specifically is I feel like a lot of the time at every we're telling people like, "Go build, go build. It's the best time in the world world to build. There's no excuses. Be the builder you want to be. And that's great, but how \>\> it's it Well, one is how, which is like you should subscribe to every We will teach you how, but two is this stuff is expensive. Um, and the stack that you use, Austin, the stack that you use, Yash, Douglas, myself, it's very expensive. We spend a lot of money at every on AI and credits. And last night we had an event in the office and a friend of mine's younger brother, I invited him to come. He's an engineer and he he's trying to figure out how to get a job as an engineer right now. Even though he is an engineer, he's really struggling to get a job and um he's not using AI at all. \>\> Yeah. And I introduced him to some people that were like telling them how they work. And then at the end of it, he was like super excited. And then he to these people were telling them like how much money their companies enable them to spend on AI. Some guy, you know, he's like a single engineer spent 30 grand last month. And this guy like, you know, I could see him like visually like gulp while he was like, "How am I going to discover this technology when it's like prohibitively expensive as an and I'm an individual. I'm not at a company right now." \>\> And the thing that I love about the builder pack is um it is, you know, I think the the codec the OpenAI uh benefit is like a great example of this because you're getting uh three months free. of uh OpenAI and Codeex and um $1,000 in overage credits. But the three months free includes I don't know what the number is anymore. $5,000 of value like these these subscriptions just like our our you know our anthropic benefit they include so much spend inside of a small subscription. Um, so I mean in it's the same thing for basically OpenAI, Cursor, uh, Gemini, and Enthropic, those offerings because they're they're model companies. So, uh, okay. It's one month, excuse me. Uh, the one month offering, \>\> right? \>\> Uh, you can use the codeex credit. \>\> You can use the codeex credit for three months. Yeah. Uh it's so much value that like you then get to go experiment with the technology so that you can um \>\> be the builder that you want to be. \>\> I use them all the time. My my stack um I mean the the builder pack is basically everything that we use at every personally. I'm in OpenAI Anthropic. I'm more of like a consumer of Post Hog than I am like \[clears throat\] a user of of like their AI credits. You're always in Notion. \>\> I'm a big Notion user because I do like a lot of ops. Um, framer user, render, and I really like experimenting with the Flora MCP. Um, so I mean, I'm kind of all over the stack. My my biggest use is like obviously like the model companies and just like doing my work inside of uh inside of Claude or or uh or or Codeex. Um, I mean, ironically, a lot of these tools, almost all of these tools, if they aren't a model company themselves, I'm utilizing them through a model company. I'm never really ever going into their tool. Even Flora, which like has like a remarkable tool. I only ever use it through the MCP. \>\> Yeah. And it doesn't uh it doesn't devalue those tools. that actually like uh to me it it incentivizes the uh those like uh SAS operators to be the very best at the thing they do. Um I think a lot of us went through a moment from like January to March where we were like let's go. We're building our own CRM. We're building our own like data dashboards. We're going to like do design all ourselves. And you start doing it and you're like man this sucks. Right? And um when you're able to sit there and be like, you know what, I I really trust Posttog to both run and automate my analytics. I really trust notion to have this like source of truth for the entire business. And even if I never open it up, even if my pages and my databases look incomprehensible to a human, it doesn't really matter because when I'm sitting in cloud code or codeex, I can which I which I do all the time. I'm like, "Hey, I need to make this plan. ity to do this thing um uh at notion at Slack at Posttog find the necessary information. That's one reason why the um this suite of tools is so powerful right now is that the leap from 55 to 56 came with this improvement in the model's ability to go find the context it needs to do work well and then to maintain that context through any amount of compaction that happens as it works over a long term. that happens through the way in which um if you looked at my prompts in in codeex, you would be like, I think this guy uh doesn't know what the hell he's doing because I'm I'm usually just like, hey, look at look at all this stuff. Um create a goal for yourself and use compound engineering and I'm like go. It's like barely any thought or work. the thought or work comes from like I've identified this is the thing to do and I know that either I or my team have set up the harness that the agents can work inside of to be trusted. Um, and I think to a lot of people that sounds like tough. It sounds like a lot of work, but the reason that that we've gotten there from every is we've we've done it incrementally, right? Is like we did one thing and it started to work okay. We've been I've been trying to automate these marketing email sends for months and it keeps getting a little bit better and through compound engineering the results keep compounding. So the project I work inside of keeps getting a better understanding of it and it it kind of goes back to like the the best time to start doing this was you know a year ago. The second best time is right now. Um, you can start this compounding flow right now with models that have have really caught up to how how quickly you can work yourself. \>\> Yeah. I'm curious to know, Douglas, what's your stack? Because you're the creative director behind this. And someone asked me like what this branding is very different from every's branding. So, like why is it green? I had I'm like, okay, I'm gonna ask you. \>\> Yeah. \>\> Yeah. Why is it green, Douglas? Um, I think it's green partly because we haven't used green that much yet in our in our brand world. But, you know, I think what's interesting that all of you are describing and that I've learned in my, you know, short few months I've been here at Every is I I think language is very interesting and I I find the way the model companies name themselves and their new models very interesting and a lot of it is very literary. It's, you know, Codex is a book. There's haiku, sonet, fable, right? These are all stories or or or forms of putting words together. But the term people use for agents is orchestration. And it feels a lot more like music to me. And I'm not super musical, but I think everyone in their job kind of played a few instruments. And it now feels like we can all take a step back without knowing how to play the rest of the instruments in the orchestra. We can conduct it, right? And as long as we understand what what the piece needs to sound like. And then you know you take that and you compound it onto you can be conducting a lot of different orchestras at the same time. And creative direction I think and and kind of brand strategy is a lot of famous uh you know designers have described it as being like a maestro and you have color type, shapes, symbols, forms, words, uh you know systems, photography a lot of the time, illustration styles and how do you kind of conduct all of these pieces together to to sing a song that that sounds beautiful? And I feel like this stack is is that for working with AI and it's applicable to a lot more than just the the highly technical work, right? So I certainly use it for knowledge work. And to answer your question, I do like Flora, so I can talk more about Flora because I'm probably the the deepest in Flora, but you know, I I've learned here too also, and I think Austin touched on this, like what to use Claude for, what to use Codeex for, and being able to, I think, use both of them through, you know, I've also built out kind of a set of marketing skills that I can use with compound engineering that really helps shorten the timeline on something like research when you're trying to come up with strategy. You need to have data that backs, you know, an insight or a hunch that you have. Do I do I think that the tools come up with the insight particularly well? Not always. Sometimes they do, but you can then give it the insight and say, prove this out. You know, what direction should we be taking this? Here's the competitive set. It's really good at competitive auditing, especially if you build a skill for it. Um, and it can compound on that. And just you can say, push more. I want pricing. I want language. I want what colors these brands use. And you take that, you can feed it into a system and have a really really sharp strategic lens in like, you know, hours or or less as opposed to what used to be a several week long process, frankly, with humans researching. And then from there, if you have an eye towards what you want to create, using a tool like Flora is really helpful because again, like similar to Austin, I feel I'm not a technical designer either, but I can I've been mood boarding for 15 years. You can now like productize a mood board, especially if you have the right prompt, and you can use Claude to write the prompt for you, put it into Flora, right? Or use the MCP as Brandon does. um and have it take a set of reference images. I often have it analyze the images and kind of say like what am I what am I doing here, you know, and it'll be interesting. It it might say something like with builder pack, this is very high contrast. Um you know, to your note about green, I think this is in a way our most explicitly technical kind of facing audience that that we've been speaking to in terms of the builder pack. like this is for people that are really ready to start experimenting with with all of these tools and it feels a little bit more matrixy and and digital than a lot of the more Greco Roman and kind of heritage driven uh elements of the the every brand. So, you know, all of those were decisions that these tools helped us kind of land on in terms of the aesthetic of everything and also helped us design the website, right? So, it's it's pretty cool to be able to it's a mind shift for me, a mindset shift of moving from playing the instrument to orchestrating. And when you learn how to, you know, get one group singing and playing, you move on to the next one and you can conduct lots of pieces at once. And that's what I find, you know, I'm just beginning to use um like have everything plug into Notion, right? Super helpful. And to Austin's point, you can just be like, "Look in Notion, find this thing. do this for me, you know, compound whatever it may be. And it has all the relevant context because it's been updated because someone else on the team has automated it to update itself. And I think the way you work as an organization also then just gets like, you know, souped up to a to a crazy degree because we're all orchestrating at the same time. Um, and it kind of pumps. So yeah, it's been it's been really exciting for me to work with these tools and apply them to, you know, it is the sandwich. You have to put a lot of work in at the beginning is what I found in terms of really doing some metacognition and figuring out like how do I think about this? What is my process? you know, and then once you've kind of codified that, these tools can run with it. And you can ask them for help if you if you don't know why something happened, which I find like very revoly. \>\> Yeah. That it's remarkable when people are like, "Well, how do I use it?" It's like, "Well, what are you trying to accomplish?" And then they say that and I'm like, "Great, just say that again." \>\> Yeah. Just just say that. I think I think uh um a good final thing here is like if we're um if we're thinking we're speaking directly to people who either like just got access to the tools in the builder pack or like thinking about it like um this has been a lot of kind of like higher level thinking about how to work with a few examples like I think each of us saying like say you have access to all the stuff in the builder pack and you're like what do I do now right like what would each of you recommend commend someone do whether it's one specific thing to try or one like uh mentality um approach to to take um if someone is like a brand new builder I think we can go around and and do that. Um, I I if I if I was uh if I had just got the builder pack and I'm just like getting my feet wet right now with with building, um, I think the first thing I would do is if you're like really early on sometimes the hardest part about building is knowing what to build and you can like just sit at your computer and be like looking for a problem is the worst way to find a problem. Um, going for a walk is also like not an effective way to like find a problem. You need to like that is a habit that you can build where you can like identify problems in your life well cuz usually we're just like so numb to those problems. So if I'm new to building and I'm new to the builder pack, the very first thing I would do is like pick something simple that I really really love, like a product that I really love and dupe it. Um, I would just make it myself. the very very simplified MVP version of that and use basically as many parts of the builder pack as I possibly could. So like I would launch it on render um and use the render credits. I would plug in Post Hog so that I could actually like maybe build in a loop or use some of Post Hog's traditional products where I can just like actually track how I use it, how my friends use it. I would build it using enthropic, using claude, using codeex, using cursor. Um, I might actually use some AI uh in that product. Uh, you know, even if it's a product that doesn't include AI, I might figure out how to do that. I might use Flora to actually like create some unique uh icons or graphics. But I would just dupe something because what I find when I dupe things, at least early on when I was duping, I would get started with the process of making it and very quickly I'd be like, I don't like that feature or I don't like that, you know, version of this thing and I'm going to very quickly it's not duping. It's like inspiration and you're off making your own thing. Um, so I would, if I'm new to the builder pack, I would dupe something and I would look through the builder pack and be like, "Which one of these things can I actually start um using in this build and not question yourself for a second? Just start doing it." I mean, that's that's like the hardest part sometimes is just like the first the first prompt. \>\> Yeah. I I find that like um one I think everyone learns uh learns everything in different ways but especially like learns how to become a AI builder in in different ways. I think some people really want to like understand what's happening and other people just want to like go and ship and and learn from what doesn't work. The thing that worked best for me was um okay I have like I actually have a lot of ideas for what I I might want to do. of the ideas I might want to do, let me pick the one that I'm the most excited about, which for me was this like um movie app that's like Fandango for indie movies. I was like, "This doesn't exist. If this worked, this would make my life a lot better." I would be so stoked. Like, one thing that I think is a good prompt to yourself is like, "What would you be the most excited to text someone like, "Hey, I made this, right?" Like, what would make you feel really good to do that? And I would actually really encourage people to try to make um not to necessarily make like a complex app for the sake of complexity, but try to make something you don't think you can and try to make an app to start because you're going to learn so much through that process. Like in doing that uh process to make this like web app that is now live that a lot of my friends use every week now. um I never done any of this stuff before and then it's taking you through like oh yeah you need to connect render you need to go through Google ooth like whatever um because it's a thing that you're so passionate and excited about and you want to get to the end it it quickly starts to feel like uh you're playing a video game and like trying to get to the next level and I do think Brandon's point about like okay to start um connect the agent whether it's Cursor Claude or or codeex to the tools in the builder pack and any tools that you have access to to be like you can connect it all and be like hey you have all this stuff the agent will figure out where to go but I think driving towards that goal of I'm going to make something great that I'm like excited to text a friend like hey go go go try it and along the way you'll realize like oh it actually works crazy it's so exciting that it works but like the design looks like ass like how do I make the design better and like you can sit and work with that you read every for some inspiration for design. You can go use it to to check stuff. Um, but that would be my best recommendation and that that's worked really really well for me. And then I've learned from seeing the V1 chip that the agent comes up with and being like, "Okay, that's not good enough. Let me figure out how to get it to a to a V2." \>\> I have a good specific one uh for marketers, writers, designers, creative technologists, uh product designers. I think to Brandon's point, I know your problem and it's probably your portfolio and this is a wonderful stack to rebuild your portfolio and it's something that I think everybody kind of hates their portfolio site, but you need it and you, to Austin's point, probably have a dream version of it in your head. You can use Brandon's duping kind of uh strategy here, too. If you see a site that you really like and you want to try and and mimic it, or you can come up with something from scratch and write the brief uh for what you what you're looking for there, put in the references and give it to Codeex or or Claude, connect it to all of these different tools and, you know, take that on as a project. I think it's a really enriching thing to do because most people have so much work that you're not liking the way you've potentially merchandised it to the world and maybe you want more interactivity or different types of visuals. Uh you can use these tools to create something really really striking that you feel good about and that also potentially helps you get more work or a better job or whatever else it is you're looking for and it kind of also proves out that you're AI native, right? So, I think that's a great project for anyone that's creative. Um, or has even a personal, you know, side hustle or or small business that they're running. Uh, try and and do something like that that's impactful right away because you can also get people responding to it. Um, you know, to Austin's point, right? His app, hey, his friends use it now, right? People can actually use this thing. They can see it. They can tell you how great it is. And that's very encouraging. Uh, as you begin to work with AI, in my experience at least. \>\> Yeah, that's cool. Yeah, I I feel uh to second that like uh or to or to close it out, what I would do is I would use the I would use cursor uh with render and what I realized my mind was blown uh when I used cursor cloud agents with Kimmy K25 which is an open source model which cursor improved. I would say dupe something use cursor cloud agents and use different models. I I feel right now if this is what you're going to be doing, you need to find your favorite model and with cloud agents you you can have 10 agents running and we have like the pro plus plan. This is above pro. So you're good in terms of like spend and stuff like that. And I would use render to deploy it and actually see which model you like working with. Like I'm I'm so picky about my models that even if a new model drops I don't I don't change so that because if I have some preference I'll test it out. You need to have like we have eval like like you know if if a model is doing better or worse. You need to have your personal taste in terms of what you like and what you not dislike. And I feel cloud agents are a very underrated way to find out like h what do you like to build and and just start to feel that out. Yeah, cool. Um, in terms of like what's next for All Access, I think we have some cool stuff coming. I mean, in the next few days, week, we're probably going to drop two more partners that are pretty sick benefits. Um, and I think that like something that's really compelling for our readers, I found, is like now they have access to these benefits. You guys have access to these benefits, but like the guides on how to use each one are people love that. So, I think that like probably what we're going to do next is for each one of these benefits, you have like amazing value that you can go capture by by by using them, but how can we pair that with a guide that you can probably just plug into one of your agents that like leaprogs you ahead with using whatever this net new technology is that you now have access to. So, I feel like guides like some cool camps for each one of these partners is going to be like probably something that we'll do. \>\> Yeah. \>\> Um, \>\> to be clear, I've I've never read one of our guides. I dropped the guide into codeex and I say like use this to help build the next thing we're doing and um I would recommend everyone do the same. And yeah, I think the best way to think about um all access, but also like how to best take advantage of an of an every membership is that we are going to keep adding partners to the builder pack that we're excited to use when the year is up because you you you know, you get these as part of a yearly subscription. We're going to try to fill it up with more stuff that you'all are excited to use and um there's a lot more perks coming. So, get excited about that will help you build. \>\> Awesome. I I think now we're handing it off to Dan's outro. So Dan, take it away. \>\> Thanks, Dan. \>\> Thank you. \>\> Oh my gosh, folks, \[music\] you absolutely positively have to smash that like button and subscribe to AI and I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard, but instead of gold, it's filled with pure, unadulterated knowledge. bombs about Chat GPT. Every episode is a roller coaster of emotions, insights, and laughter that will leave you on the edge of your seat craving for more. It's not just a show, it's a journey into the future with Dan Shipper as the captain of the spaceship. So, do yourself a favor, hit like, smash subscribe, and strap in for the ride of your life. And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.