HubSpot for Events and Media Companies: What to Configure Before You Go Live

Most HubSpot implementations fail. Not because of HubSpot, but because businesses go live with a default configuration that was never designed for how they actually sell. A generic pipeline with stages like "Prospect / Qualified / Proposal / Closed Won" tells a sponsorship sales team nothing useful. It does not reflect how deals move in an events business. It does not distinguish between a first-year sponsor and a renewal. Within three months the team stops updating it. Within six months leadership stops trusting the data. And within a year HubSpot becomes another expensive CRM nobody uses.

The failure is always in the setup, never in the software. I have seen HubSpot work well in businesses running 20+ events a year with multiple revenue streams. I have also seen it abandoned in businesses running three events because nobody configured it to match how the team actually sells. The difference is whether someone took the time to set it up properly before anyone logged in.

Start with the Process, Not the Software

Before you touch HubSpot, sit down with your sales team and map how deals actually move. Not how you wish they moved: how they actually move today, with all the messy exceptions and workarounds your team has developed.

For an events business this is more complex than most, because you do not sell one thing. A typical events company has four or five distinct revenue streams: sponsorship packages, exhibition space, delegate registrations, content partnerships, and renewals. Each moves differently through the sales cycle. A sponsorship deal might take four months from first conversation to signed contract. A delegate booking might close in a single phone call. Putting both into the same pipeline with the same stages is like trying to run a marathon and a sprint on the same track.

The mapping exercise is simple. Talk to your reps and ask them to walk you through their last five closed deals. Not the ideal version: the real version. Where did the lead come from? What was the first meaningful interaction? What caused deals to stall? What triggered the decision to move forward? You will find that the actual deal stages are different from what you assumed. That is normal. Your job is to find the common milestones that apply across the team, for each revenue stream. This exercise takes a day. It saves months of rework.

The Five Things to Configure Before Anyone Logs In

Once you have mapped your sales process, five things must be configured in HubSpot before a single rep creates their first contact.

1. Pipelines. You need one pipeline per revenue stream. Do not mix sponsorship deals with delegate sales in the same pipeline. Each pipeline should have five to seven stages maximum, and each stage should represent a real milestone your team recognises. For a sponsorship pipeline this might look like: Initial Conversation, Requirements Gathered, Proposal Sent, Proposal Reviewed, Negotiation, Verbal Commit, Contract Signed. For delegate sales: Enquiry Received, Pricing Sent, Registered, Payment Received. The stages are different because the processes are different. If you find yourself creating more than seven stages, you are probably conflating two processes that should be separate pipelines.

2. Properties. HubSpot lets you create custom properties on contacts, companies, and deals. The temptation is to build a 40-field contact record. Resist it. In practice, 10 to 15 well-chosen properties are more useful than 40 that nobody fills in. For events businesses the properties that matter are: event name, package type, renewal date, decision-maker name, competitor CRM, deal source, and estimated close date. Start lean and add properties only when you have a specific reporting need.

3. User permissions and teams. In a business running multiple events or brands, who can see what matters. You do not want the team selling your technology event editing contacts owned by the energy event team. Set up teams in HubSpot that mirror your actual sales structure before anyone starts creating records. Configure permissions so reps see their own deals, team leaders see their team, and leadership sees everything. This is a 30-minute task that prevents months of confusion.

4. Dashboards. Build the leadership dashboard before go-live, not after. If the MD cannot open HubSpot on day one and immediately see pipeline by event, revenue by rep, and renewal risk, adoption from the top will be slow. And if adoption from the top is slow, adoption from the team will be slower. The dashboard does not need to be perfect. It needs to exist, showing real data, so the first time a senior leader logs in they see something useful.

5. Integrations. Connect email and calendar before go-live so every interaction is logged automatically from day one. This is non-negotiable. If reps have to manually log emails and meetings, they will not do it. Beyond email and calendar, connect your outbound tools: Instantly for email sequences, HeyReach for LinkedIn outreach, so leads flow straight into HubSpot. Connect Fathom for call intelligence so call summaries appear on the contact record automatically. The principle is simple: do not go live with a CRM that requires manual data entry. Manual data entry is what killed the last CRM.

The Migration Question

