iKonekt

For sales teams

A Monday meeting with fewer mysteries in it

Ten sellers, one pipeline, and the ordinary arithmetic of a week: what came in, who has it, what has gone quiet. None of that requires a report. It requires that ownership existed from the first second, which is where most of it goes wrong.

The classic sales-team failure is not laziness and it is not a bad CRM. It is a shared inbox and a well-meaning culture of "we all pitch in", which works beautifully at four enquiries a week and starts leaking at fifteen. Nobody notices the leak, because the leak is defined by the absence of an event.

Give every arrival an owner before anyone has read it and the leak becomes a visible number. Sometimes an uncomfortable one. That is the trade.

What changes on a Monday

The meeting stops being a memory test. Instead of "did anyone follow up with the people from the trade fair?", which is a question with no answer, the questions become:

  • Forty-one arrived last week. Thirty-eight have a reply, three do not, and all three are Tomek's, who was in Kraków.
  • The oldest unanswered thread is nine hours old — and that is the number the team actually competes on, because it is the one a customer feels.
  • Alicja is carrying nineteen open threads and everyone else is carrying eleven. Which is worth knowing on Monday morning rather than in her resignation letter.
  • The spring flyer produced two enquiries and one booking. The trade fair produced twelve enquiries and no bookings. Discuss.
Last week41 arrivals
  • 1AnsweredMedian first reply: 1 h 12 m. Slowest: 9 h, which arrived at 22:40 on Friday.
  • 2Still openAll three owned, all three visible, none of them anybody's guess.
  • 3QuotedOf which eleven booked. The other six are on the thread, not in a memory.
  • 4UnownedThere is no state in this system where a contact has no name against it.

No report was built to produce this

Handovers, holidays and the person who leaves

Every sales team eventually discovers how much of its knowledge lived in one person's head, and it discovers this on the person's last Friday. The thread is the antidote: what was promised, what was quoted, what the customer objected to, and the small human details that make the next call sound like a continuation rather than a fresh start.

Re-assigning a departing seller's work is one action. Their notes stay, attributed to them, because the point was never to erase who did the work — it was to stop the work leaving with them.

An unsentimental note on notes: the best sales note we have seen in this system was four words long — "hates being called Bogdan". It saved a deal. No scoring model was involved.

What we are not going to give you

No lead score. No coloured temperature. No probability percentage that everybody privately adjusts before the forecast meeting anyway. A seller reading a thread knows more in nine seconds than a model does, and a manager reading the same thread can see why the seller thinks it.

What you get instead is evidence: how long since a reply, what was quoted, what was said, and by whom. If a forecast is built on that, it will be a forecast worth arguing about.

Worth knowing

Three habits this tends to produce

People answer at odd hours

Not because anyone asked them to, but because they can see that a thread is theirs. Marek replying on Saturday morning is a choice he made after seeing his own name on it.

Notes get better

Team-visible by default means notes get written for a colleague rather than for oneself, which turns out to be the difference between a note and a scribble.

Marketing arguments get shorter

Source is recorded per arrival, per flyer, per campaign. It is remarkable how quickly a strongly held opinion resolves once somebody can count.

“Did anyone follow up with the trade fair people?”

Forty-one arrived. Thirty-eight have a reply.

The Monday meeting stops being a memory test. Ownership existed from the first second, so the silence has a name attached to it — and that is the whole difference.

How assignment works →