The questions worth asking first

Send a message describing the problem — a couple of sentences is enough. I reply within one working day, and if it looks like a fit we book a short call. Nothing is charged before a written scope is agreed.

The packages page gives honest starting figures. The final number depends on scope, and you receive it in writing before any work begins. It does not change mid-project unless you ask for something that was not in the scope.

A small site is typically two to five weeks. An application is six to twelve. You get a timeline with the scope, and a live link from the first week so progress is visible rather than described.

Yes, entirely. It sits in your own repository under your account, and you keep every credential. There is no licence fee and nothing is held back to keep you tied in.

Every project includes a fixed window of post-launch fixes. Beyond that, care plans cover ongoing changes monthly, or individual work can be quoted as needed. There is no obligation to take a plan.

Typically split across milestones — a deposit to begin, a payment at an agreed midpoint, and the balance at handover. Bank transfer, EasyPaisa and JazzCash all work.

Often, yes. I will review it first and give an honest answer about whether improving it or rebuilding it is the better use of your budget — including when the honest answer is that it does not need me at all.

Not by default. Most sites of this kind are faster, cheaper to host and safer to maintain as a static build. If a project genuinely calls for WordPress, I will say so rather than talk you out of it.