Running your sales team from the field: the mobile-first playbook

Walk into a developer's sales office on a Sunday afternoon and the desks are empty. That is not a failure — it is the job. Property gets sold at a site gate, in a half-finished flat with the plaster still showing, and in the car on the way back. The problem is that most sales processes are still written for the desk: a screen someone fills in at the end of the day, a report someone compiles on Monday, an inventory sheet that lives on one laptop at head office.

The symptoms are familiar to anyone who has run a site team. Visits get written up two days later from memory, or never. Follow-ups agreed in a corridor evaporate because nobody wrote a date anywhere. And the one person standing next to the buyer — the site executive — is the one person in your company who cannot answer "is a north-facing three-bedroom still available?" without phoning someone.

This post is about fixing that with process first. Most of it works with a printed slip and a WhatsApp group. Some of it gets much cheaper with software, and there is an honest section at the end about which parts those are.

Why does a desk-shaped process fail in the field?

Because it separates the doing from the recording, and then relies on the person to bridge the gap in their own time.

Three mechanics do the damage. The first is recall decay. A visit written up on Tuesday about a Sunday is a reconstruction, not a record — the objection the buyer actually raised has been smoothed into a category, and the thing they said at the lift that would have told you how to close them is gone.

The second is batching. Nine visits entered at once at nine in the evening get nine identical two-line entries, because that is what a tired person produces. The visit that mattered and the visit that did not end up looking the same in your system, which is precisely the distinction you needed.

The third is selection. When recording is retrospective and optional, the rep chooses what to record, and people choose the version that reads well. You end up with a log of the visits that went fine and silence around the ones that did not — which inverts the value of having a log at all.

There is a fourth problem that is not about the rep. Even when the write-up is honest, it arrives too late to act on. A record written on Tuesday about Sunday gets read on Thursday. By Thursday your buyer has been to two other projects.

How do you stop visits going unlogged?

Start by deciding what "logged" means, because most teams never say. Five fields are enough: who visited, which project and which units were shown, when, the outcome from a short fixed list, and the next step with a date. Free-text notes on top of that are welcome and often the most valuable part — but they should be optional, because the moment notes are mandatory they become a sentence of filler.

Keep the outcome list short. Three options that everybody picks honestly — interested, thinking about it, not now — beat eleven precise ones that get answered at random. You can always add nuance in the note. You cannot recover a field that half your team fills in by reflex.

Then move the moment. The rule that changes behaviour is not "log your visits daily", it is "the visit is recorded before you leave the site". As the buyer's car pulls away, the rep has ninety seconds of perfect recall and nothing else to do. That is the cheapest minute of data collection available to you, and it is the one almost every builder skips.

Managing this at scale means managing the exception rather than the mass. If visits are scheduled in advance, a visit with no recorded outcome becomes a detectable event: the calendar says a visit was due, no outcome exists, and someone can ask about that specific one on Monday morning. Without scheduling, an unlogged visit is invisible — you cannot chase what you did not know was supposed to exist.

Measure two things and only two: the share of visits logged the same day, and the count of scheduled visits with no outcome. Chase the rate, not the individual record. And read some of the notes yourself. Five a week is enough to tell whether they read like someone was actually there.

One warning. If you demand logging and then never use the log — never mention it in a review, never change a decision because of it — your team will work out within a month that it is theatre, and they will be right. The log has to appear in Monday's meeting, by name, or it should not be asked for.

Why do follow-ups evaporate?

Because "I'll get back to him next week" is not a follow-up. It is a feeling with no date attached, and feelings do not survive a busy Saturday.

The fix is a rule, not a tool: no conversation closes without an outcome and a date. Even a "not now" gets a date — three months out, if that is the truth. This works on paper. A diary with a page per day, and the rep writes the buyer's name on the day they have promised to call, is a complete implementation of the idea.

The management point that matters more than the mechanism is where the date lives. A follow-up written in a rep's own notebook or their own phone is invisible to you. When that rep is ill on Tuesday, or on leave for a wedding, or has resigned on Friday, the follow-ups due next week do not exist as far as the company is concerned. The next step has to belong to the pipeline, not to the person. That single principle is the strongest argument for keeping any central record at all, and it holds whether the record is a shared sheet or a database.

A follow-up that lives only in one person’s head is not a follow-up. It is a feeling with no date attached.

Two numbers make this manageable. The share of live leads carrying a dated next action tells you whether the discipline exists. The count of overdue next actions, broken down by person, on Monday morning, tells you where it has stopped. The second number is the actual management dashboard for a field team — everything else is commentary.

Watch for the failure mode too. Mandatory fields become garbage fields when the options are wrong or the rep is optimising for closing the form. If every follow-up date is exactly seven days out, you are looking at someone clicking the default, not someone making a plan. Sample ten records a month, compare them against what the rep says happened, and correct the pattern rather than the person.

The site executive who needs the grid but must not see the buyer

Here is the tension nobody solves cleanly, so most builders solve it by avoidance.

