Four to six weeks to a working CRM, week by week.
Week 0: the audit, before anyone touches the software.
Two days mapping how the work actually flows — sources, stages, handoffs, the spreadsheet everyone secretly relies on. Most teams have never written their process down, and half the value of the project is created here, before a single field is configured.
Out of this comes a one-page picture of the pipeline and a short list of what to fix first. We do not automate a broken process — we agree the process, then build it.
Weeks 1–2: the core build.
Pipelines, stages, required fields, roles and access. The CRM starts to look like your business rather than a demo. Data import begins in parallel — and this is where timelines live or die, because dirty data (duplicates, three formats of phone number, a decade of free-text) takes longer to clean than anything else.
By the end of week two there is a working system with your real contacts in it, that one or two people can already use.
Weeks 2–4: integrations and automation.
The channels come in — telephony, WhatsApp, web forms, email — so leads land automatically. Then the automation: reminders, status notifications, handoffs between people, document templates. The aim is to remove the manual steps that made the old way exhausting.
This is also where task management and internal chat get wired, so the team runs the work in one place instead of a dozen group chats.
Weeks 4–6: training, go-live and the real test.
The system is ready before the team is — that is normal. We train on the actual workflows, not a generic tour, then go live and watch the first week closely. The first three days surface every habit the design missed; we adjust fast.
Go-live is not the finish line. Adoption is. A CRM nobody opens is just an expensive database.
Why the median is about 30 days.
A focused single-team rollout with clean-ish data and a decision-maker who answers quickly lands near 30 days. The four-to-six-week range absorbs the normal friction — holidays, a busy season, data that turns out messier than promised, a stakeholder who needs a second look.
What actually slows it down.
Almost never the technology. It is dirty data, a process no one will commit to, and the decision that keeps getting postponed. The fastest projects are not the simplest — they are the ones with one clear owner on the client side who can say yes.
Frequently asked
Can it be faster than four weeks?
Sometimes. A small team, a clean export and a single pipeline can go live in two to three weeks. We would rather hit 30 days with a system people use than 10 days with one they quietly abandon.
What do you need from us during those weeks?
One decision-maker who can answer within a day, access to your current data, and a few hours of the people who actually do the work. The single biggest accelerator is a client-side owner empowered to make calls without a committee.
What does it cost?
Implementation starts around €800 for a focused single-team rollout and scales with integrations, custom fields and data volume. We scope it after the audit, so the number reflects your process — not a package you have to grow into.