Working together
I build from India and deliver remotely. That works well, but only if the practical things are clear from the start: when we can talk, how the money is structured, who ends up owning the code, and how you know what is happening on a day when we are never online together. All of it is below.
01The time difference
Calls run in one of three windows. Here is what each one is on your clock today: if your country has just changed its clocks, this table has too.
LondonBST
United Kingdom
New YorkEDT
US East
ChicagoCDT
US Central
Los AngelesPDT
US West
DubaiGST
UAE
SydneyGMT+11
Australia
The windows are morning (10 am – 1 pm), afternoon (2 – 5 pm), evening (6 – 8 pm), Indian Standard Time. The booking box on the contact form reads your browser's timezone and labels every window on your own clock, so you are never converting hours in your head.
02How it runs
The same five steps whether you are two streets away or eight time zones away. Nothing starts building before the scope and the dates are written down.
We walk through how the work happens today, where it breaks and what a good result looks like.
Workflow, data model and the smallest useful first version, agreed in writing with clear milestones.
Built in short iterations with regular demos, so you see working software early and steer it.
Deployed to your own hosting and repository. The code, data and accounts are yours.
Monitoring, fixes and new features after launch, as an ongoing maintenance engagement.
03Money
The rate is published because you should not have to ask for it. What it adds up to depends on the scope, and that is written down before anything starts.
From$25/hour≈ £20 / ₹2,000
Quoted in US dollars. Bank, platform and currency-conversion charges are paid by the client, so the amount quoted is the amount received.
It sits just under the Indian market average for this level of work, from a developer who also designs and runs the growth side. The same mid-level work is quoted at $53–84 an hour in the UK and $85–135 in the US, so a build here lands well under a local quote without dropping to a rate that only buys junior work.
The hourly rate is what a quote is built from, not how you are billed. You get the scope, the milestones and the dates in writing before any work starts, and you pay against those milestones rather than an open-ended clock. Hourly billing is for small changes and ongoing work.
How many workflows the system has to cover, how much is genuinely new versus a pattern that already exists, the software it has to talk to, and whether you want the growth side (website, content, SEO) as well.
Describe what you need and you get a scoped quote with milestones and dates before any work starts. If the number does not suit the budget, the scope is what changes, in writing, not the quality of what gets built.
04Straight answers
Next step
One message with the problem, a rough timeline and a budget range is enough to get a scoped reply. Tick the call box and pick a window: it will be shown on your clock, not mine.