In “Why leads go missing” we argued that the rules matter more than the software. This is the next step: how to turn those rules, within a month, into a CRM the team actually uses.
The plan works for most popular systems. We deliberately don’t name products: at the start, the choice of tool affects the outcome less than the discipline around it.
Week 1. A pipeline that mirrors the real sale
Take a handful of recent deals — both won and lost — and reconstruct the steps they went through. Those steps become your pipeline stages. There are usually only a few: inquiry received, first contact, client’s need understood, proposal sent, decision.
For each stage, write down an exit criterion — an event, not an opinion. “Proposal sent” means a document was sent, not that “the client seems interested”. Agree a list of loss reasons at the same time: a month from now it will tell you more than any revenue report.
Week 2. Fields, sources and forms
Make required only the fields without which a deal gets lost or a report can’t be built:
- Lead source — where the client came from.
- Owner — one person, not a department.
- Next step and its date.
- Loss reason — when a deal is closed as lost.
Then connect the channels: website forms, email, phone, messaging apps. Every channel should reach the CRM automatically or under a clear rule about who logs an inquiry manually, and when. Send a test inquiry through every form and make sure it reaches the right person with the right source.
Week 3. Owners and response rules
Decide how new leads are assigned, how quickly they are answered and who picks up an inquiry when the owner is on leave or in a meeting. Set the response time yourself — based on what your clients expect — and write it down.
The key rule of the week: every open deal has a next step with a date. A deal without a next step is a deal someone has forgotten. Train the team on their own live deals, not on demo data.
Week 4. A simple weekly report
The first month’s report fits on one screen: new leads by source, time to first response, deals that moved forward, proposals sent, deals won and lost with reasons.
Review it in a short weekly meeting, inside the CRM itself. The rule is simple: if a deal isn’t in the system, it isn’t in the meeting. Within a few weeks the system becomes the single source of truth — no side spreadsheets, no verbal updates.
What not to do in month one
Most implementations stall not for lack of features but because of too many:
- Don’t migrate years of history — active deals and clients are enough.
- Don’t build complex automated email sequences and workflows.
- Don’t connect dozens of integrations at once — only the channels leads actually come through.
- Don’t create a field for every edge case.
- Don’t change stages every week: collect feedback and adjust the pipeline once a month.






