Objection-handling FAQ and cheat sheet

Raw source preview

Raw, unprocessed file text shown below. Preview truncated for readability.

# Objection-handling FAQ and cheat sheet

This is an internal-first draft for the founder, sales lead, and outreach owners.

It is designed for live private-beta conversations, not as a buyer-facing document to send as-is.

Competitive positioning in this draft was refreshed against current market pages on 2026-04-18.

## Why these questions will come up

Buyers are already hearing strong claims from current vendors:

- Qualtrics positions ExpertReview, response quality, and enterprise-grade security.
- Forsta now positions AI agents across setup, analysis, and reporting.
- Attest and Zappi lead hard on data quality and fast, reliable responses.
- Suzy positions AI-moderated conversational research and presentation-ready outputs.
- Dovetail, Stravito, and KnowledgeHound position repository, search, AI Q&A, and evidence reuse.

That means the real sales job is not just "What is this?" It is "Why this instead of my current stack, my current vendor's AI, or a stitched-together set of tools I already trust?"

## How to use this sheet

- Start with the short answer.
- Expand only if the buyer leans in.
- Tie every answer to a workflow, screen, or proof hook.
- Translate "confidence" into defensibility, audit trail, governance, or reduced risk when that language lands better.
- Do not improvise on legal, security, or procurement claims that are not yet packaged.
- Add new real objections from weekly GTM reviews instead of treating this as static.

## Positioning guardrails

- We are strongest when the buyer values governed redesign before launch, live quality oversight during fieldwork, and connected evidence reuse together.
- Do not position the product as a forced rip-and-replace on day one.
- Do not position the system as fully autonomous research.
- Do not imply Research Guard already matches Qualtrics or Conjointly on in-builder product maturity or one-click immediacy.
- Do not imply the platform already matches Qualtrics-class post-field response-quality coverage or enterprise security proof.
- Do not imply the trust or procurement pack is more complete than it is.
- Do not imply mature connector coverage to incumbent platforms unless the workflow shown is genuinely live.
- Do not oversell cross-study certainty if comparability still depends on context and metadata.

## Quick discovery cues before answering

- What do you use today for survey authoring, fieldwork, reporting, and repository/search?
- Where does the pain show up most: design quality, fieldwork quality, slow reporting, duplicate work, or stakeholder trust?
- Are you trying to replace a system, add a layer, or run a narrow pilot?
- Who currently owns research standards and final sign-off?
- How heavy is your security or procurement process?

## Category and fit

### 1. What exactly is this?

- Short answer: It is a research platform designed specifically to improve how research is designed, collected, and reported.
- Longer answer: The pitch is not "another AI feature" or "just another survey tool." The wedge is that QA and QC are built across the workflow instead of being handled as separate cleanup, separate oversight, or a weak afterthought once the report is already done. In practice, that means junior researchers can deliver work to a safer, more senior standard, and senior researchers can deliver more work more quickly without sacrificing quality. Because the research stays within the platform, it can also expand over time into a system of record for insight knowledge.
- Proof hook: Before / during / after confidence story, Trust Centre, connected evidence layer.
- Watch-out: Do not lead with the full suite vision if the buyer only needs one immediate job solved.

### 2. What is genuinely differentiated here?

- Short answer: The differentiation is not just that checks exist. It is that this is a connected research platform where the review carries through into actual approved changes instead of stopping at a generic checker or a single AI feature.
- Longer answer: The strongest wedge today is Research Guard as a review system that takes findings all the way through to actual approved changes, not just a questionnaire scorer. It checks whether the screener and routing qualify the right people, flags issues in the order they appear in the questionnaire, follows up on the judgment calls, turns the findings into tracked changes, and ends with a final pass to confirm the fixes were actually applied. It also leaves a clear record of what was flagged, why, and what was approved. Incumbents increasingly cover slices of design QA, response quality, reporting AI, or repository search. Qualtrics is stronger where the review is built directly into the survey-authoring tool and where enterprise packaging is already mature. Conjointly is stronger on low-friction in-product script review. The case for this platform is that quality controls, evidence, and traceability stay connected through the work instead of living in disconnected checks at different stages, and that the same system can expand over time to cover more of the team's research needs without pushing them toward more point-tool sprawl.
- Proof hook: Internal confidence narrative plus the 2026-04-18 Research Guard competitive deep dive.
- Watch-out: If the buyer only values one slice, say that honestly rather than pretending the whole-platform story matters equally to everyone.

### 3. Who is this really for?

- Short answer: This is built for enterprise client-side insight teams under pressure to move faster without losing rigor.
- Longer answer: The strongest buyer is the in-house research or insights team inside a mid-to-large company that is being bypassed by lighter-weight tools, is struggling to keep standards consistent, and needs research to become a reusable body of truth instead of a folder graveyard.
- Proof hook: Audience profiles and confidence positioning brief.
- Watch-out: Do not broaden the default answer into agencies or every research buyer if the conversation does not support that.

