“Check my Jobber account for approved quotes that never turned into jobs. Anything a client said yes to that we haven't scheduled yet.”
Catch Won Quotes Before They Slip Away
A client approving a quote feels like the finish line, but in Jobber it's only a status. If nobody converts that approval into a job, the work you already sold just sits there while the client wonders if you're coming. Ask Claude one question and it sweeps your account through your private Jobber connector (built on MCP), surfaces every approved quote with no job behind it, and helps you convert, schedule, and follow up on the spot.
Updated July 2026
The yes that nobody heard
Approvals don't arrive when you're at a desk. They arrive as a notification at 8pm while you're at dinner, or buried between a supplier email and a review request. You saw it, you felt good about it, and you fully intended to schedule it in the morning. Then the morning had a burst pipe in it. Jobber faithfully records the quote as approved and then waits, forever, for someone to do the next thing.
Meanwhile the client thinks the job is booked. Every week that yes sits unscheduled, the odds go up that they call someone else, and now you've lost work you already won, at the price you already agreed on. That's a worse leak than a missed invoice, because there's no version of catching it later.
The won-quote sweep, start to finish
Here's the actual workflow, one prompt at a time.
Claude pulls every approved quote, cross-references your jobs, and returns the ones with nothing behind them: each with the client, the quote title, the amount, and how many days it's been sitting since the client said yes.
“Convert the mulch quote into a job and get it on the schedule for Tuesday morning.”
Claude creates the job from the quote's existing line items, so the price the client approved is the price on the job, and schedules the visit. Done in one message.
“For the other two, draft me a quick text to each client confirming we're still on and asking what week works.”
Three messages: the leak found, the hottest one converted and on the calendar, and the rest one paste away from a reassured client. No tab-flipping between the quotes list and the jobs list trying to eyeball which approvals fell through.
And nothing here happens over your head. Claude finds and assembles; converting a quote, scheduling a visit, and anything a client ever sees all run on your say-so, in the conversation, where you can watch it happen.
Make it a Friday habit
The sweep is most valuable before there's anything to rescue. End of the week, one prompt:
“Any approved quotes without a job yet? Sort by how long they've been waiting.”
The Friday won-work sweep
- Run the approved-but-unscheduled sweep
- Convert the clean ones straight to jobs
- Put them on the calendar while you're there
- Draft a “you're on the books” note for each client
- Nothing you won sits unscheduled past Friday
This is one end of the same leak the uninvoiced work audit catches at the other: that one finds finished work you never billed, this one finds sold work you never started.
Converted a backlog and now the calendar's the puzzle? Run the schedule by chat too.
And upstream of all of it: creating and sending quotes conversationally, so the pipeline this page protects keeps filling.
Getting set up
If your Jobber account isn't connected to Claude yet, that's a 5-minute job, one time: How to Connect Jobber to Claude. Your connector is private, runs on your own Jobber developer credentials, and costs $47/month after a 7-day free trial. One rescued approval typically covers the year.
Frequently asked questions
How does Claude know a quote hasn't become a job?
It checks every approved quote against the jobs in your account. An approved quote with no job created from it is a flag, and the older the approval date, the higher it sorts.
Does converting a quote keep the price the client approved?
Yes. The job is built from the quote's existing line items, so what the client said yes to is exactly what lands on the job. Claude doesn't invent numbers anywhere on this site, and this page is no exception.
What if the client approved but asked to wait a few months?
Tell Claude the story and it leaves that one off the action list, or converts it with a start date out in the future so it's scheduled instead of forgotten. The point isn't to rush every client; it's that no approval should be living only in your memory.
Will Claude contact my clients?
No. Claude drafts the follow-up messages and you send them from your own phone or email. Finding and drafting is the AI's job; anything a client sees stays under your control.
How far back should the first sweep look?
Any range you ask for, but 90 days is the sweet spot on a first run: long enough to catch real slippage, recent enough that a “still on for that patio?” message lands as attentive instead of awkward.