STEP 1 — Classify the Objection Primary objection: Trust / Product fit / Status quo Secondary possibilities: Trust Product fit Lack of perceived differentiation Status quo Lack of urgency Why? “Unknown tool” is fundamentally different from “too expensive” or “we already use Greenhouse.” The prospect appears to be communicating: “I don't know this product well enough to feel comfortable choosing it.” That creates uncertainty around: whether the ATS actually works, whether it is reliable, whether it integrates with their recruitment stack, whether candidates/recruiters will adopt it, whether the vendor will support them, whether switching is worth the disruption. Important: There is currently insufficient evidence to conclude that the prospect has a genuine objection to the product. They may simply have low familiarity. STEP 2 — Find the Hidden Objection Most likely underlying concern: “Why should I trust an unfamiliar ATS enough to replace or introduce something I already know?” Confidence: Medium Evidence The phrase “unknown tool” contains almost no explicit criticism of functionality or price. That makes it more likely that the problem is uncertainty, rather than a concrete product deficiency. The buyer may be thinking: “If this is an unfamiliar vendor, why should I take the risk?” There is another possibility: “I've never heard of you, and therefore I don't see a reason to spend time evaluating you.” That's subtly different. The first is a trust objection. The second is an attention/priority objection. The salesperson needs to distinguish between them. STEP 3 — Analyze the Buyer's Position What the buyer wants Probably: efficient recruitment workflows, less administrative work, better candidate management, faster hiring, reliable reporting, integrations, minimal disruption, predictable implementation. But “efficient software” is not yet a compelling business case. Efficiency is a feature-level benefit. The buyer ultimately needs to understand: “What business problem becomes materially better if we adopt this?” What they fear The biggest fears are likely: choosing the wrong ATS, implementation problems, poor integrations, recruiter resistance, candidate experience problems, migration headaches, vendor instability, paying for functionality they don't need, discovering that the new system isn't meaningfully better. What they stand to gain Potentially: lower recruitment administration costs, greater recruiter productivity, faster hiring processes, improved visibility, better candidate experience, fewer manual processes. But none of these should be presented as facts until established for this prospect. What they stand to lose by doing nothing Potentially: continued manual work, inefficient workflows, slower hiring, poor visibility, unnecessary recruiter workload. Again, this needs discovery. What happens if they choose a competitor? They may get: greater brand recognition, established integrations, proven implementation processes, references, lower perceived vendor risk. This is precisely why an unknown ATS cannot compete purely by saying: “Our software is more efficient.” It needs to reduce perceived switching and vendor risk. Likely decision criteria For an ATS, I'd expect: Workflow fit Ease of use Integration capabilities Implementation effort Recruiter adoption Reporting/analytics Candidate experience Security/compliance Vendor reliability Total cost Demonstrated ROI STEP 4 — Should the Objection Be Overcome? Category: A + B + C — potentially misunderstanding, legitimate concern, and missing business case. It is not yet a genuine rejection. The prospect's unfamiliarity is legitimate. You shouldn't tell them: “Being unknown doesn't matter.” It obviously matters to the buyer. Instead, the salesperson needs to determine what specifically makes the unfamiliarity risky. There is also a business-case problem. If your entire positioning is: “We're a new, efficient ATS.” that's weak. Almost every ATS vendor can say: “We're efficient.” The stronger proposition is: “Your current recruitment process creates X inefficiency, which costs you Y. Our system changes X by doing Z.” The product needs to move from “unknown software” to “credible solution to an expensive problem.” STEP 5 — Response Strategy 1. Acknowledge Don't fight the objection. Something like: “That's fair. If the platform isn't familiar to you, I'd want to understand why it deserves consideration before asking you to change anything.” This reduces defensiveness. 2. Clarify Find out what “unknown” actually means. Is it: unknown vendor? lack of references? unfamiliar functionality? concern about implementation? concern about integrations? concern about security? lack of market reputation? Those require completely different responses. 3. Reframe The conversation shouldn't become: “Have you heard of us?” It should become: “Does this solve a sufficiently important problem better than your current approach?” That's the key shift. 4. Evidence Use whatever evidence genuinely exists: customer references, case studies, measurable implementation results, product demonstrations, integration documentation, security documentation, customer retention, implementation timelines. Never compensate for low brand awareness with invented credibility. 5. Resolve If the problem is vendor risk, reduce vendor risk. For example: reference call, pilot, limited implementation, technical validation, proof-of-concept, integration review, implementation plan. 6. Advance Don't end with: “Would you like another demo?” Give the buyer a concrete evaluation step. STEP 6 — Three Response Styles A — Consultative The strongest default approach is to not defend the product immediately. “That’s completely fair. If the platform is unfamiliar, I wouldn’t expect you to take that on trust. When you say ‘unknown,’ is the main concern that you haven’t seen enough evidence that the product is reliable, or that you’re not yet convinced it solves a problem that justifies changing your current ATS? That distinction is important, because if the current system is working well and there’s no meaningful business problem to solve, I wouldn’t recommend switching just for the sake of using a newer tool. If there is a specific inefficiency you’re trying to fix, though, we can evaluate the platform against that problem and see whether it actually provides enough improvement to justify the change.” B — Commercial This approach shifts the discussion toward economics. “I understand. The fact that we’re less familiar than the established ATS vendors is a legitimate consideration. The question I’d suggest we answer is whether familiarity is actually more valuable than the operational improvement available from changing systems. If your current ATS is already giving your recruiters the productivity, workflow efficiency and visibility you need, then there may be no financial reason to switch. If it’s creating measurable inefficiencies, however, we can quantify those first and then determine whether the improvement from a new system would justify the implementation cost and risk. That way you’re not choosing us because we’re new or because we claim to be efficient—you’re evaluating whether the business case is strong enough.” C — Executive For a senior decision maker, I'd make it considerably shorter. “That’s fair. An unfamiliar vendor creates additional perceived risk. I wouldn’t ask you to overlook that. I’d suggest we test the business case instead: what does your current ATS do well, where does it create friction, and is there enough measurable improvement available to justify changing? If the answer is no, we should stop there. If the answer is yes, we can address the vendor and implementation risk separately.” STEP 7 — Best Clarifying Question The single highest-value question is: “When you say the tool is ‘unknown,’ is your concern primarily that you don't know whether the vendor is trustworthy, or that you don't yet see enough difference from your current ATS to justify evaluating a change?” This is excellent because it separates two completely different sales strategies. If they say: “I don't trust an unknown vendor.” → Build credibility and reduce risk. If they say: “I don't see enough difference.” → Build differentiation and ROI. If they say: “We don't want to change systems.” → Status quo/implementation objection. If they say: “Our current ATS works fine.” → Need/urgency problem. If they say: “We already have another vendor we're considering.” → Competition. One question can therefore dramatically improve the entire sales strategy. STEP 8 — Worst Possible Response The worst response would be something like: “Actually, we're a very efficient ATS and our software has tons of features. We have automated workflows, reporting, integrations, AI functionality, dashboards, candidate management, analytics…” Why it's bad The prospect didn't say: “I don't know what features your ATS has.” They said: “Unknown tool.” Feature dumping doesn't reduce uncertainty. In fact, it increases cognitive load. Other bad responses: Immediate discounting “We can give you 20% off because we're a newer company.” This can actually reinforce the buyer's concern: “Why are they desperate to win us?” Attacking established competitors “The big ATS platforms are outdated.” Without evidence, this sounds defensive and makes the vendor appear insecure. Fake urgency “We only have a few implementation slots left.” Unless genuinely true, this destroys trust. Overexplaining A five-minute monologue about the company's history doesn't answer the buyer's question. Repeating the pitch “But our software is more efficient!” The buyer already heard the positioning. The issue is proof and relevance, not repetition. STEP 9 — Negotiation Analysis There is no demonstrated price objection, so discounting is premature. What should NOT be conceded? Don't immediately concede: price, implementation fees, contract length, premium functionality, support, custom development. The buyer hasn't earned a concession because they haven't actually asked for one. What could potentially be exchanged? If vendor risk becomes the issue, consider concessions that reduce risk rather than reduce price, such as: structured pilot, phased implementation, additional onboarding, technical validation, reference calls, implementation milestones. These may be commercially more intelligent than a discount. Principle Every concession should purchase something in return. For example: Bad: “We'll give you 15% off.” Better: “If you can commit to a 24-month agreement, we can discuss improved commercial terms.” Now the concession buys something. But even that should only happen after establishing that price is actually a barrier. Is the prospect price-sensitive? Unknown. There is currently zero evidence that price is the issue. STEP 10 — Deal Probability MEDIUM Not LOW, because “unknown tool” is not a rejection. Not HIGH, because the buyer hasn't demonstrated: a strong pain, urgency, buying intent, internal sponsorship, budget, authority, or a compelling reason to change. The most important piece of information Why does the buyer consider the tool “unknown”? That answer could completely change the probability. For example: “I've never heard of you.” → Potentially recoverable through credibility. “We don't trust new vendors with our recruitment data.” → Significant risk objection. “Our current ATS already does everything we need.” → Much harder opportunity. “We're already implementing another ATS.” → Very low probability. “Show me why this is better.” → Potentially strong opportunity. STEP 11 — Final Sales Recommendation REAL OBJECTION: Insufficient familiarity with the ATS/vendor, creating uncertainty about whether it deserves consideration. BUYER'S PRIMARY CONCERN: Likely perceived risk or insufficient differentiation, but this has not yet been confirmed. BEST RESPONSE STRATEGY: Don't defend the product. Diagnose what “unknown” means, then address the specific risk with evidence, validation, or a business case. BEST QUESTION TO ASK: “When you say the tool is ‘unknown,’ is your concern primarily that you don't know whether the vendor is trustworthy, or that you don't yet see enough difference from your current ATS to justify evaluating a change?” SHOULD WE CONCEDE? NO. There is no reason to discount or give away anything yet. PROBABILITY OF CLOSING: MEDIUM. NEXT BEST ACTION: Identify whether the obstacle is vendor trust, product differentiation, status quo, or lack of urgency before presenting another pitch. The key strategic insight Your current positioning — “new, efficient software for recruitment” — is probably too weak to overcome an unknown-vendor objection. “Efficient” describes virtually every modern ATS. The stronger sales conversation is: Current recruitment problem → measurable business consequence → specific improvement → evidence → reduced implementation/vendor risk → commercial justification. If you can't establish that chain, the prospect's objection may not be something to overcome at all. It may simply be evidence that there isn't a sufficiently compelling reason for them to change.