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 7 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
Copplestone: Supabase compensates sales reps strictly on incremental usage uplift
“Yeah, on the incremental uplift only, which I think is the big difference from what was traditionally done. You know, on a PLG motion, you could easily say, ah, get a salesperson and so on, like, reach out to anyone and then you pay them on, on the revenue gen…”
Copplestone: Supabase team was engineered specifically to be YC-friendly
“I thought at the time, again, to de-risk things, I thought, I'm going to build a, the most Y Combinator friendly team and apply for YC and that will help from a DevTool point of view. I think that's the pitch that actually convinced him he really wanted to go …”
Copplestone: Supabase resisted pressure to rush upmarket, focusing on community and PLG
“We also leaned very hard into our community and the Pyeongchee motion. So that was good. Not trying to split our focus between Let's go up market really fast. We've just kept our finger on the pulse of the community and the PLG motion, even though we get a lot…”
Copplestone: Supabase launches unproven products with zero dedicated engineers
“So we're launching a product at the moment, and there's just no engineers on it. It's just a product person engineering it. And people say, oh, should we staff this up? And I said, well, absolutely not. They don't have an idea baked yet. And so it needs to be …”
Copplestone: Supabase only hired for 'hair on fire' needs until 150 employees
“We had this idea that we'd only hire when we had a hair on fire problem for the first probably four or five years, and so we got to maybe 200 people with that mentality, or a 150 people with that mentality, and then we quickly had to change. Like halfway throu…”
Copplestone: Supabase rejects bespoke enterprise feature requests
“Now, if an enterprise comes in and they say something that is also going to benefit maybe a thousand customers, then we'll add it. But if they say something that's bespoke to them, Then, of course, we'll just end up saying no because we really want to make sur…”
Copplestone: Supabase ingests all communications and meetings into searchable AI warehouses
“Our attrition is extremely low, but the leaning into the async culture has helped because everything's written, everything's recorded, everything's captured in Slack or Notion, or one of our sales meetings is ingested into our warehouses, and this kind of solv…”