What a Great Survey Response Looks Like

The four things that turn a vague complaint into a quotable workflow

Version 1 · June 29, 2026 referencesalesmethodology

Content

# What a Great Survey Response Looks Like

_Parent: Sales Methodology_

The four things that turn a vague "this is annoying" into a workflow we can quote.

## 1. Trigger and volume

What kicks it off (an email, a deadline, a request) and how often it happens.

> "8–12 times a week" beats "often"

Those two numbers — trigger and frequency — decide whether automation pays back. Without them, we're guessing.

## 2. Programs named

Which programs are involved — Procore, Sage, Bluebeam, Outlook, Excel, SharePoint. Each one is a data source the automation can plug into. If they say "our system," push them to name it.

## 3. Manual actions and pain points called out

The specific motions:
- Drag-and-drop
- Copy-paste
- Re-typing into two systems
- The typo that breaks a running total
- The threshold missed
- The reconciliation redone at month-end

These details define what the automation needs to replace. Generic complaints ("it's a pain") don't scope.

## 4. 60 seconds of screen recording beats 60 lines of write-up

If you can get a Loom or Quicktime of someone doing the task — naming conventions, click patterns, where the data lives all come through automatically. **Always ask for the recording.** It saves a discovery call.

## How to coach a prospect through the survey

If their first responses are vague:

| What they wrote | Push for |
|---|---|
| "Invoices are a mess" | Which invoice type? From whom? How often? What systems? |
| "Excel hell" | Which sheet? Updated by whom? After what trigger? How often? |
| "Project setup is slow" | What's the trigger? What systems get touched? How long does each step take? |

You're not interrogating — you're saving them money. Vague workflows produce vague quotes (or no quote at all).

---
_Last updated: 2026-05-24_

Change notes (optional)

Cancel