Jenarius Ganlary

• Building AI products & SaaS in public.
• Sharing what I learn about building & business.
• From a job → building → financial freedom.

[Jenarius Ganlary @jenariusdev]

You’re not confused because you’re not smart enough.

You’re confused because nobody has shown you the first actual step.

Most "founder" advice starts at the finish line. I'm starting at the first rung.

A thread on how to actually start building. 🧵

[Jenarius Ganlary @jenariusdev]

@pelloiafilippo Balance both.

[Jenarius Ganlary @jenariusdev]

I’ve failed at building SaaS before.

Not once. Twice.

And honestly, the hardest part wasn't watching the product fail.

It was convincing myself to start again.

Because after a failed attempt, your brain has a million reasons to wait:

“Maybe I’m not ready.”

“Maybe I should learn more first.”

“Maybe I should build something else.”

But you eventually realize:

Consistency isn't about never failing.

It's about being willing to sit with the failure, learn from it, and build again.

Now I'm on attempt #3.

I don't know how this one ends.

But I'm still here. 🚀

[Jenarius Ganlary @jenariusdev]

Day 4 of building my 3rd SaaS.

Today I learned that sometimes your code isn't broken.

Your assumptions are. 😂

I had a strategy system returning 0 results.

At first, it looked like the filtering logic was broken.

It wasn't.

My onboarding and database were speaking two different languages.

Fixed the taxonomy → fixed the seed → fixed the matching → suddenly, personalized strategies started showing up.

And that's the part I actually enjoy about building.

You think you're building a feature.

Then the feature breaks, and teaches you something about the system you were actually building.

Day 4 shipped.

Still keeping the product under wraps. 👀🚀

[Jenarius Ganlary @jenariusdev]

@pelloiafilippo Sure Bro, I'll follow along.

[Jenarius Ganlary @jenariusdev]

@ASMIT0814 I'll reveal it soon bro. Its a social media thing.

[Jenarius Ganlary @jenariusdev]

Sunday. No rest. Day 4 begins. 😤

No rest this Sunday.

While everyone’s taking the day off, I’m back at the keyboard. (I know my fellow founder's don't)

Day 4 of building my 3rd SaaS.

Still early.
Still figuring things out.
Still breaking things and fixing them.

No idea where this attempt will take me.

But I'm going to keep building.
Keep learning.
Keep shipping.

Day 4/∞ 🚀

[Jenarius Ganlary @jenariusdev]

@ASMIT0814 At this point I’m just trying to stay curious and not pretend I know where this thing is going 😂

[Jenarius Ganlary @jenariusdev]

@yevloop That’s the scary part 😂 Day 1–3 feels exciting. Then you realize… oh, I actually have to keep doing this.

[Jenarius Ganlary @jenariusdev]

@HosseinGorji021 Appreciate it bro! 🙌 Yeah, that migration exposed a few things I hadn't thought about when the project was smaller. Still learning a lot from this build.

[Jenarius Ganlary @jenariusdev]

Nobody tells you this about building a SaaS:

The hardest part isn't always writing new code.

Sometimes it's changing something you thought was already working. 😂

Day 3, I changed the architecture of my 3rd SaaS.

Then everything started fighting back.

→ Changed the Prisma schema
→ Database migration succeeded
→ TypeScript still complained
→ Realized Prisma Client was stale
→ Regenerated it
→ Restarted the dev server
→ Fixed the mismatched layers

And that was just one problem.

The bigger one was architectural.

I was adding a completely new workflow while existing parts of the application were already depending on the old data model.

Which forced me to think about something I probably should've thought about earlier:

A database isn't just where you store data.

It's part of the architecture.

Change the model →
change the relationships →
change the application →
change the assumptions.

One small schema change can travel through the entire system.

That's probably the biggest thing I learned today:

Building isn't just making things work.

It's learning how to change the system without breaking everything that already works.

Day 3 shipped.
Day 4 tomorrow. 🚀

[Jenarius Ganlary @jenariusdev]

@yevloop The first version hides a lot of those shortcuts because everything is still small. Then one schema change comes along and suddenly you see all the places you took shortcuts.

[Jenarius Ganlary @jenariusdev]

@HakDimoz Consistency 🙌

[Jenarius Ganlary @jenariusdev]

Even while building, I’ve learned I need an off switch.

Some nights it’s just Fortnite. 🎮

No code.
No X.
No thinking about the next feature.
Just play for a while and let my brain breathe.

I used to think taking a break meant I was being unproductive.

Now I realize sometimes the best thing you can do for your work is stop thinking about it for a bit.

What do you guys do to reset when the stress starts piling up? 👇

[Jenarius Ganlary @jenariusdev]

@Biemjo Exactly bro😂. That's what got me today. The new stuff wasn't the hard part but changing the existing architecture without breaking everything around it was.

[Jenarius Ganlary @jenariusdev]

Idk why people still think vibe coding =
production-ready 😂
You can absolutely vibe code a prototype.
But what happens when you suddenly get 1K users?
Can your architecture handle it?
What about database design, security, observability, performance, and scaling?
Vibe coding gets you to the starting line. Engineering gets you past it.
But yeah, I'll agree with one thing, you're absolutely right that
We can vibe market. 😂

[Jenarius Ganlary @jenariusdev]

@gauraavvii Its never too late.

[Jenarius Ganlary @jenariusdev]

@niqudrift Make a habit of pushing the the code to GH.

[Jenarius Ganlary @jenariusdev]

You’re not confused because you’re not smart enough.

You’re confused because nobody has shown you the first actual step.

Most "founder" advice starts at the finish line. I'm starting at the first rung.

A thread on how to actually start building. 🧵

[Jenarius Ganlary @jenariusdev]

@buildwbhoomika Lets Connect🙌