Running a quantum company on two-week development cycles
From AI × Quantum: YC’s Bet to Turn 27 Years of Work into 2 Minutes on Deeptech Decoded, with Brandon Severin.
Transcript
Hmm.
the ways that you guys make decisions, the ways you set those goals, and at the same time, how do you turn things around? Perhaps you can also give us a story around, actually decision making around this always keeps up a little bit of safety nets. I hope that it makes sense.
Mm-hmm. Yeah, no, does. In fact, actually, these are the things that interested me most before doing a startup. ⁓ Like, almost the internal operations. What does it actually look like? You know, and how do you move? What does it mean to move quickly or move fast? So I think this is where we're quite unique compared to any other quantum company out there is we basically we run it.
Mm.
as close to a SaaS startup as possible. So we literally do two week development cycles. And this is something we learned before getting into YC just by like, hungrily reading as much information put out there by founders such as Michael Seibel, Tom Bonfield, Paul Grahame, you name it. So basically YC partners. And I think it was Michael Seibel, has a blog about development cycles and how they did it at Twitch or which was previously known as JustinTV. And so we basically follow that rubric and it's a rubric we had at Feynman as well. So we kind of did that was like our training wheels in a sense. And so the two-week development cycle basically means that
Mm.
We have one meeting every two weeks. It's the only team meeting we have. There's one every two weeks.
You
