Backend ops · field-sales agencies
Your board moves
at rep speed.
Your reps generate the data your board needs to decide. But it is trapped in a dozen tools and arrives days late. Mint brings it home in real time. Every call, every lead, every close in one record your agency owns.
01 · The problem
The data problem at midsize agencies
Reps hold the ground truth. Leadership works from standup notes and a weekly roll-up, a version of the floor that is already stale when it lands.
Lead data is scattered across CRM, email, phone notes and spreadsheets. Nobody owns the record, so nobody can audit it.
Deal velocity and rep performance reach the board as a summary, after the fact. Coaching happens after the miss, not before it.
Territory performance surfaces at quarter close, the one moment when it is too late to course-correct the quarter.
02 · Platform
How Mint works: three layers, one backend
Voice Board
Setter and closer transfer data in real time. Call recordings, notes and consent are captured on the line. Reps see the full handoff instead of guessing at it.
Hex Pin
Field workflows for in-field reps. Territory mapped by hex cell: lead density, rep location, market intelligence. One tap to close, one tap to record.
Data Core
Real-time visibility for leadership. Rep performance by territory, lead source, close rate. Revenue predictability in one dashboard your agency owns and controls access to.
03 · Field data layer
mintleads.bid/mapThe map is the database
Hex Pin plots every territory on a hex grid. What a rep taps in the field is the same row your analysts query: one schema, no reconciliation, no export step in between.
{
"cell_id": "NE04-7B29-C1",
"resolution": 8,
"territory": "NE-04 / Bergen",
"leads": { "open": 41, "worked": 118 },
"density_pct": 0.74,
"assigned_rep": "rep_7712",
"last_ping": "2026-08-18T14:02:11Z",
"pii_scope": "record_only",
"export": { "allowed": false, "requires": "approval" }
}select cell_id, count(*) as closes from mint.events where type = 'close' and day >= current_date - 7 group by 1 order by 2 desc;
Installs cluster. Mint reads the pattern off the same records the reps write, so an owner can point spend at the blocks that convert instead of the whole territory.
Drop lists cut to the focus zones and their adjacent cells, not the ZIP.
Routes built from install density, so a rep walks blocks that already convert.
Geo audiences exported as cell boundaries. No customer detail leaves Mint.
04 · Data control
Your customer list cannot walk out the door
In most stacks a manager can pull the full customer table with names, addresses and phone numbers, then take it with them when they leave. Mint inverts that. Reps and managers see one record at a time, only when there is a reason to. Anything wider is a request, and the request is on the record.
A rep opens the customer they are working: the account in front of them, on the issue at hand. No list view, no table, no bulk select.
Any report carrying addresses or contact detail is submitted for approval, scoped to a purpose, and released by an owner. It is not downloaded on a whim.
Who opened which customer, when, and why. Offboarding is a switch, and the trail behind it is already written.
Fields: name, address, phone
05 · Mechanics
Call placed, lead captured, close logged. From the phone or the doorstep.
Encrypted, timestamped, logged. One schema, one owner: your agency.
Territory, velocity and retention on one dashboard, current to the minute.
06 · Referral campaigns
The map writes the referral campaign
A cell with six installs and four holdouts is a campaign, not a report. Mint fires it off the install data, the same records your reps already wrote, and credits the referral back to the rep and the cell when it lands.
SIX HOMES ON YOUR BLOCK
WENT GREEN.
Four of your neighbors have not made the switch yet. Send them our way and we will put three months of energy on us.
Refer a neighborA cell crosses six installs with holdouts remaining, and the campaign queues itself. No analyst pulling a list.
The ask goes to customers who already converted, not to cold addresses. Mailer, SMS or door drop on the same audience definition.
Three months of energy, or whatever the board signs off on. Cost per referred install is set before a single piece ships.
Every referral code carries the cell and the rep who owns it, so the payout and the credit resolve without a spreadsheet, and no customer list leaves Mint to run the send.
07 · What Mint does
Two jobs: plot the backlog, route what comes next
Everything above reduces to these two. We take the data your agency already paid for and put it on the map, then we build the rails so every new call, lead and install lands in the same place, under your control.
Existing data backlog, plotted
Years of installs, closed deals and dead leads sitting in exports, spreadsheets and old CRMs. We normalize the history, geocode it to hex cells, and hand you the pattern it was always holding.
Incoming data, routed
From then on the rails are ours. Calls, handoffs, field taps and installs are captured at the source and routed to the record, the dashboard and the audit log in the same motion.
Ready to move at rep speed?
Faster board decisions, reps whose work is on the record, and an agency that scales on numbers instead of anecdotes.