Field visit tracking, kept the way a ledger is kept
Client Visit Tracker gives your field team one page to write every visit against — who went, where, what came of it, and what it's worth. Reps see their own record. Managers see the team's. Nothing gets edited without saying why.
No card required · live in one working day · Nigerian public holidays built in
How a visit moves through the system
Branch, storefront, or a client's office — logging works from any phone, no separate device and no GPS unit to carry around.
Client, purpose, outcome, and whatever custom fields your admin has added — filled in before the rep is back in the car.
You set what a visit, a conversion, or a missed day is worth. The system applies your rule the same way every time — no manager doing mental math at month-end.
A weekly summary, a missed-visit flag, an overdue follow-up — all waiting when they open the app, instead of being reconstructed from memory on a Friday.
What's on the ledger
Usually split across a spreadsheet, a WhatsApp group, and someone's memory. Here they're one page.
Set your own points for a visit, a conversion, and a penalty for a missed day. A monthly leaderboard ranks two categories at once — most visits, and most conversion value — so a quiet closer isn't invisible next to a busy prospector.
Editing or deleting a logged visit requires a written reason. It's timestamped against whoever made the change and shows up in a searchable log any admin can open.
Each company's data is isolated at the database level, not just hidden behind a login screen. Inside it: admins, managers, and employees, grouped into teams with their own reporting line.
Departments, custom visit fields, point values, and the work-week calendar — including Nigerian public holidays — are all configured inside your own account.
A daily check flags reps with missed days and clients overdue for a follow-up, and emails the relevant manager before it becomes a pattern.
Log the value of a conversion against the visit that produced it, and it rolls up into a manager-facing report — by rep, by team, or by client.
The page reps actually open every morning
Points, streak, and rank make the daily habit visible — not as a gimmick, but because it's the fastest way for a rep to see where they stand and for a manager to see who needs a nudge.
Tenant isolation
Isolation is enforced by the database itself, not just by the app's own logic — the difference matters the moment a second company joins the same system.
Postgres itself blocks a query from ever touching a row outside the caller's own tenant — isolation doesn't depend on the application remembering a filter.
Changing or removing a logged visit requires a reason. It's recorded, timestamped, and visible to admins in the audit log — never just gone.
Employees see their own visits and team. Managers see their team's reporting. Admins see the company. Platform-level data stays with platform admins.
Who sees what
| Role | Logs visits | Sees | Configures |
|---|---|---|---|
| Employee | Yes | Own visits, own points, team leaderboard | — |
| Manager | Optional | Team visits, weekly summaries, missed & follow-up alerts | Follow-up reassignment |
| Admin | Optional | Company-wide visits, audit log, conversion reporting | Departments, points & penalties, custom fields, work calendar |
Rate card
The audit trail, tenant isolation, and email reminders aren't upsells — they're in every plan below.
| Plan | Built for | Includes | |
|---|---|---|---|
| Starterper seat | One team, coming off spreadsheets |
|
Start trial |
| Growthper seat | Multiple teams and departments, one company view |
|
Start trial |
| Enterpriseper seat | Several companies or subsidiaries, one contract |
|
Talk to sales |
Balance carried forward
Add your company, invite your team, and the ledger starts the moment someone submits their first visit.