Seven months before launching his healthcare staffing platform, Marcus ran hospital workforce operations. Every quarter, he facilitated OKR planning cycles with his team — objectives, key results, grading sessions, the works. It produced real alignment in a 200-person department.
He kept doing it when he started his company. At 2 employees and $0 revenue, he ran a quarterly startup OKR planning session. The output was a beautifully structured document that said essentially nothing actionable about what they should do next week.
Why startup OKRs fail pre-product-market fit
OKRs are a coordination tool. They solve one specific problem: how do you get hundreds of people in a large organization pointing in roughly the same direction? The answer — shared objectives, measurable key results, public grading — works when you already know what success looks like, you have enough people that coordination is the bottleneck, and you're executing on a known playbook rather than discovering one.
None of these conditions exist at the 0-to-1 stage. A company of 2 people building its first product doesn't have a coordination problem. The founders are in the same room. The bottleneck isn't alignment — it's figuring out what you're actually building, for whom, and whether anyone will pay for it.
What operators actually need at the 0-to-1 stage
Operator founders come to startups with process instincts that served them well in larger organizations. The problem is that the earliest stage of a startup resembles nothing they've operated in before. There's no defined job, no existing team, no customers yet, no established playbook.
The mental model that works best at this stage isn't "what's my quarterly plan?" It's "what are the three questions I need to answer in the next 30 days to decide whether this company is real?" Those questions are usually:
- Will someone pay for this specific thing in the next 90 days?
- Can I build a version of it that demonstrates the core value proposition?
- Is there a second customer who has the same problem as the first?
Every activity in the company either moves toward answering these questions or it doesn't. Startup OKRs don't help you answer them. Customer calls and early paid pilots do.
A simple goal structure that actually works
Instead of quarterly startup OKRs, most early-stage founders benefit from a milestone map and a weekly commitment list.
The milestone map has three to five milestones: signed letter of intent from a design partner, first paying customer, $10K MRR, second design partner, seed close. Each milestone is binary — you hit it or you didn't. The milestone map tells you where you are in the journey and what's blocking the next gate. You review it monthly, not quarterly.
The weekly commitment list has three things each founder commits to completing before the next week's sync. Not goals — commitments. "Call 10 potential customers" is a commitment. "Get 3 follow-up meetings from those calls" is a goal that depends on other people. Commitments are in your control. Reviewing 3 commitments per week keeps the team honest and keeps overhead near zero.
This structure is simple on purpose. Simplicity is a feature at the pre-product-market fit stage. Every additional planning layer adds overhead a company too small to absorb it.
When to start using OKRs
Startup OKRs start making sense when:
- You have 8–12 employees across multiple functional areas
- You have enough customers that you're managing competing priorities between sales, product, and customer success
- You've found product-market fit and you're executing on growth rather than discovering the playbook
At this stage, the coordination problem that startup OKRs solve is real. A VP of Sales has different day-to-day priorities than the head of engineering, and both have different time horizons than the customer success lead. OKRs create shared alignment across those functions. The framework fits the problem.
The mistake is implementing OKRs because "that's what companies do" before you're big enough to have a coordination problem. If your company is 4 people, everyone in the room already knows the priority. Write it on a whiteboard. You don't need a framework.
What quarterly planning looks like at different stages
At 5 employees: a 90-minute meeting. What's the one thing we absolutely must accomplish this quarter? What's blocking us? What are we stopping so we can focus? Write it down, put it somewhere everyone can see it, revisit it in 30 days.
At 50 employees: a two-day offsite with cross-functional working sessions, bottom-up drafts from each team, grading of last quarter, and explicit prioritization of what will not get done because you've decided what will.
Both versions are appropriate for their moment. Running the 50-person version at 5 creates bureaucratic overhead in a company that needs speed above all else. Running the 5-person version at 50 creates the coordination failures that startup OKRs exist to prevent.
The operator founder's instinct — that there should be a process, a framework, a way of doing this — is right. The instinct needs to be calibrated to the current size of the organization. The company you're building now doesn't look like the company you managed for 15 years. It doesn't need the same tools yet.
A venture studio that has taken companies through the 0-to-seed stage has run this process with enough founders to know where the overhead comes from. The go-to-market playbook is part of it — so is the operational discipline to know which processes apply when.