मुख्य सामग्री पर जाएँ

सामान्य प्रश्न

वे सवाल जिनका जवाब पहले ही मिल जाना चाहिए

शुरू करने से पहले क्लाइंट असल में जो पूछते हैं — यहाँ जवाब दे दिए हैं, ताकि पूछने के लिए ईमेल न लिखना पड़े।

What does a project typically cost?

Pricing is scope-based rather than hourly for most work, because an hourly rate tells you nothing about what a feature actually costs to build well. After a short call about scope and constraints, you get a written proposal with milestones and a fixed price against each one. No number is quoted before that conversation — a quote without scope is a guess, and guesses get revised upward later.

How long does a typical build take?

Most engagements run four to twelve weeks depending on scope. An audit or architecture review is usually one to two weeks. The timeline is agreed before work starts and tracked against milestones you can inspect. If something is going to slip, you hear it when I know it — not at the deadline.

Can you take over an existing codebase?

Yes — legacy rescue is a large part of the work. Upgrading an old Laravel application, untangling a codebase the original team left behind, or stabilising something that breaks every deploy. The first step is always a written audit: what is actually there, what is risky, and what order to fix it in. You own that document whether or not the work continues.

Will you sign an NDA?

Yes. Send yours and it gets signed before any detail is discussed. Client work is treated as confidential by default whether or not paperwork exists. On ownership: you own the deliverables outright once final payment clears, and that goes in writing rather than being assumed.

What happens after launch?

Every delivery includes a warranty window for defects — if something shipped broken, fixing it is not a change request. Beyond that, ongoing support runs as a monthly retainer. Handover documentation is written either way, so nobody is left depending on one person's memory.

Do you work with teams, or only solo?

Primarily solo, which is why the work is deliberately scoped — you deal with the person writing the code, not an account manager relaying messages. I also work inside existing teams: code review, architecture, and unblocking developers who are stuck. For builds that genuinely need more hands, trusted specialists are brought in and stated upfront, never quietly subcontracted.

Which timezone do you work in?

Core hours are 10:00–19:00 IST, with flexibility for calls outside them when a project needs it. Written progress updates at every milestone mean you never have to be awake at the same time as me to know where things stand.

How are payments structured?

Milestone-based: an agreed percentage to start, the balance across delivery milestones. Every payment maps to something you can inspect, so you are never paying for progress you cannot see. International transfers and Indian payments are both straightforward. Exact terms go in the agreement.

अगर आपका सवाल यहाँ नहीं है, तो शायद वह अच्छा सवाल है।

सीधे पूछिए