Field visits · plan, log, claim
Field software is built to watch people. This one is built not to.
Every product in this category sells the map. A dot per rep, a trail behind it, a manager watching in real time — and a team that learns within a month to leave the phone on a desk.
There is no map here. There is no distance calculation anywhere in the product. And the rep can see, by name, every manager who looked at their week.
- No map, no geofence, no distance ever computed
- Turn location off and the server discards it
- The rep audits the manager, not the other way round
- Turn location off entirelythe server discards the coordinates, whatever the device sent
- Put a pin on a mapthere is no mapping library in the product at all
- Check whether they were really thereno distance is ever computed, anywhere
- Report on where somebody wascoordinates are excluded from the reporting engine
- Watch a rep movetwo moments are captured, both by a deliberate tap
Three answers a competitor does not have
The questions to ask a field-sales vendor, in the order that matters.
Each of these is answerable here, and each is a page you can read before you ever speak to us.
Why this is the shape it is
Surveillance does not produce data. It produces compliance theatre.
The moment a team believes the product is watching them, the product stops receiving anything true. Visits get logged from the car park. Check-ins happen at nine and check-outs at five regardless of where anybody was. The map fills up and means nothing.
So the question is not how much you can capture. It is how little you can capture and still answer the questions a sales director actually has: is the week planned, did the planned things happen, what came out of them, and what does it cost us.
Everything on this page follows from answering those four without answering "where is Priya right now".
- Check-in is off by default —
A workspace that never opens the settings captures nothing at all.
- Location is a separate switch from check-in —
So proof of presence and a coordinate are different decisions, taken separately.
- The rep is told before they tap —
The check-in bar prints the workspace's mode in plain type, and the badge reads differently when no coordinate was taken — so a manual check-in never silently looks like a satellite one.
The trust contract
Every cross-person view is written down, and nothing can be left off.
Opening somebody else's visit, pulling the team's week, loading the aggregate dashboard, opening a rep's own numbers — each writes a row the rep reads on their own page, with the viewer's name, their role as it was at the time, and what they opened.
The constraint is written into the product in four separate places, in as many words: other-person views are never filtered out, not by kind, not by role, not by anything. Views of your own data are dropped so the page stays readable, and background jobs are skipped so they do not pollute it.
- Rin Takahashitoday, 08:12Field sales manager · Opened your week
- Rin Takahashitoday, 08:14Field sales manager · Your numbers, in the team dashboard
- Sofia MarchettiTue, 16:40Regional lead · Opened one visit — Vestra Freight
The whole module
Every capability, with a page that names the screen.
Written after reading how each one actually behaves — which is why each page tells you what it refuses to do as plainly as what it does.
A visit is an activity, so everything else already understands it.
It is not a separate app with its own database. A visit is a first-class activity on the account, which is why it appears where the rest of the business is already looking.
Sales CRM
The visit lands on the account's timeline and on the deal's, so a pipeline review sees the field work without anybody reporting it.
ExploreFinance
The expenses claimed against a visit ride the same approval and reimbursement path as everything else — including for a rep with no employee record.
ExplorePeople & payroll
Where the rep is an employee, the reimbursement settles through payroll rather than through a separate payment somebody remembers to make.
ExploreReporting
Visits are reportable through the ordinary report builder — planned against logged, by rep, by week — and the coordinates deliberately are not.
ExploreQuestions that decide it
Including the ones a works council will ask.
›Is there a mobile app?
No. It is a web app designed for a phone — the week collapses into stacked day cards, the save and check-in bars stick to the bottom, and the inputs are sized so the phone does not zoom the form. It installs to a home screen with shortcuts to today's visits and this week's plan.
›Does it work without signal?
No, and that is a real limit. Every action is a live call — a rep with no connection cannot check in, log a visit or upload a photo. If your team works where coverage genuinely fails, know that before you buy.
›Can a manager see where somebody is right now?
No. There is nothing live anywhere in this module, no map, and no location captured except at the two moments a rep deliberately taps. Every manager surface is a pull against a week that has already happened.
›Can we verify somebody was actually at the customer?
No. The location is taken from the device and trusted — there is no distance check, no accuracy threshold and no spoofing detection anywhere in the product. If proof of presence is a hard requirement, this will not give it to you, and we would rather say so than let you find out.
›Does it do route planning or beat plans?
No. There is no repeating route, no territory circuit and no journey optimisation. The week is built by the rep, one visit at a time, and next week starts empty. Reps plan their own routes — that is a stated position, not an omission we are hiding.
›What does a works council need to see?
Usually three things: what is captured, who can see it, and what the worker can see about being observed. All three are on this page and on the pages under it, and the third one is the answer most products cannot give.
Book a demo
Bring a week of one rep's visits.
The third one takes ninety seconds and settles most of the conversation.
- Plan it, commit it, then change it on the Tuesday
- Turn location off and watch the coordinate never arrive
- Open a rep's week as their manager, then open their audit page as them
- Ask the dashboard for a percentage it does not have enough data for