Skip to content
HubSpot Setup & Use
ops hubspot applied

Stop Clicking. Start With a Strategy. The Set Up HubSpot.

Marc Brown
Marc Brown

Go-to-Market Strategy  ·  Ops  ·  HubSpot

Most startups buy HubSpot, connect their email, and start clicking. Six months later the portal is a mess nobody trusts and the team is back to spreadsheets. Here's how to set it up right the first time.

HubSpot  |  CRM Setup  |  GTM Alignment  |  9 min read

There are dozens of CRM and GTM platforms competing for your budget right now. Salesforce, Zoho, Pipedrive, Outreach, Salesloft, monday.com, each one with a compelling demo and a sales rep who will promise you the world. We're going to save you the evaluation time and tell you what we tell every pre-Series B team we work with: start with HubSpot, and set it up with a strategy.

This isn't a sponsored take. It's the conclusion we've reached running GTM programs across cybersecurity and AI startups at every stage from pre-seed through Series B. The platform that gives your team the best shot at execution, visibility, and eventual scale, without drowning in configuration overhead, is HubSpot. But only if you set it up right.

Why HubSpot

One platform. Sales, marketing, and ops — without the Salesforce overhead.

Salesforce is a phenomenal platform, for companies that have a dedicated Salesforce admin, a RevOps team, and the budget to sustain both. That is not your pre-Series B startup. Salesforce requires significant configuration investment before it does anything useful, and without that investment it becomes a contact database that no one updates because it takes too long.

Salesloft and Outreach are excellent sales engagement tools. They are not CRMs. They do not replace the broader platform you need, and adding them too early fragments your data before you have a foundation to fragment.

Pipedrive and Zoho are simpler to set up, but they sacrifice the marketing and ops depth that becomes essential the moment you need to run coordinated ABM, track attribution, or build a real reporting layer for your board.

HubSpot sits at the intersection of usable-now and scalable-later. Here's what it gives you in a single platform:

Sales Hub

Contact and company management, lead and deal pipelines, sequences, meeting scheduling, email tracking, playbooks, and call recording. Everything an AE needs to run a structured sales process without switching tools.

Marketing Hub

Website and landing pages, email marketing, social publishing, paid ad tracking, ABM tools, lead scoring, forms, CTAs, and AI-assisted content. From first touch to AQL, in one place.

Ops Hub

Data sync, automation, custom properties, and reporting infrastructure. Keeps your data clean and your workflows running. This is the layer most startups skip, and the reason their portals become unmanageable.

Service Hub

Ticket pipelines, knowledge base, customer feedback, and SLA management. You won't need this on day one, but when you close your first enterprise deals, customer success lives here.

Before You Click Anything

The decisions you make before setup determine whether HubSpot helps or hurts you.

The frat house problem, the messy, unusable HubSpot portal that half the startups we talk to are inheriting, is not a HubSpot problem. It's a strategy problem. Teams start clicking before they've defined how they'll use the system, and three months later they have 40,000 duplicate contacts, pipelines that don't reflect how the company actually sells, and dashboards that nobody looks at.

Before importing a single contact, four decisions need to be made in writing:

  • Lifecycle stage definitions. HubSpot's default lifecycle stages are built for a volume-based demand gen model. For pre-Series B companies running an ABM motion, they don't fit, and forcing your team to use them creates confusion, bad data, and misaligned reporting. Define stages that reflect how your company actually advances accounts.

    Aterous ABM Lifecycle Model

    Stage 1

    Subscriber

    An individual who has opted in. No company qualification yet. Marketing owns this stage.

    Stage 2

    Company

    A company record has been created and associated. Firmographic data confirms it could be ICP-aligned. Research phase begins.

    Stage 3

    Named Account

    The account has been added to the named account list and assigned a tier (T1/T2/T3). Sales and marketing are now running coordinated plays.

    Stage 4

    AQL

    Account-Qualified Lead. ICP fit confirmed, buying group identified, pain mapped. Sales receives this, discovery doesn't start from zero.

    Stage 5

    Opportunity

    A deal has been created. The account is in active sales motion with a defined next step, timeline, and economic buyer identified.

    Stage 6

    Customer

    Deal closed. The account transitions to customer success ownership. Expansion and renewal pipeline begins.

    Each stage transition needs a written definition agreed by marketing and sales before you configure HubSpot. What exactly moves an account from Named Account to AQL? Who has the authority to make that call? Write it down. If the answer differs between teams, your lifecycle data will never be trustworthy.

  • User permissions and role-based access. Not every user needs to edit every object. Define roles (AE, SDR, Marketing Manager, Admin) before adding users. Unrestricted access is how data gets corrupted.
  • Data model and custom properties. What do you need to know about every contact, company, and deal that HubSpot's default fields don't capture? Define custom properties before import, not after you realize you need them.
  • Data hygiene before import. Audit your contact lists before they touch HubSpot. Remove duplicates, standardize formats, and segment intentionally. Garbage in equals garbage out, and cleaning a corrupted CRM costs far more than cleaning a spreadsheet.

