A UK agency pays £27,000 to £30,000 a year for the person who chases agreed sales to completion. The US pays $39,000 for the same seat.
Someone is paid to chase this by hand. The UK calls the job Sales Progressor. The US calls it Transaction Coordinator. Both liaise, update, resolve and record. For a six-person brokerage there is no such hire, so the chase is the principal, on evenings, from memory.
By hand today
A product does this stage, coupled to a UK agency suite. Street.co.uk names “Offers” and “Sales Progression” as surfaces, Reapit sells the same chain, and neither prints a price; both route /pricing to a demo form, read 14 September 2026. Nothing else does it, and no public repository models an offer, a counter or a chase.
So the trade hires a person. The advert is the method:
“Sales Progression: First and foremost, you will oversee the entire sales process by liaising effectively with buyers, sellers, solicitors, and mortgage brokers to ensure smooth transactions.”
ProFind Property Recruitment, on Sales Progressor job advert
The US seat, with the offer in it:
“Make sure the buyer’s offer and counteroffers get approved by the seller to ensure a smooth real estate sales process”
Wizehire, on transaction coordinator job description
Where there is no progressor, the principal is one.
What it costs you each week
£27,000 to £30,000 a year
What a UK agency pays the person whose whole job is to chase agreed sales to completion. Basic, before commission. The US pays $39,000 for the same seat. Without the hire, the seat is your evenings.
Source: ProFind Property Recruitment and Wizehire job adverts, read 14 September 2026
“£27,000 to £30,000 PA” is ProFind’s line; Wizehire prints “$39,000 (National Average)”. No stall rate or days-to-signature average exists in any fetchable source, so none is printed. What the salary buys is a person who notices silence.
The build
Open Codex. Ask for the chase. The stage is read from the signature server itself and written to the deal. A reminder is one tool call. Days since anything moved is the number, read per deal. It is printed, never sent.
Open Codex in the engine folder, where the deal chapter 17 pitched sits at agreed. Connect the signature vendor’s own server. Docusign’s, at mcp.docusign.com/mcp, is “now available in Open Beta” and exposes the eSignature API. PandaDoc’s, at mcp.pandadoc.com/v1/mcp, tracks status and can “Send reminders for all contracts tagged ‘Q4-2024’ that haven’t been signed yet”. Then the CRM’s own: HubSpot’s reads and writes deals (developers.hubspot.com). Write deal.md once: the stages an agreed deal passes; who owes the next thing at each; the tag on your deal documents; and N, the days of silence you will tolerate. Then say what you want:
Every morning, read every deal at agreed or beyond. Read the status of
its documents from the signature server, by the tag in deal.md, and
write the stage to the deal in the CRM, reason on the record. Find the
newest thing on the deal: a signature event, a note, a call, a message.
Print days since it, per deal, beside who owes the next
thing. Where a document has sat unsigned longer than N days, send the
signature server's own reminder once, and note it. Never send anything
else to anyone, never touch a price, never write a counter, never move
a deal to won or lost. Report: agreed, moved this week, silent past N
days, reminders sent.
What comes back is a script, a schedule and a table sorted by days.
Three honest limits, which Codex will tell you about. The Docusign server is a beta, and its page says so in capitals, provided “AS IS” and “AS AVAILABLE” without warranty. The lawyer and the lender answer on email, which no signature server sees, so a deal waiting on a lawyer reads as silent until chapter 16 writes the email on the deal. And the counter is a conversation the server never hears.
What it feeds
The file, and the next pair of hands. The next stage chases the documents the deal needs, from the stage this one wrote. A won deal carries every note and field since chapter three. Nobody asks the client twice.
Chapter 19 chases the compliance file from a stage read off the signature, never typed.
The won deal also feeds whoever serves the client next, and the reader never calls that a handoff. They call it the team. The cost is named from the receiving end:
“On one transaction I was asked to give the same information to both team members every time and it became a double workload for me.”
James Gordon, Sibcy Cline Realtors, Cincinnati, on ActiveRain
The trade’s fix is to hide the seller from the client:
“So if you have someone else answering your phone, the buyers will be more likely to be okay with working with a sub-agent.”
Chris Alston, Keller Williams Realty, Campbell, on ActiveRain
The chain’s fix: the won deal already carries everything written since chapter 3: the reason, the three fields, the thread, the viewing outcome, every event, the pitch, and the stage this chapter read. The number there is questions the delivery side had to ask that the seller could already answer; the target is zero.
The number that proves this stage worked is days from offer accepted to signature, and the milestones that moved without you sending the chase.
What stays with a person
The negotiation, and the call when it stalls. The chase reads and reminds. Whether to push a party, and when, is a judgement made each time. The introduction to whoever serves them next, and the promise made in the sale, are yours.
The build chases the paperwork. It never makes the call. Nine days of silence is a number on a table; whether that is normal for this lawyer or a warning is read by the person who knows the lawyer. The reminder is the vendor’s own, sent once. The second nudge is a phone call.
The handoff stays personal too: the introduction, and the promise made during the sale, are made by the person who made it.
The tools you already pay for
Nothing new to buy.
Signature is whichever of Docusign and PandaDoc your agreements already go out through; PandaDoc’s server carries the API’s rate limits.
CRM is HubSpot through its own server, or Follow Up Boss through the broker-written community server (github.com), which can delete.
Mailbox is chapter 16’s witness, untouched.
Every agreed deal has a stage read from the signature itself, a count of days since anything moved, and a file the next person reads first. Nothing dies in silence.
Ask: Of the deals you agreed this quarter, which one went quiet, and who noticed first, you or the client?
This is stage 18 of twenty, after building the pitch from what you already know and before knowing which document is missing and from whom. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.