Respond to a Reseller Margin Objection

A reseller says proposed margin does not justify sales and support effort. Treat those words as a request for detail, not an opening bid. A quick discount response often leaves both sides unclear about who will do work after signature. Start by learning what sits inside the reseller's estimate. Ask which customer activities require people, time, or specialist attention. A useful first question is: Which part of this opportunity creates your cost, sourcing demand, technical validation, implementation, or frontline support?

Pause after asking. Let a partner describe their motion in ordinary language. One partner might say their field seller found an account, arranged two discovery meetings, and expects to involve a technical person during evaluation. Another might say their team will configure an initial environment, train local users, and take first calls after launch. Those are different work patterns. A higher margin request does not identify which pattern applies. Specific work does.

Ask for a sequence rather than a broad claim. Say, Walk me through your work from today through the first customer handoff. Then listen for handoffs, named people, timing, and assumptions. If a partner says implementation support will be substantial, ask what tasks they expect to perform. If they say support is expensive, ask which questions customers usually bring first. This approach keeps a commercial discussion connected to real activity.

Do not turn every mentioned task into a negotiation point. First separate necessary work from work assumed by habit. A reseller might expect a specialist at every discovery call because prior deals required one. This opportunity might have a smaller technical scope. A partner might plan a half day onsite meeting before anyone has asked for one. Find out whether a customer expectation, a reseller policy, or an earlier conversation created each assumption.

Use a simple working record during a partner call. Give each activity an owner, a point in time, and a reason. For example, demand sourcing belongs with the reseller during the first two weeks because their account manager knows local contacts. Technical validation belongs with both teams during evaluation because questions cover product fit and customer workflow. Initial setup belongs with a named services resource only if both parties agree work falls within their scope. A visible record prevents vague promises from becoming hidden obligations.

Here is a fictional practice situation. Jordan, an account executive, receives a message from Northline Resellers. Northline asks for an extra twelve points of margin. Jordan replies, I want to understand your plan before we discuss terms. Which activities create most of your cost on this account? Priya, Northline's partner lead, says her seller sourced an introduction and expects support during a technical review. She also expects her team to provide weekly project updates after purchase.

Jordan does not answer with a number. Jordan asks, Who would run each review, and what would weekly updates cover? Priya explains Northline's seller will coordinate customer meetings. A solutions person would join one technical review. Weekly updates would cover scheduling and open questions during an initial setup period. Jordan writes each item down. Jordan then asks whether someone on the customer side has requested project coordination. Priya says no request exists yet. Northline uses weekly updates on most deals because customers often seek a single contact.

Jordan now has a useful distinction. Sourcing and one technical review are planned contributions. Project coordination is a possible service expectation, not a confirmed customer request. Jordan says, We should confirm customer needs before placing project coordination inside commercial assumptions. For now, let us document Northline's seller lead and technical review. Once we know setup scope, we will decide whether coordination belongs with Northline, our team, or a customer owner. Priya agrees to ask a focused question during her next customer meeting.

This response does not dismiss the request. Nor does Jordan pretend every contribution has equal value. Jordan gives the partner an immediate next step and keeps untested assumptions out of a margin decision. Both sides know what evidence would change their view.

Margin conversations become harder when a reseller frames effort as a single total. Break total effort into customer facing work, internal coordination, and work supplied by another party. Customer facing work includes meetings, demonstrations, setup tasks, or first response support. Internal coordination includes forecast reviews, internal approval work, and communication between partner teams. Work supplied elsewhere might include vendor specialists, a customer project lead, or an outside service provider. Each category deserves a different conversation.

For customer facing work, ask what outcome a customer expects. A technical review might help a customer decide whether a workflow fits. Setup work might place an agreed configuration in service. First response support might route questions to an appropriate owner. For internal coordination, ask whether a simpler process would reduce effort. A standing weekly meeting often serves a large program but adds little value for a small evaluation. For work supplied elsewhere, verify availability before mentioning terms. Avoid assigning another team work through a reseller conversation.

Pay attention to language which hides uncertainty. Phrases such as we usually handle everything or customers expect white glove support do not give enough detail for a decision. Invite a clearer answer. Say, Which two activities are nonnegotiable for this customer, and who requested each one? The reseller might identify a real concern about service ownership. They might also notice a planned activity lacks a customer need. Either answer moves discussion forward.

Avoid arguing over whether a partner deserves margin. Respecting a partner's contribution does not require agreement before facts are clear. Explain your process plainly. Say, I need a shared view of customer work and ownership before I bring a commercial request forward. Here is what I heard. Then name activities, owners, and unresolved questions. A partner should leave knowing what you will review and when you will return.

Timing matters. Do not promise a commercial answer before collecting missing details. Set a specific short checkpoint instead. In Jordan's fictional situation, Priya agrees to ask the customer about setup coordination on Tuesday. Jordan schedules a fifteen minute partner call for Wednesday afternoon. Jordan will bring a written activity record. Priya will bring customer feedback and a proposed owner for any coordination work. Neither person promises an exception during Tuesday's customer meeting.

A reseller might press for an immediate answer. Stay direct. Say, I hear your request. I do not have enough detail to present a sound commercial position today. If we confirm scope and ownership by Wednesday, I will explain next steps on our call. This protects credibility. An unsupported promise creates a larger problem once people begin planning around a number.

Prepare before an internal discussion too. Bring customer segment, opportunity stage, expected deal shape, planned partner activities, other team commitments, and open questions. Do not describe a margin request as urgent without context. A reviewer needs enough information to understand why proposed terms connect to customer work. If no decision is available yet, tell the reseller when you expect an update rather than leaving them to chase several people.

Practice with a colleague using a fictional partner request. Give your colleague four minutes to describe a margin concern in broad terms. Your role is to ask for activity, owner, timing, and customer reason. Do not discuss a number. At minute four, read back your work record and circle one assumption needing customer confirmation. End practice by sending a short meeting note: Northline will confirm whether the customer seeks setup coordination before Wednesday's partner call.