It's Day 0 of my 100 micro-startups in 100 days challenge, and I'm already making questionable life choices. Instead of using WordPress like a normal person, I'm building this blog from scratch with Nuxt because apparently I enjoy pain. Why? Free Cloudflare hosting, lightning speed, and complete control over my code. But mostly because I'm a stubborn dev who can't help overcomplicating everything. Welcome to my journey of building 100 startups in 100 days – where bad decisions and good code collide.

WTF Am I Getting Myself Into? (The Challenge Explained)

So why the hell am I putting myself through this 100-day torture session? Fair question. This isn't some "rise and grind" bullshit – it's an experiment in reckless productivity. Can a single developer actually ship 100 micro-startups without losing their mind?

A micro-startup isn't your typical venture-backed cash furnace. While traditional startups begin with funding rounds and months of planning, I'm diving headfirst into an ocean of possibilities with nothing but my laptop and questionable judgment. It's like the difference between carefully planning an expedition and jumping off a cliff with materials to build a parachute on the way down.

I'll be documenting every painful step, from initial concept to launch to inevitable failure (with occasional success). This includes the code, the marketing attempts, and all the embarrassing moments in between.

Why Nuxt + Cloudflare Instead of WordPress (For Fellow Code Masochists)

It's a rainy Sunday, and instead of doing something sensible like watching Netflix, I'm rebuilding a perfectly good wheel. Who needs WordPress when you can spend hours coding a blog from scratch? Classic dev move. My time management skills are clearly top-notch.

But there's actual logic behind this madness:

1. Free Cloudflare hosting means zero monthly costs, unlike WordPress hosting that bleeds your wallet monthly
2. Lightning-fast performance because static sites just crush WordPress in load times
3. I can build custom components exactly how I want them without fighting plugin compatibility
4. No database to manage means fewer security headaches and points of failure

For non-devs reading this, there are plenty of no-code solutions that won't require you to learn JavaScript just to launch a blog. Just remember that all tools have a learning curve, even the no-code ones that promise instant magic. Pick your poison.

"100 Startups" Sounds Insane - Because It Is

Let's address the elephant in the room: 100 startups in 100 days is objectively ridiculous. Most founders struggle to launch ONE successful startup in YEARS.

But these aren't traditional startups. They're micro-startups – small, focused projects built to solve a specific problem. Think of them as MVPs on steroids, but with an actual path to generating a tiny bit of revenue.

I see myself as that idiot diver jumping straight into shark-infested waters without equipment because some rando mentioned there might be treasure down there. How stupid am I? We'll find out together. Maybe I'll get eaten alive, or maybe I'll find something valuable. Either way, it'll make for an entertaining story.

The First Startup: No Overthinking, Just Building

What's my first micro-startup going to be? No fucking clue yet. And that's the point.

The goal isn't to spend weeks overthinking the "perfect idea" – it's to spend a few hours daily actually building shit that solves real problems. Analysis paralysis kills more projects than bad code ever will.

My daily process will look something like this:

1. Identify a problem (either personal or observed)
2. Spend MAX 3 hours coding a solution
3. Deploy it (even if it's ugly)
4. Move on to the next one

If you have problems you'd like me to solve, drop your suggestions here – maybe your idea will become startup #69 (huhu).

The Marketing Problem: How Not to Suck at It

Marketing is my personal hell. I'd rather debug 10,000 lines of legacy code than write a sales page. But since I actually want someone to use these micro-startups, I need a better plan than "spam Reddit until I get banned." The documentation of my marketing failures will probably be more valuable than the startups themselves.

Instead of the classic "annoy everyone on social media" approach, I'm going to try:

1. Building in public through this blog and Bluesky
2. Creating actually useful content around each solution
3. Finding niche communities where each solution solves a real pain point
4. Leveraging each previous startup to promote new ones

I'll track what works and what flops in my weekly roundup posts.

Success Metrics: From $0 to Something (Hopefully)

My embarrassingly low bar for success: make at least $1 in revenue. Not profit – just a single dollar from someone who isn't my mom. If I can't convince even one human to part with the equivalent of a gas station gum purchase after 100 attempts, I should probably delete my GitHub account and take up gardening.

Beyond that initial dollar:

• Get 10+ monthly active users for at least 5 startups
• Generate $100 total revenue across all projects
• Learn which types of micro-startups are worth pursuing further
• Build a portfolio of code I'm not entirely ashamed of

Follow my humiliating journey on the revenue dashboard I've set up to track earnings in real-time.

Follow The Chaos: What's Next in This Challenge

Tomorrow marks Day 1 of this insanity, where I'll be tackling my first micro-startup. Will it be brilliant? Probably not. Will it work? Maybe. Will it be done by the end of the day? Absolutely – that's the whole point.

If you're morbidly curious about this train wreck:

1. Subscribe to the newsletter for weekly updates
2. Check out my startups catalog as it grows
3. Follow along on Bluesky for real-time failures

This could be the most productive disaster of my career. Or just a disaster. Only one way to find out.

FAQ About This Ridiculous Challenge

What counts as a "micro-startup"?

A functioning product that solves a specific problem and has a potential path to generating revenue. Not just a landing page or an idea.

Are you really coding everything from scratch?

Mostly. I'll use frameworks and libraries (I'm not coding a new programming language), but each startup will be built fresh. Some components might be reused when it makes sense.

Can I suggest a startup idea?

Absolutely! Submit your ideas here – if I build it, I'll credit you.

What happens after the 100 days?

I'll focus on the 3-5 most promising projects and develop them further. The rest will either continue to run on autopilot or get archived with lessons learned.

Isn't this just a gimmick?

Yes and no. The "100 in 100 days" format is definitely a hook, but the underlying goal is serious: break through perfectionism and actually ship products regularly.