The path wasn't a straight line into tech either.

I spent time working inbound customer service at Allianz and Policybazaar.

After that, I studied Elementary Education and earned a teaching certificate. Learning how to manage a classroom, build positive feedback loops, and communicate logic clearly.

Those years might have seemed like detours, but understanding how people interact under stress, and how to explain things simply, ended up being the foundation of everything I build today.

In 2020, I started taking on freelance web design and development work through platforms like Upwork and Fiverr.

The first real projects were small. Simple websites. Minor customizations.

Nothing overly complex, but enough to see how real businesses operate online.

At some point, just “building websites” stopped being interesting.

My focus naturally shifted toward:

• workflows
• logic
• systems
• operations

Instead of asking, “How should this page look?” the question became “How does this system actually run?”

That shift made everything clearer. Projects transitioned from standard templates into structured systems:

• dashboards with roles and permissions
• booking and vendor management setups
• reporting and payout architectures

Not perfect systems, but real ones—used, tested, and constantly refined by actual users.

But not everything worked.

Along the way, there were failed projects, an unsuccessful company, and ideas that never took off.

Failure isn't a dead end in this line of work. It’s just data. Every broken system and failed venture taught me exactly what not to do next time.

Today, I focus on building systems that solve operational problems.

That work lives at:
→ iframeweb.com

Not everything fits into structured projects.

Some things are:

• written
• observed
• explored
• left incomplete on purpose

This space exists for that.

There’s no fixed end to this.

Just ongoing work, learning, and a slightly better understanding than before.