On the whiteboard in my office, underneath the roadmap and the lead list and a sticky note that says "SHIP OR DIE," there's a date circled in red marker.
That's the date myrecipecard.kitchen either has a paying customer or I shut it down. I built a food costing tool because I spent 25 years watching kitchens bleed money they couldn't see. If operators don't pay for it, I need to know that now — not in fourteen months.
No pivot. No "let's give it another quarter." No "the product just needs one more feature." Sixty days of real outreach. If nobody pays, the market is telling me something, and I need to listen.
Why Most Founders Won't Do This
I've watched three friends build software over the past two years. Two of them are still building. Zero of them have revenue. Both will tell you they're "almost ready to launch." Both have been almost ready for fourteen months.
The problem isn't the product. The problem is that building feels productive and selling feels terrifying. So you keep building. You add a feature nobody asked for. You redesign the onboarding. You spend two weeks on dark mode. And every day you don't put the thing in front of a real customer is another day you get to avoid the scariest question in business:
Will anyone actually pay for this?
I know this because I almost did the same thing.
How I Almost Built Forever
This started as a $500 diagnostic — a one-time food cost audit for independent restaurants. I spent weeks perfecting the report format. Color-coded contribution margins. Menu engineering matrices. Beautiful, detailed, thorough.
Nobody bought it.
Not because it was bad. Because $500 for something you've never seen is a hard ask for an independent owner who's already skeptical of consultants. They've been burned before. Some guy in a suit came in, charged them three grand, handed them a binder of "best practices," and nothing changed.
So I pivoted to SaaS. $249/mo. Monthly, cancel anytime. But now I was building software, and software is the world's greatest procrastination engine. There's always one more thing to build before you "launch."
That's when I found Pieter Levels.
The Guy Who Built 70 Startups
Pieter Levels is a Dutch developer who builds small internet businesses. He's launched over seventy of them. Most failed. A handful — Nomad List, RemoteOK — now generate millions in annual revenue.
His rule is simple: if a project doesn't get traction in 60 days, kill it and start the next one.
Not 60 days of building. Sixty days of real outreach — putting the product in front of real people and seeing if they pay. Building doesn't count. Planning doesn't count. A beautiful landing page with zero visitors doesn't count. Revenue is the only signal that matters.
When I read that, something clicked. I'd spent months building. I had a backend, a card generator, a lead funnel, legal docs, a case study, an email sequence. I had everything except the one thing that matters: a customer.
The Rules of the Kill Date
Here's what I wrote on the whiteboard:
1. The clock starts when real outreach starts. Not when the site goes live. Not when I "soft launch." The clock starts the day I post my first forum post, send my first outreach email, or share my first LinkedIn post. Real humans, seeing the real product, deciding whether to engage.
2. Free users don't count. Ten people signing up for free Cook's Cards is nice. It means the funnel works. It does NOT mean anyone will pay $249/mo. Free and paid are different planets. The kill criteria is paid subscribers, period.
3. No moving the goalposts. If day 60 arrives and nobody has paid, I don't get to say "well, the pipeline looks promising" or "I just need to tweak the onboarding." Zero paid subscribers after sixty days of real outreach means the market said no. Respect that.
4. Walking away is not failure. The worst outcome isn't killing a project. The worst outcome is spending two years and your savings on something nobody wants. The kill date is a gift — it's permission to move on before the sunk cost fallacy eats you alive.
What Scares Me About This
I'll be honest: it's terrifying. I've spent months on this. I've built a real product that solves a real problem — I've seen the numbers in my own kitchens, I know the money is there.
But knowing the money is there and convincing a stranger to trust you with $249/mo are two very different things. Every restaurant owner I'm about to pitch has been burned by a consultant. Every one of them is going to wonder why this time is different.
If I can't answer that question convincingly in 60 days, then either my answer is wrong or my audience is wrong or both. And I'd rather know that in two months than in two years.
The Upside of Constraints
Here's what the kill date actually does: it makes you ship.
When you have infinite time, you build features. When you have 60 days, you talk to customers. When you know the clock is ticking, you stop polishing and start selling. You post the forum post that isn't perfect. You send the email that could be better. You book the walkthrough before you feel ready.
The constraint is the strategy.
And if day 60 comes and someone is paying? Then I know this thing is real. Not "I think it could work" real. Revenue real. The only kind that matters.
If you're an independent restaurant owner and you want to see what per-item food cost analysis looks like, build a free Cook's Card. That's the product. No demo call. No credit card.
See the numbers: The case study — $3,800 hiding in one menu item. • The Beverage-Down Era — why food cost is the whole game now.