I’ve spent 30-plus years as a drummer. I’ve also spent over a decade inside HubSpot, cleaning up CRMs for companies that swore their data was “mostly fine.” Those two worlds taught me the same lesson from different angles: a system only works if someone designed it around how people actually move, not how a manual says they should.
A drummer who’s never played with the band can’t keep time for them. A CRM consultant who’s never worked inside music can’t tell you why your royalty split logic doesn’t fit into a generic deal pipeline. That gap is where most CRM projects for labels, management firms, publishers, and music platforms go sideways.
Here’s what I see most often, and what to do instead.
Why does our CRM feel like an expensive spreadsheet nobody trusts?
Because it was built before anyone mapped the workflow.
Most companies buy the software first. Sales wants better visibility, someone gets budget approved, a rep sets up pipelines and fields in a few weeks, and the team is told to start using it. Nobody sat down first and traced how a creator actually moves from first contact through signed deal through active release through royalty payout.
Without that map, the CRM becomes a container for whatever people feel like typing in. Some reps log everything. Others log nothing. Six months in, you have a system full of half-finished records that nobody trusts enough to build a decision on.
The fix isn’t a better CRM. It’s mapping the ecosystem first: how information flows from creator onboarding through release management through payouts, where the handoffs happen, and where things currently break. Configure the system to match that map. Not the other way around.
Why don’t sales, ops, and royalties ever seem to be looking at the same numbers?
Because each team quietly built its own source of truth, and nobody noticed until the numbers stopped matching.
This is the silo problem, and it’s rarely intentional. Sales tracks deals in the CRM. Royalties runs its own spreadsheet because “the CRM doesn’t handle splits right.” Release management has a shared doc that three people update inconsistently. Each team’s data is internally fine. None of it talks to the others.
The cost shows up in specific, expensive ways: a payout gets calculated from stale numbers, a renewal opportunity gets missed because nobody flagged it in the shared system, a new hire spends their first month just figuring out which spreadsheet is actually current.
One system doesn’t fix this by itself. What fixes it is deciding, deliberately, which system is the system of record for each type of data, then holding every team to updating it there. That’s a governance decision before it’s a technical one.
Why does our CRM feel like it was built for a company that isn’t ours?
Because it probably was. Most CRM templates, and most consultants who set them up, are built for straight sales pipelines: lead comes in, lead gets qualified, deal closes. That works fine for a lot of businesses. It doesn’t hold up well against release cycles, rights and split tracking, sync licensing pipelines, or catalog management, because those aren’t linear sales motions. They’re operational workflows with their own timing, their own handoffs, and their own compliance requirements around creator data and payments.
When you force music-specific work into a generic sales pipeline, people start working around the system instead of in it. That’s when the shadow spreadsheets creep back in, and you’re right back to the mess you were trying to fix.
The fix is building custom objects, pipelines, and properties around what your business actually does, not what the out-of-the-box CRM assumes every business does. A label’s release pipeline and a publisher’s rights pipeline should not look identical, because the work isn’t identical.
Why does bad data keep coming back no matter how many times we clean it up?
Because nobody owns it.
Data cleanup projects fail the same way New Year’s resolutions do. There’s a burst of effort, duplicate records get merged, fields get standardized, everyone feels great for a month. Then new reps join, old habits creep back, and a year later you’re paying for another cleanup.
The difference between companies that stay clean and companies that don’t isn’t the initial cleanup. It’s whether someone is actually responsible for data governance afterward: naming conventions, required fields, duplicate checks, a regular audit cadence. Without an owner, “clean data” is a project. With one, it’s a standard.
Why don’t we trust our own reports enough to make decisions with them?
Because the reports are only as good as the workflows feeding them, and we already know those are broken.
This is the pain point that costs the most and gets talked about the least. Leadership teams are still making strategic calls on gut instinct, not because they don’t want data, but because they’ve been burned by data that turned out to be wrong. Once you’ve walked into a board meeting with a number that didn’t hold up, you stop trusting the dashboard. You go back to your gut. And your gut doesn’t scale.
Reliable reporting isn’t a dashboard feature. It’s the output of clean data flowing through a workflow that people actually follow. Fix the input, and the reporting problem mostly fixes itself.
We already migrated to a “real” CRM. Why does it feel like we’re back where we started?
Because the migration was a project, and your business isn’t.
A lot of companies treat CRM setup like a one-time event: budget it, build it, launch it, move on. But the company doesn’t stop growing the day the CRM goes live. New team members join. New release types get added. The catalog grows. Compliance requirements shift. A system built for a 15-person team starts creaking at 40 people if nobody revisits it.
The companies that stay out of the mess long-term treat their CRM as something to maintain, not something to finish. That means periodic audits, not just at setup but on a schedule, and someone whose job includes noticing when the system stops matching how the team actually works.
The Pattern Behind All Six
Every one of these mistakes traces back to the same root cause: treating the CRM as the fix, when the CRM is actually just where broken or working workflows become visible. Buy the software first, and you get an expensive record of your existing chaos. Map the workflow first, fix what’s broken, then build the system around it, and the CRM becomes what it was supposed to be in the first place: a place your whole team can trust.
Where to Start
If any of this sounds familiar, you don’t need to fix all six at once. Start by mapping how data actually moves through your organization right now, from creator onboarding to payout. That map alone usually surfaces which of these mistakes is costing you the most.
I help music companies, labels, management firms, publishers, and music platforms clean up exactly this kind of mess, and I’ve been in the HubSpot ecosystem since 2013. If you want a second set of eyes on where your data is breaking down, let’s look at your CRM setup.
Book a free 30-minute audit call, and we’ll walk through where your current workflow is costing you time, money, or trust, and what fixing it would actually take.
