FOR COMPANIES & PROFESSIONAL OPERATORS

A business requirement,
turned into a workable digital project.

Start with the problem, target or existing system. We help define the work before treating the technical answer as fixed.

FIT

This route fits when the work needs definition as well as delivery.

Create or replace

A website, web system or digital presence needs to be created, rebuilt or replaced.

Broader than one fixed product

The requirement has several moving parts and should not be forced into a one-size package.

Migrate or restructure

An existing setup needs to move, change shape or be made workable in a new environment.

Problem before solution

The organisation knows the business issue but does not yet know the right technical route.

Coordinate several pieces

Content, hosting, DNS, application work or integrations need to arrive at one coherent outcome.

Defined external delivery

The organisation wants one project handled externally with clear scope and handover.

PRODUCT

You are buying a defined engagement, not undefined technology hours.

A useful project definition identifies the requirement, current environment, responsibilities, intended deliverables, review points, third-party dependencies and what completion means.

A clearer project is easier to deliver.
LIFECYCLE

How the project moves.

  1. 01
    Requirement

    Business problem, outcome or replacement need.

  2. 02
    Business context

    Customers, market, stakeholders and operating constraints that actually affect the work.

  3. 03
    Existing environment

    What is live today and what must be preserved, migrated or disconnected.

  4. 04
    Scope & assumptions

    Deliverables, exclusions, dependencies and commercial basis.

  5. 05
    Production

    The agreed work is implemented.

  6. 06
    Review & decisions

    Corrections, approvals and material scope changes are made explicit.

  7. 07
    Deployment or handover

    Move to the agreed environment or deliver the agreed output.

  8. 08
    Completion

    Close the project and separately define any continued support.

EXISTING PRODUCTION

A live system is not an empty folder.

If a website, hosting account, DNS zone, application or integration already exists, it is production context. We identify what is live and what matters before destructive changes.

Change control.
A material requirement discovered after scope may change time, cost or delivery method. We identify the change rather than silently pretending it was included.
Client control.
Domain ownership, hosting ownership, provider billing, recovery methods, business data and final approvals can remain with the client.
Ownership & Access →
ROUTING, NOT A CATALOGUE

When a specialist route is the better answer.

Focused landing / launch

A narrowly defined landing-page requirement may fit USONL better than a broad B2B project.

Agency web production

A production relationship centred on an agency can fit the specialist WebAgencyOn route.

Broader custom work

Research-heavy or unusually broad digital work may be structured through 4ONL when that is the natural route.

NEXT STEP

Describe the business requirement.

Start with what the organisation needs, what exists today and what a useful result would look like.