I Killed This Idea Three Times in One Afternoon
I ran a ClassPass-for-cafes idea through the jynlab Product OS. It killed the idea in one afternoon, and pointed to a better one.
I'm a solo builder. I make small software products, grow them, and sell them. Before I build anything, I run the idea through my Product OS — a simple filter that judges an idea the way a buyer would. One afternoon I ran an idea called CaféPass through it. On paper, it looked great. By the end of the day, the OS had killed it — no code, no money spent. Here's how the filter works, and the better direction it found.
- I built nothing. The Product OS killed it on paper in one session.
- CaféPass had real cafés and plenty of remote workers. Still a no.
- The idea wasn't the problem. The customer was.
- The same filter pointed me to a far better space: tools for creators.
- Big takeaway: check the customer first, not the idea.
The idea
CaféPass is like ClassPass, but for cafés. You pay a monthly fee to use partner cafés as your work spot. The cafés pay me — for marketing, for filling empty seats, for letting people order ahead. The target was the busy remote-work area around San Jose.
My goal was simple: build a small software product I could sell later for a few thousand dollars. So every choice gets one test — would a buyer want this?
The jynlab Product OS
The Product OS is the filter every idea has to pass before I write a line of code. Five steps, in order:
- Real demand?Is the pain real — and is there a free option sitting right next to it?
- Exit fit?Could a buyer run this without me, from another city?
- The right customer?Five quick questions about who actually pays.
- Listen first.Find the pain in a free community before spending a cent.
- Verdict, then redirect.Kill fast, keep the lesson, point to a better customer.
CaféPass cleared the demand check — then failed everything that matters. Here's the run, filter by filter.
Filter 1 · Real demand?
Both sides looked strong
There are plenty of cafés here. And demand is huge: this is one of the most remote-work-heavy areas in the country.
Estimates from public sources (café directories; U.S. Census; Bay Area Council). Numbers vary by definition.
Sounds perfect. Here's the catch: when cafés are everywhere, the free option is everywhere too. Anyone can buy a $5 coffee and sit for hours — or go to a library, which is free and has more tables.
A paid pass isn't fighting other passes. It's fighting free.
Filter 2 · Could a buyer run it?
Why it failed — three walls
You need both sides at once
I'd need cafés and users at the same time, in the same neighborhoods. That's really hard. ClassPass took years and a lot of money to pull it off. I have neither.
Only I could run it
The money comes from deals with local café owners, made in person. A buyer in another city couldn't take that over. If a buyer can't run it without me, it won't sell.
It makes the café's problem worse
Cafés near tech offices don't need more remote workers. They're already full of people who buy one coffee and stay four hours. My app would send more of them — and help them grab seats. That's more of the thing café owners hate. The cafés that would want it are the empty ones, and they can't afford to pay.
The pivots that didn't help
I tried to save it a few times. None of it worked:
- Charge cafés, not users?Now I'm selling to the harder, cheaper, flakier side — and I can't sell cafés until I already have users.
- Show open seats in real time?Who keeps it updated? Baristas are too busy, and wrong data is worse than no data.
- Add order-ahead?Already everywhere (Square, Toast). One app, Ritual, raised about $70M doing this for office workers — then crashed when those workers went home.
- Let people make cowork friends?Now it's a social app too. More work, not more strength.
Filter 4 · Listen first
Before spending a cent on ads, I did the cheapest test in the OS: I read one r/SanJose thread. Someone asked for good work cafés and got 15+ answers in minutes — free. The real complaint wasn't "I can't find a café." It was "I can't find a seat." And people fixed that by going to the library. That thread killed the idea on its own.
Filter 3 · The right customer?
The lesson — it was the customer, not the idea
Every fix hit the same wall. Because "local café owner" is a bad customer for the kind of business I want to build. This is the test built into the Product OS:
| Question | Café owner | Creator / marketer |
|---|---|---|
| Do they have money to spend? | No — tight budgets | Yes |
| Can I reach them online? | No — in person | Yes |
| Will they sign up on their own? | No — needs a pitch | Yes |
| Do they pay every month? | No — on and off | Yes |
| Could a buyer run it without me? | No — it's all local | Yes |
| Score | 0 / 5 | 5 / 5 |
I didn't need a better café app.
I needed a better customer.
Filter 5 · Verdict, then redirect
Where the OS pointed
Funny thing: the answer was on my screen the whole time. I had a dataset about which Reddit posts go viral. So I asked a new question — what if predicting what goes viral is the product? Run through the same filter, the customer for that — creators and marketers — scores 5/5. The opposite of café owners.
But the OS keeps me honest both ways:
A generic "viral predictor"
Tons already exist. Predicting virality is genuinely hard, and most "85% accurate" claims are just marketing. A thin tool like that is easy to copy and hard to sell.
A narrow version
Pick a spot the big tools ignore — most do video; text (Reddit, LinkedIn, X, newsletters) is wide open. Change the promise from "predict virality" to "score and fix my post for this audience." And pick one buyer, not everyone.
Lessons for other builders
- Check the customer first, not the idea.
- A "hot market" can be a trap — especially when the free option is one block away.
- Sort by "are people already paying?", not by hype.
- Listen before you spend. One free thread can save weeks.
- If you want to sell it later, make sure someone else can run it.
What's next
Pick one platform and one buyer. Then go listen to that buyer's real complaints before building anything.
The best thing I got from CaféPass wasn't the idea — it was the speed. The Product OS killed a weak idea in an afternoon, for free, before it could eat weeks of my life.
Founders and future founders are already on the list. Every time I run a new idea through the Product OS, you get the teardown first.
FAQ
What is the jynlab Product OS?
It's my 5-step filter for new software ideas: real demand, exit fit, the right customer, listen-first validation, and a fast verdict. I run every idea through it before writing any code.
Should I build a ClassPass for cafés?
Probably not as a solo, sellable product. It needs cafés and users at once in the same city, the revenue is local and tied to you, and it sends cafés more of the laptop campers they already struggle with. Free options — a $5 coffee, or a library — are everywhere.
How do you decide if a micro-SaaS idea is worth building?
Check the customer before the idea. If they have money, you can reach them online, they sign up on their own, they pay monthly, and a buyer could run it without you — it's worth a look. CaféPass scored 0 out of 5.
How can I validate an idea for free before building?
Listen first. Search the community where your customer already hangs out and read what they complain about. One Reddit thread killed CaféPass before I spent a cent.
What makes a good customer for a sellable SaaS?
One who has a budget, is reachable online, buys self-serve, pays every month, and isn't tied to you — so a future buyer can run it remotely. Creators and marketers fit; local café owners don't.