Articles
I've built 30+ products over 20 years — some shipped and still running, some sold, some abandoned, some that never made it past a prototype. These articles cover what that actually looks like: where AI-powered products break in practice, how to scope an MVP when you've watched your own fail to validate, and what it costs to wear all the technical hats at once. Practical and specific — not startup advice for its own sake.
A marketing agency founder came to me with an operations problem: five low-ticket clients consuming more than their fair share of her team's time. Twenty minutes in, I realized the answer had nothing to do with automation — it was a pricing decision she hadn't made yet.
A free calculator for every upfront cost before signing a Dubai lease — rent by cheque count, security deposit, broker fee, DEWA deposit, Ejari, and appliances — plus full monthly living costs. Built after three consecutive apartment moves where the total still managed to surprise us.
There are seven ways to test an idea before you write a line of code. Each one answers a different question. Picking the wrong tool gives you the wrong signal — and you end up building something the signal never actually supported.
The reason MVP quotes vary wildly isn't vendors — it's vague briefs. A well-scoped MVP brief produces accurate quotes, fewer change orders, and a product that tests the right thing. Here's how to write one.
TinyHR started from a real incident — a Dubai business hit with fines because nobody was tracking renewal deadlines. I built a working tool, then spent time asking people if the problem was widespread. Here is what the validation showed, and why I stopped.
Both methods end with working software deployed to real users. But they exist to solve completely different problems — and confusing them is expensive.