May 4, 2026

# Transcript: 2026-05-04

> 21 time blocks from 8:00 AM to 12:55 PM

---

### Discussing someone's unexpected passing
**8:00 AM - 8:35 AM PDT** | *casual*

**Microphone:**
Thank you. It's just... we saw it. You know, he had everything you could imagine in life. I mean, just, you know, four incredible kids and, you know, financially he was obviously doing great. I mean, you know, he just... I don't know. I don't think there was anything going on with his marriage. There had to be some issues. It could have been something with the medications that exacerbated things, but that's a big move. It's just, I don't know. I just saw him at the national championship in January. No words. That is awful. Yeah, yeah. So it's just, you know, and obviously he was a supporter of all of us. So you know, he was connected to you guys indirectly, though that doesn't matter at this point.

There's a service or something coming up. You know, we don't have anything yet. I went online and typed in Ross Singletary Jacksonville, but it's not like an official obituary. I think there are a lot of things missing from it. So I've been in touch with his wife a little bit. I wouldn't be surprised if they do a family service first for close family, maybe three weeks, just to let things settle. I'm not sure when that's going to happen, but we'll see.

Now we've got a bright Monday to focus on. Friday was a lot of QA. Got, in no particular order, the requester dashboard filters feature for REL AI to programmatically invoke the object data sync pipeline. Testing went pretty swimmingly, no issues arose. It was as clean a QA run as I could have asked for. The re-indexing jobs that we had done review on should be able to get out today. I'm kind of torn about the dashboard—whether we keep it as is or have to go to relationship AI to see this new page. We haven't had the switch today, so we're kind of just figuring out this new user experience and what the most important things are for them to do.

Anyway, Todd, take notes. I've spent some time putting together configuration files. I should be able to basically set up ad hoc polls using the API service to Salesforce, or set up cron jobs the way we usually do with a server for deployment to Salesforce. It's not quite normal because, you know, it's Salesforce, but I think with my script work I'm getting somewhere. I'm just probably going to need a little help with the specifics.

We're developing what we're going to call it. We need to talk about that for a few minutes. We're extracting components out of the page into a separate page so we can offer clean help or offer help with a question about pending relationship leave or some other situation or direction, just making sure we have all of the possible component types and variants available so we can actually build them. That's where I'll be working today with David.

So there are the auditors who are never positive and shouldn't be important. And then there's the person who's kind of like the auditor gopher—you go and hunt down all the requests for evidence and stuff like that for SOC 2. We ran into trouble last week, and this is not the first time. I need to get some of that tweaked and work through it. But again, I think this approach is really going to make a lot of sense.

Separately, we're working on getting something done this week. This is going to be my priority to get with Wendy, his boss, just figuring out the timing of kickoff or whatever. So hopefully getting that done soon. Nerdy Oil looks promising because Brian Law, who's the decision maker, shot back to me on Friday saying they're ready to roll. I shared that with you guys. He needed Darren's help to finalize things, which is different from my usual approach where I do all the review. Hopefully we get that done. He told me he would sign it, but he needs their ops team to confirm timing on that.

Then there's an email from their person Prashant. Those are four different companies. They all want to move through the system with these connectors. Legally, it's converted. I told James to invoice them. We texted late last week about Anita. We might have something with them again. I even used the relationship map walkthrough that Michael put on the public website to send to them either Friday or over the weekend. Officially it's over on Friday unless something crazy happens.

We had the call with the swarm guys, by the way—I didn't mention that. Obviously you can contribute your thoughts too, but I think it was just to, you know, more than four figures with them accessing their data through. They think it would be great, and the implementation time is like zero, right? So that's very different than us. They have nothing in Salesforce, and I think it's really interesting to them. They're super interested in the concierge, of course. So we'll see where it goes.

I'm really energized by the work that Michael's put into this relationship map. We're just beginning to zero in on what we can do with that. It makes it a lot easier for our users to use our product, and it looks awesome. So to me, I'd rather revive some deals and get our customers using that and the handful of deals we've got in front of us right now. Let's get these over the goal line.

So, any other thing you wanted to build on that, Michael, or show on the relationship map? But anyway, just kudos to Michael on the work you're doing on that.

I'll clean up this transcription by merging fragments, fixing speech-to-text errors, removing duplicates, and adding paragraph breaks for clarity.

---

