Who this is for
The project can be a new website, a focused landing page or an improvement to an existing experience. I bring marketing context into the build, so content structure, search intent, campaign destinations and enquiry handling are considered together. We agree on what the site needs to do before choosing the implementation.
- Service businesses whose current website does not clearly explain the offer or next action.
- Owners preparing a campaign, a service expansion or a redesign that needs a defined purpose.
Questions worth investigating
- Visitors struggle to understand the service, audience or relevant evidence.
- Mobile content and contact paths are difficult to use.
- A redesign changes appearance without addressing content, search URLs or enquiry delivery.
Useful work. A clear scope.
Page and journey plan
Define the main visitor questions, page purposes, content needs and contact routes. Connect relevant proof to each service rather than placing all projects in one isolated gallery.
Responsive design and build
Develop the agreed visual system and pages for appropriate screen sizes. Select an editable platform or implementation that fits the content, integrations and handover requirements.
Search and migration foundations
Prepare page titles, descriptions, semantic structure and internal links. For a redesign, review existing useful URLs and scope redirects or content preservation before replacing the old experience.
Enquiry and launch checks
Check forms, contact links, delivery routes and meaningful success states within the agreed setup. Review the rendered site, public pages and handover information before calling the release complete.
From understanding to verification.
- 01
Define the brief
Clarify the audience, offer, existing website and business goal. Agree on required pages, content responsibilities, integrations and what a successful enquiry should contain.
- 02
Design and build
Prepare the content and visual direction, then implement the agreed pages. Review the mobile journey and actual interactions while the work is still easy to adjust.
- 03
Verify and hand over
Test the agreed actions and publication state. Document content editing, ownership and any outstanding dependencies so the business can understand and maintain its website.
Agree on the boundaries before starting.
- Page count, copywriting, media production, integrations, hosting and maintenance are defined in the proposal.
- A working enquiry route requires a real receiving system; a visual form or button alone is not a completed delivery setup.
- Portfolio examples show their documented scope. They do not establish that I authored every current page of every employer website.
Questions before we start
Can we improve the current site instead of rebuilding it?
Yes. A content, mobile or contact-path problem may need a focused change rather than a new platform. I review the current structure and constraints before recommending the size of the project.
Will I be able to edit the content afterwards?
Editing needs are part of platform selection. We agree on which content you need to update and how it should be managed. The handover should explain the chosen workflow and any changes that still require development.
Can you build a page specifically for an advertising campaign?
Yes, when that is the appropriate scope. The page brief should connect the ad’s promise, approved offer, supporting evidence and contact action. Tracking and lead delivery also need to be specified and checked.



