Seven years shipping, and a strong opinion about scope.

I’m Ahmad. I build software for people who have a problem worth solving and no engineering team to solve it — mostly founders, small business owners, and operations leads who have been quoted three wildly different numbers by three different developers and cannot tell which one is real.

Most of what has gone wrong on projects I have been called in to rescue went wrong in the first two weeks, before anyone wrote code. Somebody quoted a price against a brief nobody had stress-tested, and everything after that was two people discovering they had agreed to different things. So I front-load the part everyone else rushes: a week of discovery, a written scope, and then one number that does not move.

The other thing I insist on comes from running my own software. I built and still operate an ERP that manufacturers close their books on, which means I have been the one holding the pager when a migration went sideways on a tax deadline. It taught me to write documentation for the person who comes after me, to demo weekly instead of disappearing, and to make sure a client can walk away with everything — because I know what it does to a business to be trapped inside software it cannot leave.

Most projects are me end to end. When a brief is genuinely bigger — real design work, web and mobile in parallel, a date that will not move — I bring in designers and engineers I have already shipped production work with, and I lead the engagement myself. You meet them in week one and they stay until launch. It is a team assembled for your project, not an agency with a bench to keep busy.

I work from Pakistan and shift my day to meet clients in the US, UK, Europe and Australia. Seven-plus years of production work, AI-focused since 2022. Before I took clients directly I was the engineer inside other people’s teams doing exactly this, which is how the delivery habits got formed.