A London consultancy recovered $21,300/mo with progressive reveal.

Consultancy / London, UK / Scale

Consultancy, London, UK

Consultancy, London, UK, Scale plan. Primary workflow: Quote Follow-Up.

Before

23 ghosted proposals/mo
19h manual follow-up/week
18% close rate

After

5 ghosted/mo
2h follow-up/week
37% close rate

ghosted/mo

follow-up/week

37%

close rate

We were sending 60-page PDFs and wondering why nobody replied. Now we send a summary, the system follows up, and the deep strategy unlocks after they commit.Consultancy · London, UK

Why this leak mattered

Consultancy, London, UK, Scale plan had a measurable quote follow-up problem. We were sending 60-page PDFs and wondering why nobody replied. Now we send a summary, the system follows up, and the deep strategy unlocks after they commit.

Baseline signals included 23 ghosted proposals/mo, 19h manual follow-up/week, 18% close rate.

The workflow stayed narrow: capture the leak, qualify the next step, and push the useful handoff back to the business. That keeps the case measurable instead of turning it into a broad transformation project.

For this page, the related workflow is Quote Follow-Up.

Do not copy this workflow blindly if the team cannot name the leak, does not know the current baseline, or cannot define the rules for a clean handoff. In that case, start with a short audit before automation.

How to read this case

The case evidence is kept in crawlable HTML: client context, baseline, result, workflow, related service, and update date. Treat the numbers as a scoped operating snapshot for this workflow, not as a universal guarantee.

Client context: Consultancy, London, UK, Scale plan.

Baseline: baseline signals included 23 ghosted proposals/mo, 19h manual follow-up/week, 18% close rate.

Result: after-state signals included 5 ghosted/mo, 2h follow-up/week, 37% close rate.

Primary workflow: Quote Follow-Up. Payback: 5 weeks. Published 2026-05-21, updated 2026-06-09.

Evidence limit: this is a scoped operating snapshot for the listed workflow, not a universal guarantee.

Frequently asked questions

What was the main result in this Quote Follow-Up case?

A London consultancy recovered $21,300/mo with progressive reveal. is summarized by 5 ghosted/mo. We were sending 60-page PDFs and wondering why nobody replied. Now we send a summary, the system follows up, and the deep strategy unlocks after they commit.

What evidence is shown on the page?

Baseline signals included 23 ghosted proposals/mo, 19h manual follow-up/week, 18% close rate. After-state signals included 5 ghosted/mo, 2h follow-up/week, 37% close rate. The table keeps the before and after signals in HTML so the result can be extracted without reading an image.

Who is this workflow most relevant for?

This pattern is most relevant for operators with a similar quote follow-up leak, a measurable baseline, and a handoff that can be described with clear rules.

When is this not the right first workflow?

It is not the right first move when the business cannot define the leak, cannot measure the baseline, or needs a full process rebuild before a narrow recovery workflow can be tested.

Where should the reader go next?

The related service page explains the workflow behind the case: the Quote Follow-Up service at https://skoreflow.com/quote-followup/.

A London consultancy recovered $21,300/mo with progressive reveal.