SOS RelevageGeneva

Local service website and job-management CRM for a Geneva building-services company

The website launched with the business: every request goes through a four-step funnel, then lands directly in a custom-built job-management CRM.

Website
Business application
SEO and GEO
SOS Relevage on a phone: first screen

In short

SOS Relevage, a Geneva lift-pump specialist, launched its business on 24 August 2026 with a website we built: a four-step request funnel feeds a custom intervention CRM. In a manual check on 20 September 2026, the site ranked first in the local pack for “pompe de relevage genève”.

Case study by David Khazaei, Founder of DKDP·Published on , updated on

Project sheet

Sector
Building services, lift pumps
Location
Canton of Geneva
Project start
8 May 2026
Open to Google
25 July 2026
Business launch
24 August 2026
Delivered
Website, CRM, SEO, visual identity
Technology
Next.js 15, Supabase, Vercel

The context

A trade nobody searches for until the basement floods

Audience
Property managers, condominiums, homeowners
Territory
Canton of Geneva
Start
A new business, no reviews or references yet

SOS Relevage is a Geneva company that does one thing: servicing, repairing and replacing wastewater lift pumps for property managers, condominiums and homeowners. The site had to launch together with the business, with no history, no reviews and no references to show, in a market where nobody looks for a contractor before the breakdown.

It had to be found on very local queries, earn the trust of a property manager comparing suppliers, and turn a hurried visit into a complete request, address and access details included, with no call back to ask for the basics.

Our approach

A service site that feeds the field tool directly

Next.js 15 with the App Router, content versioned in code without a CMS, hosted on Vercel with functions in Europe and the database in Zurich. The heart of the site is a four-step request funnel, situation, requester, building, contact, preset by the button it was opened from: every submission creates a record in a custom intervention CRM, with scheduling, a synced calendar, appointment reminders and a photo job report.

On the search side, one page per intent (repair, maintenance, replacement, property-manager contract, flood emergency, who to call), a JSON-LD FAQ, an llms.txt file and answers written to be quoted as-is by generative engines. All of it on a visual identity created for the brand, from the logo to the signature wave.

What was delivered

  • Next.js 15, React 19, Tailwind 4, Vercel deployment, content versioned in code
  • Four-step request funnel, preset by the button, validated client-side and server-side
  • First name, last name, email and phone asked on all five forms, like the bexio contact record
  • Custom intervention CRM: scheduling, calendar synced with Google, email and SMS reminders, report per intervention type with photos
  • Address search on the federal building register, with no dependency on Google
  • JSON-LD LocalBusiness, Service and FAQPage, llms.txt and llms-full.txt generated at build
  • Eleven blog guides and intent pages for local search
  • Visual identity and logo created for the brand, 24/7 on-call service announced sitewide

The site, top to bottom

The whole home page as it appears on a computer: hover over the window to scroll through it.

Browse the live sitesos-relevage.ch (opens in a new tab)
sos-relevage.ch
SOS Relevage: the whole home page
SOS Relevage on a phone: first screen

How it flows

From request to report, with no re-typing

What happens to a request sent from the website, up to the report handed to the customer.

  1. 1Input

    Website button

    it pre-fills the subject of the request

  2. 2Tool

    Four-step funnel

    subject, requester, building, contact details

  3. 3Tool

    Record in the CRM

    address and plant-room access included

  4. 4Rule

    Scheduled intervention

    Google calendar, email and SMS reminder

  5. 5Output

    Intervention report

    photos for each checkpoint

The customer PDF report is still assembled outside the CRM, from its data.

The sections that carry the site

