Find your question.

No. Every interface is written by hand for the project it belongs to. A template is faster to start and slower to live with: the moment you need something it was not built for, you are fighting it.

Yes, and it is built on that assumption. Code is written to be read, the structure is documented, and handover includes a guide and a training session. Being the only people who can touch it is not leverage we want.

Every project is built and tested on a phone first. Most of your visitors will never see it on anything else.

That is what the revision rounds are for, and the design is approved in writing before any development begins. Nothing gets built on a design you have not agreed to.

It depends entirely on what is being built. A single landing page and a platform with accounts, roles and a database are not the same work. Tell us what needs to happen and you get a fixed figure in writing before anything starts.

Because a price list would be either wrong or meaningless. Two websites can differ tenfold in work and look similar from outside. We would rather quote what your project actually takes than quote an average that fits nobody.

Fixed for the scope you sign. It moves only if you ask for something outside that scope, and then only after you approve the addition in writing. Nothing is added to your bill without your written agreement.

In stages tied to progress, set out in the scope you sign. You see working previews before the final payment falls due, so you are never asked to pay for something you have not seen.

Set in the scope before work begins, in working days. It starts counting from three things together: the first payment, all your materials received, and the requirements approved.

The clock pauses. The timeline extends by however long we waited, and that is not treated as anyone breaking the agreement. It is the most common reason a project runs late.

Sometimes, if it is technically possible without hurting the work. It is agreed in writing before we start. We will not accept a deadline that we would have to damage the project to meet.

The project files and code, access to every account and service, ownership of the domain and hosting, a plain guide to running it, and a session walking you through it. All of it recorded in a signed handover note.

You do. On full payment the project and its code pass to you completely, and you are free to use it, develop it, or hand it to anyone else. There is no licence to renew and nothing held back.

Yours, from the start. Accounts are registered in your name and with your email. We take temporary access only to set things up, and it is withdrawn at handover.

No. That is the point of registering everything in your name. The keys were always yours, so there is nothing to take back and nothing to switch off.

A small credit line sits at the bottom of the page. It is quiet, it is normal on professional work, and it tells visitors a specialist team built the site. If you would rather it were not there, it can be removed.

Anything that is a fault in our own work is fixed at no charge during the warranty period, which starts from the signed handover note. We reply to reports within two working days.

New features, ongoing content changes, anything altered by you or a third party after handover, outages at external services, and problems caused by login details being shared or mishandled.

Yes, under a separate maintenance agreement covering monitoring, backups, updates and regular changes. It is optional and quoted separately.

That is what the training session is for. For most routine changes you will not need us. When you do want us to do it, you grant temporary access and it is returned when the work is done.

No, and nobody honestly can. We build sites structured so search engines can read and rank them properly, and we set up measurement so you can see what is actually happening. Guaranteed rankings are a claim, not a service.

Yes. Everything is done remotely, and the agreement, payments and handover work the same way wherever you are.

Often, yes. Send us what exists and we will tell you honestly whether repairing it or rebuilding it is the better spend. Sometimes the honest answer is that a rebuild costs less than the repair.

Always, before any work begins. A framework agreement plus a scope of work that names exactly what is included, what is not, how long it takes and what it costs. Both are signed before the first line is written.