### 4. How does this help without creating more bad DIY research?

- Short answer: Research Guard helps stop bad DIY research, while non-researchers still get safer access to knowledge without bypassing the insight team.
- Longer answer: The aim is to make the insight team stronger and more scalable, not to erase research standards. Research Guard and the wider confidence layer are there to put safeguards around how research is designed and reviewed, so weaker DIY-style work is less likely to slip through unchecked. At the same time, non-research stakeholders can get safer access to validated knowledge from the platform without having to run their own ad-hoc research or dig through old decks. The insight team still owns methodology, quality thresholds, sign-off, and what gets trusted. The simplest way to say it is that the insight team stays in charge of standards, while other teams get safer access to what the insight team already knows.
- Proof hook: Research Guard plus system-of-record and indispensable-function narrative.
- Watch-out: Never imply "everyone can now do research" if the buyer is worried about bypass and standards erosion.

## Stack and competitive objections

### 5. Do we have to rip out Qualtrics, SurveyMonkey, or Forsta?

- Short answer: No. We can work with your existing Qualtrics studies, and the early wedge should survive without a forced rip-and-replace.
- Longer answer: If a buyer is locked into an incumbent, position this around the missing layer: are we sure we designed the right research for the brief, captured the right context, connected that work to the rest of the team's research, and kept quality and evidence visible through the workflow? The opening move should be low-friction adoption, not a platform war. If they want to keep Qualtrics for survey execution, that can still work. If they want to use our survey workflow, the Trust Centre adds built-in quality review that helps surface poor responses while the study is still live. The strongest wedge today is review and redesign governance around the study, not a claim that every incumbent-platform bridge is already mature and turnkey.
- Proof hook: Stack-gravity analysis and pricing model.
- Watch-out: Do not make replacement the lead unless the buyer brings it up first, and do not imply mature connector coverage if the workflow still depends on imported study assets.

### 6. Why not keep our current survey platform and add a repository tool?

- Short answer: If a buyer is going to buy a repository anyway, ours is stronger when they also want the research itself to get better, not just easier to store and search.
- Longer answer: A generic repository tool may be fine if the buyer only wants storage, search, or light reuse. The case for this product is stronger when the team feels pain across more than one stage: not enough design reassurance up front, bad data discovered too late, reporting that is hard to defend, and research that disappears after the deck. In that case, buying our platform instead of a standalone repository means they get the quality-improvement layer as well as the knowledge layer. It also means the repository is tuned for an insight team rather than acting like generic document storage. In beta, we can already ingest external research into the knowledge base and process reports page by page or slide by slide to improve retrieval and search context, even as the knowledge layer keeps maturing. When we have the underlying structured files as well, we can go deeper. Because the repository sits inside a broader platform, the value can expand as the platform grows in response to customer demand instead of forcing the team to keep buying and stitching together more standalone products.
- Proof hook: Competitive review and value-prop review.
- Watch-out: Be honest about where the wedge is strongest. This builds trust faster than pretending every buyer needs the full thesis immediately.

### 7. Why not just use our current vendor's AI features?

- Short answer: Because most current vendors cover slices of the workflow, not QA and QC baked across design, collection, and reporting.
- Longer answer: Qualtrics already has ExpertReview and Response Quality, so we should not pretend they do nothing here. Conjointly is also a serious comparator for questionnaire review because it explicitly covers wording, scales, order, and screening before launch. Forsta now positions research agents across setup, analysis, and reporting. Attest and Zappi lead heavily on data quality. Dovetail, Stravito, and KnowledgeHound cover repository, search, and AI Q&A. The difference is that those offers usually help with slices of the workflow, whereas our strongest wedge today is a deeper pre-launch review paired with live quality review and connected evidence. Research Guard is strongest where the buyer cares about whether the screener qualifies the right people, whether early questions are shaping later answers, whether judgment calls are followed up properly, and whether review findings are carried through into approved changes and a final check. Qualtrics is stronger where the tooling is already built directly into the survey-authoring workflow and where enterprise proof is already packaged. Our pitch is strongest when the buyer wants that deeper review workflow rather than just another in-product AI feature. If the objection is specifically about Attest, Zappi, Qualtrics Response Quality, or Cint on data quality, jump to Q8 for the direct comparison.
- Proof hook: Competitive deep dive refreshed on 2026-04-18.
- Watch-out: If the buyer only needs one of those slices, an incumbent may genuinely be enough.

### 8. How is Trust Centre different from Attest, Zappi, Qualtrics Response Quality, or SurveyMonkey?

- Short answer: Most of those offers sell a quality score, a cleanup layer, or a managed quality promise. Our stronger angle is live, researcher-facing quality control while fieldwork