Why Quiz Bru Was Our First Product to Ship

Quiz Bru was the first product we ever put in front of real users. Not the biggest idea we had, not the one with the clearest revenue path, and not the one either of us was most excited about on paper. We picked it because it was simple, and simple was exactly what we needed our first product to be.

Every product we've shipped since, RunYourNumbers, KeyForge, Qrop, and Sorted Nexus, exists because of specific lessons that came directly out of building and running Quiz Bru first. This is the story of why we started there and what that choice actually bought us.

A live, multiplayer quiz tool sounds almost too modest to call a first product. That was the point. We had never taken an idea all the way from a Saturday conversation to something a stranger could open in a browser and actually use, and we didn't want to find out what was broken in that entire pipeline on a product that also had payments, compliance, or sensitive user data riding on it.

Quiz Bru let us prove the whole chain end to end on something forgiving: come up with an idea, build it, deploy it, get it in front of real players, and watch what happened. If something broke, the cost of that mistake was a quiz night going wrong, not a business's invoicing falling over or a fintech calculation coming back wrong. That gap between the size of the mistake and the size of the lesson is exactly why we started there.

The specifics mattered more than the general experience of shipping something. Quiz Bru is a real-time, multiplayer product: a host runs a live session, players join from their own phones, and every answer, score update, and leaderboard change needs to reach everyone in that session within a second or two or the whole thing feels broken. Getting that right taught us how to manage live session state properly, how to handle a player's connection dropping and reconnecting mid-quiz without losing their score, and how to keep a host's screen and a dozen players' screens showing the same state at the same moment.

It also forced a decision that shaped every product after it: no account required to join. Players open a link and they're in. That constraint existed for a practical reason, a room full of people at a pub quiz will not tolerate a signup form, but it taught us how much simpler and more reliable a product becomes when you design out the parts of the flow that don't need to exist, rather than adding them by default because that's how software usually works.

We also learned, the practical way, what it costs to host something that has to stay responsive while multiple live sessions run at once, and how differently you have to think about infrastructure for a product with bursts of concurrent, real-time load compared to a normal content page that just needs to render fast for one visitor at a time.

None of what we learned from Quiz Bru stayed with Quiz Bru. Each product that followed picked up a specific piece of it. KeyForge inherited the no-account rule directly: paste in a value, get a result, nothing to sign up for, because we'd already seen how much friction a login screen adds for a tool someone wants to use for ten seconds. RunYourNumbers inherited the same instinct for speed under load that came from keeping quiz sessions responsive, applied instead to making sure a calculator returns an answer the instant someone types a number in.

Qrop inherited something more structural: once you've built one system that has to handle many simultaneous users hitting the same feature at once, you start designing every new product's API with that same discipline from the start, which is exactly why Qrop's enterprise API was built to handle volume rather than bolted on as an afterthought once demand showed up.

Sorted Nexus is the product that came last, and that ordering wasn't an accident. Compliance requirements, invoicing logic, and cash flow tracking are the kind of complexity you don't want to be learning basic deployment and real-time reliability lessons on at the same time. We only took on that complexity once three simpler products had already proven we could ship, run, and maintain something reliably from end to end.

We've written elsewhere about how risk-averse both of us are by instinct, and how that instinct nearly kept us from starting anything at all. Picking Quiz Bru as the first product is the part of this story that reframes that same instinct as useful instead of limiting. Risk aversion doesn't have to mean waiting. It can mean sequencing: choosing the smallest real product that would still teach us something true about shipping, before spending that same learning curve on a product where the mistakes would have cost far more.

Starting simple wasn't a lack of ambition. Sorted Nexus, a full business admin platform, and Offloader, a portfolio risk metrics API for fintech platforms, are both far more ambitious products than a quiz tool. We just didn't attempt them first. We attempted the smallest thing that was still real, let it teach us what it had to teach, and let each product after it inherit those lessons instead of relearning them from scratch under higher stakes.

If you're building something on the side and trying to decide what to start with, that's the actual question worth asking. Not which idea is biggest, but which one is small enough to finish and honest enough to teach you something true about the rest of the process. For us, that answer was a quiz app. It's rarely going to be the same answer for everyone, but the reasoning behind picking it holds regardless of the category.

Quiz Bru is still live and still running quiz nights for hosts who want something they can set up the same day they need it, without wrangling slides, a separate buzzer app, or a scoring spreadsheet. It hasn't become a legacy product we quietly stopped maintaining once the more complex products arrived. It's still the same simple, reliable tool it was built to be, and it's a live example of our full products lineup rather than a case study we only talk about in the past tense.

If you want to see where the lessons from Quiz Bru ended up, our products page lists everything we've shipped since, and our services page explains how the same build-it-ourselves-first approach shapes the technical consulting we take on. Either way, the throughline is the same one that started with a quiz tool: pick something real, ship it, and let what you learn decide what comes next.