How I work
The answers to what you are probably too polite to ask
Hiring a developer on another continent carries four risks: will they disappear, will the bill move, will I own the result, and can I actually reach them. Here are the answers before you have to ask.
Seven steps, every project
- 01
First reply
You send the brief through the form. I reply within one business day with either questions or a scoping call slot. If your project is not something I should take, I say so then — not after taking a deposit.
- 02
Fixed scope and quote
We agree what is being built in writing: pages, features, integrations, what is explicitly out of scope. You get a fixed price and a delivery window, not an hourly rate that drifts.
- 03
Deposit and start
40% to start, 60% on completion before handover. Paid by bank transfer or Wise. You receive a numbered invoice for your accounts.
- 04
Weekly build increments
Work goes onto a staging URL you can open at any time. You see progress every week. No black box, no month of silence, no surprise at the end.
- 05
Review rounds
Two rounds of revisions are included within the agreed scope. Changes that expand scope get quoted separately before any work starts — so the bill never surprises you.
- 06
Launch
Deployment, SSL, redirects, Search Console, analytics and a pre-launch QA pass. The site goes live indexed and measured, not as a blank shell.
- 07
Handover and aftercare
You get the source code, database, credentials and written documentation. 30 days of snag fixes are included. Everything is in your name and your accounts — you are never locked in.
Working terms
| Working hours | Mon–Fri, 09:00–18:00 PKT (UTC+5). That overlaps 05:00–14:00 UK time and 00:00–09:00 US Eastern. |
|---|---|
| Response time | Within one business day, always. If I will be unreachable for longer, you know before it happens. |
| Meetings | Google Meet or Zoom, scheduled in your timezone. I will take an early or late call to reach you — that is my problem to solve, not yours. |
| Language | All work, documentation and communication in English. |
| Payment | 40% deposit, 60% on completion. Bank transfer or Wise. Invoices issued for your records. |
| Currency | Quoted in USD by default. GBP, CAD or EUR on request. |
| Contract | A written scope document and a data processing agreement, both signed before work starts. |
| Ownership | You own the code, the content, the domain and every account. All of it is registered in your name. |
The timezone question
I am in Islamabad, which is UTC+5. My working day runs 09:00–18:00 PKT, and that overlaps 05:00–14:00 in the UK and 00:00–09:00 US Eastern. In practice that means a UK client gets most of their working day overlapping mine, and a North American client gets my evening — which is why I take calls outside those hours when a project needs it. Adjusting to your clock is my problem to solve, not yours.
What you own when it is finished
Everything. Specifically:
- The source code, in a repository in your name
- The database and all its content
- The domain, registered to you
- The hosting account, in your name, paid by you directly to the host
- Every third-party account — Stripe, analytics, Search Console — under your login
- Written handover documentation
I do not resell hosting and I do not hold your domain. Those are lock-in mechanisms, and a client who stays because leaving is painful is not a client relationship worth having.
What happens when something goes wrong
Things do go wrong — a plugin update breaks a layout, a payment provider changes an API, a host has an outage. Snags traceable to my work are fixed free for 30 days after launch. Beyond that, a maintenance retainer covers it, or I quote hourly for one-off fixes. Either way you will get a straight answer about whether something is my fault, and I do not bill for fixing my own mistakes.
Data protection and cross-border transfer
If you are in the UK or EU, engaging a supplier outside those territories is a restricted international transfer under UK/EU GDPR. Pakistan does not have an adequacy decision, so a transfer mechanism is required — I provide a pre-signed Data Processing Agreement with a completed UK International Data Transfer Addendum (or EU Standard Contractual Clauses) as a schedule.
This is the part most offshore suppliers cannot answer, and it is the thing that stops a procurement process dead. See the data processing agreement and the sub-processor list.
Tell me what you are building
Send the brief and you get a reply within one business day — either questions, or a scoping call. If your project is not something I should take on, I will say so then.
- Response
- Replies within 1 business day
- Hours
- Mon–Fri, 09:00–18:00 PKT — overlaps 05:00–14:00 UK, 00:00–09:00 US Eastern
- Booking
- Booking projects from October 2026