And again, I think the devil's in the details behind how the agent's going to work and what it's going to be able to deliver. As of last evening, there's been a lot with this index protected URL. One of the things David was asking for, and one of the things that we often fail to design for, is what does the page look like when nothing has happened, or what does the page look like when bad things have happened? You have extended networks showing up, then the connector sends out strength requests, relationship leads are first generated, and connectors are finally getting involved. It's definitely a happy path—definitely what we want all of our clients to be like.

As you can see, you start in a fresh state, and then you start to move forward. At that point, the broader deal team starts to form because we have all the right information on the people we need. Let me pop over here. The point of showing that was to demonstrate all the potential. This is a page I made for David that's more client-friendly, showing all of the capabilities we're hopefully aiming to build for the underlying work—like drafting connector asks and using data from other things, such as shared cohort connectors. For example, were these two within branch of the military or something like that? Share investor paths, industry veterans—that's the thing the system can do. Even if we start with just one and add one per week, the spark engine pulls all the different cards out so we can design for all the different cases.

The idea is that within the next day, Cam and I will be showing them a static version of this page with an iframe and an actual lighting component, so it's faster. I'll keep sharing, and Michael, we'll get the tweaks of the user experience and the little things we're working on. We talked about a V1, right? That we'll figure out—a beta version, I think those integrated. Relationships exist, or relationship-releasing exists, excuse me. And so that's some straightforward things.

The notifications and interactions are going to take a little while because we have to start realigning them to this type. Cam is going to work on the front-end interface of this and the builder of that. I do think by the end of next week, probably, we can get something up. I don't know what it means for Salesforce and how we integrate that. I'm sure we have that as an example too. But I do think within the next two weeks we can have a pretty basic version of this page live.

We wanted to really get iconic feedback, even from guys who should be programming. There is ability to see those in leads or tasks in Salesforce. I think that's huge because then you see the relationship map page and understand who that connector is or what the first order of opportunity in Salesforce might be. Yeah, I think my plan will be before the end of the day—I'll have a draft of, I think, talking with Todd first. That would show the office trauma relationship leads interface better than I think our current one entails for us.

What I'm using now is that public. I can't promise anything on his side because Salesforce is more of a bugger, man. Yeah, and then Michael, on what I've been talking about—we've settled on changing that one from POST to person. I think that's really good. Any feedback or questions, Cam or Todd? It seems pretty intuitive to me. I think some of the features would be nice, if—and I love that part. I think it makes the prototypes really immersive. But I also worry that some of the features might be live server-side event stuff. I can imagine in some cases that's overkill.

All that remains missing is purely because I don't think people are going to have the page open. And so that's why I did this toast so that we queue up those notifications. Come back if you stay on the page, or you come back five minutes later, or a week later—these are all the things we've done. That might be a little overwhelming. Now I have this cool queue notifications idea. You know, we could restrict it to high-priority accounts, but some of these may not be high priority until the data has been retrieved by the agent. I'm thinking through how we build this into our current pricing and how that all works. I'm going to spend some time on that today as well and totally support it.

That's why I'm also approaching this as pulling out all the components. I don't think of it as server-side events. I do that stuff, but it'll look trivial at first, then quickly scale. I just haven't gone through that exercise yet either. Definitely something we can try to approximate as we get further—understanding where people are and how they're getting value. That'll drive how we establish value and pricing. Maybe Michael, it's just like: hey, you can run this agent for your top 50 accounts, but you don't get any more. We give them X number of accounts that we can do this for. I don't know.

Yeah, real quick on releases. I think the biggest is just going to be getting the filters. The PR—it's really the only PR that's open that's actionable at this moment. But the PR that is getting the...

I'm reading through this raw transcript to clean it up. The audio quality seems quite poor with significant gaps and fragmented speech. Let me apply the transcription editing rules:

yourself on this stuff, especially if we have customers that we want to retain and grow and add more value to. We start there and search for you with Ralei and you get out today.

Ah, and then the other hack. Otherwise, there's nothing. I've seen this for this moment. I've seen this for this week. I do have, I will have a leader in power. One last sidekick thing—it seems that our indexing runs once a day and takes three of these runs. So that's not right now.

Your stuff starts. Sounds good. Michael, you just sent me the code of conduct thing. Yes. Want them. Bye. That think it zhuzhed up a little years ago. We just need one for a second. All right. Bye.

