# Sales Scripts for Workflow Audits

## First Message

Hi {{Name}},

I help small teams find one repetitive workflow that is costing time every week and turn it into a practical automation plan.

The first step is not a big build. It is a fixed-scope workflow audit: current-state map, three automation opportunities, and one build-ready recommendation with guardrails and acceptance checks.

Would it be useful to review one workflow such as lead intake, weekly reporting, client updates, invoice prep, or support triage?

## Short Follow-Up

Hi {{Name}},

Quick follow-up. If a full automation build is too early, the audit can stand alone as a decision document. It shows what to automate first, what not to automate, and what risks need human review.

Useful if one workflow is creating repeated manual work.

## Discovery Call Close

Based on what you described, I would not start with a broad automation project. I would start with a short audit of {{workflow}}.

The deliverable would include:
- Current workflow map.
- Three ranked automation opportunities.
- Recommended first build.
- Guardrails and failure handling.
- Acceptance checklist.

If the audit confirms the value, we can scope implementation separately.

## Pricing Explanation

The audit is priced separately from implementation because it prevents guessing.

The smaller audit documents the workflow and identifies the right first build. The implementation sprint only happens after the scope is clear and the expected value is high enough.

## Objection: We Already Use AI

That helps. The audit is not about whether you use AI. It is about whether the workflow has a clear trigger, clean inputs, review points, failure handling, and measurable value.

Most teams already use tools. The leak is usually handoffs, missing fields, unclear ownership, or repeated copy-paste between systems.

## Objection: Can You Just Build It?

Sometimes, but only after the workflow is clear. The audit is the fastest way to avoid building the wrong automation or automating a broken process.

If the workflow is already clear, the audit can be upgraded into an implementation spec.

## Objection: We Do Not Want To Share Credentials

You do not need to share credentials for the audit. Screenshots, exports, field lists, or process notes are enough. Any implementation work would be scoped separately with proper access boundaries.