Most events businesses moving to HubSpot are coming from something else: Salesforce, Pipedrive, or (more commonly than anyone admits) a collection of spreadsheets that someone started in 2017. The migration question always generates anxiety, and the anxiety almost always leads to the wrong decision: migrating everything.

Do not migrate everything. Migrate active contacts and open deals. Migrate renewal records for customers who are genuinely active. Migrate key account histories where you need context for upcoming conversations. Do not migrate five years of closed deals nobody will look at again. Do not migrate contacts from events you no longer run. Every bad record you migrate pollutes your new system from day one.

The cleanest approach is a selective migration: export your active data, clean it (deduplicate, update job titles, verify email addresses), and import it into HubSpot with correct pipeline assignments and property mappings. Run both systems in parallel for four to six weeks rather than doing a hard cutover. During the parallel period, reps update both systems for active deals. This is annoying but it provides a safety net. A hard cutover on day one, with no parallel period, is how you lose deals and create resentment.

Training: Do It Before Go-Live, Not After

The single biggest cause of failed CRM implementations is training that happens after the system is live. The logic seems reasonable: let the team start using HubSpot and train them when they have questions. In practice it is a disaster. By the time training happens, reps have already spent two weeks forming bad habits. They have created deals in the wrong pipeline, invented workarounds for moving contacts between stages, and decided that certain fields are optional. Unpicking those habits takes three times as long as teaching the right approach from the start.

Good pre-launch training is process-led, not software-led. You do not start by showing reps how to click buttons. You start by teaching them how deals should flow through the pipeline, what each stage means, and what information needs to be captured along the way. Then you show them how HubSpot reflects that process. The software is the tool; the process is the point.

Different people need different training. Reps need their daily workflow: creating contacts, moving stages, scheduling follow-ups. Managers need to read the pipeline and coach reps based on the data. Leadership needs a 20-minute dashboard walkthrough. Do not train all three groups in the same session.

Every team has the rep who says "I don't need training, I'll figure it out." That rep is the most dangerous person in your implementation. They will figure out their own way to use HubSpot, and their way will be incompatible with everyone else's. Within a month they will have a pipeline full of deals in stages they invented. Make training mandatory, no exceptions, and hold the session before the system goes live.

The First 90 Days

Going live is the starting point, not the finish line. The first 90 days determine whether HubSpot becomes a genuine operating system for your sales team or another tool that slowly falls into disuse.

Data hygiene comes first. No matter how carefully you set up the system, bad data will appear: contacts with missing job titles, deals in the wrong pipeline, duplicate company records. Fix these as you find them. Do not let them build up. Assign someone to spend 30 minutes a day during the first month reviewing data quality. If bad data accumulates unchecked, the team will stop trusting the system, and once trust is lost it is very difficult to regain.

Adoption monitoring is second. Check weekly who is logging activity and who is not. Have direct conversations with non-adopters early, in the first two weeks, not after two months when bad habits are established. Most non-adoption is not resistance; it is confusion. A five-minute conversation usually solves it.

Dashboard refinement is third. The first version will not be perfect. After four weeks, sit down with the people who use the dashboards and ask what they actually look at, what they wish they could see, and what they ignore. Iterate. Declare the implementation a success when every rep is using the CRM daily and leadership trusts the data enough to make decisions from it.

Getting the Configuration Right

The difference between an events business that loves HubSpot and one that abandons it within a year is almost always the initial configuration. If you are about to implement HubSpot, or if your current setup is not working, the best starting point is a structured assessment of how your team actually sells and what the system needs to look like to support that: a detailed review of the sales process, the tools already in place, and the state of the data. Done before any configuration work begins, it gives you a blueprint, so you build once and build correctly.

If you want the whole picture in one place, get the AI Sales Stack Cheat Sheet. One page, the full framework, what to use, what to skip, and what is actually worth paying for. New writing goes out to the same mailing list.

---

About the author: David is the founder of AI Sales Stack. Senior sales leader with 23+ years driving multimillion-pound growth across B2B media and events. Pioneered AI-enabled sales operations at Terrapinn and Clarion Events, integrating tools across prospecting, outreach, CRM automation, and proposal generation to shorten sales cycles and increase conversion. Currently Commercial Director at Ocean Media Group, where his brief includes embedding AI tools across the commercial function. Writes here about what is actually working in AI-enabled B2B sales, and what is being oversold.