Software Product Engineer & SaaS Builder

I turn real business problems into working software.

Thirteen years of PHP and Laravel, now split three ways: SaaS products you can subscribe to, custom builds for clients who need something specific, and Hamrah Podcast for everything that doesn't fit in a codebase.

Not just a developer — a builder who ships and sells.

Thirteen years ago I got paid to write PHP. Somewhere along the way I started getting paid to fix a hospital's patient records, argue about parking-lot pricing with a client at 9pm, and configure a CentOS box that shouldn't have gone down but did. That's the actual job description: Core PHP, Laravel, and MySQL are the tools, but the work is whatever the business actually needs — database schema one hour, a client's Nginx config the next.

Two of the things I built — a parking application and a set of tourism websites — I didn't just hand over, I sold them. That changes how you build. You stop asking "does this satisfy the spec" and start asking "will someone pay for this again next year." That question is why this site is split into products I'm selling, client work I'm proud of, and a lab for everything else I build because I want to.

What I build because I want to, not because someone's paying.

Also on the books — descriptions not yet verified against source

  • E-commerce SystemsLaravel · MySQL · JavaScript
  • Invoicing & PaymentsPHP · Cron · REST APIs
  • Dashboards & RBACLaravel · MySQL · jQuery
  • Voice Coaching AppReact Native
  • Hospital App — FlutterFlutter

How a developer ends up podcasting about social issues.

Somewhere in 13 years of writing PHP, I stopped thinking of myself as "a developer who codes what clients ask for" and started thinking of myself as someone who builds things end to end — the database, the deployment, the pricing conversation, the support call at 11pm. Once you've sold software directly to the people using it, you can't unlearn that the code was never the hard part.

That's the thread running through everything I do now. When I design a credentialing SaaS, I'm thinking about the same thing I thought about selling a parking app door to door: will someone actually pay for this, and will it hold up when they do. When I sit down to record Hamrah Podcast, I'm applying the same instinct — find the real problem underneath the surface conversation, then build something honest around it.

The tools keep expanding — Laravel gave way to React Native and Flutter, spreadsheet-driven client work gave way to SaaS thinking, and writing code gave way to also writing scope docs, recording episodes, and cutting documentary footage. The constant is the process: understand the real problem, then build the whole thing, not just the demo.

Writing about building software people pay for.

SaaS architecture decisions, what actually happens after you sell software to a real client, and notes from building in public. New, and building up.

Read the blog

Host of Hamrah Podcast.

Conversations on social issues, one guest at a time — guest research, interview, edit, and distribution, run the same way I'd run a product launch.

Listen & learn more

Tourism documentary-style video.

Between podcast episodes, I shoot documentary-style tourism content — the real story of a place, not the brochure version.

Watch the work

Have a product idea or a problem to solve?

Whether it's licensing a product, hiring me for a build, or a podcast collaboration — let's talk.

ssheikh111@gmail.com