How to organize a lead list in Excel your sales team will actually use

A working list needs less than it seems: business name, international-format phone, verified email, website, rating, review count, city, data source, capture date, and an empty status column for the team to work. With those ten columns an SDR can call, log and advance without ever leaving the row.

What you cut matters too: fifteen maybe-useful columns (socials, hours, copied descriptions) compete for attention, bloat the file, break imports and read worse on screen. Practical rule: if a column does not change who you call first or what you say when you call, it does not belong in the working sheet — it goes to the CRM or nowhere.

Format is the difference between a sheet and a tool. Phones in international format with country code (+52 442 123 4567) dial correctly from any softphone and never duplicate under different spellings. Emails lowercase, no spaces. One row per business — not per branch, not per contact — with branches noted in their own column. Dates as year-month-day so every system sorts them right.

Formats get locked in when the sheet is created, not fixed afterwards: adding Excel data validation (dropdowns for status, length checks for phone) keeps the first week of use from deforming the file. And deduplication runs on a stable key — the normalized business name or its website — not by eye with the Excel filter at six in the evening.

The list is not read top to bottom: it is prioritized. A simple score with data you already have goes a long way: a high rating with many reviews suggests a live, moving business; a website with a published email suggests they invest in their presence and answer their channel; concentrated cities enable visit routes. Three criteria, one A/B/C priority column, done.

The goal of the score is not data science: it is making sure nobody dials the list in random order. Block A gets worked this week; B fills the gaps; C waits for volume campaigns. And because the whole list shares one format, re-prioritizing after a calling session is sorting by a column, not rebuilding the file.

The CRM handoff fails for two reasons: formats the importer does not understand, and duplicate keys that create repeated contacts. The first is solved above (locked formats, one row per business); the second by defining the uniqueness key before importing — website or normalized name — and using it inside the CRM too. A clean CSV imports in minutes; a dirty one buys an afternoon of CRM cleanup.

Finally, the list is an input, not a monument: every dial updates the status (answered, does not exist, booked, call back), and every week a fresh batch of verified leads is added instead of recycling the old one. RadarLeads is born to exactly that standard — Excel/CSV export with clean columns, normalized phones, verified emails and per-record source — so the file that reaches your team is the one that sticks.