How a WordPress project works

From first messageto a launched site.

This is my website development process in four steps, in order, so you know what is happening and what comes next. Timing depends on the size of the project and how quickly feedback comes back.

01
Discover

Understand the goal.

Tell me what the business does, who the website is for and what it should achieve. Your branding, any existing content and examples of sites you like all help.

You get: A shared picture of what the site needs to do

02
Shape

Agree the scope.

We settle the pages, content and features, along with a design direction. This is the best moment to change your mind, because nothing has been built yet.

You get: A clear scope and design direction

03
Build

Build it in WordPress.

I build the site, set up the features you asked for and adjust the layouts for phone, tablet and desktop. You review a working version and send your feedback.

You get: A working website to review

04
Launch

Review, launch, follow up.

We go through the content and the key actions, such as forms and bookings, agree the final changes and go live. If you want continuing help afterwards, we agree what that looks like.

You get: A launched site, with support available if you want it

What this means for you

What the website development process means for you

Website development process: Sami Kamboh working at a laptop

A clear website development process protects your time and your budget. You always know which stage the project is in, what is needed from you and what happens next. Nothing is built before the scope is agreed, and nothing launches before you have reviewed it.

What to prepare before the first step

You do not need a finished brief. A few lines about your business, who the website is for and what it should achieve are enough to start. Your logo, any existing text and photos, and examples of sites you like all help. If you already have a website, send the address so I can see what exists.

How feedback fits into the build

The best moment to change your mind is during the scope stage, before anything is built. Once there is a working version, feedback is most useful when it is specific: which page, which section and what you would like instead. That keeps each round of changes short and keeps the website development process moving.

Search and speed are part of the work

While building, I set up page titles, descriptions and headings so search engines can understand each page, and I keep pages light so they load quickly on a phone. Google's own SEO starter guide covers the basics this work follows.

After launch

On launch day we go through the content and the key actions, such as forms and bookings. If you want continuing help with updates and fixes, we agree what that looks like. You can see the kind of sites this process produces in the projects, read what each job involves on the services page, or start with a short message.

Questions

Good to know
before we start.

Straight answers to the things clients ask most. Anything else? Just send me a message.

How long does a project take?

It depends on the number of pages, the features involved and how quickly feedback comes back. I will give you an estimate once I have read your brief.

What do I need to prepare?

Your goals, any branding such as a logo and colours, text and images if you have them, and examples of sites you like. If you do not have text or images yet, tell me and we will plan for it.

Can I ask for changes during the build?

Yes, feedback is part of the build stage. Larger changes to the agreed scope may affect timing or cost, and I will tell you before going ahead.

What happens after launch?

We do a final check together. If you want continuing help, I can handle updates and fixes, and we agree what that covers.

Get in touch

Have a website to
build or fix?

Send a few details about the site, what it needs to do and when you would like it live. I read every enquiry myself and reply with questions or next steps.