Explain Your Offering
Organise company, service and product information so visitors can understand what the business does and identify the information relevant to them.
Show visitors what you do, why it matters, and how to take the next step. WDI creates business websites that communicate your strengths clearly and guide potential customers towards meaningful enquiries.
The website’s commercial and communication role should guide its structure, content and development scope.
Organise company, service and product information so visitors can understand what the business does and identify the information relevant to them.
Present capabilities, service information and suitable evidence that help prospective customers assess the organisation.
Connect important visitor journeys with relevant contact, consultation or enquiry actions.
Provide a practical structure for maintaining services, company information and other agreed content as the organisation changes.
Include forms, APIs or other integrations where they support a defined visitor or operational requirement.
Consider planned services, content areas or market requirements when organising the website’s information architecture.
Define the website’s business role, priority visitors, desired actions and functional requirements before moving into design.
WDI reviews existing material and known dependencies to establish an appropriate project scope.
Best suited for: Businesses that need a clear website brief before committing to design and development.
Organise page groups, navigation and content relationships around how visitors need to discover and evaluate information.
The structure should make the organisation’s offering understandable without requiring every audience to follow the same path.
Best suited for: Websites with multiple services, products or information areas.
Translate the website structure into responsive page experiences that reflect the brand and support visitor tasks.
Design considers hierarchy, navigation, content presentation, calls to action and behaviour across the intended screens.
Best suited for: New corporate websites and experience-led redesigns.
Engineer the website and supporting functionality around the agreed designs, content model and technical requirements.
The work may include frontend presentation, backend functionality and integrations according to the website scope.
Best suited for: Businesses requiring an implemented website rather than design-only support.
Define an appropriate content-management approach where internal teams need to publish or maintain website information.
The setup should reflect content types, editorial responsibilities and the level of administration required.
Best suited for: Organisations expecting regular updates to their business website.
Connect agreed functionality with required systems and validate important pages and journeys before release.
Testing and handover responsibilities should reflect the website’s actual content, forms, integrations and operating environment.
Best suited for: Teams preparing a business website for production use.
A useful website brief explains what visitors need and what the business expects the website to support.
What should the website help the business accomplish?
Who needs to understand, evaluate or act on the content?
Which paths should visitors be able to complete?
Which services, products and resources need dedicated coverage?
What should visitors do after evaluating the business?
Who creates, approves and maintains the information?
Which systems need to connect with the website?
Which known changes should influence the structure?
For WDI, page structure begins with business and visitor requirements. Design templates then support that structure.
This gives the website a clearer organising principle as new content and services are introduced.
Both are delivered through the web. Their primary user task determines the appropriate route.
A business website can include forms, search and integrations. When authenticated workflows or complex business logic become the main requirement, Web Application Development provides the more specific service route.
Similarly, a corporate redesign belongs here when communication and visitor experience lead the project. Architecture-led renewal of an existing web estate belongs within Modern Web Development.
WDI reviews the public experience and the work required to manage it. This assessment establishes the website’s purpose and scope before detailed engineering choices.
The website’s role within the organisation
Priority visitors and their information needs
What should be retained, reorganised or redesigned
Relationships between services, products and supporting information
What exists, what is required and who owns it
How users move from entry pages to useful actions
Requirements beyond content presentation
Systems or services involved in the website
Administration and publishing after release
Known changes that should influence current decisions
This assessment establishes the website’s purpose and scope before detailed engineering choices.
Clarify objectives, audiences, the current website, content requirements, visitor actions and dependencies.
Clarify objectives, audiences, the current website, content requirements, visitor actions and dependencies.
Define navigation, page groups and user journeys around the agreed information and business requirements.
Define navigation, page groups and user journeys around the agreed information and business requirements.
Develop responsive page designs using the structure, brand inputs and content requirements.
Develop responsive page designs using the structure, brand inputs and content requirements.
Define the website architecture, content-management approach, integrations and functionality.
Define the website architecture, content-management approach, integrations and functionality.
Build the website, implement the agreed content structures and connect supporting systems.
Build the website, implement the agreed content structures and connect supporting systems.
Review important pages, responsive behaviour, functionality, integrations and supplied content against acceptance criteria.
Review important pages, responsive behaviour, functionality, integrations and supplied content against acceptance criteria.
Where continued support is included, plan agreed changes as content, communication and website requirements evolve.
Where continued support is included, plan agreed changes as content, communication and website requirements evolve.
A fraction of what we have shipped.
A business website needs ongoing content ownership as services, company information and marketing requirements change.
WDI considers those responsibilities alongside the initial build.
Establishes who maintains business information
Gives related pages a consistent organising model
Clarifies who can create, review and update content
Identifies responsibility for connected systems
Supports administration and future development
Keeps planned content changes visible during the initial project
Ongoing support is defined by the engagement. Website ownership should remain clear whether subsequent changes are handled by the internal team, WDI or another agreed arrangement.
Look for a team that asks about your business and visitors before recommending page layouts.
Business website developers should be able to explain how objectives influence information architecture, how content responsibilities affect delivery and how visitor journeys connect with enquiry routes.
Discuss Your Business Website ProjectBring your objectives, priority audiences, current website, core offering, brand material and any known content or integration requirements. WDI can use discovery to clarify the remaining information architecture, visitor journeys and delivery dependencies.
An existing website can be reviewed for changes to structure, content, design and visitor journeys. When the primary requirement remains an information-led corporate website, this service is the appropriate route.
Content-management requirements can form part of the website scope. The approach depends on the content model, editorial responsibilities and architecture. Where decoupled content delivery is the central requirement, Headless CMS Development is the more specific route.
Integration may be included where suitable APIs, access and supporting architecture are available. The scope depends on which systems need to connect and what information or actions move between them.
The main purpose of those features determines the route. Limited interactive functionality can sit within a business website. If authenticated tasks, business logic and software workflows become central, Web Application Development is more appropriate.
The timeline depends on content readiness, design requirements, page structure, functionality, integrations, review cycles and release scope. An estimate should follow a review of these requirements and their dependencies.
Share your objectives, priority audiences, current website, required content, desired visitor actions and any known functionality or integrations.
WDI will review the content and user journeys, existing environment and delivery dependencies to help define an appropriate scope. The next step may involve discovery, information architecture, website scoping, design or implementation planning.
