prospectA prospect list can look organized while repeatedly sending you back to the same websites. The usual problem is not a lack of columns. It is that the information does not explain which business you found, why it matters, or what should happen next.
A useful prospect list connects the right business to evidence and an action. Check record identity, qualification, duplicates, sources, missing data, updates, tasks, file ownership, and progress measures before adding more rows.
After the nine mistakes, use the symptom table to choose the first repair for your own list.
1 Mixing companies and branches in one unexplained list
A row for a parent company and a row for one of its branches represent different things. If the distinction is missing, your company totals and territory coverage become unreliable.
Choose a record unit and label exceptions. Give branches their own IDs and connect them with a parent-company field. Count companies and locations separately when both matter to the task.
2 Treating every captured company as qualified
A tool can capture a business accurately even when that business is outside your target market. Automatically populated fields do not establish a reason to sell to it.
Require a short fit reason based on evidence. If you cannot explain how the business matches your inclusion rules, keep it in research or exclude it. Do not let a complete-looking row skip qualification.
3 Deleting every repeated domain
Several branches may share a corporate website. Removing all but one can erase valid locations and the notes attached to them.
Use the domain as a review signal. Compare addresses, location pages, and parent relationships before merging. Keep useful notes and contact restrictions in the retained record, and preserve a merge log when IDs change.
4 Saving a homepage without the relevant source
A homepage may identify the company but fail to support the email, branch address, or service claim in your notes. The next researcher has to search again.
Keep the specific page that supports important details. If one URL cannot explain the entire record, use a separate Evidence URL or a concise source note. Preserve the original link when you normalize a domain for matching.
5 Guessing missing contact information
An address pattern that looks plausible is not a published business email. A guessed field can be mistaken for verified information by the next person who uses the sheet.
Leave unavailable details blank and record what was checked. Use labels such as Not found during review or Contact form available in a separate note. Keep uncertainty visible instead of filling the cell for appearance.
6 Replacing manual notes with a fresh export
A new collection may contain updated company details but none of the context added through sales work. Pasting it over the working list can erase ownership, outcomes, and next actions.
Keep a source export separate from the current working file. Match records using stable IDs and business evidence, then update only the appropriate fields. Product-level refresh behavior does not protect a spreadsheet you overwrite manually.
7 Using vague next actions
Call, Follow up, and Research leave another decision to be made before work begins. They also make it difficult to tell whether the assigned task was completed.
Write the intended outcome: Confirm who handles branch purchasing or Check whether the company serves industrial customers. Add an owner and due date when the record is active. If no useful next action exists, reconsider why it remains in the queue.
8 Keeping several competing master files
A file on the desktop, another in email, and a third in a shared folder can each contain different notes. Nobody knows which version should control the next action.
Choose one authoritative working file or system. Label dated exports as archives and record when they were created. When handing work to someone else, state where outcomes must be written back.
9 Measuring progress only by row count
More rows can mean more duplicates, weak-fit companies, and unresolved work. A growing collection can conceal a process that is not producing usable next steps.
Track reviewed candidates, qualified records, completed actions, and unresolved items separately. Use a consistent definition for each. The counts should help explain where the process stalls, not just make the collection look larger.
Choose the first repair from the symptom
A messy list rarely needs every correction at once. Use the visible problem to choose the first change:
| Symptom | First repair | Check that it worked |
|---|---|---|
| Reps keep revisiting the same companies | Add reviewed IDs and duplicate decisions | A repeated candidate is recognized |
| Nobody remembers why a company fits | Add a fit reason and source | A colleague can explain inclusion |
| Follow-up disappears after a new export | Separate source data from activity history | Existing notes survive the update |
| Rows look complete but calls go to wrong branches | Recheck location sources | Route and branch agree |
| A large queue produces little action | Reduce intake and assign specific tasks | Retained rows have usable next steps |
Apply the chosen repair to a manageable sample and review the result before changing the entire file. Keep the original so a mistaken merge can be investigated.
Then change the habit that caused the problem. A missing source field should be captured during research; an ambiguous ownership rule should be resolved before the next handoff. Otherwise, the same cleanup returns with the next batch.
Related Questions
Should I delete every incomplete prospect?
No. Separate useful candidates with a specific research gap from businesses that clearly do not fit. Keep a bounded next action for the former and an exclusion reason for the latter. Empty cells alone do not determine value.
What is the first thing to fix in a messy list?
Clarify what one row represents and identify the authoritative working copy. Then add stable IDs and preserve sources. Those foundations make later duplicate review, corrections, and follow-up less likely to damage useful information.
Use the cleanup checklist to repair the data and the weekly routine to prevent the same problems returning.
Published by Stephen Modliszewski, publisher of Prospect — Sales Bookmarks. ProspectClip is the extension’s website. Fictional examples and illustrative calculations are teaching aids, not customer results.