The Ledger
Every statement that passed quotation and attribution checks. Mix any filter with any other: certainty 1/5, debate potential 5/5, or both at once.
why aren't all 16 resolved? a statement only gets an assessment when the public record can support or contradict it. opinions and what-ifs never can, and 0 checkable ones are still open, waiting for their date. predictions held up or didn't; assertions are supported or contradicted. on every card: ▮▮▮▮▮ certainty · ▮▮▮▮▮ debate potential. speakers are clickable
Bialecki: Klaviyo mandated all employees reach Level 3 agent proficiency by June
“We saw everybody's like, look, by the end of June, you need to be an L three, which is if you're not constantly running either end sessions or a team of agents, right? You're just not, you're not going to be skilled to survive in this next era.”
Bialecki: Klaviyo priced 50% to 100% above competitors to signal premium value
“We kind of looked at the pricing models of everybody else was out there and said, Hey, we're just going to charge, you know, 50% more, a hundred percent more. And we just made that our model.”
Bialecki: Everyone at Klaviyo codes, from the CEO down to interns
“One of the things that we have at Klaviyo is everybody, you know, we have a lot of engineers, but everybody codes. From myself all the way down to some of our like co-ops and interns for the summers.”
Bialecki: Klaviyo uses internal coaching agents to vet AI marketing proposals
“Every time it has a proposal, like, Hey, we think you should market to these customers in this way. You should send them this email. It will go check its work kind of against its coach that will say, Hey, how good will this, how good do you think this will act…”
Bialecki: Klaviyo built an agent to pre-screen ideas using past design critiques
“I took all the crits, all the feedback that we've given over the last couple of years, right? These like Zoom meetings or raw notes, we just dumped it in a database, right? Gave it to an agent and said, look, from here on out, before we even get to those revie…”
Bialecki: Klaviyo built an engineering team for headless AI agent onboarding
“Are you one last thing we've done for infrastructure is we've also gone down this path of how do we let somebody sign up for our software with their identity, right? Email, phone number, whatever it is entirely and use our product without ever touching it. So …”
Bialecki: Klaviyo bet it could add marketing faster than martech could build databases
“We said, Hey, we think we can add, you know, messaging and some of the marketing primitives on top of our database faster than all of the existing, say marketing tech companies that just did, you know marketing stuff fast. And they could figure out how to buil…”
Bialecki: Klaviyo buried open and click rates to prioritize direct revenue metrics
“We actually, in our product, we just deleted or kind of hid and de-emphasized all of the classic kind of, you know, metrics, things like open rates, click rates, all that stuff. We just said, Hey, you can find it, but it's a couple of pages deep. Instead, we j…”
Bialecki: Klaviyo keeps internal team sizes between two and five people
“I mean, we try to keep teams like, you know, two, three, four, five people. And you, you're like, you're just this David versus Goliath. Like you're trying to solve this massive problem that there's whole companies out there that are trying to solve.”
Bialecki: Klaviyo is opening its full customer database APIs to developers
“Our big goals for this year is how do we make sure we've kind of opened up? I don't think anybody's ever done this. Give you all of the APIs into our customer database. So it's a little bit like a SQL database, but just really designed for kind of customer, yo…”
Bialecki: Klaviyo sales reps build customer workflows before asking for payment
“So our sales team will, I, this is not normal, but like they'll actually get into the product, help people set up a few, you know, whether it's a few emails, a few automated workflows, get them to show them some ROI all before we ever asked them to, you know, …”
Bialecki: Klaviyo built strict agent sandboxes to protect internal infrastructure
“One of the things we've done inside of Klaviyo is we've architect our agent environment so that it has very tight access to various like tools and controls in terms of what it's allowed to build on our infrastructure and then good sandboxing staging environmen…”
Bialecki: Klaviyo built native revenue attribution in its second year
“Probably I think it was year number two for us. We invested a bunch in how do we make sure we can handle attribution internally? So you didn't have to use Google analytics or something or pay for some other software to do it.”
Bialecki: Klaviyo internally targets at least 10x to 20x customer ROI
“Our pricing model is still today is based on effectively the number of customers you have and how frequently and potentially how frequently you message them. But what we wanted to measure internally is we looked for every single, you know, business we worked w…”
Bialecki: Klaviyo has historically underperformed in supporting ecosystem developers
“One of the things I think, honestly, we've not done a great job is being there for those, you know, those
Companies really, those entrepreneurs, as they're growing up and building, whether it's specific to Klaviyo or just like adjacent to us. So we're really p…”