Here’s what I learned in the process.

1. Clarity beats chaos From day one

I had a finish line in mind. Limited time forces clarity. It makes you ruthless about scope, and that's a good thing—until it isn't. A few times I over-engineered and paid the price: lost hours, unnecessary code, dead ends. Lesson learned: build the simplest version that works.

2. You don't need to "know frontend" to build

The entire frontend was written by AI agents. Literally. I wrote zero lines of UI by hand. That’s not a weakness—it’s leverage. We’re entering an era where knowing how to orchestrate code is just as powerful as writing it yourself. And honestly? I had fun with it.

3. Copilot Agents are insane

I finally understood what all the hype around tools like Cursor and Copilot Agents was about. It's not just code generation—it's context-aware iteration. It felt like pair programming with a tireless engineer who doesn't sleep.

4. Use every lever you've got

AI, StackOverflow, DMs, Discord servers, random GitHub issues... if it helps move the needle, it's fair game. One night I hit a roadblock with an authentication provider. I found a better SDK, raised a red flag about something that didn’t feel right, and ended up getting direct access to an improved API. Wild times.

5. Deadlines move — discipline stays

Some things took longer than expected. I had to pause, rethink, adjust. But I didn’t ghost the process—I kept showing up every day. That’s what actually matters. You don’t need to ship on day 7. You just need to keep moving.

6. I’m addicted to building now

There’s no going back. I’m already sitting on over a dozen new product ideas. Some good, some terrible, all worth exploring. That’s the thing about building in public—it generates momentum, clarity, and community.

7. Speaking of community…

The best part of this challenge wasn’t the product—it was the people. I received advice, encouragement, support, and real-time feedback just by talking about what I was doing online. That’s the cheat code: share your process, be loud, invite others in. In a remote-first world, visibility is everything.

What's next?

• Open-sourcing the repo and inviting contributors

• Shipping the smart contract to Starknet mainnet

• Fixing Stripe webhooks to make the app fully functional

• Reviewing code security and database rules

• Deploying backend + frontend

• And yes… going after the first 100 paid users

This isn’t just about one app. It’s about showing myself I can go from zero to one—and from idea to execution.

The journey just started. Let's build 🚀

**Follow me on X to keep up with what I'm building next. **

I’m sharing everything in public—from experiments to breakdowns to breakthroughs.

But when I finally got the chance to start auditing, I hit a wall.

I felt like a lone wolf… and what’s a wolf without its crew?

Yes, I found bugs — but they were already reported. I realized I was missing something, and it wasn’t more theory. What I needed was real, hands-on building. I didn’t just need to keep learning — I needed to do.

Around that time, I started wondering if I should pivot. Maybe take a break from auditing and explore a different path — one that would help me understand the ecosystem even deeper before coming back stronger.

That’s when everything clicked.

During a recent call, someone mentioned that what the Starknet Foundation really wants from grantees is to bring users into the ecosystem. That stuck with me. Especially considering the AI-powered era we’re in — building has never been more accessible or exciting.

The very next day, I had a conversation about open source contributions, becoming a maintainer, and the grant opportunities within the Starknet ecosystem. My mind lit up 🤯. I opened ChatGPT (aka “Gepeto” in my house 😄) and started exploring what I could create.

The energy I once felt when I discovered the world of auditing… was back.

I scheduled a call to dive deeper into how grants, hackathons, and product building work in this space. And suddenly, it all made sense — the puzzle pieces fell into place 🧩.

That’s when I made the decision: I’m pausing my path as an auditor and starting my journey as a builder.

My goal? To build 7-day MVPs in testnet with:

• Account Abstraction

• Web2-friendly UX for non-crypto users

• A seamless testnet-to-mainnet transition that hides all the Web3 complexity

• Open Source code

• A freemium model integrated with Stripe from day one

My main focus is the wellness industry, and yesterday I started building the first product. I have exactly 7 days — after that, I’m heading to minor surgery recovery, so the countdown is real ⏳.

I’ll be sharing daily build-in-public updates in my X account with progress and the open-source repo. This is the beginning of a new chapter for me in the Web3 space.

Let’s build 🌱