60 Products in 60 Days

This post is the AI-shaped version of a raw thought dump.

The ideas are mine. The phrasing has been cleaned up so it is easier to read, easier to render, and less painful to publish. If you prefer the unfiltered version, I am also making the raw notes available separately.

The start of the 60/60 challenge

I started the 60/60 challenge because I needed a forcing function.

The challenge is simple: build 60 software products in 60 days. Not 60 perfect companies. Not 60 polished venture-backed masterpieces. Sixty real products that can be shipped, used, and learned from.

The idea clicked after I watched an Instagram video about brand building. The point was that the best content right now is often built around a visible series. People want to follow growth. They want to see a time lapse. They want the result, but they also want the lesson that came from getting there.

That format is powerful because it compresses work into value. If someone says, "I fixed 50 homes, and here are the lessons I learned," you immediately know why it is worth watching. The audience gets the shortcut without doing the whole journey themselves.

I realized I could do the same thing with software.

I build a lot. I like building. I like taking small ideas and making them real. Alex Hormozi says that when you are new, one of the best things you can do is offer value for free. That made sense to me. I can build products, release them for free, and let the work itself become the proof.

If something earns attention, then maybe there is a paid version later. Maybe there is a more advanced version. Maybe there is a business behind it. But the first move is not to overthink the business model. The first move is to ship.

Why small products

The rule I am setting for myself is that each product should be narrow.

It should solve one small problem, or create one small moment, as cleanly as I can make it. The goal is fast, modern, minimal software that does the thing it promises without burying the user in explanation.

That matters because big ideas are easy to hide behind. You can spend forever planning the perfect platform, the perfect architecture, the perfect brand, and the perfect launch. The problem is that none of that teaches you as much as putting something in front of people.

Small products remove the hiding places.

They force taste. They force tradeoffs. They force you to decide what actually needs to exist today and what can wait.

The first product: ThinkFast

The first product in the challenge is ThinkFast.

ThinkFast is a fast, high-energy word game. A word appears on the screen, and you write the first word that comes to mind as quickly as possible. That is the whole core loop.

It is small, but it is exactly the kind of thing I would use. That is an important filter for me. I do not want to build random products that I would never open again. If I am going to spend my time making something real, I want at least one clear user in mind, and sometimes that user is me.

The details of building and releasing ThinkFast deserve their own post. For this one, the important part is that the challenge started with a product I would actually open after launch.

Novelty is allowed

One thing this challenge is already teaching me is that people overcomplicate ideas.

There is a lot of advice that says you should build what already exists. That is useful advice. Existing demand is real. Markets matter.

But it is also okay to build random new things.

Uber, Airbnb, TaskRabbit, and a lot of other companies started as ideas that were not obvious to everyone. Novelty creates curiosity. Curiosity creates the possibility of momentum. A unicorn is often just a novel company that happened to win the market gamble.

That does not mean every weird idea is good. It just means that novelty should not automatically scare you away.

My criteria for ThinkFast was simple: I wanted it to exist, and I knew I would use it.

For a challenge like this, that is enough to start.

The real output is not just the product

The funny part is that the first app immediately gave me ideas for the next ten.

That might be the hidden value of the 60/60 challenge. The output is not only the shipped product. The output is also the next layer of problems you notice because you were building fast enough to hit them.

The first product immediately made me think about design systems, agent instructions, reusable product patterns, database workflows, animation taste, and the way I want my products to feel.

That matters for my current work on Varmada too. I do not want Varmada.com to be just another landing page for my business. I want it to have a story. I want the products, the lessons, and the process to sit together in one place.

The 60/60 challenge gives me that story.

What I am optimizing for

I am not trying to make every product huge.

I am trying to build proof. I am trying to build taste. I am trying to build the habit of finishing. I am trying to learn what breaks when AI helps you move faster than your old process was designed for.

The products should feel:

• fast
• clean
• modern
• sleek
• minimal
• intuitive

I want less text. I want fewer explanations. I want products that are easy to understand because the interface makes sense on sight.

AI tends to over-explain. It tends to add copy where interaction should do the work. A lot of my job is not just prompting it to build. It is pushing it toward taste.

That is part of the challenge too.

Day one taught me enough to keep going

ThinkFast is not the final form of anything. It is the first signal.

It proved that I can take a small idea, use AI as leverage, and ship something I actually want to use. That is enough for day one.

There will be more lessons as the challenge continues. Some products will be useful. Some will be strange. Some will probably fail. But each one should leave behind a product, a lesson, or a sharper sense of what I want to build next.

That is the point of 60/60.

Ship the thing. Learn from the thing. Build the next thing.

If this process is useful to you, follow the challenge and join the Varmada newsletter. I do not want to spam people. I want to share what I am learning as I try to become a better builder and, God willing, a serious entrepreneur in this space.