Work with a partner.

The single most consistent mistake we see early-stage teams make is trying to self-implement HubSpot without a plan.

A HubSpot partner doesn't just configure the tool, they build the incremental plan: what to set up in week one, what to add in month three, what to defer until you have the pipeline volume to justify it. That sequencing is the difference between a platform that accelerates your team and one that becomes a tax on it.

Sales Setup

The sales foundation: what your team needs on day one.

Sales setup is where most teams start, and rightfully so. But there's a right order. Don't build sequences before you have a pipeline. Don't build a pipeline before you've defined your deal stages. Sequence matters.

01  —  Deal Pipelines

Build at minimum two pipelines from day one: a new business pipeline and a renewal/expansion pipeline. Stage names should reflect your actual sales motion, not HubSpot's defaults. If your sales cycle has a formal POC stage, name it that. If discovery happens in two phases, build two stages. Your pipeline is the first thing your board will look at; make sure it tells the truth.

02  —  Products & Service SKUs

Set up your product library before deals are created. This enables accurate deal value attribution, quote generation, and revenue reporting by SKU. If you're selling multiple tiers or modules, get them into the product library now retrofitting this later is painful.

03  —  Contact & Lead Routing Automation

Define how inbound contacts get assigned. Round-robin by territory? Hard-assigned by named account list? Routed by company size? Whatever your model, build the automation before your first lead comes in not after. Unassigned leads are dead leads.

04  —  Sequences & Email Templates

Build a small library of core sequences: cold outbound, post-demo follow-up, re-engagement, and renewal/expansion. Templates save time and create consistency but train your team to personalize them. A sequence that sounds automated gets ignored. Start with fewer, higher-quality sequences. You can always add more.

05  —  Calendar & Email Integration

Connect every rep's Gmail or Outlook and calendar before they log a single activity. Without this, you get manual logging which means you get no logging. Meeting scheduling links, email open tracking, and activity sync all depend on this integration being in place from the start.

06  —  Playbooks & Call Recording

Build qualification playbooks inside HubSpot the questions your SDRs and AEs should be asking at each stage. When reps use them during calls, answers populate CRM fields automatically. Add call recording (native or via an integration like Gong or Chorus) and you have a coaching layer that most early teams never build.

Marketing Setup

The marketing foundation: attract, convert, and attribute — from day one.

Marketing setup follows the same principle as sales: sequence matters. You can't attribute pipeline to campaigns before your tracking code is live. You can't run ABM before you have a named account list. Build the foundation, then build upward.

  • Domain and tracking code. Connect your website domain and install the HubSpot tracking code. Everything (e.g., page views, form submissions, attribution) depends on this. Do it on day one.
  • Brand kit. Upload your logo, set your brand colors, and configure your email sending domain. Every piece of marketing that leaves HubSpot should look like your company, not a default template.
  • Website and landing pages. If you're using HubSpot CMS, build your core pages here (.e.g., home, product/service, about, contact, and at least one conversion landing page). If you're not on HubSpot CMS, ensure your external site has the tracking code and forms connected.
  • Inbound and outbound campaigns. Set up your first campaign structure, even if it's simple. One inbound campaign (content → form → nurture) and one outbound campaign (target list → sequence → follow-up). Campaigns are how HubSpot builds attribution; if you don't create them, you can't report on them.
  • Lead scoring. Define your scoring model before you have volume. Behavioral signals (page visits, email opens, content downloads) and firmographic fit (company size, industry, title) should both feed the score, but in an ABM motion, scoring operates at the account level, not the contact level. The threshold you're trying to cross is AQL status: enough account-level intelligence that sales can advance without starting discovery from zero. Marketing and sales need to agree on what that threshold looks like, in writing.
  • ABM configuration. Build your ABM target list from your sales named account list. They should be the same list. Set up company-level scoring and configure ABM dashboards. Connect your LinkedIn Ads account to enable ABM ad targeting directly from HubSpot.
  • Social and ad account connections. Connect LinkedIn, Twitter/X, and any paid ad accounts (LinkedIn Ads, Google Ads). This consolidates performance reporting and enables retargeting audiences built from HubSpot lists.
  • Marketing automation workflows. Build the essentials: new contact welcome, AQL notification to sales when an account crosses the threshold, deal stage change alerts, and re-engagement for cold contacts. Don't over-automate on day one. Four well-built workflows beat forty broken ones.

