Working together, wherever you are.
I am in Lahore, Pakistan, and I say so. What matters is whether the work gets done, the price is fixed and the paperwork works in your country. This page explains the practical side: time zones, money, contracts, data and communication.
1. Time zones are not a problem
Pakistan does not observe daylight saving. Calls are scheduled in a window that works for your day; everything else is handled in writing.
| Your location | Typical call window (PKT) |
|---|---|
| US East Coast | 19:00–23:00 PKT (09:00–13:00 ET, winter) |
| UK | 13:00–19:00 PKT (08:00–14:00 GMT) |
| Central Europe | 13:00–19:00 PKT (09:00–15:00 CET) |
| UAE / Gulf | 11:00–18:00 PKT (10:00–17:00 GST) |
| Australia | Async by default; early-morning calls by arrangement |
Outside a call window, email and WhatsApp still arrive; I answer them the next working morning.
2. Money: USD by default
- Currency: USD by default. EUR or GBP invoices are available on request.
- Payment: bank transfer or Wise. Payoneer is available. Card processing through a merchant of record can be arranged on request.
- Structure: 50% to start, 50% on delivery, unless the written scope says otherwise.
- Invoice entity: AbdulTSD Solutions, Lahore, Pakistan. The invoice shows the service, the period and the tax treatment.
- Tax: EU B2B services are generally subject to the reverse-charge mechanism. The invoice states the applicable treatment; confirm the wording with your accountant.
3. Contract, NDA and DPA
Every project starts with a written scope: deliverables, exclusions, price, timeline, payment milestones and change control. The scope is the contract attachment.
- NDA: available on request, before you share access or credentials.
- DPA: available where the work involves EU or UK personal data.
- Transfers: where personal data moves from the EU/UK to Pakistan, the transfer terms are based on the EU Standard Contractual Clauses (and the UK Addendum where relevant).
- Governing law: Pakistan law by default. For international contracts I will agree to a neutral arbitration seat (for example London) if your procurement team requires it. That is a change of forum, not a change of where the work happens.
- Liability: capped at the fees paid for the engagement, excluding indirect losses.
4. Communication
- Email for decisions and written scope.
- Cal.com for calls; WhatsApp for quick questions and urgent fixes.
- Progress updates in writing, with screenshots or links where useful.
- Reply within 6 working hours, Monday–Friday. Urgent care-plan clients get same-day triage where capacity allows.
5. Data protection in practice
For a typical fix or build I may process contact details, business information, hosting and CMS access, analytics exports and any files you send. I do not sell data, and I do not use client data to train public models.
- Access is limited to the accounts needed for the job.
- Credentials are transferred through a password manager or a one-time link, not plain email where avoidable.
- Access is removed at handover unless you ask me to keep a care plan.
- Analytics on this site is consent-gated; see the cookie policy.
6. Security and continuity
The studio recovered its own site after a webshell compromise in October 2026. The incident note is public because a fix-and-care provider should be able to explain its own recovery.
7. What you can ask for before paying
- A sample scope and a sample invoice.
- The NDA and DPA templates.
- A reference call with a past client, where that client has agreed.
- The security note and the accessibility statement.
- A paid, fixed-price health check if you want to test the working relationship before a build.
8. What I will not do
- Claim a local office, team or phone number that does not exist.
- Publish your name, logo or results without written permission.
- Promise a price before the scope is understood.
- Use your data for anything outside the engagement.
Questions before the call are welcome. Email contact@abdultsd.com or message +92 348 624 2544.