What currency will I be invoiced in?

GBP. Quotes, milestones and the final invoice are all written in GBP so you are never comparing a converted figure against a local supplier's. Regarding tax: VAT at 20% once you are registered — my invoices are outside the scope of UK VAT and you account for them under the reverse charge.

Who owns the website when it is finished?

You do, completely. The domain is registered in your name, hosting sits in your account, the code lives in a repository you control, and any payment provider account is opened in your business name. Credentials are handed to you as they are created rather than at the end, so you are never locked out of your own site.

Do you actually work with businesses in Wigan?

Yes, remotely. I work with British clients from Islamabad, quoting in GBP and invoicing in GBP. I have no office, address or phone number in Wigan and will not pretend otherwise. If your project needs someone physically present, hire locally — I will say so in the first reply rather than after a deposit.

How much does a website cost in Wigan?

A business website starts from £65 and goes live in about three days. An e-commerce build starts from £120 in around seven days, and a custom application from £160 in ten. Those are starting figures — the exact number is fixed in writing once scope is agreed, and it does not move after that.

How long does a Wigan project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

What hours will you be available to us in Wigan?

My standard day lands at 05:00–14:00 your time — about 5 hours of genuine overlap with a normal Wigan working day. That is enough for one reliable daily window rather than constant back-and-forth, so Wigan projects run on written updates plus one scheduled call a week.

How do you handle our customers' data under UK GDPR?

Your customer data is governed by UK GDPR and the Data Protection Act 2018, and sending it to a developer in Pakistan is a restricted transfer. That is resolved by a pre-signed DPA with a completed UK International Data Transfer Addendum, published on this site and pre-signed before you send an enquiry — not drafted after you ask about it.

North West England · United Kingdom

Website maintenance and support in Wigan

Almost every website emergency I get called into was preventable and cheap to prevent: an expired domain, an unpatched plugin, a backup nobody had ever restored. Maintenance is not a subscription for reassurance — it is the specific set of checks that stop those three things from happening to you. For Wigan businesses, quoted in GBP from $45, typically live in ongoing monthly.

What website maintenance and support includes for a Wigan business

Fixed scope, agreed in writing before development starts. From $45, typically live in ongoing monthly.

Core, plugin and dependency updates applied on staging first, then live
Offsite backups taken on a schedule and test-restored quarterly, because an untested backup is a hope
Security patching, plus header and SSL certificate checks
Uptime and certificate-expiry monitoring, with alerts that reach a human
Domain and hosting renewal watch — the single most common cause of a site going dark
A monthly allowance of small content and layout changes, with anything larger quoted separately
Search Console and analytics checked monthly for coverage errors and traffic anomalies
A short written monthly report: what changed, what was found, what needs a decision

The terms for a British client

Starting price	From $45, quoted and invoiced in GBP
Typical timeline	ongoing monthly once content is supplied
Tax position	VAT at 20% once you are registered — my invoices are outside the scope of UK VAT and you account for them under the reverse charge
Data protection	UK GDPR and the Data Protection Act 2018 — resolved by a pre-signed DPA with a completed UK International Data Transfer Addendum
Payment rails available	Stripe, GoCardless for Direct Debit, and Klarna or Clearpay where basket sizes justify it
My day in Wigan time	05:00–14:00 — about 5 hours of overlap

Why this matters for United Kingdom specifically

UK local search is the most saturated in the English-speaking world, so a merely competent site does not win the job — the quote form does. Every UK build I ship is specified around the enquiry step first and the homepage second.

What actually ships when a Wigan project goes live

A handover for a Wigan client is not a link and a login. It is the repository, the hosting account in your name, the domain registered to you, the payment provider account under your business, and a written record of every credential as it was created rather than dumped in one email at the end.

The test I apply is uncomfortable but correct: if I disappeared tomorrow, could another developer pick this up on Monday without calling me? If the answer is no, the handover is not finished. That standard is why the documentation takes a day I do not bill separately — it is part of the build, not an upsell.

Retail and e-commerce in Wigan

A store is judged at the checkout, not the homepage. For United Kingdom that means the payment methods have to match what people actually use — Stripe, GoCardless for Direct Debit, and Klarna or Clearpay where basket sizes justify it — and the cart has to survive a slow connection and a page refresh. Most abandoned baskets are not indecision; they are a checkout that broke and gave no reason why.

The second issue is stock truth. A product page saying "in stock" when it is not costs you the sale and the customer, and the fix is unglamorous plumbing between wherever your stock actually lives and the storefront. That is worth a day of work far more than the product photography carousel is.

A mobile layout nobody tested on a real phone

Desktop-first builds fail in predictable places: a navigation menu that cannot be closed, a table forcing the whole page sideways, tap targets too close together, and a sticky banner sitting over the button. Each one is invisible on a laptop and each one loses customers.

Most visitors to a Wigan small business site arrive on a phone, so I design at phone width first and widen from there. That ordering is not a stylistic preference — it is the only way the small screen gets the attention the majority of your traffic deserves.

What I am not claiming about Wigan

I have no office, postal address or phone number in Wigan
I cannot meet you in person, and if that is a requirement you should hire locally
I am not claiming existing clients in Wigan specifically — my live work is listed on the work page and you can check it
Nothing on this page is a guarantee of search rankings, which no developer can honestly offer