Visibility & Dashboards

If your leadership team isn't looking at HubSpot, your data is meaningless.

Dashboards are the interface between your GTM execution and your leadership team's decision-making. Build them with one question in mind: what does this person need to see to make a faster, better decision? Not everything, the right things.

Build separate dashboards for separate audiences. Your CEO does not need the same view as your SDR manager. Start with these five:

Core Dashboard Stack

Dashboard Audience Key Metrics
Revenue & Pipeline CEO, CRO, Board ARR, pipeline by stage, closed-won rate, average deal size, time to close, new vs. expansion revenue
Sales Performance Sales Leaders, AEs Pipeline by rep, deal stage velocity, activity counts, sequence performance, POC close rates, quota attainment
Marketing Attribution CMO, Marketing Team Pipeline influenced by campaign, AQL volume and quality, lead source breakdown, cost per AQL, content conversion rates
ABM & Contact Engagement Marketing, SDR Team Named account engagement scores, buying group coverage, Named Account → AQL conversion rate, email engagement by segment, website visits from target accounts
Events & Programs Marketing, Leadership Webinar and event registrations, attendee-to-pipeline conversion, live stream engagement, follow-up sequence performance post-event

"Start simple. A dashboard with five metrics your team reviews every Monday beats a dashboard with thirty metrics nobody opens. The goal isn't comprehensiveness, it's the cadence of looking."

What Comes Next

Once the basics are running, build your growth layer, not before.

The biggest mistake after a solid HubSpot setup is adding complexity too fast. Give the foundation 60 to 90 days of real data before you layer on advanced automation, AI-assisted tools, or third-party integrations. You need to see how your team actually uses the system before you build on top of it.

Once the foundation is stable, clean data flowing, pipelines being worked, dashboards being reviewed, sequences running, the next layer typically includes:

  • Revenue attribution modeling. Multi-touch attribution across first contact, form submission, meeting booked, and deal created. This is what connects marketing spend to closed revenue and is essential before your Series A pitch.
  • Advanced workflows and automation. Deal rotation rules, SLA enforcement, auto-task creation at deal stage changes, and win/loss automation that populates reason fields without rep input.
  • AI-assisted tools. HubSpot's Breeze AI layer (content assistant, prospecting agent, conversation intelligence) becomes genuinely useful once you have 90+ days of CRM data to train against. Don't turn it on day one.
  • Tech stack integrations. Zoom, Slack, Gong, ZoomInfo, Clearbit, or your CPQ tool. Integrate when the use case is clear and the data mapping is defined, not because the integration exists.
  • Service Hub activation. When you have customers to manage, tickets to route, and SLAs to enforce, stand up Service Hub. Before that, it's premature configuration overhead.

The Bottom Line

HubSpot is the right platform. Strategy is what makes it work.

The platform advantage is real, breadth of function, ease of use, and a genuine path to scale from Seed through Series B without ripping and replacing your tech stack. But the platform is only as good as the plan behind it.

Define your lifecycle stages before you touch the platform. Build your pipelines to reflect reality. Set up tracking before running campaigns. Train your team before expecting adoption. Build dashboards your leadership actually uses. And work with a partner who will tell you what to set up now versus what to defer.

