You Don't Need More Confidence. You Need Better Reps.

Better business reps are structured attempts that produce external feedback, an observable outcome, a debrief and an informed change to the next attempt. Confidence cannot repair poor targeting or an unclear offer. The practical task is to diagnose a narrow skill gap, test it within safe limits and let evidence improve the work.

Key takeaways

• Choose one specific capability to practise, such as qualifying a buyer's problem or securing a clear next step.
• Record observable responses and debrief each attempt; volume alone does not turn repeated mistakes into learning.
• Review comparable attempts at a planned point, make limited adjustments and keep experiments within authorised, reversible boundaries.

Confidence is a convenient explanation for a problem you have not diagnosed.

You hesitate before a sales call, so you decide you need confidence. A proposal goes unanswered, so you work on your mindset. A buyer challenges your price, so you tell yourself to be more assertive.

Perhaps. Or perhaps your questions are weak, your proposal solves the wrong problem, and you cannot explain the commercial value without hiding behind adjectives.

Confidence will not repair any of that.

Tennis offers a simple analogy: watching is not the same as learning to play. Business also requires selling, negotiating, leading, testing and adapting.

But there is a second problem. Getting onto the court is not enough. You can practise badly. You can repeat a mistake until it feels natural. You can become more comfortable without becoming more capable.

The useful question is not: how do I feel more ready?

It is: what kind of repetition would give me better evidence about what I can do, what is failing, and what I should change?

Spectatorship can look like preparation

Business spectatorship has excellent packaging.

You listen to founders explain their strategy. You save negotiation frameworks. You study pitch decks. You can describe a sales process more fluently than you can conduct a sales conversation.

None of those activities is worthless. The problem begins when familiarity with the language becomes your substitute for competence.

Knowing that discovery matters is not the same as discovering something useful from a buyer. Understanding the concept of delegation is not the same as giving someone a clear responsibility, the authority to deliver it, and a sensible escalation path.

Consumption offers a particular comfort: the problem stays tidy. Someone else has already selected the facts and explained the result.

Execution is less cooperative. The buyer is distracted. The requirements conflict. The person making the decision is not in the meeting. Your elegant framework encounters a situation it does not fully cover.

That is where a rep begins. Not because discomfort is valuable by itself, but because reality can now contradict you.

A business rep has four parts

For a customer-facing business rep, I would insist on four things: external contact, an observable outcome, a debrief, and a changed next attempt.

External contact means somebody outside your preparation responds. A real buyer answers a question, reviews an offer, rejects a proposal or agrees to a next step. Rewriting a pitch alone can improve it, but it is preparation for this kind of rep, not a replacement for one.

An observable outcome means you can say what happened without interpreting it as a personality verdict. “They asked for implementation details” is observable. “They loved us” is not. “They declined a follow-up” is observable. “The market does not understand innovation” is an escape route.

A debrief separates your intention from what occurred. What were you trying to learn? What did the other person actually say or do? What remains unknown?

A changed next attempt means the observation affects your behaviour. You ask a sharper question, narrow the offer, bring the right person into the conversation, or stop contacting a segment that does not fit.

If the attempt confirms that something worked, the change might be making that element deliberate and repeatable. You do not need to invent a new approach after every call.

Without this structure, activity can accumulate while capability stands still.

One hundred attempts can be one mistake repeated

A busy calendar is not a practice system.

If you make the same pitch to poorly qualified buyers, receive the same objection, and conclude that you need more volume, you may be repeating a targeting mistake rather than improving your selling.

The answer is not constant reinvention either. Changing your audience, price, message and product after each rejection makes the next result difficult to interpret.

Better reps need enough consistency to reveal a pattern and enough adjustment to address it.

Choose a skill narrower than “sales”. It might be identifying who owns the buying decision. It might be asking about the cost of an unresolved problem. It might be securing a specific next step instead of ending with “let me know”.

Then keep a record. Not a diary of how confident you felt. A record of the question, the response, the outcome and the adjustment.

Experience becomes useful when you can inspect it. Otherwise, “I have done this a hundred times” may tell me more about your endurance than your judgment.

Engineer the next call

