Skip to main content
Loading...
sales

Handle the 'You're Too Small or Too New to Trust' Objection

Practice answering a late-stage buyer who says your company is too small or too new to trust. Build a calm, credible response that lowers perceived risk and keeps the deal moving.

Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Healthcare · Saas · B2b services

Overview

This roleplay practice scenario helps a seller respond when a buyer says the company is too small, too new, or too unproven to trust with their business. The situation is a late-stage sales call with a mid-market healthcare procurement manager who already sees product fit but is worried about vendor risk after learning the company was founded only three years ago.

Use this template when the conversation has moved past features and into decision risk, references, continuity, and procurement approval. It is especially useful for enterprise or mid-market deals where the buyer needs reassurance without feeling pressured. The learner practices acknowledging the concern, offering concrete credibility signals, asking what would reduce the buyer’s risk, and proposing a next step the buyer can reasonably accept.

Do not use this template as a generic discovery exercise or a broad pitch practice. It is not about convincing a skeptical audience in the abstract; it is about handling one specific objection in a realistic sales moment. If the real issue is price, security, implementation capacity, or product fit, use a different scenario. This one is for the trust objection that appears when the buyer likes the solution but is still deciding whether the vendor is safe enough to choose.

How to use this template

  1. Read the situation and note the buyer’s concern, the deal stage, and the specific risk signal the persona is likely to raise.
  2. Start the roleplay by responding to Jordan’s opening line and keep the conversation focused on trust, continuity, and decision criteria.
  3. Use the persona’s reactions to test whether you acknowledge the concern before you defend the company or jump into a generic pitch.
  4. Complete the attempt until you have addressed the rubric criteria and proposed a concrete next step the buyer can evaluate.
  5. Review the scored feedback, identify where you sounded defensive or vague, and retry with a tighter acknowledgment and stronger proof points.

Best practices

  • Acknowledge the buyer’s risk concern before you mention your company’s strengths.
  • Use concrete credibility signals such as named customer types, implementation support, references, or operational safeguards.
  • Ask what would make the buyer comfortable so you can learn their decision criteria instead of guessing.
  • Keep your tone steady and matter-of-fact; sounding defensive makes the trust gap feel larger.
  • Reframe the objection into a smaller, lower-risk next step such as a reference call, pilot, or stakeholder review.
  • Match the buyer’s procurement mindset by speaking to continuity, accountability, and rollout support rather than hype.
  • If the buyer pushes back again, stay curious and narrow the issue instead of repeating the same reassurance.
  • Avoid overpromising maturity you cannot prove, because vague claims weaken credibility in this scenario.

What this template typically catches

Issues teams running this template most often surface in practice:

The learner defends the company before acknowledging the buyer’s concern.
The learner gives vague credibility claims instead of specific proof points.
The learner talks only about product fit and ignores vendor risk.
The learner fails to ask what would reduce the buyer’s perceived risk.
The learner pushes for a close without offering a safer next step.
The learner sounds apologetic or defensive, which lowers confidence.
The learner does not adapt to procurement language and decision criteria.
The learner treats the objection as a one-line rebuttal instead of a real trust conversation.

Common use cases

Healthcare procurement review
A procurement manager at a mid-market healthcare company likes the workflow fit but worries the vendor may not be stable enough for a long-term rollout. The learner must respond with calm proof points and a low-risk next step.
Founder-led enterprise pitch
A founder is selling directly to a buying committee that questions whether the company can support a larger deployment. The roleplay tests whether the learner can build trust without sounding like they are overselling the startup story.
Mid-market security and continuity concern
A buyer is open to the solution but wants reassurance about support, longevity, and implementation follow-through. The learner practices translating company maturity into manageable risk rather than trying to eliminate all doubt.

Frequently asked questions

What kind of sales call is this template for?

This template is for a late-stage sales conversation where the buyer likes the product fit but hesitates because your company is small, new, or not yet widely proven. It is designed for a procurement-minded buyer who is evaluating vendor risk, not for an early discovery call. Use it when the objection is about trust, longevity, or business continuity rather than price or features. The goal is to practice a response that reduces risk without sounding defensive.

Who should run this roleplay?

A sales rep, account executive, founder-led seller, or sales manager can run it. It is especially useful for anyone selling into procurement, operations, or finance stakeholders who care about vendor stability. A coach or manager can also use it in team practice to assess how well the learner handles skepticism. The persona is built to push on credibility, so it works well for reps who need stronger objection-handling language.

How often should a team use this scenario?

Use it during onboarding, before enterprise pipeline reviews, and any time a rep is preparing for a deal where company size is likely to come up. It also works well as a recurring practice scenario because the objection changes depending on the buyer’s risk threshold and decision criteria. Reps can repeat it to improve their opening line, proof points, and next-step framing. It is most useful when paired with other objection scenarios like pricing, security, or implementation risk.

What should the learner actually say in the roleplay?

The learner should acknowledge the buyer’s concern first, then answer with specific credibility signals such as customer references, implementation support, financial stability, or product maturity. They should ask what would reduce the buyer’s risk and use that answer to propose a concrete next step. The best responses do not argue that size does not matter; they show how the buyer can evaluate risk in a practical way. The template rewards calm, specific, and buyer-centered language.

How is this different from a generic objection-handling template?

This template is built around one specific objection: trust concerns tied to company age or size. That makes the persona more realistic, the situation more concrete, and the rubric easier to score. Instead of practicing broad persuasion, the learner practices a targeted response that addresses vendor risk, procurement concerns, and decision criteria. That specificity helps the roleplay feel closer to an actual late-stage sales call.

What are the most common mistakes this scenario surfaces?

The most common mistake is jumping straight into a company pitch before acknowledging the buyer’s concern. Another is overcompensating with vague claims like 'we’re growing fast' instead of offering concrete proof points. Reps also often fail to ask what would make the buyer comfortable, which means they miss the real decision criteria. The scenario surfaces whether the learner can turn skepticism into a manageable next step.

Can this template be customized for different industries or deal sizes?

Yes. You can swap in a different buyer persona, industry context, or proof points while keeping the same trust objection. For example, a healthcare procurement manager may care about continuity and implementation support, while a finance buyer may care more about stability and references. You can also adjust the difficulty by making the persona more skeptical or more open to evidence. The core structure stays the same: acknowledge, prove, ask, and propose a next step.

What integrations or supporting materials work well with this roleplay?

This scenario works well alongside customer references, case studies, security summaries, implementation plans, and renewal or retention data. Those materials give the learner realistic proof points to reference during the conversation. It also pairs well with call coaching notes or a rubric-based scorecard so managers can review the attempt consistently. If your team uses a CRM or sales enablement library, this template can be linked to the assets reps should pull before the call.

What should a manager look for in a strong attempt?

A strong attempt shows the learner acknowledged the risk concern before defending the company, asked a clarifying question about the buyer’s criteria, and offered a concrete next step that feels safe. The rep should sound steady and credible, not reactive or apologetic. They should also avoid overselling and instead frame the decision as a manageable evaluation. If the buyer still hesitates, the rep should keep the conversation open rather than forcing a close.

Go deeper on the topic

Related guides

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Handle the 'You're Too Small or Too New to Trust' Objection ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.