From spreadsheet to system: setting up a new sales vertical in your CRM

Every RevOps professional knows the moment.

A new VP or Head of Vertical joins the company. They’re sharp, motivated, and they arrive with a “golden list” – a spreadsheet of 300 target accounts they want to go after immediately.

The ask is almost always the same:

“Can we just upload this and get started?”

This is the most dangerous moment in a CRM’s lifecycle.

Say yes, and you invite duplicates, confused ownership, and spreadsheet logic that never quite makes it into the system. Say no, and you become the blocker who is “slowing sales down”.

I recently worked through this exact Day 1 setup with a new Vertical Lead. Here’s how we turned a spreadsheet into a scalable GTM motion – without over-engineering or compromising the CRM.

1. The “Dyson” dilemma – global brands vs local selling reality

The first issue surfaced immediately.

The VP wanted to target major high-street retailers.

• The data: His enrichment tool surfaced a single global entity, headquartered in the US.
• The reality: He was selling to UK operating teams, with local budgets, local decision-makers, and local procurement.

If we had imported the list as-is, all UK outreach would have attached to a US head office record. Ownership, territory reporting, and pipeline attribution would have been wrong from day one.

The fix

We defined a strict parent / child model before creating a single record:

• Parent: Global HQ (financial and legal entity)
• Child: UK operating company (the sales target)
• Rule: Operational deals and local decision-makers live on the child record. Group-level procurement, legal, or enterprise agreements stay at the parent.

This wasn’t a data decision. It was a sales strategy decision. We weren’t trying to create the perfect universal model – we were solving for where this VP’s team would actually be spending their time: in regional conversations with operational buyers.

Lesson

If your account hierarchy is wrong, your territory planning, reporting, and pipeline forecasts are wrong too. You don’t “fix that later”. Later never comes.

2. The “90 stakeholders” problem

One of the first target accounts already had over 90 associated contacts in the CRM.

The VP asked a very reasonable question:

“How do I email the right people without spamming the entire company?”

His instinct was to manually cherry-pick contacts one by one. That works once. It does not scale.

The fix

We turned noise into signal using automation.

Instead of manual filtering, we set up a background workflow in HubSpot using job title pattern matching and seniority filters:

• Ingest: Pull all relevant contacts above a defined seniority threshold
• Categorise: Scan job titles automatically
  • “Head of People” → HR
  • “Store Operations Director” → Operations
• Target: Build live CRM segments based on function and seniority

Now the VP could say: “Show me leadership in retail where function = operations.”

Ninety contacts became four. No manual effort. No guesswork. No one getting spammed “just in case”.

The setup took about 20 minutes. It’s saved roughly 3 hours per week in manual contact research.

3. Killing the shadow CRM before it forms

The spreadsheet had a column called “Phasing” – Phase 1 targets vs Phase 3 long shots.

The plan was to keep managing this in Excel.

This is how shadow CRMs are born.

When priority, intent, or sequencing lives outside the system, the CRM becomes a historical record, not an execution tool. Forecasting degrades. Handoffs break. Context disappears.

The fix

We operationalised the spreadsheet logic immediately.

• Created a “Target phasing” property inside the CRM
• Imported the VP’s unique IDs
• Mapped spreadsheet phases directly to system fields

Now “Phase 1 targets” isn’t a tab on someone’s desktop. It’s a saved view the whole revenue team can see, use, and report on.

The Outcome

Forty-five minutes of upfront architecture delivered results we’re still benefiting from three months later:

• Zero duplicate accounts created
• 100% of outreach properly attributed to the correct entity
• Average contact research time reduced from 15 minutes to under 2 minutes per account
• The VP hit 87% of his Q1 pipeline target in a brand new vertical

More importantly, we avoided what I’ve seen happen dozens of times: a vertical launch that creates six months of data cleanup, confused reporting, and a sales leader who loses trust in the CRM entirely.

Summary

The difference between a messy vertical launch and a scalable one isn’t the software. It’s the discipline of the first upload.

By spending 45 minutes upfront to:

• Define parent / child relationships
• Standardise target phasing
• Automate job function classification

…we avoided months of cleanup and hundreds of hours of manual work later.

If you’re launching a new sales vertical, don’t just upload the spreadsheet.

Architect the strategy first.

Contact

To get in touch, please drop me a line at tom <at> tjmdigital <dot> com