I'm Steven. I built OKRs Tool because I watched OKRs quietly die at every company I worked at — including mine.

3 years of running OKRs in Basecamp.

"Wait, that's not OKR software." Yes — you're right.

Like most teams new to OKRs, our setup was fine to start. Small team, simple goals, manageable scope. But as we grew, things got messy. Updates went stale. Progress became hard to track. Alignment slipped.

Eventually we lost track entirely and found ourselves wondering one Monday morning:

What were our goals again?

We missed more goals than we hit that quarter. Not from a lack of effort — we didn't have a system designed to track OKRs. We had a tool we'd repurposed, and it had quietly stopped working months earlier.

So I built one — OKRs Tool.

Before writing a single line of code, I spent months understanding the landscape. I signed up for every OKR platform I could find. Not demos. Real accounts. I created objectives, set key results, ran weekly check-ins, and tested every corner of the UI. I wanted to know what existed, where the gaps were, and what nobody was doing well.

What I found: enterprise platforms (Lattice, Quantive, Betterworks) were optimized for HR roll-ups and quarterly governance. Lightweight tools (Tability, Weekdone, Perdoo) were either too simple to scale past a single team, or charged per user in ways that punished growth. Nobody was building for the operator running OKRs inside a 50–200 person company — the person who needs structure to make OKRs survive cycle two, but doesn't want a procurement process or a six-figure annual contract.

That's the gap. That's what OKRs Tool fills.