**Note:** This transcript has significant audio quality issues with fragmented speech, unclear references ("Ralei," "zhuzhed"), and incomplete thoughts. Some passages remain unclear even after cleaning (e.g., "One last sidekick thing," "Your stuff starts"). If you have access to the original audio, reviewing those sections would improve accuracy.

**System Audio:**
It's just it. You know, he had everything you just—I don't know if there was some issue there. Yeah, is there a service or something coming up? You know, we don't have anything yet. I mean, if you went on like a good chunk and, you know, not that that matters at all at this point, but he was connected to you guys indirectly. Yeah, yeah, so it's just, you know, and obviously he was a supporter of all of us. So, you know, he funded us with a pretty significant amount. He literally jumped off an overpass into an 18-wheeler. I mean, it's just—I just saw him at the national championship in January. You know, we were together kind of quickly. Well, it's not an official obituary. In fact, the ripple effect is hundreds of people. I mean, he'll be missed, you know, big time.

Sorry, okay. Can't have money kick us off, Postman. It's like a relaunch tomorrow. So in a perfect world, I'm working from—and then, sorry to interrupt, but thinking, Michael, that we would have the requester, yeah, that's fine. By end of today, I just want to figure out how I do the new user experience with the filters, you know, alongside the prompt, because it can be a lot if I don't focus on, you know, the most important things for them to do. So, either spend almost no time on the requester dashboard as it stands today, or spend a little time there and then move to the prompt or kind of figure out the new requester dashboard that we aimed to deliver. We'll still start working on it—has the prompt at the top and we'll have the filters. So I think we want to switch this to a new page. I think they land on the requester dashboard as it stands right now, just because we haven't made changes there yet.

Yeah, as Cam stated, I spent some time putting together packages, doing a little testing, and found some issues. And then, wow, it was kind of cooking. I started on issue 274 to upload the configuration files for Salesforce, which is not complete. And then I think today and like this week, I need to look into the next step of setting up ad hoc workflows. And also, I know that there is work—I'm not sure where everything lays anymore with using the API service to Salesforce or the cron jobs using how we do everything else with cron within the app. That needs to be done, but I could use a little help with it. But yeah, I'll just continue to work in the Salesforce world. That's it for me.

Yeah, we'll get the next order of operations organized. Friday I got muted and then I spent a good chunk of the day iterating on developing and did that, plus spent a good time over the weekend running through about—so accounting for every possible offer for help—it's a clean offer for help, or it's an offer for help with a question, or it's pending. I think we're in a really good place. I also started—and we'll talk about that for a few minutes just at the end to catch everybody up. I also started working on kind of pulling together an introduction, and that's what I'm working on. Yeah, and I'm just waiting to hear back.

So there's the auditors who I've never talked to. It's not too big and important. There's the account manager, and then there's this first-time gopher-type person. She was asking for Cameron Khan's off-boarding documentation from 2023. Yeah, you're done. I'll talk to her on Monday when she's—because this is not at all useful, right. But I will hopefully hear more today.

Cool. Yeah, really excited to get some other feedback. Michael and I are going to sort of tweak that and work through it. But again, this is, I think, an approach. This relationship map—I've spent part of this morning just trying to socialize it with some people already. Got some positive feedback from Kathleen, and I think we'll start doing things obviously with customers' sign-offs. They needed a letter from our bank, which I didn't have, and the bank then we need a nice firm $25,000, $30,000 deal, which is good. And then, uh, priority-like, not do anymore. And typically it's me doing all that review, but in this case I needed Darren's help. So, done. Woods got back. I shared that with you guys. But he needed to finalize it. Nerdy looks promising because Brian Law, who's the decision maker, thinks that middle end of May is realistic. So that's positive.

Fastly is frustrating. I'm stuck with their ops team and then a handful of other kind of interesting ones. Josh Damon from Medicine Dearborn got me introduced to this company, NextGen, for the next two weeks. It's going to be important that we get Fortune 500 big names like Postman doing that. And so I think once we can—either artificially or start testing some things right, like with their target accounts. They've got so many in there that we ought to be able to find some nuggets showing tangible results. There is going to be important.

