The weekend builder experiment

This weekend I ran an experiment.

Over the last year I’ve had more conversations than I can count with designers who were recently laid off or quietly looking for their next role. The mood in the industry has shifted. A lot of talented designers are suddenly asking what the hell the next move is. Roles are tighter, teams are smaller, and a lot of very capable designers are asking the same question:

What now? Because the traditional path suddenly feels shaky as hell.

My answer has been the same for a while now.

Designers might actually be the best positioned founders of the next few years.

This is the year of the builder.

So this weekend I decided to test my own thesis. Not a startup launch and not a side hustle announcement. Just a question I wanted to test.

My thesis for this year has been simple: this is the year of the builder.

AI tools have fundamentally changed the game, and product designers are sitting in a very strange position right now. We already understand user problems, product thinking, interfaces, workflows, iteration loops, and shipping. Historically the missing piece was engineering. That barrier is starting to collapse.

So I wanted to see something for myself. How far could a product designer push an idea in a single weekend using modern tools?

---

The experiment

I gave myself a simple challenge: build a real SaaS product as fast as possible. Not a landing page and not a fake prototype. An actual working product that someone could log into and use.

I didn’t clear my calendar and I didn’t disappear into a startup bunker. I worked on it nights and small pockets of time across the weekend. In total I probably spent somewhere between 14 and 18 hours.

I have a full-time job. I have a wife and kids. Life still happened around the experiment. Which is kind of the point.

---

The idea

The project I built is called SaaSifyOS.

The simplest way to describe it is this: most productivity tools track tasks, but they rarely track whether the work actually created value. They tell you what got done, but not whether the bet paid off.

SaaSifyOS treats work like a portfolio of bets. Each project begins as a hypothesis about value creation and ends with a recorded outcome.

The system revolves around something I call Builder Kickoff.

Instead of immediately creating tasks, every project starts by defining the economic intent of the work. The kickoff captures five simple things: the project title, the problem being solved, the expected value of solving it, the type of value (revenue, growth, cost reduction, time saved, or strategic leverage), and a numeric goal for success.

Example: generate $10,000 in new revenue, save 20 hours per week of manual work, increase conversion by 8%.

That small shift transforms a project from an idea into a clear hypothesis about value creation.

Once the kickoff is defined, the project moves into execution. Tasks can exist, but they are not the core artifact. The project remains anchored to the value goal defined at the start.

When the work finishes, the builder records the actual outcome. Expected value versus real impact. Over time the system becomes a ledger of value creation.

Instead of asking "what tasks did we finish," the system answers a different question: did the bets we placed actually pay off?

---

The moment it clicked

There was one moment during the build where the whole thing changed.

I had just wired up the analytics page and the system started calculating expected value versus delivered value across the projects. Suddenly the dashboard started telling a story. You could see which bets were working, which ones were not, and how the portfolio was evolving.

Up until that moment it still felt like a toy. After that moment it felt like a real product. That was the point where I realized the experiment was working.

---

The stack

The stack itself wasn’t particularly exotic: React, TypeScript, Node, Tailwind, Vercel, and a handful of AI-assisted development tools. The interesting part wasn’t the stack though. It was the speed.

Idea to working system in roughly two days.

---

The real blocker

Ironically the biggest friction wasn’t engineering. It was design.

The product revolves around value and ROI, which meant the hardest questions were things like what metrics actually matter, how value should be visualized, and how simple the system should be.

The UX decisions took longer than the engineering. Which is a reminder that the hardest part of building products is rarely the code. It's deciding what actually matters. Which is exactly where product designers tend to create the most leverage.

---

The bigger realization

This email is not a launch announcement. In fact I almost don’t want you to sign up because the product isn’t the point.

The point is the experiment.

For years the biggest barrier to building products was engineering capacity. You needed a cofounder, a team, funding, and time.

Today that barrier is collapsing.

If you’re a product designer right now, you’re sitting on a strange amount of leverage. You already understand how products work. You already know how to iterate and ship. The missing piece was the ability to build, and that piece is getting easier every month.

---

The takeaway

The lesson from this weekend isn’t that everyone should go start a company tomorrow.

It’s something simpler.

Designers are massively underestimating their ability to build. We spent years being told we couldn't ship without a whole engineering org. That narrative is starting to look like bullshit.

For years the path for designers looked very narrow: get hired, move up the ladder, join a bigger company, ship better work.

But something has changed.

AI has collapsed the barrier between idea and software. The distance between design thinking and a real product is smaller than it has ever been.

Which means there is another path now.

Not every designer will want it. But for the ones who do, the opportunity is enormous.

Over the next three years I believe we are going to see a wave of product designers become founders.

Not because they suddenly learned business.

Because they already understand products.

This weekend was just a small proof of that.

I built the first version of SaaSifyOS in two days.

If you’re curious you can see it here:

​www.saasifyos.com​

You can even create an account and explore the system yourself.

But the real offer isn’t the product.

The real offer is the idea behind the experiment:

Designers can build.

And the ones who realize that early are going to have a very different next few years.

If you're curious you can see it live at saasifyos.com, register for Free. I even wired up a simple login and signup. But again, the point of this experiment isn’t to get users. It’s to prove something to myself: designers are far closer to building real products than they think.

​
Talk soon,