Blog · SaaS & software business
Notes from building software people actually pay for.
Architecture decisions, what happens after you sell software to a real client, and the unglamorous parts of turning a dev skillset into a business — written as it happens, not cleaned up after the fact.
Posts
All posts
-
Sep 8, 2026·6 min read
Reusing a foundation across two businesses, without turning it into a framework
Wander Yak and Diksha Learning Center run on the same admin/CMS/RBAC bones under completely different businesses. Here's why that's deliberate reuse, not laziness — and why I stopped short of generalizing it into "one system for everything."
-
Aug 22, 2026·4 min read
Killing the license-plate OCR feature before shipping it
I built automatic plate scanning into the parking app. It's not in the shipped product. What "not reliable enough yet" actually looks like from the inside, and why I'd rather ship a manual override than a feature that's wrong 1 time in 10.
-
Aug 5, 2026·5 min read
A coaching institute asked for a website. It actually needed an admissions system.
"Put our courses online" was the request. The real bottleneck was staff time spent chasing phone enquiries into paid enrollments. Notes on the gap between what a client asks for and what the business actually needs.
-
Jul 18, 2026·7 min read
Why I didn't reach for Laravel to build a hospital management SaaS
The hospital SaaS runs on a custom PHP MVC, not a framework. Not a "frameworks are bloated" take — the actual reasons, tied to who runs this software and what their servers look like.