Clockwork was supposed to convert yesterday. So legally, it's converted. And I told James to invoice them. Joe Tarantino and I—they're really excited. They're leaning in. Who else is this week? As I mentioned on the customer set and I shared that with you guys, you know, he told me he would sign it, but he needs like the blessing of this gal who's—it sounds like she's spinning a few plates, so we may be like third on her list right now. The check just did not seem smart, and so I think there was a gap. Means that they hopefully won't want more time. And I'm not feeling good about Grafana. I think I told you guys like I am, and I even used this relationship map as a last ditch effort. But that one's official. I'm not sure, you know, heads down. Um, you can obviously contribute your thoughts too. I think it was just a sort of high-level product conversation.

I'll clean up this raw transcript for you. Let me process it to fix speech-to-text errors, merge fragments, remove duplicates, and organize it into coherent paragraphs.

---

We walked through our core capabilities and talked a little bit about what we're building. They did the same. Very different, very complementary. They've got over 100 customers spending in the four figures with them, accessing their data through a PLG model and through these APIs. So they just have this crazy database of 1.5 terabytes of data that they're pulling from. But Michael and I both thought it's a lot of data, which is very different than us. They have nothing in Salesforce, and I'm just beginning to zero in on what we can do with that, which I think just makes it a lot easier for our users. I'm really energized by the work that Michael's put into this relationship map, and I think what could come from this is really clean. Especially given the context, anyway, kudos to Michael on the work you're doing on that. I think the devil's in the details behind what's actionable and what agents are going to work.

So anything you want to say about where we currently are as of last season? Every time we commit to this prototype sprint, there's one of our two million taxes. This is kind of where we ended up as of last evening. There's still a lot to do, but one of the things David was asking for that we often fail to design for is like a little control panel with a play button. I'll press run through some of the ideas for this first week. This is a very productive first week with the perfect happy path. It's definitely what we want all of our clients to be. You start, go through immediately, we start seeing the Concierge send out strength requests, relationship leads are first generated, and connectors are finally getting involved and making offers for help. At that point, the broader deal team starts to form because we have all the information. You can see there's a lot of jobs running over here. Within that first week, hopefully somebody has made potential introductions. This page shows all the potential. It's more client-friendly, just showing all the capabilities we're aiming to build. Straight out of data, their endpoints for researching stories, the secret sauce that we might use with other things. The founders were all within the same branch of the military. Like the thing we were talking about with Stephanie Cohen being in finance, trying to find all these different agent executions we can do. Even if we start with just one and add one per week, it quickly adds up to a really good smart event.

What I'm also doing is pulling all the different cards. The idea is that within the next day, Cam and I can work on the front end. I'll also be putting together for Todd a version of this page—a lot more static version that we can drop onto an actual Lighting component. So it's faster and more consistent with Salesforce. I'll keep sharing, Michael. Assuming we get the tweaks of the user experience, we'll figure out what's already built or easy to do. We can capture relationships, verify relationships, notifications for offers for help, and bulletin board posts. If you had your druthers and things went well, 2027 is definitely our year for it. We can get this page built pretty quickly with what we have. These orchestrations exist and they're basic, but not exactly what we're talking about. So we can get those integrated relationships and so forth. But I do think we can probably get a first V1 by the end of next week. Cam's going to do four things, and he's going to do seven. So those first chunk of agent cards—we want to make sure that can have a pretty big impact. Really network program there. Doug Pepper introduced me to him, and he even said they're building something like that. So the assumption is if we do a good job with the agent or persuade these connectors to do that more proactively, and if you guys read the feedback, even people in Salesforce, I think that's huge. Because then that may drive you in here to get more details. You just have a notification in Salesforce, but you want to get more details about who that connector is. My plan will be before the end of the day. We have so many things to take on, but I do think that would integrate the main column first, which would show offers to help in an interface better than our current one in Salesforce. We've got to place that whole component. I don't want to chat with that before. I don't promise anything on his side because Salesforce is more of a hassle about it.

Michael's going through some of the details. What I'm noticing now is the link that was given, and it's almost got left. So changing that one from Postman to Wells Fargo because it forces that person to sort of do that walkthrough. The plan for today is some Slack stuff done related to this, just notifications and a Salesforce draft.

Here's the cleaned transcript:

---

Public, a place for you to. Cool. Yeah. Uh, Todd on all this would be server-side events purely because just host so that we queue up those notifications so that when they a day or two later. It's not entirely user-friendly, but if you come back a week later, these are all page.

