07 / 08
Most founders set a new business goal the way they set a New Year's resolution — with genuine intention, some rough arithmetic, and a quiet assumption that momentum will sort out the details. It rarely does. The goal sits on a slide, gets referenced in weekly standups, and slowly loses its grip on actual decisions. By month two, the team is busy but the goal is decorative. This isn't a motivation problem. It's a specificity problem.
A real business goal isn't a number. It's a filter. When someone proposes a new feature, a partnership conversation, or a pricing experiment, a well-formed goal should make it obvious whether that thing belongs in the next 90 days or not. If your goal can't do that work — if it doesn't help you say no to things that feel productive — it's not a goal. It's a direction. Directions are useful, but they don't make decisions for you.
What Makes a Goal Specific Enough to Be Useful
The test is simple: can two people on your team independently look at the same opportunity and reach the same conclusion about whether it serves the goal? If the answer is no, the goal is still too loose. Specificity here doesn't mean adding decimal places to a revenue target. It means being clear about who you're trying to win with, what behavior you're trying to change or create, and what the constraint is. A goal like "grow revenue" fails all three. A goal like "get five logistics companies with under 200 employees to run their first automated dispatch cycle without support from us" passes all three. You know who, you know what success looks like, and the constraint — no hand-holding — tells you something about the kind of product work that matters.
The constraint is the part founders most often drop. It feels limiting, and at an early stage, limitation feels dangerous. But the constraint is exactly what gives the goal its teeth. It rules things out. It tells you what kind of win counts and what kind doesn't. A sale that only works because you personally onboarded the customer is useful data, but it shouldn't count toward a goal that's testing whether your product can stand on its own. Knowing that distinction in advance changes how you build, not just how you measure.
The 90-Day Horizon Is Not Arbitrary
Seed-stage founders often either set goals that are too short to reveal anything meaningful — a two-week sprint target that could be hit by luck — or too long to stay honest about. Ninety days is long enough to see a real signal and short enough that you can't hide from a bad one. It's also short enough that if you set the wrong goal, you haven't lost a year. The discipline isn't in picking the perfect goal on day one. It's in setting one that's specific enough to be wrong, running toward it with focus, and then being honest about what it told you.
Before you finalize a new business goal, ask one more question: what would have to be true about your customers, your product, or your market for this goal to be achievable? Write those assumptions down. They're not obstacles — they're the actual things you're going to learn. If any of those assumptions feel embarrassing to say out loud, that's a signal the goal is built on something you haven't tested yet. That's not a reason to soften the goal. It's a reason to go test the assumption first, or to make it explicit that the goal includes validating it. The founders who make the most of the seed stage aren't the ones who hit their first goal. They're the ones who know exactly why they did or didn't.