SandsDX
Back to Research
AI & Automation6 min read

How to Evaluate a Customer Harness: 20 Questions for Your CRM Vendor

Twenty questions for RevOps leaders and CROs evaluating a customer harness: data, approvals, logs, pipeline measurement and what you keep if you leave.

Page Sands ·

Fifteen years building B2B SaaS revenue systems: a Microsoft preferred vendor, Drift, Avalara, Blackbaud, ConnectWise. About →

A customer harness is the software around AI agents that act on customer relationships: what they read, what they can do, who approves it, and how you know it worked. The explainer covers the term. This is the question list I would take into a vendor evaluation.

Before you talk to a vendor

Answer these about your own stack first. A harness runs on them.

  1. Do we have one written ICP, specific enough to build an account list from?
  2. Do sales, marketing and RevOps agree on stage definitions, with entry and exit criteria?
  3. Is lead source stamped once at creation and never overwritten?
  4. Which of our messaging sources is current: website, deck, sequences, enablement? Do they agree?
  5. Who approves anything that reaches a customer today, and is that written down?

If more than one answer is “no,” fix those first. An agent will act on whatever version of the definition it reads.

Data and context

  1. Which objects and fields can the agents read, and can we restrict them by team or segment?
  2. How fresh is the data the agent sees: live, hourly, nightly?
  3. Can the agents read our own documents (positioning, ICP, playbooks), and which version wins when two disagree?
  4. Can we see exactly what context an agent had when it took an action?

Rules and approvals

  1. Which actions can an agent take alone, and which wait for a person? Who sets that, and where?
  2. Can approval rules differ by segment, deal size or region?
  3. What stops an agent from contacting the same person from two motions at once?
  4. How are rule changes recorded, and can we roll one back?

Evidence and logs

  1. Is every agent action logged with its inputs, output and the rule that allowed it?
  2. When an agent writes a claim about our product or a customer, can it show the source?
  3. Can we export the logs?

Pipeline measurement

  1. Can the platform report opportunities created, meetings held and win rate for agent-touched accounts, against a holdout?
  2. How does it attribute a deal that a person and an agent both touched?

Leaving

  1. If we leave, do we keep our rules, prompts, definitions and logs in a format we can use elsewhere?
  2. What does it cost as agent volume grows: per seat, per action, per credit?

How to score the answers

Weight questions 1 to 5 and 17 most. The first five decide whether agents will act correctly. Question 17 decides whether you will ever know if they did. If a vendor answers 6 to 16 well and cannot answer 17, you will be able to count what its agents did, and you will not be able to tell whether they created pipeline.

For a working example of these rules in a small operation, see How I run SandsDX on a GTM harness.

Frequently Asked Questions

How do I evaluate a customer harness?

Check five areas: what customer data the agents can read and how fresh it is, which actions need human approval and who sets those rules, whether every agent action is logged with its inputs, whether the platform can show pipeline created rather than activity, and what you keep if you leave, especially your rules, prompts and definitions.

What should I fix before buying a customer harness?

Write down one ICP, agree stage and lead source definitions across sales, marketing and RevOps, and set an approval rule for anything that reaches a customer. Agents act on those definitions, so gaps in them become errors at scale.

What is the biggest risk with a customer harness?

Measuring it on activity. Agents can send far more email and create far more tasks than people. If the platform reports volume and cannot connect agent work to opportunities created, you will not know whether it is helping pipeline or burning your audience.

Put this to work on your GTM

Thirty minutes. Bring the number you need to move and I'll tell you what I'd check first in your system.

Schedule a Conversation

Not ready to talk? Run the AI Visibility Baseline on your company →