5 screens, in the order a visitor meets them. Each one answers a moment: arriving, recognising the problem, asking for help, coping with an emergency, knowing who to call.

  1. sos-relevage.ch/
    SOS Relevage home page: headline, before-and-after slider on a flooded plant room brought back into service, technician in the foreground
    SOS Relevage on mobile: the same first screen with stacked title and buttons, call bar at the bottom
    01ArrivingUI

    A before-and-after slider as the promise

    The first screen does not describe the trade, it shows it: the same plant room flooded on the left, back in service on the right, with the technician in front. The slider follows the mouse without a click and drifts back on its own when released. One title, one sentence, a red button to send a request and, second, the emergency line.

    • A 24/7 on-call strip above the menu, visible before anything else
    • Red carries the main action: the request, or the call when it is urgent
    • The slider reacts to hover, not only to dragging
    See it on the home page (opens in a new tab)
  2. sos-relevage.ch/
    SOS Relevage, the eight-signal section: symptoms sorted by urgency, photo of a Flygt pump and a Describe my breakdown button
    SOS Relevage on mobile: the eight signals with the sticky image following the scroll
    02RecognisingUX

    Eight signals to self-diagnose before calling

    Someone whose basement is flooding does not always know they have a lift pump. Eight symptoms sorted into emergency, to schedule or preventive, an image that changes with the hovered signal, and on mobile a sticky panel driven by scrolling: you go down the list, the image follows without an extra gesture.

    • On mobile, scrolling drives the image: nothing to learn
    • Each signal opens the right request directly
    • A “which pump do I have?” block for those who are not sure
    See it on the home page (opens in a new tab)
  3. sos-relevage.ch/
    SOS Relevage request funnel opened on the home page: “Which subject?” step with four tiles
    SOS Relevage on mobile: the request funnel full screen, four subjects stacked
    03AskingUX

    A four-step request, preset by the button

    Every button on the site opens the same funnel: the subject, who you are, the building, your details. The originating button pre-fills what it already knows, the address is looked up in the federal building register, and access to the plant room is asked for right away. Every submission creates a record in the field CRM, with no call back to ask for the basics.

    1. 1Subject
    2. 2You
    3. 3Address
    4. 4Contact
    • Four subjects: urgent repair, repair, check-up and maintenance, works
    • The same validation rules client-side and server-side
    • First name, last name, email and phone asked every time, for a complete record
    See it on the home page (opens in a new tab)
  4. sos-relevage.ch/urgence-inondation-geneve
    SOS Relevage flood emergency page: “Safety first, damage second”, six numbered steps in a grid
    04When it overflowsContent

    An emergency page that also says when it is not us

    Six steps in order, four water origins to recognise before calling, who to call and in which order, with the fire brigade ahead of everyone. The page states in plain words what the company does not do: it restores drainage, it does not dry the building. That is what makes it quotable rather than promotional.

    • A direct answer at the top of the page, quoted as is by engines
    • The 118 as a phone link, never competing with the form
    • A companion minute-by-minute article on the blog
    See this page live (opens in a new tab)
  5. sos-relevage.ch/qui-appeler-pompe-relevage-geneve
    SOS Relevage “Who to call” page: two cards comparing the lift-pump specialist and the general plumber, what each handles and does not
    05Knowing who to callSEO

    A pivot page comparing four trades

    Lift-pump specialist, plumber, drainage company, electrician: for each, what it handles and what it does not. The page answers the “who” questions Search Console surfaced without a single click, then ends with the laws and official services cited at the source.

    • Four cards, two lists each: what it handles, what it does not
    • Reference texts linked: LEaux, OIBT, OCEau, the 118
    • “Who” FAQ reused in the structured data
    See this page live (opens in a new tab)

See it in action

Recorded on the live site, without editing.

The request funnel, on the live site. From the “Faire une demande” button to the contact step, in 14 seconds, unedited.
What the video shows

From the home page, a click on “Faire une demande” opens the four-step funnel. The visitor picks the subject (check-up and maintenance), then their profile (property manager). At the address step, they type the first letters and pick the official address suggested by the federal building register. The last step asks for contact details. The video stops before sending.

Visual direction

An identity created for the brand: two blues for clean water and the technical side, two browns for wastewater, and an arrow going up. The shift from brown to blue tells the trade in one image, on the logo as in the gradients of the site.

BrandSOS Relevage logo: SOS letters with a wave and an arrow going up, from brown to blue

« Pompes de relevage. Un seul métier. »

Palette
  • Night blue#09365fheadings, footer
  • SOS blue#186092links, secondary actions
  • Technical blue#0d4b7bhover, depth
  • Light blue#46b0d6accents, clean water
  • Water brown#5f3716wastewater, before
  • Mud brown#97713etransition
  • Action red#a8332athe main action of the screen
Typography

Spécialiste des pompes de relevage à Genève.

Hubot Sans · headings and body copy, variable from 200 to 900

04 · Identification · 8 signaux

JetBrains Mono · labels, section numbers, footer

Rules the site never breaks (SOS Relevage)

  • One red per screen

    Red carries the main action: sending a request in normal times, calling when it is urgent. Everything else is blue, which makes the expected action impossible to miss.

  • Never a heading in capitals

    Capitals live in buttons and small mono labels. Headings stay in sentence case, more legible and less loud.

  • One gradient, one direction

    Brown turns to blue from left to right or bottom to top, never the other way: the direction of lifting.

  • Nothing decorative

    No animated bands, no abstract illustration. A plant room, a pump, a technician, at eye level.

  • Pages that read like a file

    01, 02, 03 in mono labels ahead of each section: a structure the eye finds again from one page to the next.

  • Thumb before mouse

    A call bar that fades while reading and returns when scrolling up, a full-screen funnel, 44-pixel targets.

SEO and generative search

Search is not a layer added at the end. Each page answers one precise search intent, each answer is written to be quoted as is, and the structured data is generated from the content, never duplicated.

The result as declared to Google
SOS Relevagehttps://sos-relevage.ch

SOS Relevage - Dépannage & Entretien de pompes à Genève

Pompe de relevage en panne à Genève ? Contrôle, entretien et dépannage pour éviter l'inondation. Urgence 24h/24, audit gratuit.

Brand name first, the query in plain words, and no delay in the snippet: a promise you cannot keep in 600 pixels is a lost click.

Structured data emitted
  • LocalBusiness
  • Plumber
  • Service
  • FAQPage
  • Article
  • VideoObject
  • BreadcrumbList
  • WebSite

Generated from the same content the visitor reads. Nothing is declared in the markup that is not visible on the page.

