Case · CCB CleanCare
A cleaning company whose website and tools work as one.
For CCB CleanCare, the public site, the client dossier and the tools behind them were designed as one chain, so that what the site promises is what the team can deliver.
- Client
- CCB CleanCare, Ostermundigen
- Area
- Bern, Biel/Bienne, Seeland
- Languages
- French, German
- Scope
- Website, client portal, operations, automation
- State
- Live and in use


Context
CCB CleanCare is a local cleaning company based in Ostermundigen, working across Bern, Biel/Bienne and the Seeland. It cleans offices and businesses, buildings for property managers, flats at the end of a tenancy and private homes. It is run by two people who stay close to every job and to the team that carries it out.
The problem
- Prices depend on the situation. A flat at the end of a tenancy is not an office cleaned every week, so a price list alone cannot answer.
- Two languages, one region. Customers write in French or in German, sometimes both within the same property manager.
- A promise to keep. The company commits to a written offer before any job. That only works if requests arrive complete and quotes go out quickly.
- A small team. Everything typed twice was time taken from the jobs themselves.
What we designed
The public site. Every page in French and German: services, prices and estimate, real work, about, careers and a request for an exact offer. The work page shows only photographs taken on real jobs, and says so when a photograph is missing rather than replacing it.
The client dossier. After a request, the client receives a private link. There they see their request, accept or decline the offer, send a message and add photos, without creating an account.
The operations side. One system for customers, quotes, invoices, planning, jobs and the team, with a mobile workspace for the people on site.
The experience
A visitor who is not sure what a cleaning will cost answers a few questions and gets an indicative estimate, with no account and nothing sent while they explore. If they want a firm answer, the request form asks for the type of service, the frequency and the kind of customer, which is what CCB needs to write the offer. From there the conversation continues in the client dossier rather than in scattered emails.
People who want to work for CCB apply from the careers page, and the team is notified by email.
The system behind it
Inside the operations system, customers, offers, planning, jobs and invoices sit on one data model, so information entered once is reused along the chain. Documents such as quotes, invoices and handover certificates are generated from that data. Access rules decide who can see and change what.
The public site is static and fast, served from a global network. The client dossier and the internal tools run on a managed database.
Where it stands today
The website is live at ccbcleancare.ch. The client dossier and the internal tools are in use. The next version of the operations system is being built on top of the current one, without changing what customers see.
We do not publish figures for this project. Everything on the public side can be checked on the live site.
What it shows
- One chain, not separate deliverables. The site, the client dossier and the operations tools were designed to meet.
- A public promise backed by the tools. “A written offer before any job” is possible because the system makes it quick.
- Built to keep moving. The next version is being developed while the current one runs the business.
Related: websites for small businesses, client portals, business systems and automation.
Running a service business like this one?
Tell us how requests reach you today and what happens after. We will show you which part to build first.
