Business websites, e-commerce, publications and custom applications. We choose technology around your business, with SEO and GEO built into the design process.
Let’s talk about your projectDirect answer · reviewed
A Navanem web project begins with objectives, audiences, content and the systems that need to connect. Scope may cover a business website, store, publication, portal, business application or the redesign of an existing platform.
We work on architecture, journeys, art direction, content, development, integrations and launch preparation as one system. Technology follows the requirement: Astro, React, Next.js, WordPress, Payload, an API or another solution may fit depending on expected autonomy, connections, load and maintenance. SEO, GEO, performance, accessibility, redirects and handover are not added at the end; they form part of the design and verification criteria from the beginning. To get started, read our guide to preparing a business website and see our starting prices.
Last reviewed:
We design websites and applications for businesses, brands and publishers in Geneva, Lausanne and French-speaking Switzerland. A business website, shop, publication, customer portal or internal tool starts with its intended use. We connect strategy, art direction, content and development. Visitors should understand your offer; your team should be able to operate the tool; the system should be able to evolve. Technology is a way to meet these needs, never an arbitrary limit on your project.
Presenting a business means more than collecting pages. We clarify positioning, organise the offer and place evidence, content and calls to action where they are useful. Design expresses an identity while helping people understand why they should get in touch.
Catalogue, product pages, search, basket and checkout form one journey. We also consider connections to stock, invoicing and team tools. Platform choice follows your catalogue, markets, operational constraints and the level of customisation that will be useful.
Customer areas, extranets, booking systems, dashboards and business applications begin with real tasks. Roles, permissions, data and connections to existing systems come before adding screens. A clear interface should simplify a concrete operation.
A publication, directory or knowledge catalogue should remain easy to expand. Content types, categories, search and languages are designed with editorial workflows in mind. Teams should be able to publish and update information without a developer for every change.
We can adapt a CMS, connect services, create an API or develop a specific feature. Reusing a suitable component can avoid unnecessary work. Access control, error handling and the movement of data belong in the design scope.
A redesign should preserve what works. We review content, journeys, URLs and dependencies before proposing changes. Migrations, redirects and data transfers are prepared to preserve continuity and reduce surprises.
A website that explains your offer, gives people reasons to choose you and makes the first conversation easier. For businesses and independent professionals in French-speaking Switzerland.
Rethink your website while preserving what already serves your business. Content, journeys, technology and the transition belong in the same plan.
SEO helps people find you in search engines. GEO addresses how generative search experiences understand and use your content. Both start with a useful, accessible and well-structured website.
We plan a coherent structure, crawlable pages, distinct titles, stable URLs and relevant internal links. Performance, images, indexing, structured data and language versions belong together. For a redesign, redirects are part of the work.
We explain what you do, for whom and in which context. Clear definitions, direct answers, evidence and identifiable sources help make content understandable. There is no magic tag for an AI citation: quality and consistency matter.
We size media appropriately, limit unnecessary scripts and check mobile and keyboard journeys. Loading and visual stability measurements guide improvements. A fast, readable and usable site removes obstacles between a visit and a useful action.
Objectives, audiences, content, constraints, budget and existing systems. We define what the project should enable and the criteria used to assess it.
Structure, journeys and visual direction, then the CMS, framework, backend and hosting. We explain trade-offs in autonomy, cost, maintenance and integrations.
Development in stages, content integration and checks covering functions, permissions, responsive layouts and SEO foundations. Reviews focus on concrete pages and journeys.
Access, documentation and onboarding accompany delivery. Support and future development follow the agreed scope, with understandable priorities.
Your objective, audiences, available content and systems to connect. An existing site or a few examples are enough to begin scoping.
A prioritised scope, a page or user journey structure and explained technical choices. This provides a basis for a proposal with identifiable deliverables.
Selected pages and features, content responsibilities and launch criteria. Hosting, maintenance and future development are specified in the proposal.
No. We choose according to the task: static generation, server rendering, interactive applications, traditional or headless CMS, custom backends and APIs. Astro, React, Next.js, WordPress or Payload may be among the options. We can also work on an existing system after assessing its condition and your objectives.
Publishing needs, team skills, integrations and maintenance costs matter more than novelty. A familiar, suitable solution may be preferable. We explain what a choice enables, what it costs and what it makes more difficult.
Yes, autonomy is part of discovery. We define who publishes, what they can edit and which controls help. CMS fields, page templates and onboarding should follow your team’s daily work, not just a developer’s preferences.
No ranking, traffic level or AI citation can be guaranteed. We deliver verifiable foundations and relevant content. Visibility also depends on the market, competition, information quality and ongoing work after launch.
They depend on content, integrations, user journeys and customisation. An initial conversation identifies the scope, dependencies and a realistic first step. We prefer a proposal tied to clear deliverables over a package that hides the requirements. Our starting prices give a first reference.