Think about and work through how we commercialize this, because we can't do this for 7,000 companies. We wouldn't want to. And you know, you could restrict it to high priority accounts, but some of these may not be high priority until... I think thinking through kind of like how we build this into our current pricing and how that all works, I'm going to spend... there's okay if we're gonna do this for 500 that starts to add up quickly. Totally. And again, where people that'll drive how we've and what we charge for and what we don't. So you don't want to be able to do that. Grow as long as it doesn't any more than 50. If you're an existing customer or something like cool. Yeah.

Real quick, this week releases, I think the biggest is just going to be filters. Uh, filters is kind of suggested inputs. And yeah, we should just make sure once that's out, just make sure we're getting aware of that today. And then the only other one will be the Salesforce package. Otherwise, there's nothing that are playing releases for this week.

I do have, I will have later in an hour to do a QA. Indexing all people's runs once a day and takes three days to run. So that's not going to work out well. So I have a really effective. But otherwise, um... Right now, it's a kind of quiet deploy week. We have a lot of new stuff starting up.

Thanks, fellas. Look forward to being in touch. All right. Thank you, everybody. Oh, and Michael, you Estrategate that think I zhuzhed up a little a year, two years ago. Yeah, of course.

### Playful confrontational banter
**10:16 AM - 10:20 AM PDT** | *casual*

**Microphone:**
I'm going to go. Whoa, whoa, whoa, whoa, whoa, whoa, whoa, whoa, whoa, whoa. Relax. Get back here, get back here. Gotta whoop your ass, Paul. I smack you upside the head. What is it doing on there? What is it, pal? Oh! Huh? Oh yeah.

### Apologetic energy comment
**11:00 AM - 11:01 AM PDT** | *casual*

**Microphone:**
I'm taking the energy, guys. I'm sorry.

### Dog training or pet interaction
**11:12 AM - 11:18 AM PDT** | *personal*

**Microphone:**
You're too strong. Thank you.

I'm going to go to the next one. Poe, what are you doing? Yeah, let's go. Good girl.

Simple then I'd really like for you to do and how. Hey Popo. You want to go over there. Nice work, Papo.

### Excited casual catch-up with friend
**11:25 AM - 11:48 AM PDT** | *casual*

**Microphone:**
How are you doing? Like, yeah, dude, yeah, man. Come on, you can't fucking hide your excitement from me. Sorry bro, it's a word shirt bro. I lord around basically, I mean, I'm just saying, dude, like, I have so much fun at work than you now, dude. Bye. Yeah, that's uh... I'm mad, seriously dude. Trying, it's gonna be hard, man. I'm just fucking running around doing Y-chart shit. Fucking... Aw, come on, man. If you were going out there for eight days and it wasn't a work trip, you would have fucking packed it. Get to that. Hi. Yeah, that's all Emily does, yeah. It's the reason he hasn't had us up in so long. Yeah, I was going to say, it's been awfully quiet. What money say? And like, yeah, we could have saved our asses so much time if we just did this off-roof. I'm not. Exactly, exactly. We'll see you guys. Peace out. So we're fucking smart, dude, and uh, do you think these webinar guys? Yes. Yeah, it's really confusing to me that they can use ChatGPT to figure out how the fuck to use Cloudflare instead you fired and the car jams, so like, you know, we were happy that we didn't join the part, so percent too, no? Yeah, the fire right, the back. But they also prefer the posers then, right? So I mean, they earned their job. I'm glad it's not us.

Also providing him then with booking four or five closers on that call. They just have a system in place. That's how you want to do it when you're doing these sort of deployments. Like having it all bespoke, done, custom, every single time, it's just mix recipes there might be to make some good. I mean, numbers game, it's just gonna become unmanageable without bigger teams. Do some exploration stuff, some legion tooling. Going to get my brother there's selling. Um... Yeah. You can take it to me. Nice, nice. No. Yeah, nah, fuck that dude. Who wants to train these people unless you have fucking equity in their future? We're gonna have to serve you. I know. Brick by brick. A half. It's all. I'm not sure if someone's trying get to you, pop, twice. Yeah, I know. I just wish I could play. 160 cent flip. Let's talk about bot ripping trades for us on Ethereum that could not train these people fast enough to fucking replace them. Okay. I need one to go there expected that. First. Yeah, all we got is will be interesting though. I'm gonna jam-pack two weeks here. I'm gonna start putting process is continuously improved, brother. I don't... But not 4x. Maybe 3x. Possibly 2x. Yeah, well, if we're using that timeline, then yes, 4x faster. Thank you.

