It’s a familiar scene. The sales team loses opportunities, follow-up depends on each person’s memory and management has no clear view of what’s happening. The answer usually comes fast: “we need a CRM” or “let’s automate this.” Months later, the tool is paid for, but the team is still working in spreadsheets and WhatsApp chats.
The problem is almost never the tool. It was chosen before anyone understood the process it was meant to support.
Technology amplifies what already exists: if the process is clear, it speeds it up; if it isn’t, it makes it more expensive and harder to fix.
Before investing in a new tool, it pays to answer five questions.
1. What are the real stages of your sales process?
Not the ideal ones, the real ones. What happens from the moment a prospect arrives until they become a client? When are they qualified, when is a proposal sent, what happens if there’s no reply? If two people on the team describe the process differently, that is already a first finding. A tool configured around stages nobody uses ends up abandoned.
2. Who owns each step?
Many opportunities aren’t lost because the client lost interest, but because nobody knew it was their turn to reply. Defining an owner for each stage (who qualifies, who prepares the proposal, who follows up) matters more than any automated feature.
3. What information do you need, and why?
It’s tempting to log everything, but every extra field is one more task for the team. Before adding a data point, ask what decision it will inform. If there’s no clear answer, you probably don’t need it. A minimal record the team actually keeps is worth more than a complete one nobody updates.
4. How will you know it is working?
Before implementing, define how it will be measured. Without a baseline, there’s no way to tell whether the change improved anything or just made it different. A few simple indicators to start with:
- Time to first reply to a prospect.
- Opportunities with a defined next action.
- Conversion between stages of the process.
- Actual use of the tool by the team.
5. Is your team willing to use it?
Adoption is where most implementations fall apart. A tool the team feels is imposed on them, or that adds work without giving anything back, ends up being one more cost. Involving the people who will use it from the design stage, and supporting them through the first weeks, changes the outcome entirely.
Process first, then the tool
Answering these questions doesn’t require technology: it requires time, conversation and judgment. With clear answers, choosing the tool becomes simpler, and sometimes you discover that the one you already pay for is enough, configured differently.
That’s the principle we work by at ETZA: understand before you act, diagnose before you implement and measure before you declare success.