The problem
Quotes go out and the follow-up dates go on a pad, in a diary, or nowhere. The chase happens when somebody remembers, which is usually when the pipeline looks thin. By then the client has decided, or forgotten, or gone with whoever chased first.
Chasing is not hard. What gets missed is the remembering, and the sitting down to write a note that does not sound like a template.
What it does
When a quote reaches its chase date, a chase email is drafted in your wording: the job, the price, the date it went out, and a plain question. A person reads it, changes it if they want, and sends it. If a reply comes back, the outcome is logged against the job: won, lost, waiting, or a date to try again. If nothing comes back, the next chase is drafted on the schedule you set.
What you see is a short list each morning: the chases waiting to go, and the ones that got an answer.
What it needs from you
Where your quotes are recorded and where the sent date lives. The gap between a quote going out and the first chase, and between chases, in your words. A few chase emails you have actually sent, so the drafts sound like you.
Some quotes will have no sent date because the quote went out from someone's personal email. Those are found in the data check.
What it does not do
It does not send anything on its own. It does not change the price, offer a discount or negotiate. It does not chase a client you have marked as do-not-chase. It does not know when a client is worth a phone call instead of an email, so the person reading the list decides that. Version one will chase somebody it should not have, and the person sending will catch it.
Nearest route: Estimation. Back to Services.