Home/Blog/Founder-Led Sales/How to Keep an Objection Log That Shows …
Founder-Led Sales

How to Keep an Objection Log That Shows the Pattern

How to keep an objection log: one line per lost or stalled deal, in the buyer's own words, reviewed monthly until the repeated sentence shows you what to fix.

Cover of the FIKR Space guide: How to Keep an Objection Log That Shows the Pattern

To keep an objection log, write one line after every lost or stalled deal: what stopped it, in the buyer's own words, and nothing more. Then review the list once a month and look for the sentence that keeps coming back.

Most founders say they will remember why deals fall through. They will not. Memory is kind to us, and it rounds a messy run of conversations into a story that feels reasonable. A log replaces that story with the actual record, and the record is usually less flattering and far more useful.

How to keep an objection log without turning it into a project

The whole idea is its size. A log that takes seconds gets written. A log that needs a form, a category and a severity score gets abandoned by the second week, usually on the day you most needed it.

The rule is simple. When a deal is lost, or when it stalls and you close it out, write a single line. That line says what stopped it, using the words the other person used, not your summary of them. If they said it was not the right moment, write that. If they said someone else would have to agree, write that. Resist the urge to translate it into your own vocabulary, because the translation is where the signal leaks out.

There is a reason the guide keeps stressing the buyer's words. When you rewrite an objection as "price" or "timing", you have already decided what it meant. Three different sentences can all collapse into the same neat label, and once they do, you can no longer see that they were three different problems.

Why the repeated sentence matters most

The playbook calls the repeated sentence the single most valuable thing this stage produces. That is a strong claim, so it is worth saying why it holds.

During the first conversations, every loss feels like its own event. This buyer was distracted, that one had a reorganisation, another already had something that worked. Taken one at a time, each explanation is plausible and none of them asks anything of you. Written in a column, they stop looking like separate events. The same two or three sentences account for most of the losses, and that pattern was never visible from inside the week because memory smooths it away.

The repeated sentence is also the one you did not prepare for. Founders arrive ready to talk about features and price. What actually decides deals tends to be something else: the cost of switching, internal politics, a workaround that is already good enough, or a risk that nobody wanted to be responsible for. You cannot find these by thinking harder at your desk. You find them by hearing the same line for the fifth time and finally noticing.

Free guide, 32 pages: The First 100 Customers Playbook. Send me the guide.

What goes in the line, and what stays out

A good entry is short, specific and attributed to the buyer. A weak entry is an interpretation. The table below shows the difference in shape, using only the kinds of reasons the guide itself names.

What the entry should holdWhat it should not hold
The reason, in the buyer's own wordsYour summary of what you think they meant
What actually stopped the dealA list of everything that might have contributed
One line, written the same dayA paragraph written at the end of the month
The stage the deal had reachedA score or rating of how likely it once was
A note when a stall was closed outSilence about deals you quietly let drift

Notice that stalled deals belong in the log as well as lost ones. A deal that never gets a clear no is the easiest kind to forget, and it often hides the most honest objection, because the buyer found it easier to go quiet than to say it. If you have a stall limit, closing a deal out at that limit is the moment to write its line. The post on how to follow up with sales prospects covers the limit itself.

The monthly review

Writing the lines is half the habit. The other half is reading them together, on a day you have fixed in advance. Put it in the calendar like any other appointment, because otherwise it will lose to the next conversation every single time.

When you review, you are looking for one thing: the repeated sentence. Do not try to analyse every entry. Read down the list, notice which phrases rhyme with each other, and ask what they have in common. Often the answer arrives quickly, because the pattern was already there waiting.

It helps to work through three questions.

  • Which sentence appears most often, and is it really the same objection each time or only the same label?
  • At which stage of the pipeline do these deals usually stop?
  • Is the objection about the product, the price, the message or the person you were talking to?

The second question connects the log to the rest of your records. If you keep clear stages, as described in how to build a startup sales pipeline, the log and the stage data tell you the same story from two directions.

What the log is for

The guide describes the output as a product roadmap, a pricing conversation and a messaging rewrite, delivered by your market for free. Each of those is a different use of the same list, and it helps to decide which one the repeated sentence is pointing at.

If the repeated sentence is aboutThe work it points to
What the product does or lacksA product change
What the buyer thinks it should costA pricing conversation
A misunderstanding of what you offerA rewrite of your message
Buyers who were never the right peopleA narrower or different target

The last row deserves attention. Sometimes the objection is not really an objection at all. It is a sign that you keep talking to people for whom the problem is not urgent. In that case the fix lives upstream, in the way you chose who to call, which is the subject of how to narrow your target customer.

FIKR Hub, the sales and marketing platform: every contact and deal from first touch to closed won. See FIKR Hub.

Reading the log alongside the stage where deals stop

An objection means more when you know where in the process it arrived. The guide offers a simple way to read drop-off, and the log lets you apply it to real sentences instead of guesses.

Where the deal stoppedWhat it usually means
Before the first conversationA targeting or message problem
After discoveryYou are talking to people who lack the problem, or you did not connect to what they said
At proposalUsually price, packaging or a risk nobody addressed
After a verbal agreementAlmost always a decision maker who was never in the room

Put the two together and the log becomes sharper. A repeated sentence that always arrives after the proposal is a different job from one that always arrives after discovery. Without the stage, you might spend a month rewriting your pitch when the real gap was that you never asked who else had to agree.

It also protects you from a quiet kind of self-deception. When a loss is painful, it is tempting to file it under bad luck or bad timing. Writing the buyer's actual words next to the stage makes that harder to do, and that discomfort is part of what makes the habit work.

Turning the log into something you can hand over

An objection log has a second life later. The guide's list of what you owe a first sales hire includes an objection playbook, and Checklist 3 asks that the two or three real objections are written down with the answers that work. You cannot write that page from imagination. You can write it from a log, because the log already tells you which objections are real and how often they appear.

So the habit pays twice. In the short term it tells you what to change. In the longer term it becomes the raw material for the document that lets someone else sell. A founder who never kept the log has nothing to hand over except a feeling that objections were mostly about price.

Free guide, 32 pages: The First 100 Customers Playbook. Send me the guide.

Common ways the habit breaks

The log fails in predictable ways, and they are all avoidable.

Making it too elaborate. Extra fields feel like rigour, but they are a well-known way to avoid the next call. Keep the entry to one line.

Writing it late. The exact phrasing is the valuable part, and phrasing fades within a day or two. Write the line when the deal closes out, not when you remember.

Logging only the clean no. If you record only the deals that said no in plain terms, you miss the slow maybes, which the guide treats as the costlier problem.

Skipping the review. A log nobody reads is just a diary. The monthly look for the repeated sentence is what turns notes into a decision.

Arguing with the entries. If a buyer's words sound unfair or mistaken, write them down anyway. You are recording what the market says, not defending the product against it.

FIKR Hub, the sales and marketing platform: every contact and deal from first touch to closed won. See FIKR Hub.

Frequently asked questions

How long should an entry be?

One line. The point is that you will actually write it, every time, straight after the deal ends. If you find yourself writing a paragraph, you are interpreting rather than recording.

Should I log deals I won?

The guide asks for a line after every lost or stalled deal. Wins carry other records, such as where the deal came from and what the buyer said the problem was. The log itself is for what stopped a deal.

What if every entry says something different?

Then look at the target before the objections. A broad target produces many different objections, which reads as noise when the cause is that you were talking to too many kinds of people.

How often should I review it?

Monthly, on a day you fix in advance. Within a few weeks of starting, the repeated sentence usually shows itself.

The full method, with the checklists, is in The First 100 Customers Playbook, a free 32-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us