Written to be quoted

  • Answers written to be quoted

    On every service page, a heading phrased like the question (“who can replace a lift pump in Geneva?”) followed by a 40-to-60-word answer that names the company and makes sense outside the page.

  • The out-of-scope, in writing

    The emergency page says what the company does not do. A generative engine reading “we restore drainage, we do not dry the building” does not present it as a post-disaster remediation firm.

  • llms.txt and linked sources

    A hand-written llms.txt, an llms-full.txt generated at every build from the site data, and the laws cited with their link: LEaux, OIBT, OCEau, SIG, the 118.

Stack

Next.js 15Tailwind 4SupabaseVercel

The numbers, over time

Every curve shows its source, its retrieval date and its raw data.

Google impressions, rolling 7 daysLatest value : 540 impressions
Google impressions, rolling 7 days: from 0 on 25.07.2026 to 540 on 23.09.2026, peak of 556 on 22.09.2026.
24.08 Business launch
08.09 Brand name back in the home page title

Source : Search Console, retrieved on 25.09.2026. From 25 July to 23 September 2026, each point adds up the previous 7 days. Search Console hides more than half of this site’s queries: the curve counts every impression, including those whose query is hidden.

See the data
Google impressions, rolling 7 days
Dateimpressions
25.07.20260
26.07.20268
27.07.202614
28.07.202617
29.07.202620
30.07.202621
31.07.202624
01.08.202626
02.08.202620
03.08.202621
04.08.202619
05.08.202620
06.08.202622
07.08.202622
08.08.202622
09.08.202621
10.08.202617
11.08.202618
12.08.202623
13.08.202621
14.08.202624
15.08.202624
16.08.202629
17.08.202627
18.08.202627
19.08.202625
20.08.202630
21.08.202636
22.08.202649
23.08.202671
24.08.202694
25.08.2026124
26.08.2026142
27.08.2026168
28.08.2026190
29.08.2026203
30.08.2026201
31.08.2026223
01.09.2026240
02.09.2026265
03.09.2026261
04.09.2026255
05.09.2026245
06.09.2026243
07.09.2026242
08.09.2026285
09.09.2026322
10.09.2026347
11.09.2026388
12.09.2026407
13.09.2026439
14.09.2026455
15.09.2026432
16.09.2026445
17.09.2026449
18.09.2026445
19.09.2026460
20.09.2026472
21.09.2026511
22.09.2026556
23.09.2026540

Results

Each figure shows where it comes from and when it was measured.

Google local pack

1st

for “pompe de relevage genève”, and 3rd in organic results

Manual check of the results page, from Geneva, retrieved on 20.09.2026 · single check

  • 1'802Google impressions

    and 44 clicks since the first impressions

    Search Console, retrieved on 25.09.2026 · from 25 July to 23 September 2026

  • 5.0Average position

    of the home page, all queries combined

    Search Console, retrieved on 25.09.2026 · 28 days, from 27 August to 23 September 2026

What we would do differently

What this project taught us, and what we now apply to the next ones.

  1. 01

    Search Console hides a large share of a local site’s queries: 57% of SOS Relevage impressions were anonymised in the 20 September check. Before concluding that a query does not rank, we check the results page ourselves, from Geneva.

  2. 02

    Removing the brand from the home page title was a mistake: for six weeks, Google never showed the site for “sos relevage”. The name went back to the front of the title on 8 September 2026.

  3. 03

    For a repair business, the phone number matters as much as the site: until 24 September 2026, its Google profile was the only one of the three in the local pack without a number.

Questions about this project

Why a custom CRM rather than an off-the-shelf tool?

Because the website and the field tool share the same data: each request arrives with the address, the plant-room access and the type of intervention, and becomes a scheduled job with no re-typing. A generic tool would have meant copying that information from one system to another.

Can the site be quoted by answer engines such as ChatGPT?

Every service page opens with a 40-to-60-word answer that names the company, and an llms.txt file describes the site for generative engines. Nothing guarantees a citation, but these passages are written to be quoted as they are.

Where is request data hosted?

The site is served by Vercel, with functions in Europe, and the CRM database is hosted in Zurich.

The services behind this project

Keep reading

The MKR Caucasian Camp website on a laptop and a phone: first screen of the French version and the application choice, real screenshots staged in a wrestling gym

Next case study · Website

MKR Caucasian Camp · Dagestan and Chechnya

Brand, bilingual website and application platform for a wrestling and MMA camp

For MKR Caucasian Camp, which runs wrestling camps in Dagestan and MMA camps in Chechnya, we created the brand, the Next.js website in French and English, the online application, the back office that follows every file until departure, the emails, the presentation film and the Google Ads campaigns.

Read the case study
Custom websites✦Artificial Intelligence✦Corporate training✦Local SEO Geneva✦UX redesign✦Business apps✦
Custom websites✦Artificial Intelligence✦Corporate training✦Local SEO Geneva✦UX redesign✦Business apps✦

Let's talk about your project

15 minutes, free of charge, and we tell you honestly whether we can help, and how.

No commitment · Reply within 24h · Eaux-Vives, Geneva or by video call