A sent proposal isn't a closed loop. It's an open one, and open loops need someone checking them on a schedule — not whenever it occurs to someone to look.
Professional-services firms run on trust and judgment, which makes this trickier than it sounds. Nobody wants a client to feel chased. But there is a wide gap between "chased" and "forgotten," and a proposal with no follow-up date is easier to forget than to chase.
Four places the loop breaks
- High-value inquiries. Important requests need fast ownership and a clear review path — not a reply whenever someone has a spare ten minutes.
- Consultation requests. Scheduling interest stalls the moment nobody creates the next task for it.
- Proposal follow-up. A sent proposal without a reminder date is a proposal that depends on the client remembering to reply first.
- Old prospects. Conversations from a few months back deserve one real review before they're closed out or quietly abandoned.
Referral tracking has a version of this problem too: a referral without its source context and next action attached is a referral that's easy to lose in the shuffle of current work.
A follow-up structure that doesn't feel like automation
The goal isn't to remove the person from the relationship. It's to make sure the next step always has an owner and a date, so judgment gets applied on schedule instead of by accident.
- Proposal sent → review date set, owner assigned.
- Review date arrives → task surfaces, not a message goes out.
- Owner decides → send, wait, revise, or close.
- Decision logged → CRM record stays accurate for the next person who looks.
Client-facing communication stays behind that review step every time. What changes is that the review step actually happens on a schedule, instead of whenever someone remembers.
An example reminder ladder
This is an illustration of a policy a firm might choose. It is not a standard, not a recommended cadence for every firm, and not something that runs automatically. Replace the intervals with ones that fit your sales cycle and your clients.
| Step | When | What surfaces | Who decides |
|---|---|---|---|
| 1 | The day the proposal is sent | A review date is set and an owner is named | The partner or owner |
| 2 | About a week later | A task: has the client replied? | The owner |
| 3 | Two weeks later | A task with a short draft check-in to review | The owner reviews and edits the draft, and chooses whether to send it |
| 4 | A month after sending | A task: revise, wait, or close the proposal | The partner or owner |
A draft check-in might read, in the firm's own voice: "Hello [name], I wanted to check whether you had any questions about the proposal we sent on [date]. I am happy to talk it through, and I understand if the timing has changed." Nothing sends itself, and a client who says no, or asks not to be contacted, ends the ladder.
Capacity without lowering the bar
The firms that get this right aren't sending more messages — they're making sure the messages that matter don't get lost in the gap between "we should follow up" and someone actually doing it. That's a records and ownership problem before it's a communication problem.
Is this something Vayna does?
Not today. The 30-Day Revenue Recovery Pilot is built for owner-led home-service businesses, and professional-services work would be a custom scope that is agreed and approved separately, with no assumed availability or price. This article describes a structure you can adopt yourself. See the professional services page for what is and is not available.
Next step
Start with one workflow: proposals, consultations, or old prospects — whichever has the most silent gaps right now. A Lead Leak Check is a fast way to see where that gap actually is.