Website strategy, design and development

Website concepts

Different structures. Distinct visual worlds.

Self-initiated website concepts for fictional brands and organisations show how visual design, content structure and interaction work together. These are not client engagements; no measured business results are claimed.

Series 2 · more complex website structures

Website type: Corporate website
Pattern: Audience-led navigation

A corporate concept with 33 pages in each of three languages: audience-led navigation, search, services, projects, team information, news and governance.

Website type: Catalogue website
Pattern: Multiple ways to explore and select products

A light blue catalogue with four ways to explore and select products: a specification table, category browsing, load-guided selection and comparison.

Series 1 · four single-page worlds

Website type: Brochure website
Pattern: Searchable archive

A light editorial brochure for a fictional private-archive studio, with a searchable 12-record index, combinable filters and relationships between records.

Website type: Landing page
Pattern: Single-action product journey

A cinematic luxury landing page for one fictional light-and-sound object, built around one proposition and one primary action.

Website type: Promo website
Pattern: Interactive collection explorer

A restrained fragrance promo website with four atmospheric states across one imagined day, botanical compositions and an interactive collection explorer.

Website type: Catalogue website
Pattern: Faceted search

An editorial catalogue with taxonomy, filters, materials and a close study of every object.

GIVSITE - this studio website and portfolio.

Website type: Brochure website
Primary function: Service and work discovery; project enquiries
Specialisation: Studio portfolio
Core modules: Three languages and enquiry flows

Outcome

What will be ready at launch.

We plan visual design, content, implementation, launch and handover together. For each agreed deliverable, we define what you receive and how it is checked or approved.

Clear structure

What we deliver: A site map, content hierarchy and clickable prototype for the key journeys.
How we verify it: We walk through the prototype with you and approve the structure before visual production.

Coherent visual language

What we deliver: Typography, grid, components and states designed around real content.
How we verify it: We stress-test the system across screen sizes, real content lengths and key states.

Working website

What we deliver: A responsive build with the agreed content, forms, data flows and integrations.
How we verify it: We test agreed journeys, browsers and devices: keyboard use, forms, integrations, error recovery, accessibility, security and performance. We record the results and remaining limits.

Handover and guidance

What we deliver: The completed website within scope, the agreed access to its accounts and connected services, and concise operating guidance.
How we verify it: We verify the live domain and service access, then the person responsible completes an agreed routine task using the guidance.

How we work

Five stages from first conversation to launch and handover.

For each stage, we define its output and how it is approved. Content preparation and technical checks can run in parallel; work that depends on a decision begins after that decision is approved. You see intermediate results at agreed stages - from the structure and prototype to the design and a test version of the website - and can give feedback before the next step.

Context and constraints

We examine the product, audience, materials, goals and constraints with you, then record the assumptions that shape the work.
Context brief approved
Structure and prototype

We shape the site map, content order and key journeys before visual refinement.
Structure and key journeys approved
Visual system

We develop typography, grid, components and content across real screens and states.
Visual system approved
Development and testing

We build the responsive website, connect the agreed integrations and test the critical user journeys. We repeat these checks after related changes and before launch.
Pre-launch version approved
Launch and handover

We publish the agreed version, verify it on the live domain and provide the access and guidance defined in scope.
Launch and handover confirmed

Services

Website type and scope - shaped around the task.

We start with the business goals, audiences, content, priority actions and constraints. From these, we agree the website format, pages, functionality, integrations and services. Formats may overlap and are not fixed packages. The scope defines content and editing responsibilities, quality requirements, dependencies, exclusions and acceptance criteria. The estimate and project agreement set out the schedule, price and payment plan.

Website types

Brochure website

Introduces a company, project or professional, explains the offer and makes it easy to get in touch.

Landing page

A focused page for a defined offer and audience, organised around one primary action. It can serve a campaign or an ongoing offer; content and navigation support that decision.

Promo website

A dedicated website to present and promote a product, campaign or event. It can have one page or several.

Corporate website

A website that represents an organisation to several audiences. Its services, projects, team, news, careers and other sections, together with the editing and publishing model, follow the organisation's needs.

Catalogue website

A website for exploring and evaluating a structured range of products or services, using listings, search, filters, comparison or guided selection where needed. Visitors enquire or request a quotation rather than place an online order.

Webshop

A website for ordering goods or services online. The scope defines the relevant product data, order flow, payment methods, tax requirements, fulfilment, order management, returns, refunds and integrations. Payment does not have to take place online.

Cross-cutting services

SEO and AI search visibility

Search strategy, technical SEO, content structure, relevant structured data and trustworthy content that help search systems find and understand the website. We define the search platforms covered; indexing, rankings and inclusion in AI search answers are not guaranteed.

Analytics

A measurement plan, event specification and any required data layer; tracking configured for the agreed consent and data-handling requirements; implementation checks, reporting and interpretation.

Development & support

Monitoring, maintenance, dependency and security updates, fixes, content changes, integrations and iterative improvements under an agreed support scope.

What the scope covers

Five areas for defining the work and responsibilities.

Deliverables describe what you receive; the process shows when decisions are agreed; these areas define the website and the work around it. Every project has an appropriate baseline, content and operational responsibility. Features, integrations and ongoing support are selected to fit its needs. Quality requirements apply to the whole agreed scope, and the estimate distinguishes included work from optional enhancements. These are not sequential stages or fixed packages.

