Laravel & AI full-stack developer, based in India
Every other market page on this site has to open by explaining why working with someone in Ahmedabad still works despite the distance. This one doesn't need that argument — I am based here, which means no overlap-hours negotiation, no cross-border invoicing question, and no "what time is it for you" at the start of every call.
There isn't one. Same business hours, same public holidays, same working day — a 10am call is 10am for both of us, not an arithmetic problem either side has to solve first.
Most of what I do is sell the same rigour into the US, the Netherlands and Finland — senior Laravel and AI engineering, one person, no account manager between you and the code. That work exists because it holds up against buyers who can pick anyone in the world and chose to check references first. The same standard applies here, minus the overlap-hours tax those buyers pay for working with someone eleven time zones away.
Full-stack means the actual stack, not a slide: Laravel on the backend, React or React Native when the frontend needs a serious application rather than server-rendered pages, Python when a task is genuinely a Python problem — data processing, an ML pipeline, a script that shouldn't be forced into PHP — and Rust where raw performance or a CLI tool actually earns the extra complexity it costs. AI work means integrating LLMs into a real product surface — retrieval, structured output, agents that a user can actually trust — not a chatbot bolted onto a landing page to say the word "AI" in a pitch deck.
Indian SaaS and product teams get pitched two extremes: a large agency with a bench and a sales process, or a junior freelancer learning on the job at a discount rate. Both have real costs — the agency's account-manager layer and the junior's cost of ramping up. What's between them is one senior engineer who has already been through the versions of these problems that get uncovered by demanding clients abroad, applying that to a team down the road instead of across an ocean.
What this gets used for: SaaS builds that need to be architecturally right from the start rather than rebuilt at 50,000 users; Laravel applications that have picked up years of shortcuts and now cost more to change than they should; AI features that need to survive contact with real data and real edge cases, not just a demo; performance work on a system that has quietly become the thing everyone is afraid to touch.
The honest limitation: I am one person, not a bench. For scope that genuinely needs more hands, I bring in developers from partner firms I have delivered alongside before — you interview each one, you know who employs them, and I stay the person accountable for the outcome. I don't pretend a one-person operation scales infinitely, and I'd rather say that here than have you find out mid-project.
Are you actually based in India, or is this outsourced?
Based in Ahmedabad, Gujarat, working directly — no outsourcing, no account manager relaying messages to someone else's engineer. The person you talk to is the person writing the code.
Do you only work with clients outside India?
No — most of the published case studies on this site happen to be international because that's the work that's been written up, not because Indian clients are out of scope. The engineering standard is the same either way.
Can we meet in person?
For teams in or visiting Ahmedabad, yes. For everyone else, video calls work fine — the same way they do for the US, Dutch and Finnish clients on this site.
Can you provide a full team rather than one person?
For scope beyond one senior engineer, I bring in developers from partner firms I have delivered alongside. You interview each one, you know who employs them, and I stay the technical owner — I don't keep an unnamed bench.
Something holding you back?
New build, rebuild, or adding AI to what you already have — I'll take a look and give you an honest perspective.