Customer reviews Google reviews Read our reviews
How I work

A clear process. No unnecessary complication.

You tell me what you need. I work out the sensible route, build it properly, test it and support it after launch if you need me to.

Direct communication Clear scope Safe releases Ongoing support
01
Understand Tell me what you need
✓
02
Plan Agree the right scope
✓
03
Build I build it properly
✓
04
Test Check the important journeys
✓
05
Launch Release it carefully
✓
06
Support Keep improving it
→
The process

From first message to launch and support.

Smaller jobs may move through these stages quickly. Larger builds simply need a little more detail at each step.

01 Understand

Tell me what you need

Send the idea, the problem, the existing website or the workflow that is getting in the way.

02 Plan

Agree the right scope

I’ll explain what I recommend, what is included and what the finished result should do.

03 Build

I build it properly

Website, ecommerce, CRM, portal or automation — built around the actual requirement.

04 Test

Check the important journeys

Forms, mobile layouts, checkout, logins and the requested functionality are tested before release.

05 Launch

Release it carefully

Live changes are handled with sensible backups, staging or rollback routes where needed.

06 Support

Keep improving it

If you want ongoing support, updates and future improvements can continue after launch.

Swipe through the process →
Safe delivery

Fast is useful. Careless is not.

If a live website is already taking enquiries, bookings or payments, the change needs to be released without creating a second problem.

Explore services →
01

Backups & rollback

A recovery route is considered before higher-risk work is released.

02

Staging when useful

Larger changes can be tested away from the live website first.

03

Important journeys tested

Forms, checkout, logins and other key actions are checked around the change.

04

Controlled releases

Changes stay understandable and reversible wherever practical.

Direct communication

You deal with the person building the project.

No account-manager hand-off. If something is unclear, risky or unnecessarily complicated, I can tell you directly.

01

Straight answers

If there is a simpler route or a trade-off, I’ll explain it before unnecessary work is added.

02

Clear updates

You should know what is being worked on, what is waiting and what I need from you.

03

Support stays organised

After launch, ongoing requests can be kept together through the client portal.

Client portal ↗
Starting a project

You do not need a technical brief.

A useful first message can be very simple. Tell me what the problem is, what you already have and what you want to happen instead.

01 What you need help with
02 Your existing website or system, if there is one
03 Anything time-sensitive
04 Screenshots or examples if useful
FAQ

Before we get started.

Ask me something →
Do I need a technical brief? +
No. A useful first message can simply explain what you need help with, what is already in place and what you want the business to be able to do.
Will I deal directly with you? +
Yes. You deal directly with me throughout the project, from the first conversation through to build, launch and support.
How do you keep live changes safe? +
I reduce risk before changing a live website by using backups, staging, testing and smaller controlled releases where appropriate.
Can you support the project after launch? +
Yes. Ongoing support is available for updates, fixes, improvements and future development.
Next step

Tell me what you need. I’ll tell you what makes sense.

Website, ecommerce, CRM, automation or a technical issue — send the rough details and we can work out the sensible next step.