Blog
The system is installed. Nobody uses it.
The rollout went fine. Fields, stages, dashboards, one training session. Six weeks later you open the pipeline on a Monday and half the deals were last touched in the month the system went live.
Nobody is sabotaging you. The team is still selling. Quotes go out, site visits happen. It’s just happening somewhere else: chat threads, a notebook, a spreadsheet. The system got installed. The sales operation never moved in.
Here’s what to do on Monday, starting with the step nobody selling software will tell you: don’t change the software yet.
Why your sales team won’t put data in the system
Ask a rep directly and you rarely hear “I don’t want to.” You hear one of four things, each a design problem, not an attitude problem.
- It costs more than it returns. Filling in a deal takes eight minutes and the rep gets nothing back worth eight minutes. Entry that’s a tax with no refund loses to a chat thread.
- The fields don’t match how they sell. A project sale with a site survey, a spec revision and a three-month wait doesn’t fit stages named for someone else’s business. So the rep guesses, then stops guessing.
- Nobody wrote down what “qualified” means. If two reps would put the same deal in two different stages, the data was never going to be trustworthy. Everyone knows it.
- The real review doesn’t use it. This is the big one. If Monday’s meeting runs on what people say out loud, then talking is the system and typing is homework.
Underneath all four sits the same thing: the sales process still lives in people’s heads. Software can hold a written process. It cannot hold one that was never written.
Why the three fixes owners try first don’t work
Mandating it. “From now on, everything goes in the system.” This lasts about two weeks, then fails in a new way: reps update on Friday, from memory. Now you have complete-looking data that’s wrong. That’s worse than obviously empty data, because you’ll act on it.
Tying it to KPIs or commission. Whatever you measure gets filled in. Pay for stage movement and deals reach “negotiation” right on schedule. The numbers improve; the forecast doesn’t.
Switching software. The most expensive move, and the most common advice. It’s common because most people giving it sell licenses. If the process was never written down, the second system inherits the problem of the first. Change tools when you hit a real limit, not when adoption is the symptom.
How many required fields do you actually need?
Fewer than you have now. For most B2B pipelines the honest answer is five. These five answer questions you already ask out loud:
- Who it is (company and contact)
- What stage it’s in, defined so two reps would agree
- What it’s worth, roughly
- When you expect it to close
- What the next step is, and on what date
Source, products, competitor, site notes are optional. If a field never shows up in a decision, it shouldn’t be mandatory. Every extra required field raises the cost of entry, and the cost of entry is the whole reason nobody enters.
One rule worth protecting: no open deal sits without a next step and a date. A pipeline where every live deal has a dated next step is already more useful than most fully configured systems.
The same rule applies to quotes. One with no follow-up date attached is already going quiet.
Move the sales meeting onto the system: one source, no exceptions
This is the step that does the real work, and it costs nothing. Next Monday, run the pipeline review with the system on screen and nothing else open. Nobody presents from memory. You go down the list in the order it sits, asking two questions on every deal: what’s the next step, and when.
Deals that aren’t in the system don’t get discussed. Not as punishment, just as a fact of what’s on screen. That one rule flips the economics of data entry in a single meeting: entering a deal stops being homework and becomes how a rep gets airtime for their work.
The first meeting will be bad. That’s the real state showing. By the fourth, updating before Monday is a habit.
Five checks: is it the people, or a process nobody ever wrote down?
Answer honestly:
- Can you write down, in one sentence each, what moves a deal from one stage to the next?
- Would two of your reps put the same deal in the same stage?
- Is there a written rule for when a deal is dead?
- Does any recurring decision depend on the data being current, such as a meeting, a forecast, or a commission run?
- Can a rep update a deal in under two minutes, on a phone, after a site visit?
Four or five yeses and you have a people problem. That’s a management conversation. Two or fewer and it never was. Your team is behaving rationally inside a process that was never finished.
If you’re starting over, what the 30 days should look like
Order matters more than speed.
- Days 1–5. Write it. Stages, entry and exit criteria, what “qualified” means, who owns a deal at each point. Write it in your team’s own words, from the deals you actually run.
- Days 6–10. Cut it. Reduce to the smallest set of required fields that supports the written process. Argue for deletions, not additions.
- Days 11–20. Install it, by your team. The people who will use it do the configuration, with a pattern to follow. A system installed for a team dies. One installed by a team sticks.
- Days 21–29. Run it live. Real deals, weekly review on screen, fix what’s awkward while it’s cheap.
- Day 30. Measure against three criteria you wrote on day one. Written in advance, or the review turns into a feelings check.
That’s the shape of a BUILD 30 install: we design the pattern, your team installs it, day 30 measured against criteria agreed up front.
Notice what isn’t on the list: choosing software. In most of these situations the tool you already own is enough.
If you’re looking at a system that’s paid for and mostly empty, that’s the conversation worth having first. Book a 45-minute call and we’ll go through your stages, what your team actually fills in, and whether this needs thirty days of work or one changed meeting.