When a prospect asks for pricing mid-sequence: pause, handoff, or price-band reply

"What does this cost?" lands on step three of a cold sequence. The next scheduled bump is already queued. If you do nothing, the prospect gets a case study email after they asked for a number.

That is the failure mode. A pricing ask is a state change. Treat it like any other human reply: pause first, then choose a path.

Always pause the sequence

Cognlay's pause-on-reply playbook is the baseline: a human reply should stop scheduled follow-ups, get classified, then earn a context-aware response. Digital Applied's 2026 agentic outreach triage piece puts pricing-style questions in the objection / qualified-interest bucket with a defined handoff, not another automated step.

Do this in order:

1. Stop the sequence on the reply
2. Tag the intent as pricing ask
3. Route to the owner with the thread, account context, and a recommended next action
4. Only then draft the human reply

Skipping pause is how agencies look careless at the exact moment intent showed up.

Choose one of three reply paths

Path A: pause and handoff to the AE. Use when the client sells complex scope, custom packages, or enterprise deals where a written number without discovery mis-sets the deal. Growtoro's reply-handling playbook keeps the SDR in the thread until the meeting is booked, then hands the meeting to the AE. Continuity through the commitment beats dumping the prospect onto a new face mid-email.

Path B: send a price band and offer a short call. TaskBlink's pricing guidance is practical for packaged or semi-scoped offers: answer in the same message with a fixed figure if the offer is packaged, or a range plus the one variable that moves the number if the work is scoped. Then attach two specific times. A reply that only says "it depends, book a call" reads as a dodge.

Path C: hold the number and ask one clarifying question. Use when the ask is vague ("ballpark?") and the client has multiple SKUs that would make any band misleading. Ask one scope question, keep the thread warm, and still offer times. Do not reopen the automated sequence while you wait.

Pick the path per client workspace in the voice brief. Do not let each AE invent a different policy on Tuesday.

What not to do

• Send a full quote PDF into a cold thread with no call attached
• Ignore the ask and let step four fire
• Hand the thread to a new AE before the meeting is booked, unless the client already owns that handoff rule
• Invent discounts to "keep momentum"

Dobble's pricing-inquiry write-up pushes hard toward discovery calls. That can work for high-touch sales. For many agency clients with clear packages, a honest band plus a call converts cleaner than a pure pivot. Match the path to the offer, not to seller anxiety.

Ops checklist for multi-client rooms

1. Classify pricing asks as a positive / qualified intent label in the shared inbox
2. Store the client's default path (handoff, band, or clarify) in the workspace brief
3. Require a human owner within the same SLA you use for other positive replies
4. Log whether the thread booked, stalled, or asked again
5. Review pricing-ask conversion weekly next to conversations booked

GTM's motion stops sequences on reply and routes through shared inbox plus CRM follow-through inside client-isolated workspaces. Pricing asks are where that stop-on-reply rule either protects the relationship or gets ignored.

If you want reply triage and AE handoff inside the outbound motion, join the waitlist.