Good collaboration.
Starts with understanding.

Start with who you are, who you serve, what the website should achieve and what is not working today. For a personal site, gather your background, expertise, work and contact details. For a business or organisation, outline your story, services, audience, projects, team information and enquiry process. Share only material you can publish and have permission to use. Tell us what is missing; you do not need every detail ready for the first conversation.

References help most when you explain what appeals to you: typography, colour, space, content order or interactions. Similar-looking screens may have very different content and functionality behind them. We identify useful principles rather than copying another brand, its imagery or code. Your reference basket starts a conversation; it does not automatically include every feature in every example.

Prioritise a clear journey: understand who you are, explore your services, see relevant work and make contact. Separate essential launch features from later additions such as accounts, languages, booking or data integrations. A focused first phase gives us a clearer quality and scope target than trying to deliver every idea at once.

We can assess it first; using a third-party platform is not inherently a problem. Updating copy, images, colours or supported sections may be a sensible refresh. Platforms, plans, themes and plugins differ in their control over layout, custom code, data export and integrations. We need to understand the platform, plan, existing features and available permissions before promising what can change. A homepage screenshot alone is not enough.

A rebuild may be worthwhile when essential layouts are restricted, key functions depend on fragile workarounds, the structure is difficult to use or maintain, or the brand has outgrown it. A new build also needs content migration, URL planning, testing and a maintenance approach. We compare keeping, improving and rebuilding the site rather than presenting a rebuild as the answer to every problem.

Custom development can offer greater control over structure, visuals and interactions, but budget, timing, devices, performance, browsers and external services still matter. Payment, booking and data providers have their own capabilities and rules. The right approach supports long-term use and maintenance as well as creative expression.

A website involves more than building screens. Copy, photography, background information, feature decisions, integration access and feedback all affect what can happen next. Indicative schedules assume the agreed inputs arrive on time. If content is delayed or scope grows, we discuss the impact and revise the schedule rather than automatically compressing testing. Portfolio and package durations are planning references; the proposal establishes the project schedule.

Some structural work can start with provisional content, but headline length, project counts, image proportions and copy volume affect the layout. Identify placeholders and agree when final material will arrive. Clarify whether writing, translation, photography, asset licensing or substantial content preparation is included before work starts, rather than discovering the gap just before launch.

Words such as minimal, premium or creative can mean different things to different people. We use specific references, colour directions and representative screens to align before extending the design. Helpful feedback identifies the area, the feeling or action you want, and an example that is closer. We make a thoughtful effort to understand your view, explain the reasoning and find a workable balance; no first concept can be guaranteed to match every expectation.

Changes can be discussed, with revision scope and rounds agreed in advance. One contact should consolidate team feedback and distinguish defects, refinements within the approved direction and new requests. A new style, additional pages or a different workflow may affect completed work, fees and timing. We agree the impact before proceeding. Regular checkpoints are more useful than a major reversal at the end.

Inventory existing URLs, important pages, forms, analytics settings, files and external links. Plan content mapping and redirects where appropriate, keep backups, and clarify who controls the domain, hosting and email. Launching a website does not automatically mean moving email; DNS or other service changes need separate coordination. A rebuild does not guarantee improved search rankings.

The proposal defines deliverables, editable areas, source files, access, guidance and ongoing support. A static site and a content management system have different editing workflows, so tell us who will update the site and how often. Hosting, domains, paid services and ongoing maintenance may have continuing costs. A working launch does not eliminate the need for future checks and upkeep.