Questions, answered
Before we
start — the answers.
Everything people ask before the first call, grouped by topic. If your question is not here, send it through the contact form and it will probably end up on this page.
01 — Working together
Location, stacks, ownership and the practical details.
Do you work remotely?
Yes, remote only, from Ahmedabad, India (UTC+5:30). Working hours overlap with Europe every day and with North America every morning US time.
Which technologies do you work with?
Laravel and PHP first, then Python, TypeScript, SQL, REST and GraphQL APIs, cloud deployment and AI integration. If your stack is something else, ask; the answer is usually yes.
How quickly can you start?
Usually within one working day of agreeing the scope. The 7-day website package starts on the kickoff call; hourly work starts once you approve the written estimate.
Who owns the code?
You do. Work is delivered to your repository and your servers, with no lock-in to me or to any platform.
Can you sign an NDA?
Yes. Send yours, or I can provide a short mutual NDA before we discuss anything sensitive.
How do payments work?
Agreed before any work starts. Hourly work is invoiced for the hours used; fixed-price work is invoiced on the milestones we agree at kickoff.
How do we communicate?
WhatsApp, email or a call, with one accountable engineer from the first conversation to the handover.
02 — Forward deployed engineering
What the role is and why it is different from an agency or a consultant.
What does "forward deployed" mean?
The term comes from engineers who are sent out to work directly with the customer rather than staying inside a product team. A Forward Deployed Software Engineer sits with your business, understands the actual problem, and builds and deploys the solution inside your environment.
How is that different from a consultant or an agency?
A consultant usually advises and hands over a document; an agency routes you through account managers and a changing team. A forward deployed engineer is one person who talks to you, writes the code, deploys it and stays accountable for it working.
Do forward deployed engineers have to be on site?
Not any more. I work remote only, embedded in your tools: your repositories, your chat, your meetings and your servers. The "deployment" is into your problem, not your office.
Which companies use this model?
Palantir made the title well known, and similar roles exist under names such as solutions engineer, implementation engineer or deployment strategist at many software companies.
How is forward deployed work priced?
Two ways: a fixed price for a defined outcome, such as the website-in-7-days package, or by the hour from $10 depending on the stack, with a written estimate first for everything else.
How do I start?
Send a short description of what is slow, broken or blocked. You get a reply within one working day with questions, then a scope or an estimate.
03 — The 7-day website package
What the fixed price covers and what happens around it.
What do I need to provide?
Your domain, a server or hosting login, and the requirement: which pages you want, your text and images, your logo and brand colours. During the 7 days I also need feedback from you within a day so the schedule holds.
I do not have a server yet. Can you help?
Yes. I recommend hosting that fits your budget and set it up as part of the package. Hosting and domain fees are paid by you directly to the provider.
Is the site really dynamic?
Yes. It is built on Laravel with an admin where you edit pages, products or services, images and enquiries yourself. You do not need a developer for text changes.
Can the site sell products online?
A catalogue with enquiries and WhatsApp ordering is included. Online payments and a checkout are extra and are quoted separately or built at the hourly rate.
What does basic SEO cover?
Page titles, meta descriptions, heading structure, sitemap, robots rules, structured data, fast loading, and submission to Google Search Console. Ongoing SEO campaigns and content writing are not included.
What happens after the 7 days?
Once the site is deployed and working, the job is done. If you need changes later, message me and we agree a fixed quote or work hourly from $10 per hour, depending on the stack.
What if the requirement changes during the week?
Small adjustments are part of the week. A larger change in scope is quoted or billed hourly so the 7-day price stays at $399.
How do we communicate?
WhatsApp, email or a call, with one accountable engineer from the first call to the handover.
04 — Upgrading old software
AI, dashboards and performance for systems you already run.
What counts as "old software"?
Any system you already run: a custom PHP or Laravel app, CodeIgniter, WordPress with plugins, a Node or Python backend, or an off-the-shelf tool with a database you can reach. If it has data, it can have a dashboard; if it has users, it can be faster.
Do you need the source code?
For AI features and performance work, yes. For a dashboard, database access is enough: the reporting layer is built beside your software and reads from it without touching how it works.
What happens in the free 10 hours?
An audit of the code and the database, a short written plan, and the first improvement live: usually one dashboard screen or one fixed bottleneck, so you can judge the work on something real.
What does "AI" actually mean here?
Practical features that use your own data: search that understands questions, automatic replies and reminders, extracting fields from documents and photos, forecasting demand, flagging unusual activity. Not a chatbot for its own sake.
Will it break what already works?
No. Dashboards are added as a separate module, performance fixes are measured before and after, and nothing changes in production without your approval and a backup.
What happens after the 10 hours?
You decide. Continue hourly from $10 per hour with a written estimate for each step, agree a fixed price for a defined scope, or stop. The work already done stays yours.
05 — Hourly engineering
Estimates, tracking, team and payment for hourly work.
Why do rates differ by stack?
Laravel and PHP are my home ground, so that work is quickest and cheapest. Python, TypeScript, mobile backends, AI and rarer stacks take more care, so they carry a higher hourly rate. The tier is agreed with the estimate, before any work starts.
Is there a minimum number of hours?
No retainer and no minimum block. Small tasks are welcome; you get an estimate first so you know what a task will cost.
How are hours tracked?
Every task has an estimate up front and a log of hours as the work happens. You see the log and the summary with each report.
Which technologies do you work on?
Laravel and PHP first, plus Python, TypeScript, SQL, APIs, cloud deployment and AI integration. If your stack is something else, ask; the answer is usually yes.
Can a task switch to a fixed price?
Yes. If the estimate is large or the scope is clear, I can quote a fixed price instead, including the 7-day website package at $399.
Who does the work?
Me, directly. For larger builds a vetted team of 50+ can be brought in, 90% of them with 10+ years of experience, agreed with you before it happens.
How do payments work?
You are invoiced for the hours used, on a schedule we agree before the first task.
06 — Still a question?
ask it directly
Ask me anything.
Questions get a reply within one working day, from me, not a bot.
Ahmedabad, India · IST (UTC+5:30) · --:-- IST · Mon–Fri 09:00–18:00 IST · US & EU overlap daily