High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / belief

Published · transcript-backed

Flo Crivello: belief

14 Aug 2026 The Cognitive Revolution Lindy Teammate: Flo Crivello on Multiplayer Agents, Memory & Why He'd Ban the Chinese Models He Uses

“You know, Luke, I think that's one reason why PLG, eventually, you tap out of it as you go up market.”

— Flo Crivello

Source trail

Everything needed to verify it.

Speaker
Flo Crivello
Attribution
Verified speaker
Claim type
belief
Recorded
14 Aug 2026
Publisher
The Cognitive Revolution

Transcript context

…In in my case, I am the admin of at least the Slack accounts that matter to me the most, but there are, like, workspaces that I'm in where I'm not the admin, and so I can't grant this kind of access. From a business standpoint, does that mean that you have to have admin buy in from the beginning? Is there that seems like it makes it hard to do product led growth land and expand type stuff. That's that's a good point. You know, Luke, I think that's one reason why PLG, eventually, you tap out of it as you go up market. Like like, yes, you you have to be an admin. You have to have permissions to install applications on your Slack workspace. So it tends to be fine for teams of up to, like, 50 to a 100. Like, after a 100, it's pretty rare to to to to to for everyone to have this kind of access, but many teams up to a 100, like, pretty much anyone can just Slack, like, install, like, an app. And, yeah, I mean, if you if you go up pocket and and you're, like, part of a bigger organization, then we we have some users who are, like, just, like, championing us internally, and they're basically begging the IT to let us in. And then they're, like, making making these meetings happen. And and, you know, IT is is is rightfully cautious. But look. You know, we're, like, SOC two compliant. We're HIPAA compliant. We're GDPR compliant. We we know we've got our ducks in a row, and we're we're quite used to navigating the internal review processes, which can be burdensome. And and and so, you know, he's not in the business of being a pain in the butt of anyone, and and they are actually themselves very eager. Very often, IT was given an an an addict like, hey, guys. We need to we need to actually become an AI native company. So they're actually seeking this kind of solution. But, yeah, I mean, you need you need admin access for sure. Okay. So let's go back to the data structure for a second. Let me give you my data structure, and you can tell me what you think I might be leaving on the table with my homespun version compared to your professional version. And then it's one of my favorite habits these days. I'll take the transcript and give it to to Claude, we'll see if we can close the gap a little bit. So my version is simply take all of the content that, you know, all the sort of digital exhaust that I've created over the years, which is email and DMs and Slack and Google Docs and whatever. Right? Put with Slack being the most painful one, make all the API calls to export all that stuff into a SQL database. I have everything there mapped onto a threads and messages structure. And sometimes that took a little bit of squinting, but it basically seems to mostly work. And that's like the raw ground truth. And I do agree. For me, it's I've found that it is quite important for the model to be able to get to raw ground truth. Then I've just done and this only goes back five years, but that's usually plenty. It's not too often that something happened more than five years ago. It was, like, operationally relevant today. I just do a month by month export. I found that for me, personally, it was, like, a couple 100,000 tokens per month that I'll then compress into a monthly summary, which is, like, 1010% at the length. Right? So whatever, two to 300,000 of raw monthly content goes to 20 to 30. Then I'll do that at the yearly level as well. So again, you've got another 2 to 300 that goes down to a 20 to 30. And then on top of all that stuff, then I just have the model go make a wiki. And one of the key things that I found along the way in terms of how to get to ground truth, of course, the model can always just send a SQL query, but what should it be querying is is not always obvious to it. So what I tried to do in my summaries is have the summarizer capture distinctive short sequences of words that would be like needle in a haystack. Fine. So it'd be like, here's what happened, blah blah blah. And then a quick little footnote at the end of what the source was, DM from whoever, and these four words will take you exact to that and probably only that in, like, all of my personal history. It's works pretty well for me. I'm usually pretty happy with it, and I do to the right ground truth more often than not. It is only one person. Multiplayer is gonna be as I start to onboard my wife, and then that'll complicate things at least a bit. What do you think I might be leaving on the table, especially as you think about multiplayer that demands an even more sophisticated approach?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.

Search evidence