Loading
The questions operators actually ask before booking. No padding, no pricing theatre.
Ranges, not fixed menus. Projects run from a scoped sprint to multi-month programs. Pricing reflects founder hours, not a day-rate multiplier.
Usually within the week for a short diagnostic conversation; production work typically begins the following week once scope is agreed.
One working session. You describe where you are and what you want; I write back with a scope, timeline, and the first milestone. No multi-page proposals.
Yes, happily, for anything substantive. Standard mutual NDAs — no custom legalese required.
Milestone-based invoicing. Razorpay for India, Stripe or direct bank transfer for international. No surprise retainers, no auto-billing ambushes.
I do, personally, for the hard parts. A small dev team and a handful of contractors pick up scope that doesn't need me. Everything ships through me.
Remote, async-first, writing-over-meetings. One focused call a week, usually, plus written updates. No status-theatre.
Most clients are. Dubai, London, Singapore, Jakarta. I overlap each zone deliberately and write plenty of async updates.
You get a working conversation, not a change-order tangle. If it isn't right, we fix it or unwind cleanly. Reputation is the product.
When it's warranted. Not as a policy. Operating at a sustainable pace is how the quality stays up over a year, not a month.
Honestly and early. If something's going to slip, you hear it the day I know — not the day it's due. No silent creep.
Whatever you're already using, within reason. Slack or email for threads. Linear / Notion / GitHub for the work itself.
Almost exclusively. Most work ships to Dubai, the GCC, Southeast Asia, and globally-minded brands in India.
Occasionally, through contractors. It's not my strongest value — if design is the whole job, there are design studios I'll refer you to.
No. I don't have a sales team, procurement gauntlets are inefficient for my size, and I'd rather spend the hour writing code.
Yes — retainer arrangements for ongoing ops are common. Many engagements start as projects and convert into long-term relationships.
Rarely, and only in specific contexts where the relationship, the cap table, and the work all align. Most engagements are cash for work.
Not by default. Happy to build a good product that happens to touch crypto; not interested in pure speculation plays or token mechanics that bury the business model.
For HIPAA / SOC 2, yes — with the caveat that compliance is an audit relationship, not a claim. We work to the control framework; formal audits are run by certified auditors. PCI is case-by-case.
Existing open-source contributions (Freepik MCP, others) are on GitHub. For client code I can share architecture notes and anonymised extracts under NDA — not live codebases.