How to record every offer, tell the vendor, and ack the buyer
We help businesses implement AI to make more money, save time and improve customer experience.
That is the job. naitive.work finds the repeating work, scores it, and either names a tool you can try this week or takes the work on.
The grind on a sales desk is not finding buyers. The portals do that. The grind is what happens after the walk-in or the viewing: an offer comes in, and someone has to write it down, tell the vendor what landed, and let the buyer know it was received, all before the next call. When that lives in WhatsApp, on a sticky note, or in one negotiator's head, the desk is the log.
The loop is the log, not the negotiation
The desk is not the negotiation, the advice on whether to hold out, or the call on which bidder is real. The desk is the offer that just landed and now has to go somewhere. Take it down: who, how much, any conditions, and when (capture). Put it against the property so the whole trail reads in one place (log). Tell the vendor what came in and where it sits against the last bid (tell the vendor). Confirm to the buyer, in writing, that the offer was received (acknowledge the buyer). When the next bid lands, do it again, and keep the trail current so anyone on the desk can read the property cold (keep the trail current).
Someone does that for the next offer. Then the next. The work has a right answer: the offer is on the record, the vendor knows, the buyer has it in writing. Until it is, a negotiator is the log.
In Ireland this is not a preference. The licence already asks for it. A licensee has to keep a record of every offer received on a sale for at least six years, disclose all offers to the vendor by the means and in the time agreed with them, and give each offeror written confirmation when their offer lands. The rule describes the loop. The only question is whether a person is doing it by hand between calls.
This is not lead generation, and it is not the reply to the portal enquiry. It is not booking the viewing. It is not the full sales file either: the letter of engagement, the vendor ID, the ads, the deposit receipt. That is another pile. This pile is the offer that already landed. One workflow. Not a department. Not "admin." The desk: capture, log, tell the vendor, acknowledge the buyer, keep the trail current.
Same log, different desks
The field guide already has the rule of thumb: the work nobody fights to keep is the work an agent can do. Nobody on a sales desk fights to keep the log. They fight to keep the vendor and the negotiation.
The flavour changes. The steps do not.
- Estate agents and sales desks. The offer on a three-bed semi, the bid on a site, the conditional offer on a shop unit. Each one taken down, put against the property, relayed to the vendor, confirmed to the buyer, and then the next one on top of it. The negotiator still decides what to advise. They should not also be the ledger.
- Letting desks. Several applicants on one unit, each offer to rent recorded, the landlord told, the applicant acknowledged. The same regulation covers offers to rent, and the same loop runs under it.
- Anywhere bids land on one item. A dealer with three buyers on one car. A tender log where each submission is recorded, the client told, the bidder acknowledged. Same shape: the bid exists, it needs a record and two people need to hear back, and someone senior is doing all three by hand.
Score this desk on the five signals
This is not a generic score. It is this loop, scored the same way as the free audit. The long form of the signals is in which workflows absorb well, and which don't. How to run the score on your own list is in how to audit your workflows for automation.
1. Repeatability
Strong. Same fields, different property: who offered, how much, on what conditions, when, and what the vendor was told. A junior could follow a one-page form and a rule for who gets told what.
2. Already outsourced
Strong, and already separable. On most desks a negotiator or an admin takes offers down between calls. Nobody sells "we keep a tidy offers record" as the service. Where the person who won the instruction is also the person typing the acknowledgement, that is the leak, not the design.
3. Clear right answer
Strong. The offer is on the record or it is not. The vendor was told or was not. The buyer has written confirmation or does not. The licence even fixes the form of the record.
4. Measurable outcome
Strong. The vendor cares that they heard about every offer and that the trail stands up, not how long the desk spent typing it. The buyer cares that their bid was received and is on the record. Count the offers that reached the vendor the same day and the acknowledgements that went out. Either is one number.
5. Enough margin
Depends on the bid count, and it is not the same on every desk. If you need a number prompt, sketch it on the whiteboard: 20 offers a week across the book, 15 minutes each to take down, log, text the vendor, and email the buyer, at €40 an hour is about €200 a week. That is a sketch, not a client figure. Run it at your own rate and your own bid count. The real cost is the offer that never reached the vendor, or the one the desk cannot prove it acknowledged. If it is three offers a month, leave it.
Count how many signals score 4 or 5. Four or five: the desk is ready. Two or three: start narrow, one branch or one property type. One or zero: you are looking at negotiation, not logging. Leave it.
One tool this week
Do not buy a CRM. Put one small tool on this desk: one place the offer goes the moment it lands, the record built from the same fields every time, the vendor's note and the buyer's acknowledgement sent from that record rather than typed fresh. If it lives in WhatsApp today, the tool is whatever gets it out of WhatsApp and against the property.
Judge it by Friday. Every offer that came in this week is on one trail per property, the vendor heard about each one, and each buyer has it in writing, or the desk is still the log. If the tool is wrong, you learned that in days, not in a quarter.
Sometimes that is the whole fix. Sometimes the desk is bigger than a tool, and the next step is a build that takes the offer in, keeps the record, tells the vendor, acknowledges the buyer, and answers for the trail. You cannot tell which until this loop has a name and a score.
A person keeps the call
Software can take an offer down, put it against the property, keep the record, send the vendor the update, and confirm receipt to the buyer. It cannot decide which offer the vendor should take forward, whether this bidder is real, what to advise when two bids are close, or how to run the negotiation.
That call is judgment. Leave it on a person. The log around it, the capture, the record, the vendor's note, the buyer's acknowledgement, is what should come off the desk.
Common questions
Is this only an estate-agent problem?
No. The item changes. The loop does not. A sales desk logs offers against a property. A letting desk logs applications against a unit. A dealer logs bids against one car. A tender desk logs submissions against one job. Wherever several bids land on one thing and two sides need to hear back, this is the same desk. Estate agents are the one where the licence writes the loop down.
Does the negotiator stop talking to the vendor?
No. The conversation about which offer to take forward stays with a person. What stops is the negotiator typing the same facts three times: once into a notebook, once into a text to the vendor, once into an email to the buyer. The offer goes in once. The record, the vendor's note, and the buyer's acknowledgement come out of it.
What tool should I start with?
None by name. Put one small tool on this desk this week: one place the offer goes the moment it lands, the record built from the same fields every time, the vendor told and the buyer acknowledged from that record rather than typed fresh. The free audit names the tool for your loop.
What about the record the regulator wants?
It builds itself if the log is the tool. The point of taking the offer down once, in one place, is that the six-year record is written as the offers land instead of being reconstructed from texts later. Check the specified form with the PSRA. The tool's job is to make sure nothing is missing from it.
How do I know this desk is worth handing over?
Score the offer log on the five signals. Four or five strong signals means the production loop is ready. One or zero means you are looking at negotiation, not logging.
Do this next
Score this desk, or the loop that actually eats the week, in five minutes at the free audit. It names the most absorbable workflow and ends with one tool to try this week.
If that pass finds something worth a wider map, The Assessment is the paid next step: €499, a 60-minute conversation, five to seven prescriptions across the business, credited 100% against any build.