The Guy Who Likes To Start Things
Hello Kind Reader,
I launch bizarre business ideas, document the chaotic process, and abandon them without apology — then do it all over again.
For me, the most important part of any business is starting. I love the rush of a new idea, the first test print on the Kobra S1, and that elusive first sale.
But there is a problem: I have more ideas than time.
Most people think quitting is a bad thing. They think it means you gave up. But for me, quitting is how I make room for something new. I don’t “bail” because I’m lazy. I bail because I found a new idea that I’m dying to start.
This blog is an open notebook of that cycle. We build fast, we learn the truth, and then we clear the deck so we can start the next big thing.
I’m not looking for a reason to stay. I’m looking for the next reason to start.
The Spark (New Ideas)
Every bizarre idea has a beginning. I’ll share why I chose to start a project, whether it’s laser engraving brass golf markers or spinning up a satirical corporate coaching brand.
The Build (Making it Real)
This is the messy part.
I’ll show you the tools, the Claude prompts, and the chaos of turning a raw thought into a working digital app or physical object.
The Process (No False Timelines)
I don’t spend years on one thing, but I’m done forcing artificial sprints. I document the chaotic, messy reality of building with AI, tuning 3D printers, or spinning up a new brand in a weekend.
The Reality Check
(No Fluff)
I share what actually happens when you launch an idea. If an app gets 340 views and zero sales, I write about it. If a specific prompt sequence saves me three days of coding, I give you the exact sequence.
Why I Bailed
Quitting isn’t a failure; it’s a strategic move to clear the deck. I’ll explain the exact moment I decided to stop a project to make room for something better.
What’s Next? (The Loop)
My brain never stops, so there is always a new “start” waiting in the wings. I’ll give you a sneak peek at the next bizarre idea I’m about to launch.
The Build & Bail Origin Story
Before this was a brand, it was just a habit I couldn’t shake.
Muck The Fets shirts: I wanted one, couldn’t find one online, so I had 20 printed and started selling them myself. Moved a few rounds of orders. Then bailed. That was the blueprint for everything that followed.
The Affiliate Hype Wave: When rumors leaked that Sony was dropping a slim PS3, I built a site, wrote about it obsessively, and when Amazon pre-sales went live, I made thousands of dollars in a few days off a 4% referral commission. Sold the site. Total profit: $15,000. Bailed.
KingOfAllGeeks.com: My attempt to cover every geeky passion at once. I got traffic, made a few bucks, and scored press passes to Comic Con and Toy Fair. Eventually figured out I wasn’t niche enough. Classic bail.
The Bane Costume: Another hype wave for The Dark Knight Rises turned out to be a goldmine — another $15,000 profit and a genuinely excellent Halloween costume. Bailed.
GeekDecor.net: This was supposed to be sustainable. Traffic was growing, I hired people, and then I hit a wall fighting for high-competition keywords with zero strategy. Bailed smarter than I built.
PimplePoppingVideos.net: The idea was simple: share gross-but-fascinating videos from YouTube and let the ad revenue flow. It worked way too well, hitting over 1 million monthly pageviews and a Facebook group with 60,000+ members. I learned more about hosting, ad networks, and audience building from this disgusting little site than anything else I’d ever built. Ran into content policy issues. Bailed.
The Rest of the Graveyard: ConJunkies.com (too much work), TheASMR.com (got bored, sold it), PlayingInTraffic.co (never got traffic), and LeveledUpDads.com (a mess of interests that bailed on itself).
All of that leads here. Build and Bail isn’t a pivot. It’s just the first time I’ve been honest about what I’ve been doing all along.
Want to skip the struggle?
I’ve spent over a decade figuring out how to build fast and bail smart. If you have an idea stuck in your head and don’t want to spend the next six months trying to learn the tech stack, let me do the heavy lifting.
We can jump on a 60-minute planning call to map out the exact AI prompts you need to launch, or I can just build the v1 for you in a weekend.