How we work
How we work, from first message to handover.
Written scope first. Backups before changes. Staging before live. The same careful order on every job, so you always know what’s happening and what comes next.
Written scope first. Backups before changes. Staging before live. The same careful order on every job, so you always know what’s happening and what comes next.
Tell us what is happening and we will reply with a clear next step.
Every job, from a one-hour fix to a full platform migration, follows the same order: understand the problem, agree the scope in writing, protect what you have, do the work somewhere safe, then hand it back with notes you can understand.
That order exists because most website disasters we’re asked to fix were caused by skipping a step: an update applied straight to a live store, a migration started before anyone listed the URLs, a “quick fix” made without a backup. The process below is how we avoid adding to that list.
What’s happening
In writing
Access & backup
On staging
Review & go live
Notes & next steps
Use the contact form, the quote form or email. You don’t need technical language. “The site shows a white screen since yesterday’s update” is far more useful than a guess at the cause.
Things that help us reply faster and more accurately:
If the site is hacked or down, choose Something’s broken on the form. Urgent requests are read first.
Before any payment or any change, you get a short written scope that says:
If we find something during the work that falls outside the scope, we stop and tell you what it is, why it matters and what it would cost. Nothing extra is billed without your written approval.
Investigations are scoped differently. For a hacked site or an intermittent server error, we can’t know the full extent until we look. In those cases we agree a diagnosis stage first, then quote the fix once we know what we’re dealing with.
We ask for the least access the job needs and never for passwords by email. Typically that means:
Created for us with the right role. You remove it when we’re done.
Only when the job involves files, logs or server settings.
For SEO and indexing work. Owner access is rarely needed.
Only for migrations, SSL and email-record work, and only when the change is due.
Then, before touching anything, we take a full backup of files and database, stored separately from your server. If your host already keeps backups, we still take our own: host backups are sometimes older than expected or stored on the same machine.
A staging site is a private copy of your website where changes can be made and tested without customers seeing them. Wherever your hosting and platform allow it, that’s where we work: updates, redesigns, plugin changes, performance work and migrations.
Some things can’t be staged: an active malware infection on the live server, a DNS change, or an urgent fix to a broken checkout. In those cases we work directly on the live site, but only after the backup in step 3, and we tell you beforehand.
Key templates on mobile and desktop: home, service pages, posts, cart and checkout.
Forms send, search works, logins work, payments reach the test or live gateway as agreed.
No new slowdowns: page weight, scripts and Core Web Vitals in lab tests.
For projects, you review the staging site and tell us what to change. When you’re happy, we deploy at a quiet time for your audience. Because we work from Pakistan (UTC+5), that often means the change happens overnight in US time or early morning in the UK. For UAE sites, one hour behind us, we agree a quiet window with you in advance.
After going live we repeat the key checks on the real site, because some issues only appear there: caching layers, CDN settings, live payment gateways, real email delivery.
You get a short written summary:
For migrations and SEO work we also monitor afterwards, checking 404s, redirects and Search Console, for an agreed period set out in the scope.
We’re based in Faisalabad, Pakistan (Pakistan Standard Time, UTC+5) and work with businesses in the UAE, the United States, the United Kingdom and Canada.
Every message gets a reply, even if the reply is “we’re on it, here’s when you’ll hear from us next.”
Websites are complicated, and occasionally a change has a side effect nobody predicted. When that happens:
If the problem was caused by our work, fixing it is on us.
For small fixed-price jobs, payment terms are set out in the written scope before work begins. For larger projects, payment is usually split into stages tied to milestones you can see.
Yes. We often handle a specific problem (a migration, a malware cleanup, a speed project) alongside an existing team. We agree who owns what before we start.
We can set one up on most hosts, or create a private copy elsewhere. If neither is practical, we’ll explain the risk and how we’ll limit it.
Yes, on request, before we review anything confidential.
info@webexpert.solutions · +92 345 7723858 · Faisalabad, Pakistan · Serving the UAE, US, UK & Canada