Why CAS Proposals Stall at “Sent” — and What Unsticks Them

Why chasing feels unbecoming — and what that instinct gets right

The profession trains a specific identity: objective, independent, understated. You do not oversell, and you certainly do not pester. So the follow-up email sits in drafts, justified by a quiet rule — if they wanted it, they would sign. Meanwhile the proposal landed in the client’s inbox between a payroll notice and a bank alert, during their own busiest quarter, and they filed it under “later” without deciding anything at all.

The instinct is half right, which is why it survives. Nobody wants their CPA closing like a car lot. But there is a category error inside it: following up on work the client asked you to scope is not sales pressure — it is finishing a conversation the client started. They came to you with no forward visibility, a surprise tax bill, a bookkeeper who quit. Silence does not respect their time; it abandons their problem.

One hard number is worth borrowing here. James B. Oldroyd’s Lead Response Management study compared response times for web leads. It does not tell us how quickly a scoped CAS proposal loses momentum. The pain that made your client say “yes, scope it” in June is the pain they have learned to live with by late September.

The partner-owned cadence that reads as service, not sales

The fix is not a CRM drip and not a marketing hire. For the clients a CPA firm actually wants in CAS, follow-up belongs to the partner who signs the return — that is where the trust already lives, and trust is what is being purchased. The cadence works when every touch gives the client something, and none of them says “just checking in.”

• Never send a proposal cold. Book the walkthrough call before the proposal goes out, so “sent” always has a live next step attached to it.
• Make every touch a unit of service: an observation from their own file, a note on something moving in their industry, an answer to a question they have not asked yet — never a bump to the top of the inbox.
• Put the cadence in Karbon, Canopy, or TaxDome as real work items with dates and an assignee, so the pipeline ages as visibly as a late PBC list.
• Tie the decision date to the client’s calendar — their fiscal year-end, their loan renewal, their slow season — never to your revenue goal.
• Close every loop. A proposal ends as a yes, a no, or a dated next step. “Sent” is not a resting state.

Notice what this cadence is not: it is not persistence theater, and it does not require anyone at the firm to become a different person. It takes the rigor the firm already applies to statutory deadlines and points it at revenue. And a fast no is a genuinely good outcome — it releases the capacity you were quietly reserving and tells you something true about the scoping.

Onboarding stalls that eat the first year’s margin

Closing is not the last place the pipeline dies. Plenty of CAS engagements sign and then bleed out in the first months, and the pattern is depressingly consistent. The onboarding request list goes out shaped like a tax PBC — long, unexplained, unchased — and the client goes dark before the first monthly close ever runs. The engagement that was sold as advisory begins its life feeling exactly like compliance.

Then comes the cleanup surprise. The ledger is rougher than discovery suggested, the fixed monthly fee was priced for a clean file, and the extra hours land as WIP nobody has the stomach to bill. The write-down happens quietly, the realization report absorbs it, and a year later the partner group concludes advisory does not pay — when what actually happened is that the firm priced onboarding as if it were free.

The same cadence logic applies on this side of the signature. Onboarding needs a named owner, a dated path in the practice management system, and a separately scoped cleanup phase — priced and agreed to before the monthly fee starts, not discovered under it. Clients do not resent a cleanup phase presented up front. They resent the version that arrives as a surprise invoice or, worse, as your team’s quiet resentment.

Count the parked pipeline before you hire a BD person

When advisory stalls, the reflex is to hire — a business development person, a growth role, somebody who likes selling. Before you post that job, run one filter in Ignition: every proposal at “sent” or “viewed” older than a few weeks. Add up the first-year value of that column. That number is the honest answer to whether the firm has a lead problem or a follow-through problem — and a BD hire does not fix follow-through, because your clients want to buy from the partner, not from a rep.

That count is the kind of arithmetic we do in The Revenue Review — a fixed-fee ($4,500) operational audit built in two weeks from your firm’s own records: Ignition statuses, Karbon or TaxDome work items, WIP and write-down history, onboarding timelines. Not a strategy retreat. A written report that shows where your pipeline actually parks, what each stall costs, and a 90-day plan for the two or three fixes that matter most. There is a worked sample on the method page if you want to see the shape of it first.

If you would rather size it yourself first, the Leak Calculator is free and takes the same view of your numbers. And a 20-minute call costs nothing — worst case, you leave with a clearer read on your own “sent” column than you walked in with. Either way, do the count before extension season ends and the parked proposals quietly become last year’s idea.