Ch #1 - A Non-Tech Guy’s Quest to Build a Web App: My First Leap into the Unknown

Hi, as you know —i am a finance professional with zero tech background, zero coding knowledge, and a whole lot of curiosity. I’ve been exploring AI tools and large language models (LLMs) to create things I never thought I could, one project at a time.

After my first adventure of building an Android app [read here], I’ve decided to tackle something new: a web app.

How will it turn out? I honestly don’t know. But here’s the deal—I’ll share every step, success, and stumble along the way.

So, let’s begin with the problem I’m trying to solve and why it matters to me (and maybe to you, too).

The Problem: The Disappearing Money Mystery

Every month, I start with a savings target. But by the end of the month, my wallet—and my bank account—tell a very different story. Sound familiar?

With credit cards, mobile wallets, and the convenience of “just tap to pay,” it feels like I’m spending within my limits. But at month-end, I’m left wondering: Where did it all go?

I need something to answer that question. An app that lets me:

• Upload my bank statement (no linking bank accounts, please!).
• See a simple, visual breakdown of where my money is going.
• Spot subscriptions I’m paying for but barely using.
• Get actionable insights into where I can save.

No complex integrations. No fancy dashboards. Just straightforward answers to why I have less money than I should.

And honestly, I need this app as much for accountability as for answers. Seeing the numbers in black and white might finally force me to have those tough conversations with myself: Do I really need this? Can I cut back here?

The Dilemma: To Build or Not to Build?

The moment this idea hit me, I was ready to start building. But then I stumbled upon a piece of advice that stopped me in my tracks:

“Sell Before You Build.”

It’s a simple idea that floats a lot around the community of app and web developers—before you spend weeks (or months) building something, validate if people actually want it. But as a non-coder relying entirely on AI tools, this got me thinking:

1. Does validation even matter for me? I’m not investing months of work or learning complex coding. At most, I’ll spend a few weeks experimenting with AI tools. Even if this idea flops, I’ll still gain invaluable experience—and that feels like a win to me.
2. How do you even validate an idea? This part wasn’t clear. Blogs, YouTube, even experts gave me vague advice that sounded nice but wasn’t actionable.

My Validation Experiment: A Crash Course in Learning

With no clear roadmap, I decided to just figure it out. Here’s what I did:

Step 1: Built a Landing Page

I created a simple, single-page site hosted on Render (shout-out to their free tier). It was basic, but functional. I integrated a free form collection tool so visitors could leave their email addresses if they were interested in the app. You can check it out <here>.

and how do i know what is a landing page and how to build one and what is Render and what are free form collection tools and how to integrate all that you ask ?

One Word : ChatGPT

Step 2: Launched a Facebook Page

I set up a page for the app idea and made my first post.

I learned how to build a Facebook page from University of Youtube. You can check out the page <Here>

Step 3: Ran a $10 Ad Campaign

This was the big one. I dove into the world of Facebook ads, learning the basics through YouTube tutorials. My ad explained the app idea and encouraged people to sign up via the landing page.

The goal?

See if anyone found the idea interesting enough to share their email.

What Did I Learn?

The process was eye-opening:

• Landing Pages Matter: Even a basic site can teach you so much about presenting an idea.
• Facebook Ads Are a Skill: Learning to target the right audience is as important as the ad itself.
• Validation Is a Journey: Even if no one signs up, I’ll have learned something valuable.

What’s Next?

So, did anyone sign up? Did the ad work? Or did I just waste $10 on a wild goose chase?

I’ll share the results in my next update. For now, I’m proud of what I’ve learned: building & deploying a landing page, integrating a form, and running ads—all for the first time.

Even if no one else finds this app useful, I’m still building it.

Why?

Because it’s my first web app, and I need the experience.

This journey isn’t just about creating an app—it’s about creating a better, more capable version of myself.

Stay tuned for the next update, where I’ll reveal what happened with my ad, what I learned, and what’s next in this wild experiment.

#NoCode #WebAppJourney #LearningInPublic #BuildAndLearn #Buildinpublic