Recurring objections

How do you spot recurring objections from one meeting to the next?

To spot the objections that keep coming up from one meeting to the next, a Muzau agent notes on each customer's record the objection that customer raised, based on your Granola note. When the same one comes up with at least three different customers, Muzau suggests it to you as a recurring objection. The agent does not write the answer: you write it with your business's verified facts, and your agents can then repeat it.

Why recurring objections go unnoticed

An objection is heard in a meeting, one at a time: "it's more expensive than expected", "the lead time is too long", "I need to talk to my partner". In the moment, the salesperson answers as best they can, then the next meeting starts. The sentence ends up in a note, when it ends up anywhere.

What is missing is not the objection, it is the count. Three customers stumbling over the same thing, with three different salespeople, and nobody sees it: each of them has only heard it once. And each answers in their own way, with arguments that are not always the same. Seeing the repetition lets you prepare a single, accurate answer, and stop losing a sale over a question you had the answer to.

How the agent goes about it

Input

Your meeting notes taken in Granola

It does

Notes each customer's objection, then counts the ones that come back

It delivers

A recurring objection suggested to the Brain, waiting for your approval

The objection noted on the customer's record

After each meeting you take notes on in Granola, Muzau records on the customer's record, under "Customers met", what that customer said themselves, objection included, with the meeting date and the link to the note. If the note has a transcript, the objection is kept only if its wording is found word for word in what the customer said; otherwise, it is taken from the note's summary. Nothing is kept on a sensitive subject. The rest of the record is described in the sales visit report, and how it links to your CRM in updating your CRM after a meeting.

Three different customers, not the same one three times

When the same objection comes up in at least three meetings, with three different customers, Muzau suggests it as a recurring objection for the Brain, what your agents know about your business. A customer who repeats theirs at every meeting counts only once: Muzau relies on the latest objection on each record. In a team, each salesperson connects their own Granola and a single agent receives all the notes: the objections heard by one and by the other are counted together.

The answer comes from you, with your facts

Muzau suggests the objection, it does not write the answer in your place. What a customer says remains their word, not an established fact about your business. Nothing enters the Brain without your "Keep" click. You write the answer yourself on the Brain page, with what is true for you: a lead time, a guarantee, a condition. What you write there goes in directly, and each piece of knowledge has its audience: your team only, your customers, or everyone.

Your agents repeat the same answer

The answer kept in the Brain is then used by your Muzau agents, depending on the audience you give it: the agent that answers emails, and the site chat if it is public. The agent is instructed to state only the prices, lead times and commitments present in the Brain, and to hand over when the information is missing. The answers your team gives in meetings are also suggested to the Brain: if one contradicts what it knows, a card flags it to you, and nothing changes on its own.

How to answer an objection with facts

An objection that keeps coming back deserves a prepared answer, written once and shared by the whole team. This method works with or without a tool.

• Note the objection in the customer's words, not in your interpretation. "It's expensive" and "I don't have that budget right now" do not call for the same answer.
• Look for what it really carries: a price, a lead time, a risk, or a person who was not there to decide.
• Answer with a verifiable fact: what is included, the real lead time, the guarantee, a written condition. Not with an adjective.
• Keep the answer to two or three sentences, which anyone on the team can repeat without rewording.
• Add an example if you have one: a customer in the same situation and what happened, without naming them if they did not agree.
• End with a question, so the objection becomes a step: "If the lead time is met, does the rest work for you?"

The mistakes to avoid: contradicting the customer, promising something written nowhere (a discount, a tight lead time) to save the meeting, and letting each salesperson answer in their own way. An objection that comes back without a prepared answer often ends in an improvised discount. To pick it up again with the same customer next time, see how to prepare a meeting with a customer you have already met.

What it does not do

• It does not spot an objection without a Granola note: a write-up forwarded by email gives a recap, but records no objection on the customer's record.
• It does not write the answer to the objection: it suggests the objection to you, and the answer comes from you.
• It counts only the latest objection of each customer: one from an older meeting is not added up.

Frequently asked questions

Do you need Granola to spot recurring objections?

Yes. In Muzau, objections come from the "Customers met" records, filled in from the Granola notes you take yourself: they need the meeting participants, which the note knows about. A write-up forwarded by email gives a recap, but no objection on a record.

How do you note a customer's objections during a meeting?

Note their exact sentence, in quotation marks, rather than your interpretation, and what triggered it: a price, a lead time, an absent person. With a Granola note and its transcript, Muzau keeps the objection on the customer's record only if its wording is found word for word in what they said.

How do you answer the "it's too expensive" objection?

First ask compared to what: another quote, a budget, or what is included. Then answer with a fact: what the price covers, what it avoids, the payment terms if there are any. An improvised discount settles the meeting, not the objection.

How do you share the answer to an objection with the whole sales team?

Write it once, in two or three sentences and with verifiable facts, somewhere everyone looks. In Muzau, that is the Brain: your agents use it to write, and if a salesperson answers differently in a meeting you took notes on, a card flags it to you.

How do you remember a customer's objection before seeing them again?

Reread their exact sentence, noted at the last meeting, and prepare the fact that answers it. With Muzau, on the morning of a new meeting with a customer you have already met, you receive a brief that picks up what they said, objection included, with the commitments and the number of emails exchanged since. The meeting must be in the connected calendar or have been booked by Muzau.