Create or replace
A website, web system or digital presence needs to be created, rebuilt or replaced.
Start with the problem, target or existing system. We help define the work before treating the technical answer as fixed.
A website, web system or digital presence needs to be created, rebuilt or replaced.
The requirement has several moving parts and should not be forced into a one-size package.
An existing setup needs to move, change shape or be made workable in a new environment.
The organisation knows the business issue but does not yet know the right technical route.
Content, hosting, DNS, application work or integrations need to arrive at one coherent outcome.
The organisation wants one project handled externally with clear scope and handover.
A useful project definition identifies the requirement, current environment, responsibilities, intended deliverables, review points, third-party dependencies and what completion means.
Business problem, outcome or replacement need.
Customers, market, stakeholders and operating constraints that actually affect the work.
What is live today and what must be preserved, migrated or disconnected.
Deliverables, exclusions, dependencies and commercial basis.
The agreed work is implemented.
Corrections, approvals and material scope changes are made explicit.
Move to the agreed environment or deliver the agreed output.
Close the project and separately define any continued support.
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.
A narrowly defined landing-page requirement may fit USONL better than a broad B2B project.
A production relationship centred on an agency can fit the specialist WebAgencyOn route.
Research-heavy or unusually broad digital work may be structured through 4ONL when that is the natural route.
Start with what the organisation needs, what exists today and what a useful result would look like.