From blank repo to paying customers.
I'm Mahesh — a software engineer in Vancouver, seven-plus years in production. Days, I work on release infrastructure for FortiClient at Fortinet. The rest of the time I run TapNGame, a sports booking platform live on the App Store and Google Play, and build custom platforms for businesses like Dakshin Foods.
Two products, two stories.
real users, real money — not toy demos
Founder · Live productTwo players tap the same court at the same second. Only one should win.
TapNGame — founded and operated solo: player app, venue dashboard, admin console. Live in Metro Vancouver.
Client work · In productionA family kitchen was paying rent on software that couldn’t run their business.
Dakshin Foods — a custom subscription, kitchen, dispatch, and delivery platform. Built for one client, run by the owner herself.
Meanwhile, 9–5Release infrastructure for FortiClient at Fortinet — endpoint security on millions of machines.
The short version, over coffee.
I take software the whole way. I write the spec, build the system, ship the release, watch the metric, read the support email, and write the patch. Seven-plus years of that — across mobile, web, backend, and release infrastructure — taught me that the hard part of software was never the code. It's the thousand small decisions between an idea and a user getting what they came for.
What's open on my machine this week.
TapNGame multi-city architecture
Tenant-aware schemas and per-city pricing — making the Vancouver product portable without rebuilding it.
AI-native release verifier
An LLM-as-verifier pipeline for release readiness — a structured eval harness with a confidence score the human can override.
Pickup-game discovery agent
A Claude-powered agent that turns "I want to play badminton tonight near me" into a real booking.
Let's talk.
Hiring for a role that needs real ownership — or running a business that needs software built around it? Either way, I read everything that comes through here.
