Session 4 - Unlock Super Productivity Build Your 2nd Brain With AI === Justin Zimmerman: [00:00:00] All right. Nice and smooth fantastic start to our next session here. Uh, we were just in our previous session with Ty Lingley from Work day, and now we have another amazing session here. I was giving you some love and appreciation around, uh, what I've watched you build over the years. Uh, you and I have worked together on other projects. Justin Zimmerman: Um, I love the way you think, by the way, and so you just... You have great catchphrases. You're able to distill complex ideas into, like, two or three words, not even sentences. And so, uh, I was telling them, people don't get to come onto this show unless I've sat down with them and seen what they've done, what they've built, and we do a practice session and, uh, you just have some great things that you're gonna share with us here today. Justin Zimmerman: Uh, I know I'm taking for granted years of relationship and understanding of who you are and what you do, and so why don't I give you the opportunity for this first couple of seconds here, um, as everyone joins us to let you, uh, introduce yourself, a little about where you've worked, what you've done, things you've [00:01:00] accomplished, and of course, what we're gonna get out of our session here today. Justin Zimmerman: And, uh, while he does that, please everyone in the chat, uh, share a link of, uh, your, your LinkedIn URL, uh, or where you are in the world. Let's create some love, appreciation, and engagement 'cause, of course, um, this is about not just the content, but it's also about the connection. So welcome, Alan. Let's give you a round of applause. Justin Zimmerman: Take it away. Allan Adler: Awesome. Thanks, Justin. And, and I love, uh, I, I love Believe even though Believe is backwards, uh, mostly because, uh, at the end of the day, um, AI is something you either believe in, um, or you don't, and if you believe in it, you go deep, and if you don't believe in it, you stay back, and I think the people who stay back are gonna be the ones who will regret not having jumped earlier. Allan Adler: So, um, for those of you who know me, I've been in the partner space for four decades. Um, I've done a lot of first things all the way back to wholesale distribution and laying the foundations for cloud computing and establishing foundations for ecosystem-led growth and creating platform business models and all that [00:02:00] other stuff. Allan Adler: Um, got a management consulting pedigree, Boston Consulting Group, went to Harvard Business School, all that kind of stuff when I was a, a youngster, and since that time, I've been hanging around, you know, trying to really, for, for lack of a better word, figure out how to make this whole partner thing really work, um, given all this complexity. Allan Adler: And my most recent, uh, change is that I have now self-designated myself as the chief AI architecture of our company, and we have a, we have a 400-person company in tier one. Thirty of us focus exclusively on partner ecosystems, and we're leading a transformation starting in the partner ecosystems space to actually turn our organization into an AI first services as a software provider. Allan Adler: You may have heard that term services as software versus software as a service. And what it really means is that gone are the days when you can basically have a service where you're producing artifacts. You now have to architect solutions that produce those artifacts for you, and if there's one catchphrase for my entire Second Brain story, it is stop producing artifacts, start [00:03:00] producing architecture. Allan Adler: If you produce architecture really well, everything improves. Your artifacts improve, your scale improves- And ultimately, you get to take advantage of all this stuff we've been hyping around agents, right? If my presentation's about second brain, I'm gonna explain what a second brain is and why it's so critically important for everyone to understand it. Allan Adler: Because what ultimately is, it is a system of intelligence. It is something that sits between a system of record and a system of action. And today, if you think of PRMs and CRMs as system of records and, you know, things like, you know, um, Outreach and others as systems of action, there is no real system of intelligence. Allan Adler: So if you're a partner business manager, a partner marketing manager, a selling partner manager, you're sitting in the middle between these records and these actions without intelligence. And it's not that we're not intelligent, it's that the world is too complex to rely just on this human brain. We need a second brain, and that's what the system of intelligence in this story is gonna be all about. Allan Adler: But it's not import- it's not just one [00:04:00] second brain, it's, it's federating a bunch of brains. And so we'll talk about how we've been pioneering the second brain concept at Tier I. Again, we're a management consulting firm, and my group focuses exclusively on helping tech companies, SaaS companies, hardware companies to transition to becoming more ecosystem-led. Allan Adler: And ultimately, now we're using the second brain as a mechanism to drive that services that we offer. But ultimately, today I'm gonna show you how you can use that in managing your partnerships. And in fact, if you stick around for the whole thing, there's a gift at the end, which is a skill that will let you create a second brain over the weekend, you and Claude, and you can, uh, you can put this to work for yourself. Allan Adler: So ultimately, we'll talk a little bit about how every deliverable, a PowerPoint deck, a Word document, a QBR, um, a pitch deck, a better together story, all of those things that we normally spend time creating, AKA artifacts, ultimately should come out of a brain. We design the brain, the brain produces the artifacts, [00:05:00] and we're the editor. Allan Adler: And that ultimately, the, the way that works is when you think about any kind of project, you're gonna think about a brain as a, as a unit of operations, a unit of architecture. When stitched together with other brains, like say you would have a sales brain for your partnership with, with AWS, and you would have a marketing brain for your partnership with AWS, and each of those brains would come together to give you your go-to-market brain or your demand gen brain, if you will. Allan Adler: And so we'll talk a little bit more about how that's gonna work at scale. Uh, we're gonna talk about the shift of work. I've already talked about this, the advantages, how to apply it to partnerships, and applying this, uh, this, this interstitial intelligence between the record and the action, and talk about one operating model. Allan Adler: This is a big stretch. We're gonna propose that this second system of intelligence could manage all partnerships, and I'll show you, uh, a little science experiment we're doing on that. And finally, an invitation, which is I'm gonna give you at the end of this session your own skill that you can take and build second brains with. Allan Adler: [00:06:00] Okay. So far, so good? Awesome. Justin Zimmerman: Yeah. Allan Adler: All right. Um, so what is this system of intelligence? So think about, like, all the things that you're gonna do, right? You're gonna create decks, reports. You're gonna need to build automations. You're gonna need to create these things that make for outcomes because, you know, at the end of the day, these are the things that make outcomes happen, right? Allan Adler: You have a QBR, it creates the outcome of a good quality meeting. You have a better together story, it creates the outcome of a go-to-market strategy. You're gonna create a bunch of campaign assets on the basis of creating top-of-funnel activity. You're gonna create some kind of funnel management system that'll tell you how you're doing on converting things. Allan Adler: All of these are artifacts, right? But those artifacts need to come from an architecture where the goals, evidence of success, decisions we're making, and target states are all contained within an AI architecture. So this is one place, and if you've heard this concept of interlinked markdown files, markdown files are AI talk for a doc. Allan Adler: And when something lives in a markdown file, it is [00:07:00] essentially connectable So what we'll talk about today is how the second brain produces a whole series of these markdown files, and when they're all tied together and connected and each node knows what the other nodes are doing or each node knows what its roles are and its neighbors, you get context and not just storage. Allan Adler: So an example of this would be if I have a second brain for marketing and it has the Better Together story connected with, uh, evidence of success, we know what good looks like, I can ask it, "Help me create my ideal customer profile for me and the partner based on what we know." Or if I have an ideal c- partner-- ideal customer profile, I could accid- I could ask it to help me identify the triggers that are associated with high propensity to buy. Allan Adler: These are all just artifactual outcomes, but they all come from that architecture, which once built, starts to create compound effects. Now, the, these brains are generative, and why that's important is [00:08:00] because you're not hand-authoring them, right? What you're doing is you're basically asking the AI to think through what's gonna needed t-to get to the next step. Allan Adler: So if I wanna create an ICP, I will say I would define an ICP and I say, "Okay, brain, we need to create an ICP for this Better Together story. What inputs do you need? Go research what an ICP is 'cause I don't... maybe don't know all about it. Go tell me what ICPs are composed of. Tell me what data you have and tell me what data you don't have." Allan Adler: And it would say, "Oh, well, you're gonna need data on this." You say, "Oh, I know. There's a Word document over there that has the, the data I need. Let me import that into the brain." It takes that, synthesizes into a markdown file, and makes the connectivity that, that allows you to go about creating that ICP. So ultimately, this is this notion of turning this generative machine into a capacity that can then launch agents. Allan Adler: So what-- a way I was thinking about the title of this slide, it was to be second brain and the agentic agents that follow. Because what happens when you sign these second brains up [00:09:00] is be you managing a partnership with seven or other digital agents who are off doing research, designing this part, collecting the transcripts, going out and figuring out what needs to happen in from a competitive perspective. Allan Adler: How does that partner work with someone else? What information do I not have? These are agents that help you to achieve this, and that all is sitting inside that second brain. Now, I mentioned that a second brain is not just one thing. Uh, let's take a consulting project, right? Where we, we need to solve a problem with-- for one of our clients, and I'm actually gonna show you a live version of this in a consulting project where we're solving a partner problem for SAP. Allan Adler: Uh, ultimately, let's imagine that there's a program brain that everything rolls up into, so it's like l- the place you'd start with a big question. But big questions need to decompose themselves into workable brains. So in this particular project example, we have these series of interlinked brains. The corpus [00:10:00] brain has all the raw materials. Allan Adler: So we go to SAP, we say, "Tell us everything we need to know about this project." Documents, references, interviews, links, stick them all in the corpus brain. Now that becomes, let's call it the, the, the honeypot for all the stuff that we need to know that SAP gave to us. But now we have to establish a methodology. Allan Adler: How will this project take that corpus material and combine it with other information to create rules so that, for example, you'll pull a raw material from this, you'll do an interview from that, and from that raw material in the interview, you'll come up with the next step and the next step. And each of these things, as I mentioned in the last slide, is an evolving thing. Allan Adler: A corpus brain is a little bit more content-rich. A methodology brain is more process-rich. A constituency brain is more, is more network-rich, like who is out there that we need to talk to? Who are all the individuals in this project that we need to know about? You could imagine doing this with a large partnership. Allan Adler: Say you're managing PwC, or you're managing, um, um, some-- a large corporate reseller where you typically have lots and lots of stakeholders. Well, you [00:11:00] gotta know who they are, and then once you identify their constituency, you can start making rules. You know, Bob, the CRO, is interested in this thing and needs to get this information. Allan Adler: Jim, the VP of marketing, is interested in this stuff and this information. So the constituency brain holds all of the who and the what and the archetypes and the stakeholders. And then we have a synthesis brain. This is the brain that takes all of the methodology and the corpus and all the other stuff that we do, maps it to the constituency and tells us, "Okay, output time." Allan Adler: Now we're gonna talk about patterns and insights. What are the things we've learned that can then be instrumented into yet another set of brains that actually walks us through how to turn that into an artifact? But hopefully, I gave you an orientation. And what's cool is this may sound very complicated, but when you start working with my skill- You'll be able to talk to the AI, and it will automatically help you figure out, "Okay, this is my problem. Allan Adler: Help me design four brains or f- how many brains do I need?" It'll say, "You need six brains, and here's the-- what they are." And they'll describe it to you, and you [00:12:00] know, the corpus methodology constituent. You say, "Wait a minute. That doesn't make sense. Why is there that brain?" And they'll go, "Oh, you're right. Allan Adler: Good question. I actually got it wrong." Now, that's a really important moment for those of us who use AI. All the time people say, "Oh, AI makes up stuff, and AI is useless because it's fanta- fantasizing about stuff." The only reason that's true is because we don't know that this AI thing is actually a dumb genius. Allan Adler: It's incredibly powerful, but it's also stupid at the same time. So the job of the human at the construction of the brain is to be smart. Say, "Is this brain make sense?" If it doesn't make sense, you challenge it, and you say, "I don't think it should be a synthesis brain. I think it should actually be this." Allan Adler: And then you start to debate with the AI, and you actually engage in a sparring event where you say, "How about this, and how about that? Yeah, that makes sense. How about this? What if we did it that way? You're right. Let's do it..." So you think of it as like this interactivity, and literally, I spend about 70% of my day talking to Claude Cowork. Allan Adler: No kidding. I'm actually using it as my [00:13:00] engine of innovation, my engine of execution. I'm the one who's architecting these things, and then it goes off and does amazing things. And the compound effect of this, I can't overemphasize how much value you get once you've done this for a little while and you start to see the, the snowball going down the, the, the road Okay, so let's, let's look at, let's look at one brain. Allan Adler: Let's, let's take, for example, um, a brain whose job it is to, um, ultimately produce a strategy or a playbook or a change management plan. And this is again, you know, the, the stuff that we do as consultants, right? So in the brain builder skill that you'll, you'll see, right, you're gonna see a target state model. Allan Adler: This is where you're gonna define what is the end state you want. Every brain is only as good as the specifics of what you ask it to be and do. Your job is to... And then you have a sentence, and that is fundamentally the most important sentence you articulate to the brain. What are [00:14:00] you here for? Your job is to. Allan Adler: And then from there, you start to ask it about the siblings. The siblings I've mentioned, I talked about these siblings here. These are all sibling brains of this program brain. You start to ask it, "What am I trying to accomplish?" And many times it'll start to say, "Oh, okay, well, you're gonna need some kind of evidence and synthesis," right? Allan Adler: You're gonna need some way to code the insights, figure out what the stable identifications of t- of patterns are, and we're gonna help you then figure out how you federate that, what brains, what families, what sync rules, and all of that stuff then comes together to give you the, uh, give you the outputs you're talking about. Allan Adler: So I thought I'd actually show you one of these, right? So something that's conceptual, right? But what we did is we did a large project for, uh, SAP's top s- system integrators, and we, uh, we had a bunch of activities, uh, and we put them all in different layers. You could almost think of these as data sources and brains that feed into methodological l- layers that meet in s- feed into synthesis, that feed into the program. Allan Adler: Remember [00:15:00] when I talked about the program brain was at the top? I'm gonna go reverse order and show you how you get there. So in this particular instance, this is a, this is a live landing page of, of what we did. You can see over here, like these are all the inputs. So we had tons and tons of interviews. So you can almost imagine this being in your case Justin Zimmerman: as you're managing- Is there any way to zoom in for us? Justin Zimmerman: It's pretty tiny Allan Adler: Yeah, you bet. Better? Justin Zimmerman: Yeah. Allan Adler: So this is an example. I'll, I'll kind of scroll like this. So we're in the field interview. So these were all the, all the people that we spoke with, right? And then these were all of the source documents that we were able to ingest. So all of these things are basically being ingested by the machine. Allan Adler: This is the-- this is all of the, the corpus, the raw information that we were able to bring in, programs, past playbooks. One of the things we were hired to do is to, is to build a, a playbook, and so we had 11 great examples of playbooks that we'd built for other clients. We also had a whole bunch of, uh, past, um, uh, change management plans. Allan Adler: So then we have the methodology brain. It tells us all [00:16:00] of the, uh, the interviews that we needed to do, the barriers we heard about, the probes we had, all the maturity dimensions, all the weighting. This is where a lot of the stuff that synthesizes itself into the constituency brain. And then these are all the people. Allan Adler: Now, this is really powerful. So when you have a project or, or, or any kind of activity involving loads and loads and loads of people, you're gonna need to assign responsibilities to them so that if in fact I know I'm going to have to have a presentation to a certain level, I wanna know what group are they in. Allan Adler: I wanna know, um, are they global? Are they regional, et cetera? All of that gives you the ability to then say, "Okay, now when we get to the program brain and we're starting to articulate, 'Okay, what are the different things we're doing?'" We can now know that everything from our risks to our commitments, to our decisions, to our index, to open questions are all programmed associated with that methodology and with that l-level of constituency. Allan Adler: And that, of course, then lets us do these were our two deliverables, a, a playbook brain, um, that talked about all the stuff we need to do [00:17:00] achieve for that, and then a change plan brain. So again, many of this stuff might not be particularly relevant to partnership people because we're talking here about running a project. Allan Adler: But in this case, we're management consultants doing partner-led growth activities, and we use the brain to do everything that we did. So let's talk a little bit now about, um, what we can expect from this transformation. So first and foremost, what we can expect from this transformation is we can expect that we're gonna stop spending our time drafting artifacts And start spending our time architecting and curating. Allan Adler: Now, this is probably the biggest first mile you have to clo- you have to cross. I would ask each of us to answer the question: how much of your day do you spend developing documents? Developing documents. Because I will tell you that this presentation was built off of a second brain that I created for when Justin asked me, "Hey, can you talk about this thing?" Allan Adler: And so we st- I built a second brain for second [00:18:00] brains. And this presentation comes out of a markdown file that's produced by the second brain that got dropped into Claude Designer, and I spent maybe 15 minutes max editing this. This is all developed by AI, the whole, the whole thing, including some of the fancier graphics that I think I've shown you. Allan Adler: But ultimately, if you're spending time building documents, you are in yesterday's world. Tomorrow's world and today's world is spent architecting a living system that generates outputs. And so here's your kind of run the new race. The human designs the brain, that's the first mile. The brain drives the output, most of the miles. Allan Adler: And the human drives the edits and the polish, the last mile. So you got human, brain, human. Now, to be fair, a very important role is to continue to architect that brain. You don't just architect it once and walk away. Think of it like a continuous job of reimagining the [00:19:00] architecture so that it does a continuous job of reimagining the outputs. Allan Adler: And so you're-- the brain drives most of the output, but you're still in there curating. And maybe you guys have heard of, of engineering language that said we, we've gone from prompt engineering to context engineering. Well, now we go to the next level. We go to harness engineering, and we go to loop engineering. Allan Adler: And harnessing and looping is this, is this work to basically take the context that is the brain, harness it to make it work, and then loop it to make it continue to evolve. So that's just kind of the evolution of AI best practices in that context Okay. So four reasons to start building brains. It's cheaper if you do it at the beginning. Allan Adler: You can retrofit a bunch of scattered work, but you're essentially just building tech debt. I call it brain debt. If you build it early, it's nearly free, and you get [00:20:00] all these benefits. Probably the single most important output, if you were to really put it into perspective, is con-coherence under speed. Allan Adler: There is a notion that coherence and speed are conflictual, just like chopping wood and sharpening axe are conflictual. But in fact, what AI is doing is it's reshaping canonical ideas of like you either learn something-- How many of you know this problem, right? "Oh, um, I would love to learn AI, but I don't have time because I have my day job." Allan Adler: Okay. Wrong. The right one is, you must spend the time to learn AI so that you change your day job If you got, get nothing for more from this, sharpen the ax while chopping the wood. Don't go off and do a seminar to sharpen the ax and then take the old ax out and chop the wood. Spend-- The, the coherence under speed is so strong that you can spend the time to figure out how to make it coherent at the same time as you deliver your work, and that's why it's coherence under speed, because it means you can continue [00:21:00] to update, you can continue to make fast decisions producing more and better outputs, but you have to sharpen the ax and chop the wood at the same time. Allan Adler: So another thing that's really important is memory and onboarding. So when I was explaining this to our leadership, I said, "Look, look how dumb it is the way we do consulting, right? We get these big projects, and then we have our smart people running around delivering artifacts, and then they leave. And when they leave, there's nothing except a dead PowerPoint. Allan Adler: Why not build an architecture that stays in the project, and then when the client says, 'Oh, could you put an AI front end on that? Could you give us a change management order? Could you help us figure out how to apply that to Spain versus Portugal?' No problem. Fang, I can just turn it." So this ability to have a memory that stays on and an ability to onboard both teams and new projects is amazing. Allan Adler: And finally, the teaching quality is outrageous. I can now create a second brain with an instruction that says menu. You load it into Claude, press the word-- type the word menu, and it gives you the entire artifact, all of the brain [00:22:00] described. So I can literally onboard a new consultant with this brain in about thirty minutes, and they know everything that's here. Allan Adler: So imagine if you're running a partnership and you have a second brain for that partnership, and you, and you leave or you bring on new people. You simply turn them to the brain, and then the onboarding is like zero. Like onboarding is-- goes away with second brains because essentially you can ask any question, you can organize any content, you can facilitate any activity. Allan Adler: I could even design a market-- um, um, a markdown file to be the onboarding of a new employee into a partnership or into a program. All of these things just are more of the reasons why the second brain, this system of intelligence, is so great. Okay, now you've been patient, and I have, like, let's see, uh, seven minutes left, right? Allan Adler: Eight minutes. Oh, more time. What if you applied this directly to partnership? Okay, maybe a little less. So the other day I took my iPhone to the coffee shop, and in a couple of hours I was able to create a system [00:23:00] of intelligence for partnership in which I said, "Okay, I got all these system of record things over here. Allan Adler: I got all these system of actions things over here." And by the way, this slide was of course produced by a markdown file by the brain, so you're able to produce slides that are beautiful like this in, like, no time. Again, this would normally take an artist to, to futz around for two weeks. It took me three minutes. Allan Adler: But we produced a system of intelligence for partnership. So bear with me a minute on this other busy slide, but you know what you can do? You can break partnerships down into three motions. The business alignment and the solution alignment, why are we here? The go-to-market, which is the value creation, and then the value-- and then the, which is the value promise, and then the value creation, which is the value delivery. Allan Adler: And each one of these little things, these white things are brains See them? They're all brains. And, and these brains apply in two dimensions. For example, there is a marketing brain, right? It happens to be inside a lens, don't worry about the [00:24:00] lens, but a marketing brain that would apply to AWS and roll up to the AWS brain, and a marketing brain that would have AWS and Azure and CDW that would roll up to a marketing brain. Allan Adler: And so you'd be able to manage partnerships in marketing across, and you'd be able to mark- manage partnerships and partnerships vertically. And this, this is a vertical view that says if I were to roll up my relationship with AWS, these are the brains that I would need to have. And I have to have a governance layer and an enablement function, but ultimately we could build together, and we're gonna do it, um, this interstitial system of intelligence that sits between the system of record. Allan Adler: So let's take an example of this. Let's take the selling brain. Okay, the selling brain is gonna get its intelligence from PRM and CRM, right? The marketing brain is gonna get its intelligence from marketing automation. But ultimately, in order for you to have decision-making about what to market and how to sell, you need this intelligence layer. Allan Adler: So that's what this does. So to make a long story short, [00:25:00] um, I can... Anybody who wants to geek out on this, I'll show you what we're doing. We're just still early days, but we're defining each of these right now. We're gonna, we're applying it to a couple of partnerships just to test it out. Um, but I wanna make you a promise, which is, I made you a promise, which is if you hit this, if you hit this link, um, you can download our Second Brain skill. Allan Adler: Um, there's the link, secondbrainskillpage.netlify.app. So, um, I think you're gonna send out the PDF of this, right? Um, or I can- I'll send out Justin Zimmerman: the PDF. Send me that link. And also for everyone who's eager and anxious right now, I just dropped your LinkedIn profile URL, so I feel like people can just DM you. Go do that right now, so you... Justin Zimmerman: If, if you're, if you want what he's saying so you don't forget, uh, you, you can respond to everybody who hits you up right now from the chats with, uh, with that link to go get the, uh, the skill itself. Allan Adler: Cool. Cool. I cannot wait for you guys to try the Second Brain and give me feedback, because I'd like to make this an offer, continue to [00:26:00] offer these skills to the partnership community so that you can try them. Allan Adler: Uh, sh- uh, fair warning- Oh, yeah ... this brain is designed for- Mackenzie, Justin Zimmerman: Mackenzie just dropped like the most simple brilliant duh. Why don't you hover over that link again, left click, see what... Yeah. Yep, yep. Copy the link if you can see a copy button there, or if you can double-click it and open it up. Yeah. Justin Zimmerman: And then just, just, uh, open it up in a browser right now for us, and then come into- Yeah ... the attendee chat and- Save everybody some steps. Allan Adler: Awesome. Uh, one last thing is that this link works with Cloud CoWork. So if you don't have Cloud CoWork, go get Cloud CoWork because Cloud CoWork is fr- fricking cool, amazing. Allan Adler: Um, if you have Cloud, you can get Cloud CoWork and launch the brain inside of a new project in Cloud CoWork. The landing page... This is the landing page, by the way, so I'll give you the landing page. It's, it'll give you all the stuff you need Awesome. Thank you. Thank you so much. Good to- it's good to meet, good to see you guys.[00:27:00] Justin Zimmerman: Yeah. Well, I think that's a good place for us to wrap up. I appreciate you giving, uh, at least me a little bit of breathing room between sessions right now. It's nice to have a couple seconds right now. Um, and so if you do have a chance to click that link and drop it into the chat, um, that would be great. Justin Zimmerman: Uh, if not, I can understand there's maybe some complexity stopping you, but, uh, for everybody who's in this session right now, uh, you're gonna get the slides. Uh, I'm gonna send you the link that, uh, Alan's trying to, uh, maybe you need a second brain to, uh, drop the link in here. Ha ha ha, funny. It is second brain. Justin Zimmerman: Um, there it is. All right, everyone. Let's hit that link up. Uh, grab that link, and so let's show Alan some thanks and love. Let's type the word brain in the chat, right? Can't think of a better keyword right now. For the time and energy he put into thinking through this, uh, laying out his thoughts and ideas, some really great concepts. Justin Zimmerman: I think you... Two things you always impress me with. Number one, you've been a fantastic graphis- [00:28:00] graphic artist, graphic depiction creator of, like, uh, flowcharts and processes and systems. You've been able to visualize, uh, a lot of what you've been doing, not just now, but for years, and so I've always appreciated, uh, how you are, you're able to do it now better, faster, more effectively. Justin Zimmerman: And of course, uh, uh, you know, you've got some really great quotable quotes, so I appreciate that as well. So for those of you who are, uh, got another half an hour willing to wanna get to the next level, speaking of creating artifacts from AI and creating the architecture from artifacts, our next session is all about that. Justin Zimmerman: So, uh, I wish I could say that was intentional, and I was smart and strategic. It just happened to work out where, um, our next speaker, who runs partnerships at Quo, a, uh, communications phone tool system for salespeople, uh, in the HubSpot ecosystem, uh, she runs a quarterly, uh, state of partnerships report to keep her executives and managers informed. Justin Zimmerman: And so again, right, like if you want your value to be visible, we all know how important that is. [00:29:00] Instead of creating the report by hand, manually documentation, as, uh, Alan, you were saying, that's the old world. Well, let's jump right into a tactical, practical implementation from another AI operator. And so click on this link now. Justin Zimmerman: Come join us for this next session. Uh, thank you, Alan. You and I will follow up, have more conversations about this. I know this is obviously not the last time we'll see you here, and so thank you so much. I'm gonna shut this session down. Alan, double, triple, quadruple thanks, and I'm gonna head over to meet our next guest to talk about, uh, title, Report Up: How to Create Your Quarterly State of Partnership Program with Claude. Justin Zimmerman: So a nice transition. Let's head over there. Thank you, everybody, and see you soon.