Less deck.More website.

An awkward sentence can cost less to fix than an awkward website. First, look at what people fail to understand or find. If the offer is buried, better structure and copy may be enough. If the site is difficult to maintain or the business has outgrown it, rebuilding makes sense. The diagnosis should not mysteriously require the most expensive treatment every time.

Give both demos the same job: find a service, answer a real customer question and get in touch. Try it on a phone. Notice where the route is obvious and where you hesitate. Taste still matters, but it gets some evidence to argue with. Two demos give us a comparison; they do not magically replace research with your actual customers.

Then we need useful feedback, not a polite yes. Is the offer wrong, the tone off, the structure confusing, or something missing? We refine a direction through the agreed revision rounds. Parts of both can work together if the result stays coherent. A changed brief is possible too; the extra work and cost are agreed before it starts.

Enough real material to understand the business, yes. A perfect content folder, no. Existing pages, brochures, photographs and recurring customer questions give us a start. We agree who writes, translates and approves the rest. Bring a brand book if you have one. Final content still needs a deadline: a layout built around imaginary sentences eventually sends someone a bill.

Distinct layouts, languages, content work, integrations and migration all affect the job. Twenty similar product pages may be simpler than three unusually demanding ones. The proposal separates the build from hosting, domain renewal, paid plugins, external services and optional care. You should be able to understand the cost after launch without enrolling in a course on agency invoicing.

Missing content, missing access and five people giving contradictory feedback. The timeline starts with an agreed scope and the necessary material ready. We identify one person who can approve decisions and collect comments together. New requirements can move the date; that is discussed before adding them. A calendar cannot negotiate with a photograph that has not been taken.

The move is planned before anything live changes. We check domain, hosting and email arrangements, identify existing pages worth keeping and map changed addresses. The new site can be prepared while the old one stays available. Email is a separate service, not collateral damage. Any necessary changes to it are agreed explicitly, alongside the actual switch and checks afterwards.

Research should answer a real uncertainty. If nobody knows why customers abandon a booking, watch them try to book. If the menu is unreadable on a phone, fix the menu. Interviews, prototypes and usability checks can be valuable. A wall of sticky notes is not valuable by the square metre. Agree the question before buying the ceremony.

Usually that is a question about the specific system, not a yes on a sales call. We check its connections, permissions, fees and the visitor’s route. A clear link may do the job; a deeper integration may be worth the work. Demos show the agreed journey. Live bookings, payments and data exchange are connected and tested during the final build.

Everyday edits shape the WordPress setup: prices, photographs, service text or new projects. The handover covers those tasks and the agreed administrator access, hosting, source files and licensed components. Another developer should have a clear starting point. Staying should be a choice made because the working relationship is useful, not because nobody can find the password.

Anything without a clear job or someone to maintain it. Start with the offer, the questions customers ask before buying and a clear next step. A blog nobody will write is a future apology, not a launch requirement. Extra languages and elaborate features can follow when justified. The proposal can separate the useful first release from the things that need more evidence.

Define a useful outcome before building: a relevant enquiry, a booking or a question answered without a phone call. After launch, look at actual enquiries, customer feedback and appropriately configured analytics together. A busy chart can hide a quiet inbox. The website can make a decision easier, but demand, pricing and service still belong to the business. Sales guarantees would be theatre.