The frat house portal is optional. It only happens when you skip the strategy, tolerate shadow systems, and go straight to the clicking. Outside of your finance and engineering tools, HubSpot is the only system of record your GTM team needs, and the only one they should be using.

Single Source of Truth

Outside of finance and engineering, HubSpot is the only system of record. Full stop.

Your company has three operating systems. Your finance system (e.g., QuickBooks, NetSuite, or equivalent) owns the numbers that flow to your accountant, your board, and your investors. Your engineering system, such as Jira, Linear, or equivalent, owns product work, sprint cycles, and bug tracking. Everything else that touches a customer, a prospect, a campaign, or a revenue motion lives in HubSpot. No exceptions.

This isn't a preference. It's a discipline that determines whether your GTM team can actually execute. The moment a rep tracks contacts in a personal spreadsheet, the moment marketing maintains a separate named account list in Google Sheets, the moment a manager keeps their own deal tracker because "HubSpot is too slow", your data fractures. And fractured data means every conversation about pipeline, attribution, or account status starts with ten minutes of reconciliation instead of ten minutes of decision-making.

The Three Systems. Nothing Else.

Finance System

QuickBooks, NetSuite, Xero

Invoicing, recognized revenue, expenses, payroll. Feeds your accountant and your board deck, not your GTM motion.

Engineering System

Jira, Linear, GitHub

Sprints, bugs, feature requests, and roadmap. Product and engineering live here. GTM does not.

HubSpot

Every contact, company, deal, campaign, and customer interaction

If it touches a prospect or customer, it lives here. Marketing, sales, SDRs, account management, all in one system, all in one record.

Where spreadsheets still belong

Spreadsheets are not the enemy, misused spreadsheets are. There is one legitimate use case for a spreadsheet in your GTM motion: analyzing your GTM performance alongside financial data. When you need to model CAC payback, calculate blended ARR growth, or reconcile recognized revenue against pipeline velocity for a board deck, you pull HubSpot data into a spreadsheet and run the analysis there. The spreadsheet is a calculator, not a system of record. The data originates in HubSpot. It does not live in the spreadsheet.

Sticky notes, personal CRMs, shared Google Docs with deal lists, Slack channels used as pipeline trackers, none of these have a seat at the table. They don't get a "we'll migrate them later" grace period. They get replaced on day one. The discipline of a single source of truth is hardest to enforce in the first 90 days, when the team is small and informal systems feel faster. That's exactly when it matters most, because the habits formed in the first 90 days are the habits you'll spend the next two years trying to undo.

If it's not in HubSpot, it didn't happen.

The HubSpot Health Check

Nine questions that tell the truth about your portal

  • Have you defined what each lifecycle stage means for your specific motion  (Subscriber, Company, Named Account, AQL, Opportunity, Customer)in writing, agreed by both marketing and sales?
  • Is HubSpot the only system of record for every contact, deal, and customer interaction, with no parallel spreadsheets, personal trackers, or shadow CRMs in use by your team?
  • Do your deal pipeline stages reflect how your company actually sells, or did you accept HubSpot's defaults?
  • Is your HubSpot tracking code live on your website, and can you see visit-to-contact attribution in your reports?
  • Is every AE and SDR's email and calendar connected, and are activities being logged automatically, not manually?
  • Can your CEO open one dashboard and see ARR, pipeline, and closed-won rate without asking anyone to pull a report?
  • Is your ABM target list in HubSpot the same list your sales team is working, or are they maintained separately?
  • Do you have a HubSpot partner or admin who owns the platform, runs a monthly audit, and has an incremental build plan?
  • If your entire GTM team were onboarded tomorrow, could they understand and use your HubSpot setup without a two-hour training session?

Coming Next

The setup is the foundation. The next question is management, how to keep your HubSpot portal clean as the team grows, when to upgrade tiers, how to build a recurring audit process that prevents technical debt from accumulating, and what a mature RevOps operating model looks like inside HubSpot for a team heading into Series B.



HubSpot Should Support the Strategy — Not Become the Strategy

Build HubSpot around your GTM motion, not the other way around.

We help cybersecurity and AI startups design, implement, and optimize HubSpot around lifecycle stages, attribution, reporting, campaigns, and revenue operations — so your systems actually support how you sell.

Explore HubSpot Consulting

Book a Discovery Call

Share this post