# Objection Handling Script ## B2B Project Management SaaS ($49/seat/month, mid-market ops teams) — Mid-Stage Deal --- ### CARD 1 — EXECUTIVE SUMMARY Three objections are in play, and they are not equally risky. **OB3 (SOC 2 requirement)** is the highest-risk item: it's phrased as a hard gate ("before we can even consider this"), not a negotiable preference, and the product context provided does not state the company's actual SOC 2 status (certified, in progress, or absent). Until that's confirmed internally, this objection cannot be responsibly scripted past — it may be a **potential disqualification signal**, not a routine objection. OB2 (price vs. two named competitors) is a standard comparative price objection but carries **moderate sequencing risk** into feature and status-quo territory. OB1 (switching cost from Asana) is the most conventional of the three and the most directly addressable with a consultative approach, though no migration-specific evidence was supplied to work with. --- --- ### CARD 2 — OBJECTION CLASSIFICATION REGISTER | ID | Objection (verbatim) | Category | Underlying Concern (flagged as interpretation) | |---|---|---|---| | OB1 | "We already have Asana and switching costs too much" | STATUS-QUO | Likely concern is disruption/effort of migration and sunk investment in current workflows — **interpretation, not confirmed**; could also mask an unstated Feature-Gap ("Asana already does enough") | | OB2 | "Your price per seat is higher than 2 competitors we looked at" | PRICE | Likely a straightforward budget/value comparison — **interpretation, not confirmed**; framing ("2 competitors") suggests active comparison shopping, which may indicate Competitor-category concerns are close beneath the surface | | OB3 | "We need SOC 2 before we can even consider this" | TRUST-RISK | Stated as a procurement gate rather than a preference — the "before we can even consider this" phrasing suggests this may function as a **hard blocker**, not a negotiable trust concern — **interpretation, not confirmed**, since actual internal urgency/flexibility is unknown | --- --- ### CARD 3 — OBJECTION DIAGNOSTIC **OB1 — "We already have Asana and switching costs too much"** | Factor | Score | Status | Rationale | |---|---|---|---| | Underlying Concern Clarity | 3/5 | INFERRED | Surface concern (switching effort) is clear; whether it's really about time/cost of migration vs. satisfaction with Asana itself is not confirmed | | Deal Risk If Unresolved | 3/5 | MODERATE | Common objection at mid-stage; rarely fatal alone, but compounds if paired with price resistance | | Trust Level Implied | 3/5 | MODERATE TRUST | Buyer is engaging with cost/effort tradeoffs rather than dismissing outright — signals real evaluation, not stonewalling | | Objection Sequencing Risk Index (OPERATIONAL EXTENSION — NOT A PSYCHOLOGICAL DIAGNOSIS OF THE BUYER) | — | MODERATE | Addressing switching cost by emphasizing migration support may prompt a follow-up price question ("does migration help cost extra?") | **Core Objection Reading:** A conventional status-quo/switching-cost objection with no indication of insincerity. Treat as genuine friction to reduce, not a smokescreen. --- **OB2 — "Your price per seat is higher than 2 competitors we looked at"** | Factor | Score | Status | Rationale | |---|---|---|---| | Underlying Concern Clarity | 4/5 | CONFIRMED (surface level) | Buyer explicitly states the comparison basis (per-seat price vs. two named alternatives) — clearer than OB1, though *why* price matters more (budget ceiling vs. perceived value gap) is still inferred | | Deal Risk If Unresolved | 4/5 | MODERATE-HIGH | Explicit competitor benchmarking signals active shopping; unresolved, buyer has a ready alternative to default to | | Trust Level Implied | 3/5 | MODERATE TRUST | Sharing competitor pricing openly suggests the buyer is negotiating in good faith rather than using price as a soft exit | | Objection Sequencing Risk Index (OPERATIONAL EXTENSION — NOT A PSYCHOLOGICAL DIAGNOSIS OF THE BUYER) | — | HIGH | Justifying the price gap invites direct feature-by-feature comparison against the named competitors and against Asana (OB1), risking a Feature-Gap objection surfacing next | **Core Objection Reading:** A legitimate comparative-price objection. No basis in the stated objection to assume it's pretextual — the buyer has named specific comparators, which is a substantive claim requiring a substantive answer, not a generic value pivot. --- **OB3 — "We need SOC 2 before we can even consider this"** | Factor | Score | Status | Rationale | |---|---|---|---| | Underlying Concern Clarity | 5/5 | CONFIRMED (as a stated requirement) | Buyer states the requirement plainly; ambiguity is not in what they said but in whether it is truly non-negotiable or has flexibility (e.g., roadmap commitment accepted) | | Deal Risk If Unresolved | 5/5 | CRITICAL | Phrased as a precondition to further consideration, not a concern to be managed alongside others | | Trust Level Implied | 2/5 | LOW-MODERATE TRUST (procedural, not personal) | This reads as a procurement/security-policy gate rather than distrust of the sales rep — but it is a hard trust-and-risk control nonetheless | | Objection Sequencing Risk Index (OPERATIONAL EXTENSION — NOT A PSYCHOLOGICAL DIAGNOSIS OF THE BUYER) | — | LOW | Unlike price or switching cost, resolving or failing to resolve this is unlikely to *surface* a new objection — it either clears the path or ends the conversation | **Core Objection Reading:** This is the objection most likely to be a **disqualification signal** rather than something to script through. The product context supplied does not confirm current SOC 2 status (certified / in audit / not started). No response framework below assumes an answer that wasn't given. --- --- ### CARD 4 — RESPONSE FRAMEWORK PER OBJECTION **OB1 (STATUS-QUO) — Switching cost from Asana** - **Acknowledge:** "That's a fair concern — migrating a team's active project data and habits off a tool you're already running is real work, not a small ask." - **Reframe:** Shift the frame from "cost of switching" to "cost of staying, compounded" — e.g., what specifically about the current setup prompted them to take this meeting at all, since that gap doesn't close by staying put. - **Evidence to offer:** UNKNOWN — the product context does not include migration tooling details, a typical migration timeline, or a customer switching case study. **Do not invent a migration timeframe, data-import capability, or customer name.** This must be sourced internally before the next conversation. - **Question to ask back:** "When you picture switching, is the bigger worry the time to migrate, the risk of disrupting active projects mid-flight, or team resistance to learning something new?" --- **OB2 (PRICE, comparative) — Higher per-seat price than two competitors** - **Acknowledge:** "You're right to flag that — and I'd rather you compare us on the numbers you actually have than have me wave that away." - **Reframe:** Move the comparison from sticker price per seat to total cost of the outcome the tool is meant to deliver — but only using facts actually in hand, not invented ROI figures. - **Evidence to offer:** UNKNOWN — no specific ROI statistic, efficiency benchmark, or differentiating feature-to-price mapping was included in the product context. **Do not fabricate a percentage, dollar figure, or case study to close this gap.** Confirm what differentiators justify the price delta before responding further. - **Question to ask back:** "Which capabilities were the other two tools offering at that price — was it feature parity, or a lighter/less complete version of what you'd need here?" --- **OB3 (TRUST-RISK) — SOC 2 required before consideration** - **Acknowledge:** "That makes sense — for an ops team running project data through a new vendor, security review isn't optional, it's table stakes." - **Reframe:** Separate "is this a hard blocker today" from "is this something a documented roadmap and interim safeguards can satisfy" — but this reframe is only usable once internal compliance status is confirmed. - **Evidence to offer:** UNKNOWN — current SOC 2 status (certified, Type I/II, in progress, or not started) is **not present in the product context**. This response framework will not state or imply a compliance status that hasn't been confirmed internally. Get this answer from the compliance/security team before the next buyer conversation. - **Question to ask back:** "Is this a Type I or Type II requirement, and is it a hard gate with no exceptions, or would a documented compliance roadmap plus current security controls be something your team could evaluate in parallel?" --- --- ### CARD 5 — OBJECTION SEQUENCING RISK MAP | If You Address... | You May Surface... | Sequencing Risk | Suggested Order | |---|---|---|---| | OB2 (Price) by breaking down the cost delta vs. named competitors | OB1 (Status-Quo/Feature-Gap) — buyer starts comparing line-by-line against Asana too, not just the two named competitors | HIGH | Address after OB3 is resolved | | OB1 (Switching cost) by proposing migration support | OB2 (Price) — migration support could read as an added cost, reviving the price conversation | MODERATE | Address after OB3, alongside or just after OB2 | | OB3 (SOC 2) by proposing a roadmap/interim-controls path | Possible new TIMING objection if remediation or audit timeline is long — but not a new deflection, a legitimate follow-on constraint | LOW–MODERATE | Address first — this gates whether OB1/OB2 are worth pursuing at all | **Suggested overall order:** OB3 → OB2 → OB1. OB3 determines deal viability; there's limited value in negotiating price or switching effort before knowing whether the compliance gate can be cleared. --- --- ### CARD 6 — DO-NOT-SAY LIST - **"SOC 2 is basically in progress / almost done"** — unless confirmed true internally, this risks a false compliance claim to a security-conscious buyer, which is a trust-destroying and potentially legally exposed statement. - **"We're basically the same as Asana, just better"** — invites direct feature-by-feature scrutiny (compounds OB1→Feature-Gap sequencing risk) rather than differentiating. - **"Our price is competitive"** (unqualified) — vague, defensive-sounding, and non-responsive to a buyer who named specific comparators; reads as avoidance. - **"Switching is easy, it'll only take a day"** — dismisses a concern the buyer raised as real; if untrue or unconfirmed, damages credibility the moment they start migration. - **Any invented statistic, customer name, or case study** for either the price or switching-cost response — none were supplied in the product context, and fabricating one is a controlled-vocabulary violation regardless of how natural it would sound in the moment. --- --- ### CARD 7 — FOLLOW-UP EMAIL SNIPPET *(Strongest response — addressing OB3, since it gates the rest of the deal)* > Hi [Name], > > Thanks for being direct about the SOC 2 requirement — that's exactly the kind of thing better surfaced now than after weeks of evaluation. > > Before I give you a firm answer, I want to check two things internally: our current certification status and whether Type I or Type II is what your security review requires. I'll have a clear answer for you by [date] rather than guess in the meantime. > > In parallel, it'd help to know — is this an absolute precondition to any further evaluation, or would a documented security roadmap alongside our current controls be something your team could review while certification progresses? > > I'll follow up with specifics as soon as I have them. > > [Name] --- --- ### CARD 8 — DISQUALIFICATION SIGNAL CHECK **Disqualification signal present — pending internal confirmation.** OB3's phrasing ("before we can even consider this") functions as a stated precondition, not a soft preference. The product context supplied to this exercise does not confirm the vendor's actual SOC 2 status. Two distinct outcomes are possible and cannot be guessed here: - If SOC 2 (or an equivalent, buyer-acceptable interim posture) exists or is credibly near-term, this is a **routine, addressable trust-risk objection**. - If SOC 2 is absent with no near-term path, and the buyer's "before we can even consider this" is a literal hard gate with no flexibility, this **is a genuine disqualification signal** — no amount of consultative reframing changes an unmet hard compliance requirement. This must be resolved with the compliance/security team and, if the answer is unfavorable, escalated rather than scripted around. --- --- ### CARD 9 — METHOD NOTE This script is a preparation aid for the upcoming conversation, not a guarantee that any given objection will resolve favorably — real buyer conversations will surface details this document can't anticipate. Classifications and diagnostics are built on a seven-category Objection Root-Cause Taxonomy (Price, Timing, Authority, Trust-Risk, Competitor, Feature-Gap, Status-Quo), extended with an Objection Sequencing Risk Index that is strictly an **operational note on conversational order, not a psychological read on the buyer's intent or honesty**. Given the consultative sales style and mid-deal stage, tone throughout favors direct, collaborative questions over pressure tactics or premature closing language — appropriate for a stage where trust-building still outweighs urgency. Because OB3 carries a **DISQUALIFICATION SIGNAL PRESENT** reading pending confirmation, a sales manager (or whoever owns compliance status internally) should weigh in before further pursuit of this deal, particularly before any commitment — implied or explicit — is made regarding SOC 2 status or timeline. --- --- **VERDICT: NEEDS MANAGER INPUT — OB3 (SOC 2 requirement) is the highest-risk objection and cannot be resolved from the information given; its status as a routine trust-risk objection versus an outright disqualification signal depends entirely on the company's actual, unconfirmed compliance posture, and no further price or switching-cost negotiation (OB1, OB2) should be prioritized until that is confirmed.**