How we turn detail into progress

01 / Establish what is true

We start with the business model, audience, service area and current customer journey. The first output is an evidence inventory: what we know, where it came from and what still needs confirming.

For search work, that includes the published business identity, relevant public registrations, analytics access and the pages that already attract useful enquiries. We distinguish an observed problem from an assumption before prescribing a fix.

• Record an owner and source for every business fact.
• Agree what counts as a qualified enquiry or successful sale.
• Capture a baseline before changing the site.

02 / Connect content, design and data

SaaS experience puts tasks and product journeys first. Ecommerce experience adds attention to product decisions, margin and checkout friction. Software development brings clear data contracts, validation and maintainability.

We use those perspectives together. A service page needs a clear proposition, credible evidence and a working next step. A polished layout cannot compensate for a broken form or an unsupported claim.

• Sketch the decision a page helps someone make.
• Map entities and URLs before writing structured data.
• Prototype the difficult interaction before polishing the whole page.

03 / Build a release we can verify

We define acceptance checks alongside the scope. These cover keyboard use, mobile layouts, forms, metadata, redirects and the actual response sent to a crawler. Calculators get tests for boundary conditions as well as the happy path.

Our default is to keep content available in the first HTML response and add JavaScript where it earns its place. We measure production performance once real visitors and infrastructure are involved. A laboratory score is useful evidence, not a promise about every device.

• Check the smallest supported viewport and a large desktop.
• Test failure, empty, loading and success states.
• Confirm ownership of secrets, domains, hosting and integrations.

04 / Measure the next decision

We separate visibility, engagement and commercial outcomes. Each is useful, but they answer different questions. A ranking change does not tell us whether the enquiries were suitable; a conversion rate change needs the traffic mix beside it.

Each review ends with a decision: keep the change, refine it, investigate it or stop it. We prefer a short list of changes with an owner and a reason over an expanding report with no next step.

• Compare equivalent periods and record important changes.
• Use qualified enquiries and contribution where the data allows.
• Keep a change log so results can be interpreted later.

Clear ownership, from day one

You approve business facts, professional claims and final messaging. We own the agreed design and technical delivery. Together we define acceptance, access and handover before launch.

Our published guides explain the approach, while your proposal specifies the work. Tools provide estimates and starting points. They do not promise a ranking, replace professional advice or manufacture evidence.