About
I am an engineer by training, with an MBA in IT. My start in software goes back to college, where I cracked a C Marathon and trained under Yashavant Kanetkar, the author of the C programming classic Let Us C. My career started in 2006. In the years before I struck out on my own, I worked across the industry and kept running into the same two problems, again and again, at all kinds of teams.
The first was what tends to happen after the deal closes. A client signs, and then, at a lot of teams, the attention quietly drops. I hated seeing it. So I built my companies around the opposite habit: stay close after the contract, not just before it. That is why close to 90% of ScalaCode's clients come back for their next project.
The second was scalability. Too many teams build for the demo and ignore what happens when the product actually grows. I build for the version of a product that has real users, not just the one that passes the first review.
I started ScalaCode in 2012 on those two ideas. More than a decade later it has shipped over 500 projects for more than 1,300 companies. I carried the same habits into iWebServices, which helps small local businesses get online and win customers. Different market, same rules.
Away from work, I am a husband, a father to two little daughters, and a serious cricketer. I bat in the middle order, right handed, bowl medium pace, and wear number 9. Most of what keeps me interested in technology is the same thing it always was: using it to solve problems that are actually real.
How I help
Where founders, CTOs, and teams bring me in.
Building offshore engineering teams you don't have to babysit. Vetting, structuring, and running a software partner that acts like your own team, not a vendor you have to chase.
Scaling software without rebuilding it. The architecture and delivery calls that hold up as you grow, made before they turn expensive.
Putting AI to real work. Cutting through the hype to find where AI actually helps your product or your delivery, then building it.
Getting a startup from idea to shipped product. The first build, the first team, and the first 30 days that decide the whole thing.
Digital transformation that sticks. For established businesses moving real operations online, not slideware that never ships.