Here is a hypothetical example, not a story from my own business.

A founder sells scheduling software to small service companies. Several prospects have said, “It looks good, but we cannot justify another subscription.” The founder assumes the problem is price and considers a discount.

That is a conclusion ahead of the evidence. The objection could reflect limited budget, a weak problem, poor timing, switching costs, or a failure to demonstrate value. The next call should help distinguish those possibilities.

Before the call, the founder writes a working hypothesis: “We are presenting features before establishing whether scheduling creates a costly problem for this buyer.”

The skill for this rep is problem qualification. The founder keeps the price unchanged and prepares questions about the current process, where it breaks down, and what happens when it does.

On the call, the buyer says: “Our spreadsheet works. Moving the team will take time.”

Instead of defending the software, the founder asks: “Where does the spreadsheet cause difficulty, if anywhere?” Then: “Who would have to change their routine for a switch to work?”

Suppose the buyer explains that missed updates cause occasional double bookings, but training the team is the bigger concern. That does not prove the sale is available. It identifies something more specific than “too expensive”.

The founder checks the interpretation: “It sounds as though reducing booking errors could matter, but only if adoption is manageable. Is that accurate?”

If the buyer agrees, the next step might be a demonstration with the person responsible for scheduling, focused on the transition. If the problem is minor and nobody wants to change, the appropriate outcome may be disqualification.

Afterward, the founder records the buyer’s wording, the evidence of a problem, the adoption objection, and whether a relevant next step was accepted. A friendly conversation without a commitment is recorded as exactly that.

The debrief is specific: “We still do not know how often the errors happen or who can approve the purchase.” The next changed attempt adds a question about frequency and brings decision ownership into discovery earlier.

The proposal should then reflect what was established: the buyer’s problem, the scope, implementation responsibilities, commercial terms and an agreed decision process. It should not claim savings the buyer has never validated.

If “another subscription” returns, ask what makes it unjustifiable. Do not assume every objection conceals a deal you can unlock. Sometimes the buyer is telling you there is no deal.

Review on a clock, not on an emotion

One rejection can provoke a dramatic pivot. One enthusiastic response can provoke an equally dramatic expansion.

Neither deserves that much authority.

Set a finite review window before running the test. For example, you might review after ten reasonably comparable conversations or two weeks of outreach. Those are operational boundaries, not statistically reliable thresholds, and not evidence that every sales cycle fits inside them.

At the review, look at who was contacted, who responded, which objections appeared, what advanced and what stalled. Include the inconvenient cases, not just the conversation that supports your preferred story.

Small samples are fragile. Buyers differ. Timing changes. A reply is not revenue, and a sale is not necessarily a repeatable process. In a long buying cycle, the useful evidence may concern qualification or progression rather than closed deals.

This discipline is not exclusive to sales, but the same test design does not belong everywhere. Hiring, regulated services and technical validation have different stakes and evidence requirements.

A review window is also not permission to ignore an immediate safety problem. Stop when an attempt breaches a limit you set, not when the calendar finally allows discussion.

Keep the experiment small enough to reverse

“Learn by doing” is not a licence to create damage and call it tuition.

Test a question before changing a contract. Test a limited, clearly scoped pilot before promising a broad rollout. Agree a budget cap, an end date, ownership and stop conditions before committing resources.

Financial commitments, legal obligations and hiring decisions need more than an operator’s appetite for learning. Use appropriate professional advice, approvals, due diligence and applicable safeguards. Do not gamble with client funds, misrepresent capabilities, bypass consent or treat a person’s livelihood as a casual experiment.

Some decisions are expensive or impossible to reverse. Their preparation must be correspondingly stronger.

The useful principle is not maximum action. It is bounded exposure to reality: enough to learn something meaningful, without taking risks you are not authorised or equipped to carry.

Education needs a live address

Books, MBAs and experienced mentors can be useful. Dismissing them is another way of avoiding precision.

A structured education can expose gaps you did not know you had. A good book can supply a framework. An experienced mentor can recognise a contractual risk or operational mistake before you repeat it.

The question is what you do with the input.