Project baseline

What we agree: Goals, audiences, information architecture, the appropriate visual system, editing and publishing model, CMS where needed, hosting and deployment responsibilities, accessibility target, privacy, consent and security requirements, performance targets and resource limits, baseline technical SEO and a verification plan.
Outcome: A clear technical and editorial baseline

Content and navigation

What we agree: Content types and responsibility for preparing, approving and updating them; pages, copy, media, categories, navigation, search and selection where needed, the editing model and any required catalogue data.
Outcome: Information people can find and the team can maintain

Key user journeys

What we agree: Forms, enquiries, booking or registration; for ecommerce, the basket or direct-order flow, checkout, payment methods and fulfilment required by the sales model.
Outcome: Clear paths to the agreed actions

Integrations

What we agree: Required connections to CRM, ERP or PIM, email, consent and analytics platforms, payment, tax, fulfilment and inventory systems. We define the data, direction of exchange, responsibility and recovery from failures.
Outcome: Automated exchange of agreed data

Operation and improvement

What we agree: An operational owner and handover responsibilities; monitoring, technical SEO, measurement, experiments, content changes, dependency and security updates, maintenance and support where separately agreed.
Outcome: Improvements guided by data and feedback

Project frame

Agreement before work

We document the stage outcome, schedule, price, exclusions, included review rounds, approval window and decision points.

Payment

Tied to clear stages

Every payment is connected to a specific scope and an outcome you can verify.

Flexible schedule

A stage payment can be divided

When the project schedule allows, we agree in advance to spread payment for a larger stage across several dates. The total price of the stage does not change: there is no interest or commission.

Third-party costs

Separate from our work

Domains, hosting, licences and other external services are not folded into our fee: we show them separately before approval.

If the project changes

We first show the effect on scope, schedule and price. Additional work begins only after written approval.

Delivery work packages

Work required by the agreed scope

The estimate identifies the work needed to deliver and verify the agreed website, alongside clearly identified optional enhancements.

We can adapt a suitable component system or template, redesign an existing website, move it to another platform or create a custom build. Content migration, URL mapping and redirects are specified where needed.

Each selected work package is identified in the estimate. Strategy, interpretation and ongoing support are specified separately where required.

Template adaptation

We select a suitable base and adapt its structure, styles, components and content to the project.

Content model and editing

We define content types, fields and responsibilities, structure and edit the agreed material, and specify photography or illustration requirements.

Search and measurement implementation

We implement approved metadata, structured data, consent-aware tracking events and data-layer requirements. Strategy, dashboards and ongoing optimisation are scoped separately.

Integrations and transactions

We implement the agreed forms and ordering flows, configure the applicable payment, tax and delivery rules, and connect the required CRM, ERP, PIM or fulfilment services.

Extended verification

Verification needed for the agreed scope belongs to the implementation. Additional work can cover more browsers, devices, assistive technologies, journeys and failure conditions, while checking the agreed performance targets and resource limits.

Animation and 3D

We use animation or 3D for an agreed purpose: product explanation, interaction or brand expression. We define performance limits and keep content and controls usable when motion is reduced.

Content migration and redirects

We inventory and migrate the agreed content, map URLs, configure redirects and verify the moved content after publication.

Extended handover and team training

Beyond the standard access and concise guidance included at launch, we can provide role-based training, an operating runbook and recorded editor walkthroughs.

How this affects the estimate

For each selected package, the estimate defines deliverables, timing, dependencies and acceptance criteria, and states whether it is required for the agreed scope or is an optional enhancement.

Questions

What matters before we begin.

How is the website price calculated?

The price depends on the number and variety of pages, required capabilities, content readiness and external services such as payments, delivery or a CRM (customer relationship management) system. Before paid work begins, we agree the scope, schedule, price, payment plan and exclusions in writing. We explain the proposal and answer your questions before you approve it.

How long does it take to create a website?

The schedule depends on the website's size and complexity, content readiness and the time needed for review and decisions. We propose stages, dates and review windows after understanding the project. If required materials or approvals arrive later than agreed, we update the schedule rather than promise a launch date we cannot support.

What do you need to provide?

You do not need website expertise or a large team. If you are running the business yourself, tell us about the organisation, audiences, goals and outcome you need - or simply describe the idea. If the website type is unclear, we propose the structure and scope that best serve those goals.

How do we communicate during the project?

At the start, we agree the main communication channel and how we will share project updates. We keep requests, decisions and next steps in a shared record so both sides can see what has been agreed and what needs attention.

Who prepares the copy and images?

We can work with your finished materials, structure and edit them, or scope content creation and translation separately. We agree who prepares and approves each item before it is needed for design or development. Content rights and permissions are identified separately.

What if the scope or requirements change?

We first show how the change affects scope, schedule and price. Additional work begins only after your written approval - with no surprise charges.

Can I try editing the website?

If the project includes content editing by you or your team, we demonstrate the agreed editor through a typical task. Before handover, you or the responsible team member try making and publishing a change using the instructions.

What will you receive after launch?

At handover, you receive the completed website within scope, the agreed account access and operating guidance. Before paid work begins, the estimate and working terms state which design files, source code and repository history transfer; which third-party components remain licensed; and which accounts you own or can access. We agree the defect-correction period and conditions before work begins. New features, optional support and further development are agreed separately. We also state who can change which content, how it is published and who handles publication failures.