The person at the gate must be able to answer availability questions or the buyer's momentum dies on the spot. But the phone in their hand may be their own, it will leave when they do, and a full buyer contact list plus the price sheet is precisely the asset a competitor would most like to receive. So the inventory stays on a laptop at head office, and the field team gets nothing.

That avoidance has a price, and it is paid at the worst possible moment. "Let me check and call you back" is the sentence that ends more site visits than any objection. Two reps promise the same unit to two buyers on the same weekend because neither can see what the other has done. Holds get agreed verbally, with no owner and no expiry, and a unit sits quietly blocked for a month for a buyer who stopped answering in week one.

The right answer is not more trust or less information. It is information defined by role.

Write the split down explicitly, because a rule that lives in your head is not a rule. A site executive needs unit availability states, configuration, carpet area and the floor plan — enough to answer any question a buyer asks while standing in the flat. They do not need the price and cost sheet, the buyer's name or phone number, or other reps' leads. A sales manager needs all of that plus the ability to approve a hold. Accounts needs bookings, receipts and demands, and nothing about the pipeline.

Then write down what happens the day someone leaves. If your answer involves asking them to hand over a personal phone, or hoping they delete a spreadsheet, the design was wrong before the resignation.

Holds deserve their own rule. A verbal hold is a promise with no expiry, which means every verbal hold is permanent until someone remembers it. Any hold needs a named owner and a time it dies. On paper, that is a hold register with an expiry written next to each entry, reviewed at the same time every day by the same person, and a company rule that a hold does not exist until it is in the register.

What about WhatsApp?

Your field team already runs on WhatsApp, and a policy against it will lose. The useful question is not whether but whose number, and where the record of it lives.

A thread on a rep's personal number has three problems. It leaves when they do. A colleague covering for them on Sunday cannot see what was promised on Friday. And a chat cannot be queried — you can scroll it, but you cannot ask it how many buyers were quoted a price this month.

The workable compromise is a business number for buyer conversation, plus a standing rule that anything agreed in chat gets written into the lead record as a sentence: the price discussed, the hold promised, the date given. WhatsApp is an excellent place for a conversation and a poor place for a record. Use it for the first and stop pretending it does the second.

What should you watch every week?

Four numbers, and deliberately no targets attached to them.

Visits logged the same day, as a share of visits that happened. Live leads carrying a dated next action. Overdue next actions, by person. Scheduled visits with no outcome recorded.

I am not going to give you benchmarks for these, because credible India-specific ones barely exist — a point worth reading in full in our piece on site-visit conversion benchmarks. Your own baseline is the target. Measure the four numbers for a month, then watch the direction. A same-day logging rate that climbs from half to four-fifths over a quarter tells you more than any borrowed percentage would.

Can you run this without buying anything?

For a while, yes, and it is worth knowing exactly how far.

The paper version is a printed visit slip at the gate — name, phone, project, units shown, outcome tick-box, next step date, rep signature — photographed and sent to one group before the rep leaves the site, with one person entering the day's slips into a sheet each evening. Add a hold register with expiry times owned by a single named person, and a Monday review that opens with overdue next actions rather than ending with them. That is a genuine, working field process, and plenty of good builders sell out of a project on exactly that.

It breaks in four places. It breaks at the second site, because one register cannot be in two places. It breaks on speed, because an availability question answered in three minutes has already cost you the moment. It breaks on expiry, because holds do not lapse by themselves on paper — somebody has to remember, and eventually somebody does not. And it breaks the week the person who owns the register goes on leave.

Where Sthan fits

This is our blog, so here is the honest version of how our own product does the three jobs above, offered as one illustration rather than the only answer.

Sthan Sales is the field app, on iOS and Android. Site visits are scheduled in advance, checked in at the site with a location check-in rather than from the desk two days later, and their outcome is logged there and then. Visits that were scheduled and never written up raise an unlogged-visit alert, which is the "manage the exception" idea made automatic — the manager gets the short list instead of auditing everything.

Call logging carries the second rule structurally: a call cannot be closed without an outcome and a next follow-up date. That is not a nudge or a reminder, it is a required field, which is why follow-ups stop evaporating. And the record sits on the lead, not on the rep, so a resignation does not take next Tuesday's calls with it.

For the third problem, the app is role-aware. A site executive sees the live tower, floor and unit grid — available, held, booked, sold — without the buyer name, contact or price. The same role rules that run on the web run on the phone. Holds on that grid are time-bound and expire on their own, which is the part a paper register cannot do. You can see the whole thing on the platform page, and the price is published on the pricing page rather than held back for a call.

What it does not do is make a rep sell. No app does. What it does is make the record true, and a true record is the only way to manage a team whose work you cannot watch.

Which is the real point, and it survives whether you buy anything or not. Any tool that enforces the three rules will do, and the test to apply to all of them is the same: does the recording happen where the work happens, is the dated next step a condition of closing the conversation, and can you give the field the unit grid without handing over the buyer list? Get those three right and the discipline holds. Get them wrong and you will keep running a sales team on Monday-morning memory, which is a slower and much more expensive way to lose the same buyers.