Website development

Our focus is corporate websites and portals, promotional websites and visually expressive, engaging landing pages. We also support and develop large, complex websites, including banking and pharmaceutical projects. The scope can cover UX/UI, development, integrations, content, SEO foundations, analytics, launch and ongoing support.

We connect audience understanding, information architecture, user journeys and visual design. The project can include research, interviews, wireframes, prototypes for key flows, desktop and mobile layouts, and reusable interface elements. We define the deliverables and review stages with your team.

Yes. We bring the creative idea, visual language, copy and interaction together around the brand and the offer. Motion and interactive elements are planned alongside usability, mobile performance and a clear next step. The Tefal and Samsung projects above show different approaches to presenting a product.

We can review the current website, customer journeys, content and technical requirements before defining a redesign. The scope should identify what to retain, what to improve and how to handle useful URLs, content and integrations during the transition.

The decision depends on content management, functionality, integrations, maintainability and the needs of your team. We review those requirements and explain the trade-offs before recommending a platform or framework. A familiar platform alone is not a sufficient reason to choose it.

Integrations and databases are part of our experience with complex corporate projects. For your project, we review the required systems, available interfaces, access and responsibilities before confirming feasibility and scope.

Foundational SEO and analytics are part of our approach. The proposal specifies the technical settings, GA4/GTM setup, events and checks included. Ongoing SEO, advanced analytics and additional integrations can be scoped as related work.

These services can be included where the project needs them. We agree whether your team supplies existing materials or new production is required, along with responsibilities, approvals and the estimate.

The estimate depends on structure, functionality, custom design, content, integrations, migration and launch requirements. We review your brief and starting point before quoting. Hosting, licenses, third-party tools and ongoing support should be clearly identified in the proposal.

Timing depends on scope, technical dependencies, content readiness and approval stages. We agree a schedule after reviewing the project and identify the decisions and materials needed from your team. A fixed timeline without that review would be unreliable.

We plan a responsive experience and check key layouts, navigation, forms and interactions on the agreed devices and browsers. The mobile journey is considered during UX and design, rather than left until the end of development.

Ongoing support and further development can be agreed for the project. Handover should clarify access, content management, hosting, maintenance and responsibilities. Analytics and user feedback can then inform the next improvements.

Yes. Support and further development of complex websites are part of our focus, including banking and pharmaceutical projects. We review the existing platform, integrations and technical dependencies before agreeing priorities, access, release approvals, response arrangements and responsibilities with your marketing and IT teams.

Content management is part of the requirements discussion. We identify the pages, content types, languages and approval workflows your team needs to manage, then define the appropriate CMS setup, access roles, handover and guidance.

We clarify ownership, account access and third-party licenses before work starts. The handover scope identifies the files, documentation, access and guidance your team needs, together with any ongoing hosting, maintenance or support arrangements.

We define the website’s role and relevant measures at the start. Depending on the business, these may include useful inquiries, completed applications, engagement with product information or customer self-service. Advertising traffic, analytics and available CRM data provide context; launch alone does not prove commercial success.

Share your business goals, current website, audiences, required functionality, key integrations and target launch date. If available, bring brand guidelines, content, analytics and constraints. We can use that information to define the next discovery step and the basis for an estimate.