Rebuilding From Scratch: The Day We Built Our Own AI-Powered E-Commerce Engine
Wow.
Today was one of those real builder days.
I decided to rebuild the entire Klara Paket project from scratch.
Not because we had built a lot. Not because something was broken. But because I wasn’t satisfied with the machine we had created.
Even though we hadn’t done much yet, the systems felt fragmented. Slightly messy. Not wrong — just not scalable. And if something doesn’t feel scalable early on, it rarely becomes scalable later.
So I made a clear decision:
Let Claude Code rebuild it properly — from its own architectural logic.
And surprisingly, starting over didn’t feel frustrating.
It felt clean.
Finally Discussing the Core
During planning, we went deeper than before.
Interactive app experience vs downloadable PDFs.
This question has been in the background of the project for a long time, but I hadn’t fully explored it in previous AI discussions. It stayed surface-level.
Today we discussed the core.
What are we actually building? A content library? A printable product? Or a living interactive experience?
That conversation alone made the session valuable.
Because product direction always starts there.
What We Actually Built Today
We began with a robust architectural plan.
Then we built:
👉 https://questbox.vercel.app/
And this is what we truly created:
- A full e-commerce platform from scratch
- Multi-language support from day one
- An admin panel with a working dashboard
- An AI Creative Pipeline where three models collaborate
- Fully deployed live using GitHub + Vercel
I also learned two new tools today:
- Supabase
- Vercel
We configured the database. Set up authentication. Connected environments. Established a deployment flow.
Everything worked on the first attempt.
That almost never happens.
Even though these tools were new to me, they felt right immediately. Clean. Modern. Built for exactly this type of product.
The Moment It Clicked
After setting up the database, we created the first user.
At first, I didn’t fully understand what that user represented.
Then it clicked.
It was the admin account.
The account that controls the system. The one that creates products.
And in that moment I realized:
We didn’t just build a website.
We built infrastructure.
We built our own e-commerce engine.
And I still have Anthropic tokens left.
That feeling.
We Can Now Create Products
We now have a system capable of generating products.
Real products.
That’s a major shift.
But here’s the honest part:
The quality is not high enough yet.
The machine exists. But the output needs refinement.
And that’s okay.
Because now we can focus purely on quality inside a working system — instead of constantly rebuilding the foundation.
That changes the game.
The Next Step: Mixture of Experts
Before ending today’s session, we planned the next evolution.
A Mixture of Experts setup.
Three different AI models. Each generating ideas. Each reviewing and critiquing the others. Structured feedback loops. Iterative refinement.
AI workers collaborating instead of operating alone.
If every product needs to be strong enough to stand on its own, then the creative pipeline must be stronger than a single model output.
We are not there yet.
But designing AI systems that evaluate and improve each other is exactly the direction I want this project to go.
Energy Reset
Now it’s fun again.
The kind of fun where you feel momentum.
Tomorrow isn’t about starting something new.
It’s about increasing the quality inside a machine that now exists.
My energy will be recharged.
Claude’s tokens will be reset.
And the system is live.
Let’s build.