What does a project cost?
It depends on what you're building, but you won't be surprised. You get a written number for a defined scope before any work starts. If your budget and the problem don't match, I'll tell you early rather than after you've spent.
When could we start?
It depends on my current capacity and the size of the first milestone. After the initial conversation, I'll tell you honestly when I can begin and include the start date in the proposal. I don't accept work and quietly leave it waiting in a queue.
What if my project is small?
Small is usually how these start. The first milestone is deliberately contained — one process, one system, one decision — because it's the cheapest way for both of us to find out how the other works. Most engagements grow from there, once the first piece is running and the next bottleneck is obvious. Some of the most useful things I've built began as one annoying process someone finally wanted to stop doing by hand. What doesn't fit is a one-off afternoon's fix: not a bad thing to need, just not what I'm for, and I'll point you somewhere better.
Who owns the code and the intellectual property?
You do, from the first commit. Work happens in a repository you own, the IP is assigned to you in the contract rather than licensed to you, and I'll sign an NDA whenever you'd like one.
What if it isn't working out?
The first milestone is fixed in scope and price precisely so that ending there is a clean, cheap decision rather than an argument. I'd much rather you stop after one milestone than spend six months regretting the third.
How quickly will I see something working?
Most first milestones land in weeks rather than months, and that's deliberate. You should see working software early enough to change your mind while changing it is still cheap.
How do you use AI while building software?
I use AI to accelerate research, implementation, testing, debugging and documentation. Architecture, security decisions, code review and accountability remain mine. It helps me deliver more quickly; it doesn't replace engineering judgment or become an excuse for code nobody understands.
Can you take an idea to a launched product?
It's a large part of the work. Weavzi and Vyoma Veda Astro were both taken from nothing to complete, working systems, including the parts founders tend to discover late: accounts, permissions, payments and the operational tail behind the demo.
What if what we have is breaking under load?
That's a different job from building new, and it's one I've done for years. I've run production systems handling 20 billion events a day and 1.5 billion requests a day, and cut response time on a live AI product from twelve seconds to five. The first step is almost always measurement, not a rewrite — most systems are slow somewhere nobody has looked.
Can you lead a team, not just write the code?
Yes. I've worked as a lead engineer and a founding engineer, which means architecture and delivery and the people side of it, not just the commits. On smaller projects I build it myself because that's faster. On larger ones I bring in and direct engineers I've worked with before, and you still have one person to talk to.
Why not hire a full-time engineer or agency?
If the work is permanent, continuous and central to your company, building an internal team may be the right decision. I make sense when you need senior execution now, before a full team is justified, or when one important system needs focused ownership without a long hiring process. You work directly with the person who designs it and answers for it, not with an account manager relaying to someone you never meet.
Do you work with manufacturing businesses?
Yes. It's some of the work I know best. Weavzi is a full factory system I built for textile and job-work manufacturing, so terms like job-work billing, subcontractor movement and shop-floor tracking don't need explaining from scratch.
What if I already have a developer or a team?
Then what you probably need isn't more hands, and that isn't what I'd be. It's usually one of two things: a decision nobody has the context to make yet, or a system nobody on the team has the room to own. I'll work alongside them on either, and say so plainly if the honest answer is that you just need to hire.
Can you handle sensitive or regulated data?
Yes. I've built production systems on HIPAA and SOC 2-aligned architecture for health data, where access control, encryption and audit trails aren't features you add later. If your data carries obligations, tell me early and they shape the design rather than getting bolted on at the end.
Do you work with clients in other countries?
Yes. I spent nine years in the US building for eBay, Branch Metrics and Descript, so I know from the inside how teams there expect to work: the review culture, the planning rhythm, the standards a piece of work is held to. I deliver to teams several timezones away, which is how Yuna was built. Tell me your working hours early and we'll set the overlap deliberately rather than discovering it in month two.