I don't know. It sucked. But it's okay. We're not. It's, I kinda wanna plan a Chicago trip. Do a slow bear? I think shit. I'm sorry. Not gonna be motivated to come out there and grind if I that. Oh, yeah, no, I'm not doing the dark movie. That thinking like Memorial Day or something. Uh, except my fucking brother's graduation. And that's also an integration, so that's fine. Yeah, I know, that makes them feel special. And be like, hey just give us another month, one more month, brother. I wanna go. Wonder. What are you studying? I cannot imagine. I mean, I kind of wish I understood there. Their financial situation a little better? Is he just like, are you using Abdullah's credit cards? Ah, yeah, yeah, yeah. So they just got like a couple hundred tae in the checking account and Abdul just gets to rip duel of his demochrome. That's crazy dude. I would never in a million years if my brothers fucking debit card would buy. I remember he was talking about like a duel one month or a duel one month fucking takes the account from 375 to 300. 100th just like buying fucking leaves. 70K for daily, what the fuck? Never, never. My brothers will need to make that back 10 fold too. Hey, it could be different though if they were responsible for a survey, right? Like, I would need to be able to see. I don't think Abdul, obviously he knows that. Abdul does his job and getting a close and steal, kind of, yeah. Like he knows that there's some... there's proof in the pudding. What exactly do they have no way to attribute anything to anyone? Like it's really like in my eyes the only person in here how much marketing and shit. Mm-hm. From a little, yeah. That's tough, that's tough. That's when they pay us the big bucks, right? Little bro coming through, man. I'm trying to put his ass on Facebook, me too. I'm trying to make him a fucking keyword, bro. Help him get this job on LinkedIn. And uh. Yeah. I told him last week, bro. Remember that job coach that Jack spoke to? Yeah. I told him to talk to a job coach and do a free fucking training with him because he has that. Yep, yep. When the fuck would he do that, dude? Bye. Eight hours gentleman who signed up with there without him, but he's helped him. Digital LinkedIn. So it's making 80 to 100k, but it pays for itself. I think lot easier, but it's only paying 200 bucks a month. Two years is from there. Oh it's gotta be. You. I know, and that's all again, we're fucked by the day. Should have been on our issues with us, but he graduated late. Two years later. That's what I'm saying, 2021 bro, was the fucking, you had to graduate and get a job, and John Martin was hot, they wanted people, and AI wasn't crazy. Mm-hmm. Yeah, no, it was sweet pickings for us. I got recruited by a white shirt. I mean, damn, I was a fucking senior in class. I got called. Thank you. I'm the worst person to give advice about fighting a Johnny, I've never done it. Yeah. Be so bad? Yeah, that's funny. That's like portfolio store. That job to this day. Really? Mm-hmm. It's wild. I don't know. And she just bought the socks I told her to buy. Ha ha ha ha. I'm sorry. Gonna create a fucking... game plan a little bit more, right? In. Working cohesively across multiple fronts. Think we gotta keep pushing on the AI stuff because are probably better suited for this shit. All right, what's that? We'll get there. Alright, that's our plan, boss. Alright, there's some...

### Brief project step mention
**12:15 PM - 12:17 PM PDT** | *work*

**Microphone:**
costume. Right. So this is the first step.

### Discussing Google Slides workflow
**12:30 PM - 12:42 PM PDT** | *work*

**Microphone:**
Well, it's good. What's up? I was gonna ask you how to do this. Are you seriously having trouble?

I just want to make sure I understand a couple of things that anyone can use it. For example, the first thing I got stuck trying to do this morning was making sure that it outputted a Google slide deck. I was like trying to go into the outputs thing and I couldn't figure it out.

The one I sent you to wait—did you message me telling you that? Yes, I did. I don't understand. I said it's removed now in response to what you said. Oh, it should be removed now. Okay, sorry. It's okay. I saw the pergola thing.

I just want to ask—can you put different sources into like five slides? All right. So it's kind of a one-off. It's not a normal thing. Yes, that's my first question. I just want to make sure I'm not holding it wrong. So that's a workflow, even though it's like an ad hoc thing.

What you can help me with today is figuring out if the default workflow that I've set is a good primary driver for people to use, and with as little confusion as I can. I don't want to create a new workflow. Well, you can do that. And then there's Workflows, and then there's Workflow Console again down here. Yes. Don't worry. But I'm just trying to make sure I don't hold it wrong.

