The first time I was trained on objection handling, the framework I was given was a list of rebuttals. "When they say it is too expensive, say..." "When they say they need to think about it, respond with..." It was a script designed to push back, to overcome, to wear down resistance until the buyer gave in. I used it for about six months before I noticed that every deal I closed using those rebuttals resulted in either a slow, painful sales cycle or a customer who was quietly resentful of having been pushed. The ones I closed by genuinely engaging with the objection , by treating it as information rather than resistance , converted faster and retained better. That observation shaped my entire approach to objection handling for the next fifteen years, including the framework I teach at Imoye Academy today.
Why Most Objection Handling Fails
Standard objection handling training fails for one fundamental reason: it positions the seller as an adversary of the objection rather than a collaborative explorer of it. When a buyer says "it is too expensive," the conventional training says: counterattack with ROI. Show them why the price is justified. The buyer hears: the seller is defending their position. That is not a conversation , it is a negotiation, and it signals that the seller's primary motivation is to close, not to help. The result is defensiveness from the buyer, which makes the conversation more difficult, not less. A more functional frame is this: an objection is not resistance. It is a question in disguise. "It is too expensive" usually means one of three things: I have not yet understood the value clearly enough to justify this investment; my budget is constrained and I need to understand what flexibility exists; or I am not the final decision-maker and I am worried about justifying this internally. Each of those is a legitimate, addressable concern , but they require completely different responses. The first step in any effective objection handling framework is diagnosis: which of these is the actual objection? According to Gartner research on the B2B buying journey, 77% of B2B buyers describe their recent purchases as very complex or difficult. In that context, unaddressed objections are often the result of unresolved complexity , not buyer reluctance.
“An objection is not resistance. It is a question in disguise , and the question determines the answer, not the objection category.”
The ACCA Framework
The framework I use and teach is ACCA: Acknowledge, Clarify, Connect, Advance. It is simple enough to internalise and flexible enough to apply across every objection type. Acknowledge means genuinely validating the objection before responding to it. Not a performative "great point" , something real. "I hear that, and it makes sense given what you have described about your current budget constraints." This accomplishes two things: it signals to the buyer that they have been heard, which lowers defensiveness; and it gives you a moment to process before responding. Clarify means asking a diagnostic question before attempting a response. "When you say it is too expensive, can I ask what you are comparing it against?" or "What would change your assessment of whether this is worth the investment?" The clarification question is the most important step because it transforms the objection from a statement you have to counter into information you can use. Connect means linking your response directly to what they said in the clarification, not to a pre-prepared rebuttal. If the clarification reveals that the objection is about internal justification, the connect step addresses that specifically: "Let me walk you through how other teams have presented this internally, because that exact challenge comes up often." If it reveals a genuine value gap, the connect step fills the gap: "That makes sense , let me show you how teams in similar positions quantified the return." Advance means ending the objection conversation with a clear next step that moves the deal forward. Not a close , a step. For a look at how this fits within a broader methodology, see the difference between consultative and transactional selling.
The Four Most Common Objections in African Tech Sales
In the context of African B2B tech markets specifically, four objections appear in nearly every sales conversation, each with specific underlying causes. The first is "it is too expensive." In markets where enterprise software budgets are often smaller than comparable Western organisations and where procurement cycles are longer, this objection is structurally common. The diagnosis question is critical here: is this a genuine budget constraint, a value perception gap, or an internal approval challenge? The second is "we need to think about it." This is almost never about thinking. It usually means: I am not yet convinced, or I have other priorities competing for attention right now, or I need to align with someone else before I can move. The clarification question should surface which of these is true. The third is "we already have a solution for that." In fast-growing markets, this often means they have an improvised solution , a spreadsheet, a manual process, a workaround , that is technically "a solution" but is not fit for scale. The response is not to attack the existing solution but to ask what happens to that solution as the business grows. The fourth is "our management has to approve this." This is a champion problem, not an objection problem. The buyer wants to move but does not have the authority. Your job at this point is to equip the champion with the tools to justify the decision internally , a business case template, relevant case studies, an ROI calculation, and a clear understanding of what objections will come from leadership and how to address them. Read how to follow up without being annoying for context on sustaining momentum after the objection conversation.
“The champion objection is not a dead end. Your job is to equip them with the tools to win the internal battle on your behalf.”
Building the Muscle Through Practice
Objection handling cannot be learned from a framework alone. It requires reps, which means practice, which means role-playing scenarios where real objections come at you in real time and you have to respond without a script. The first ten times you use the ACCA framework in a live call, it will feel mechanical. The acknowledge step will sound rehearsed. The clarify question will not be perfectly calibrated. That is fine. The framework is a scaffold , not the destination, but the structure you use until the approach becomes instinctive. By the fiftieth time, the structure will disappear and what will remain is a genuine orientation toward the buyer's concern rather than a defensive posture toward their objection. That shift , from defensive to curious , is what separates the top 10% of sales professionals from everyone else. In the 12-Week Tech Sales Pro Programme, every session on objection handling includes live role-plays with structured feedback. You will face the most common objections in your specific market segment, in front of peers and with a coach who has spent fifteen years managing these conversations at the Oracle level. That is not preparation you can get from a blog post or a sales book. It requires repetition under observation. That is what we build.