Your merge fields are the first thing a prospect reads and the fastest way to prove you bought a list. “Hi JOHN, I noticed ACME MANUFACTURING SOLUTIONS, INC. is expanding” is grammatically fine and commercially fatal — nobody writes their own company’s legal name in a sentence. Raw exports from Apollo, Sales Navigator and Crunchbase all carry registry-formatted data, so cleaning it is a required step, not a polish step. Here are the exact rules we apply to every list before it ships.
KEY TAKEAWAYS
- Strip legal suffixes (Inc, LLC, Ltd, GmbH, Pvt Ltd) from company names used in copy.
- Fix ALL-CAPS and all-lowercase names — but preserve genuine capitalization like McDonald and O’Brien.
- Resolve nicknames carefully; when unsure, use the name as written rather than guessing.
- Keep a raw column and a display column — never overwrite your source data.
- Always define a fallback value for empty merge fields, or your sequencer will send “Hi ,”.
Rule 1: Strip Company Legal Suffixes
Databases store registered entity names; humans say the short version. Remove these when the company name appears in copy: Inc, Inc., Incorporated, LLC, L.L.C., Ltd, Ltd., Limited, Corp, Corporation, Co, Co., GmbH, AG, S.A., B.V., Pty Ltd, Pvt Ltd, Private Limited, LLP, PLC, SAS, SRL.
Three cautions that trip up naive find-and-replace:
Only strip at the end of the string. “Ltd” appearing mid-name is part of the name. Anchor your rule to the trailing position.
Clean up the leftover punctuation. “Acme Solutions, Inc.” → stripping “Inc.” leaves “Acme Solutions,” with a trailing comma. Strip trailing commas and periods after suffix removal.
Protect names where the suffix is the brand. A handful of companies genuinely read as their full form. Keep a small exception list and review anything under two words after stripping.
Rule 2: Fix Name Casing Without Breaking Real Names
Exports arrive as “JOHN SMITH”, “john smith” and “John Smith” in the same file. Naive title-casing fixes the first two and destroys the exceptions. Preserve: Mc/Mac prefixes (McDonald, MacLeod), O’ names (O’Brien), hyphenated surnames (Anne-Marie, Smith-Jones), and genuine internal capitals (van der Berg conventions vary by region — when in doubt, leave as written).
Rule 3: Handle Nicknames Conservatively
Robert→Rob feels friendlier and is a coin flip: plenty of Roberts are never called Rob, and getting it wrong reads as sloppy automation. Safe approach — use the first name exactly as the source has it, and only shorten when the source itself shows the short form. Never expand in the other direction (Bob→Robert) — that reads like a database record, which is exactly the impression you’re avoiding.
Rule 4: Never Overwrite Source Data
Keep company_raw and company_display, first_name_raw and first_name_display. When a rule turns out wrong, you can re-run it; if you overwrote the original, the information is gone. Point your sequencer at the display columns only.
Rule 5: Define Fallbacks for Every Merge Field
Any row with an empty display field will render “Hi ,” in production. Set defaults in your sequencer — “there” for first name, “your company” or “your team” for company — and audit the file for blanks before import.
💡 Pro tip: Sort your final file by each merge column and read the first and last twenty rows. Alphabetical extremes are where the weird data hides — punctuation-prefixed company names at the top, all-caps entries at the bottom.
These rules sit at stage four of the full cleaning process — after deduplication, before verification.
Lists that arrive already formatted
Every Rooster4am list ships with suffix-stripped company names, corrected casing and sequencer-ready merge columns — no spreadsheet surgery on your side.
Frequently Asked Questions
Should I remove Inc and LLC from company names?
Yes, for any name used inside email copy. Keep the full legal name in a separate column for records and invoicing.
How do I fix ALL CAPS names in a spreadsheet?
PROPER() in Excel or Google Sheets handles the bulk, then manually review Mc/Mac, O’ and hyphenated surnames, which it breaks.
Is it safe to shorten first names automatically?
No. Use the name as the source provides it; automated nickname substitution reads as sloppy more often than it reads as friendly.
What fallback should empty merge fields use?
“there” for first names and “your company” for company names — and audit for blanks before import rather than relying on the fallback.