I would go and type out a prompt with the information about the deck that I want to create, the slides. So here I have that, right? Through 100 real examples. I sit here and make sure I just do what's fine. Now, so I don't need to put turns in here anymore, right? Mm-hmm. Okay, so that's fine. You can run from inside Claude Code. I don't do that. You know that? No. I gotta go figure out what the difference is from inspiration versus not, you know? Okay. I don't need that. And now down here, can you change there, right? Yeah, I mean... I might just want a good deck, come on. So okay, then where's turns? I swear there's a turn budget. Hmm. I guess that really tends to be good. I don't know.

Balanced orchestration. I'm not going to run published, right? Yeah, I just run this draft for now. But... So there's jobs over here. Yep. Okay. That looks good, right? It's for wallpaper? Walmart. I'm not sure. Thank you. I don't know if that's good. I figured you are. All right. You basically use the user interface for you and configure things. I think for non-technical users it might make sense. Hey, Popo. Oh, my socks bubble. I don't know.

### Talking to pet or child
**12:54 PM - 12:55 PM PDT** | *personal*

**Microphone:**
What are you doing? Stop looking so sad. I'm going to use a saddle. I wish I was.

---

<details>
<summary>Background Noise (13 blocks)</summary>

### Brief audio fragment
**8:38 AM - 8:40 AM PDT** | *background-noise*

**Microphone:**
Thank you.

**System Audio:**
you

### Single word fragment
**9:21 AM - 9:21 AM PDT** | *background-noise*

**Microphone:**
I'm not.

### Unintelligible noise fragment
**9:26 AM - 9:27 AM PDT** | *background-noise*

**Microphone:**
. .

### Frustrated outburst fragment
**9:31 AM - 9:31 AM PDT** | *background-noise*

**Microphone:**
Fuck, dude. Damn it.

### Brief unclear statement
**10:31 AM - 10:32 AM PDT** | *background-noise*

**Microphone:**
I'm going to go ahead and get it.

### Single word fragment
**10:38 AM - 10:38 AM PDT** | *background-noise*

**Microphone:**
so

### Unintelligible noise fragment
**10:42 AM - 10:42 AM PDT** | *background-noise*

**Microphone:**
.

### Single word fragment
**10:46 AM - 10:46 AM PDT** | *background-noise*

**Microphone:**
so

### LLM transcript processing artifact
**10:50 AM - 10:54 AM PDT** | *background-noise*

**Microphone:**
I'm having difficulty understanding the raw transcript you've provided. The text appears heavily corrupted or unclear at the speech-to-text level, making it difficult to distinguish individual words or meaning.

Could you clarify or provide:
- The original audio file (so I can work from that directly)
- Context about what's being discussed
- Any specific words you know are being mangled

If you have access to the audio, that would be most helpful. Otherwise, if you can tell me what this recording is about, I can make better educated guesses about the corrupted sections.

### LLM transcript cleaning artifact
**12:03 PM - 12:03 PM PDT** | *background-noise*

**Microphone:**
I appreciate the instruction, but the raw transcript you've provided only contains "Thank you. Thank you." — which is already clean and doesn't require any edits.

If you have a longer transcript you'd like me to edit, please paste it and I'll apply the cleaning rules you've outlined.

### Unintelligible noise fragment
**12:08 PM - 12:09 PM PDT** | *background-noise*

**Microphone:**
. so

### Music or media playing nearby
**12:25 PM - 12:25 PM PDT** | *background-noise*

**Microphone:**
Thanks. Music

### Dramatic media or TV fragment
**12:48 PM - 12:48 PM PDT** | *background-noise*

**Microphone:**
What is happening? Please remember. Here's a gun. Whoa, whoa, whoa, whoa, whoa.

</details>

The morning centered on a SmallWorld team standup where the team processed the shocking news of Ross Singletary's passing before pivoting to business. The primary work focus was on a new "relationship map" page that Michael has been prototyping — a client-facing interface showing agent-driven relationship intelligence, connector activity, and deal team formation. The team is targeting a V1 by end of next week, with Cam handling front-end components and Todd working on Salesforce integration. On the sales side, several deals are in motion: Clockwork has legally converted, Nerdy Oil looks promising with Brian Law targeting mid-May, and Grafana appears lost. The afternoon shifted to a casual catch-up with a friend discussing business operations, hiring challenges, and AI tooling, followed by a session helping someone navigate Google Slides workflow configuration.