Bring the unanswered proposal to the mentor, not just your ambition. Bring the conflicting incentives to the classroom discussion. Read the chapter because you need to understand the decision in front of you, then apply what is appropriate and inspect the result.

Education and execution should inform each other. Neither replaces the other, and nobody needs to learn every expensive lesson firsthand.

Founders must build the review into the company

A founder’s operational competence is not measured by how often they personally rescue a deal.

It includes making useful judgment available to the team. Can people see what a qualified opportunity looks like? Do they know which promises require approval? Can they explain why a proposal changed?

Build a short, regular review around actual work. Examine a call summary, a proposal and a stalled opportunity. Use recordings only where permitted and with appropriate consent; written notes may be sufficient.

Ask what the team expected, what occurred and what the next attempt will change. Separate an execution error from a targeting problem or an unsupported assumption.

Someone owns the adjustment. Someone checks whether it happened. Useful findings enter the shared playbook, with their limits attached.

If people expect humiliation for admitting uncertainty, the review becomes theatre. If nobody has to change anything, it becomes conversation. Neither improves the work.

Thirty days, one capability

For the next thirty days, choose one commercially relevant capability, not a complete personality renovation.

In the first week, inspect recent work and define the gap. Choose a narrow question, establish a baseline from available records, and decide what evidence you will collect. Set the test’s boundaries and review dates.

In the second week, run comparable attempts. Capture observable responses promptly. Keep unrelated variables stable where practical, while recognising that real customers will never be identical laboratory conditions.

In the third week, review the accumulated evidence. Make a limited adjustment supported by what you have observed. If the evidence is thin or contradictory, say so. Another careful test may be more useful than a confident explanation.

In the fourth week, examine what changed and what remains unresolved. Decide what to retain, what to stop, and what needs a longer window. Share the usable learning with the people doing the work.

Thirty days may improve the quality of your process without producing a sale. It may expose a weak offer or show that you were practising against the wrong problem. Those findings matter, but they are not guaranteed rewards for effort.

Let evidence challenge your identity

Sometimes ego demands a pivot because rejection feels unbearable. Sometimes ego refuses a pivot because changing direction feels like admitting the original judgment was wrong.

Evidence does not care which version protects your identity.

Confidence can emerge from a record of competent action: you have handled a relevant objection, delivered what you promised, recognised a limit, or corrected a mistake. That gives you something firmer than encouragement.

It does not give you certainty. The next buyer can differ. The market can change. A capable operator still needs to ask questions.

This is also why fund judgment is more than a persuasive strategy: when real resources are committed, the quality of the review and the response to weakened assumptions matter more than projecting confidence.

Stop treating confidence as the entry requirement. Design attempts that can teach you something, review them honestly, and change the work where the evidence warrants it.

If you repeated your current approach thirty more times, what would you actually learn—and what have you changed to make the next rep worth doing?

Frequently asked questions

What is a useful business rep?

For customer-facing work, a useful rep combines external contact, an observable outcome, a debrief and an informed next attempt. It should reveal something about the buyer, the offer or your execution rather than merely increase your activity count.

How can a founder improve sales practice without changing everything?

Choose a narrow skill, such as problem qualification or identifying decision ownership. Keep unrelated variables reasonably stable, record what buyers say and do, and review comparable attempts at an agreed point before making a limited adjustment.

Is confidence necessary before taking action?

Confidence is not a substitute for preparation or competence, and it need not be the entry requirement for a bounded attempt. Appropriate preparation, consent and safeguards still matter. Confidence may follow evidence of competent action, but it does not remove uncertainty.

Will thirty days of better reps guarantee more sales?

No. A thirty-day review may improve the process, expose a weak offer or identify a targeting problem without closing a sale. Longer buying cycles may require more time; the aim is usable evidence and better decisions, not a guaranteed commercial result.

References

• Related perspective: Hedi Mesme — learning tennis and business through execution, not spectatorship. The practice framework and thirty-day application above are proposed working methods, not claims of empirically proven effectiveness; the software-sales example is hypothetical.

Continue the conversation

Choose one capability and write down what your next attempt should reveal. Explore Hyper Hedi for further reflection, and browse the blog for more perspectives on execution.