You're not ambitious enough
The tools stopped holding you back months ago. The only thing left is you.
Notion is killing Notion Mail. The one email client I’d actually started to like.
The old version of me spends the next hour being sad about it. Reading the shutdown notice twice. Googling alternatives. Weighing Superhuman against Missive against crawling back to Gmail and hating it. Migrating. Grumbling. Settling for whatever’s least bad.
That’s not what happened.
What happened is I built my own. A native mail client. All the best features of Notion Mail. None of the ones I didn’t use.
Running on my iPhone, my Mac Mini, and my MacBook. The only reason it didn’t also run on my iPad was that I forgot to charge it.
All of that in about two hours. While I was doing other work.
None of it was in the room
Halfway through, the build needed me to approve something on my Mac Mini. Which was at home. I was at work. The Mac Mini was sitting there running its own job the whole time, a tmux orchestration platform I’d also vibecoded, quietly coordinating agents while I wasn’t in the room.
So I logged into it from the office. Through an iOS VNC client. Which I had also vibecoded, a few weeks earlier, because every free one I tried choked on the auth handshake macOS remote display insists on. The existing tools all said no. So that one exists too.
I clicked the buttons it needed. I let it continue. And went back to my actual job.
From work, I used a remote desktop tool I’d built for myself to reach a machine at home running an orchestration platform I’d built for myself, so I could approve a step in a mail client I was building for myself. Three things. None of them existed a year ago. None of them are products. None of them have names or landing pages or pricing tiers.
Then there was getting the app onto my phone. The orchestration platform at home ran tailscale serve and threw up a plain web page with a single button on it: install. I tapped it from my phone, in the office. The app sideloaded straight off a walled-off machine sitting in my house, over Tailscale, with nothing physically connected to anything. It felt like actual magic. It was a button.
They’re just things I needed. So now they exist.
The word that died
Something changed under all of us, and most people haven’t felt it land yet.
“No” is gone.
Not “no” the answer to a question. “No” the wall. The one that used to quietly end the conversation before it started.
“Can you build your own mail client?” No.
“Is there a tool that does exactly this one weird thing you want?” No.
“Can you just make the software behave the way you’d prefer?” No.
For your entire life as a person who uses computers, the answer to “can I have software that works exactly like this” was no. You got what shipped. You filed a feature request into a void. You bent yourself around the tool, because the tool was never going to bend around you.
That’s over. That specific “no” does not exist anymore.
A market of one
Let me make the claim as plainly as I can, because it’s bigger than mail clients.
Anything digital is now buildable by one person, in an afternoon, on the side.
Not “buildable by a team over a quarter.” Not “buildable if you happen to be an expert in it.” Buildable by you, this week, in the gaps between your actual work. A mail client. A remote desktop tool. A dashboard nobody sells. The niche integration that no company will ever prioritize, because you are the only human alive who wants it.
The market of one is finally served. And you’re the only vendor it will ever need.
But a market of one is not a product
There’s a catch to all of this, and I spend a good part of my day explaining it to everyone around me.
A product for one only works because it’s a market of one. That’s the entire trick. There are no users to support but you. No bug reports except the ones you shrug at. No feature requests, no roadmap, no user research, no caring about migrations or explaining the new features to users, no newsletters, no marketing copy, no sales demo, nobody paged at 2am. You are the whole userbase. You know how it works. You know the limitations, and every time a limitation annoys you, you fix it.
The moment that stops being true, the bill for the magic arrives.
It really is easy to build something in a weekend that handles a good chunk of your support tickets. It feels solved. Then you try to take it from “a chunk” to “most of them,” and you run straight into all the tooling you don’t have yet. So you build that. Then the observability. Then the guardrails. And somewhere in there you look up and realize you’re not vibing an afternoon project anymore. You’re building a whole product.
And it doesn’t hold still. A new model lands every month, faster or cheaper or better, with new things your users now want you to wire in. They want analytics on what else it could be handling. They want real guarantees, that a refund can never go out twice, that some action never fires by accident. And they want all of it without burning a small fortune in tokens every single month.
Maintenance. Cost. Quality. That’s the tax on turning a market of one into a product for many. The weekend demo doesn’t remove that tax. It just hides it, right up until you try to grow past yourself.
What’s actually stopping you
So if it’s all possible now, why is your list of things you’ve built for yourself still so short?
Because the last wall isn’t technical. It’s in your head.
You’ve spent decades being trained that most things aren’t possible. That software is something other people make and you receive. That “I wish this existed” is a wishful little thought, not a Tuesday afternoon. The instinct to not even ask is baked in so deep you don’t notice you’re doing it.
You’re still scoping your ideas to a world that already ended. Trimming your ambitions down before you’ve even said them out loud. Still assuming the answer is no.
Stop doing that.
The constraint moved. It used to be capability. Now it’s imagination. The only thing standing between you and the exact tool you want is whether you still believe you’re allowed to build it.
You are. Obviously you are. I built a full-featured mail client while doing other work.
Nobody has better access to this than you do. It’s an API and a subscription. It comes down to who unlearns “no” the fastest. Who looks at a discontinued product, or a missing feature, or an annoying little workflow, and feels the old wall just not be there anymore.
Your tools got a thousand times more powerful this year. Your ambition didn’t move.
Fix that part. The rest already works.
Building the things I used to just wish for, at neople.io.