Questions, answered clearly.

Yes. We first inspect the theme, builder, plugins and content, then recommend whether a careful redesign inside WordPress or a cleaner rebuild is the safer route.

Usually. Useful and accurate content can be retained while the structure, visual system and customer journey change. We identify what will be reused before quoting the migration work.

Yes. Mavie can plan, design, build and launch a new website, from a focused one-page site to a fuller business website.

Yes. The platform should fit the editing needs, integrations, ownership and ongoing cost. WordPress is one option rather than the automatic answer.

Yes. A single page, form or mobile journey can be improved without automatically rebuilding everything. We check whether the isolated change can be made safely in the existing site first.

That is the preferred direction. We agree which parts you need to control and provide an appropriate editor, handover and focused training rather than leaving you dependent on a developer for ordinary changes.

Yes, where the feature and provider suit the business. These are scoped separately because a payment link, a booking flow and a complete online shop have very different responsibilities.

Yes. We measure the current site and inspect hosting, themes, plugins, images, fonts and third-party scripts before proposing changes. We do not promise an arbitrary score without seeing the system.

Usually. We reproduce the fault, check recent changes and logs, protect the current site with a backup where possible, and then quote or carry out the smallest safe repair.

We can help assess, contain and recover many incidents when suitable access and backups exist. If the incident needs a hosting or security specialist, we will say so rather than pretending a quick clean-up is enough.

Yes. We check backups, compatibility, logs and a safe rollback or test path before changing the live site. The exact route depends on the site and the access available.

Yes. We first inspect the site, accounts, backups and deployment path, then define what maintenance covers. Urgent help depends on availability unless a response arrangement has been agreed in advance.

Yes. We can recommend and configure a suitable setup while keeping the domain and important accounts in your name wherever practical.

Yes, but website and email migration are planned as separate risks. We confirm records, mailboxes, backups and a rollback path so a website move does not casually interrupt business email.

Yes. We can help choose and configure an email provider, domain records and devices. Business email is often best kept distinct from inexpensive website hosting.

The written quote states the exact terms. Our normal direction is that you control your domain, content and essential service accounts, with renewals and management responsibilities made explicit.

Prices depend on the condition of the existing site and the scope of the work. After the scope is clear, you receive a written quote that states what is included rather than a vague estimate presented as a promise.

Defined outcomes can use a fixed package or fixed quote. Uncertain repairs may begin with a small diagnostic step; the proposed basis and any limit are stated before work starts.

A current website link if one exists, the problem or goal, important pages or features, available content, timing and relevant access are enough to begin. You do not need to write a technical specification.

It depends on scope, content, decisions and integrations. The quote includes a realistic working schedule once those are known; a one-page site and a multi-system website should not be given the same stock deadline.

Yes. The quote should state the payment schedule, included review rounds, hosting, licences, care and any other recurring cost. A cost that is known should not appear as a surprise after launch.

We check the agreed launch items, provide the handover that was scoped and clarify who owns updates, backups and support. Ongoing care is available, but it is not silently added to a build.

We can improve technical foundations, page structure, local signals and useful content, but nobody can honestly guarantee a ranking. The work is based on the searches and customer actions that matter to the business.

Sound technical basics, sensible page titles and indexable structure are part of a professional build. Keyword research, content programmes, outreach or competitive SEO are separate work when needed.

Yes. We can configure proportionate analytics and meaningful events such as enquiries or purchases, while accounting for consent and privacy rather than collecting data simply because a tool allows it.

We can help with profile setup, focused landing pages and reliable campaign tracking. Ongoing ad management is quoted explicitly or coordinated with a specialist; it is not implied by building the page.

Yes. We can choose a practical set of channels, improve the profile basics and create a usable content direction based on the audience and the job each channel should do.

Yes. The format, volume, source material and publication rights are agreed first so the result is a repeatable visual set rather than a pile of disconnected assets.

We can set up a publishing workflow and agree ongoing scheduling where useful. Approval, account access and who responds to comments or messages are made explicit before anything is posted.

We choose measures connected to the aim, such as qualified enquiries, event interest or useful reach, rather than reporting follower counts alone. The business does not need to be active on every platform.

Common examples include enquiry routing, follow-up reminders, bookings, reports, document preparation and repeated data entry. We start with one clear workflow and its exceptions rather than automating a confused process wholesale.

Often, yes, when the systems provide suitable APIs or supported connectors. We define which system owns each piece of data, the permissions required and what happens when a connection fails.

Yes. The timing, consent, message, stopping conditions and route to a person are designed with the workflow so automation remains helpful rather than intrusive.

Yes, for a bounded and useful job. Its source information, limitations, escalation route, logs and data handling need to be defined; it should not pretend to know more than it does.

It should not replace contact that needs judgement or care. Good automation handles routine steps, makes the handover visible and helps a person respond with better context.

We estimate the current volume, time, error cost and exceptions, then compare that with build and running costs. A small checklist or reminder is sometimes the better answer, and we will say so.

Yes. Mavie is designed around focused work for small organisations, independent businesses and people who need a responsible technical partner without a large-agency process.

Yes, subject to practical timing, payment and legal requirements. Most work is already handled remotely with clear previews and written decisions.

Mavie keeps a named point of contact and clear responsibility for the work. If another specialist is involved, their role and who decides what are explained rather than hidden behind a team label.

Yes. We agree boundaries, access, handovers and the source of truth first so several capable people do not accidentally create duplicated or conflicting work.

Send a short message through the contact form, email or WhatsApp. If a call is the useful next step, we can arrange one before you commit to a project.