HubSpot implementation

HubSpot implementation built around how your team sells

We set up the hubs, properties, pipelines and workflows in your own account, and move your old data in clean.

Scope your HubSpot setup
Trusted by the world's fastest-growing brands

Hubs, editions and seats

Three choices that set what HubSpot can do

HubSpot implementation here means choosing the hubs, editions and seats you need, then building the properties, pipelines and automations inside them. Those three choices come first because they decide which features your team can switch on.

Products and seatsSample accountSales HubIncludedStarterProfessionalEnterpriseWorkflows and sequences includedMarketing Hub · Service HubNot included4 Sales · 1 View-Only

Hubs

HubSpot sells its CRM in hubs, such as Marketing, Sales, Service, Content and Data. Sales Hub adds sequences from Professional. Marketing Hub is where email, forms and campaign workflows sit. Buy the hub that matches the work your team does.

Editions

Each hub comes in Starter, Professional and Enterprise editions. Workflows and sequences sit in Professional and above, and permission sets sit in Enterprise, so the edition follows the features you need.

Seats

A seat decides which tools a person can open, and a permission decides what they can do there. Changing a seat does not change permissions, so we set both and write them down.

Alongside HubSpot’s onboarding

Setup done in your portal, or guided from HubSpot

HubSpot sells its own onboarding for some editions. Check its current list at purchase. Our work runs alongside it, and the two cover different parts of the setup.

HubSpot onboardingHubSpot guides setupImplementation scopeWe build it with you
Who does the workHubSpot specialists guide setup, with sessions run by HubSpotWe configure the portal, and your team approves each stage
Where it is set outIn HubSpot’s own list for the edition you buyIn a written scope you agree before work starts
Your old dataCheck HubSpot’s list for what it says about dataWe map, match and import it, and give you an import log
Your other toolsCheck HubSpot’s list for what it says about integrationsWe build and test the connections, and set the sync rules
What you receiveWhatever HubSpot’s list names for your editionDocuments: blueprint, property list, import log, dashboard list
How do the two fit together?

HubSpot’s onboarding gives your team HubSpot’s own view of its tool. Our scope adds the build for your sales process, the migration and the connections. Read HubSpot’s current onboarding list when you buy, and tell us what it covers, so our scope leaves out what you already have.

What HubSpot says

Six HubSpot facts that shape the setup

Each one comes from HubSpot’s own documentation. The source sits under it.

  1. Lifecycle stagesAutomatic updates

    HubSpot’s automatic lifecycle stage updates only move a record forward.

    The default stages run from Subscriber to Evangelist, with Other at the end. HubSpot says moving a record back means clearing the value first, by hand or with a workflow. So we decide which stage changes are automatic before any workflow is switched on.

  2. SequencesEditions and limits

    A HubSpot sequence holds up to 10 email templates and needs an assigned Sales or Service seat.

    Sequences are in Sales Hub and Service Hub Professional and Enterprise. By default a contact leaves the sequence when they reply or book a meeting from a link in it. Task reminders have no stated cap. We size the cadence to those limits.

  3. WorkflowsRe-enrollment

    HubSpot workflows do not re-enroll a record by default.

    A record already in a workflow cannot enter the same one again until it finishes, and re-enrollment is a setting you turn on. A workflow built for repeat triggers, such as a returning customer, needs that setting chosen on purpose.

  4. Data syncDirection and conflicts

    HubSpot’s data sync lets you set the direction, and which app wins a conflict.

    The direction can be both ways, into HubSpot only, or out of HubSpot only. A separate setting names the default app whose value wins a conflict, unless it has no value, and it does not override the direction. We pick both settings per connected app and write them in the sync map.

  5. Outside formsTracking code

    HubSpot collects submissions from a form it did not build only if its tracking code loads and the form meets its conditions.

    The form needs an email field of the email input type, must not sit in an iframe, and must have no script bound to its submit button. HubSpot says a script conflict or a visitor’s blocker can also stop collection. So we test the form on the live page.

  6. Permission setsEnterprise

    HubSpot permission sets are an Enterprise feature, with up to 100 per account.

    A permission set bundles access that can be assigned to many users, and it overrides an individual’s permissions. On other editions, access is set per user or team. We write the access sheet first, then build it the way your edition allows.

The scope

What a HubSpot implementation produces

The work in six parts, each finishing as something you can open in your portal and keep.

Deal pipeline4 stagesInquiry2$6,000Mesa DentalTax prep$3,600Pier 9 CafePayroll$2,400+ Add dealDiscovery2$12,000Lakeview InnAdvisory$7,200Oakline Co.Tax prep$4,800+ Add deal

Properties and pipelines

We list the properties your team needs on contacts, companies and deals, and drop the ones nobody would maintain. Deal pipelines get stages that match how you sell. You receive: a property list with each property’s type and who fills it in, and the pipelines set up in your portal.

Lifecycle stageForward onlyLeadSQLOpportunityCustomerLead status inside SQLNewOct 3A rep is assigned to the contactConnectedOct 6First call or email reply is loggedMoving back means clearing the value first

Lifecycle stages and lead status

We decide what each lifecycle stage and each lead status means for your team, what moves a record from one to the next, and which moves are automatic. You receive: a stage map with a rule for each move, set up in the portal.

Workflow · Assign leadOnStage becomes SQLLifecycle stageRotate to a repSets contact ownerCreate a call taskTask for the ownerSettingsRe-enrollmentOffOff by defaultOwner rotation4 Sales seats

Workflows and sequences

We build the workflows that assign leads, create tasks and update properties, and the sequences your reps use for follow-up. Re-enrollment and exit rules are chosen on purpose. You receive: a workflow list naming each trigger and action, and the sequences ready to use.

Data sync · Billing appConnectedSync directionTwo-wayInto HubSpotFrom HubSpotDefault app in a conflictHubSpotBilling appunless it has no valueField mappingEmailEmailService lineCustom fieldneeds Data Hub

Forms, tracking and data sync

We put the tracking code on your site, connect your forms so submissions create contacts, and set the sync direction and conflict rule for each connected app. Custom field mapping needs a Data Hub subscription, which we flag in the scope. You receive: a map of the forms and connections, with what each passes across.

Access sheet5 usersRoleSeatViewEditExportOwnerSalesSales reps · 3SalesBookkeeperView-OnlyA seat change leaves permissions as they are

Seats and permissions

We match seats to the work each person does, then set what they can view, edit and export. A bookkeeper or an advisor can view without editing. You receive: an access sheet by person and role, set up in your account in your name.

Import logMatchedRecords imported4,1904,700 rows in510 duplicates mergedOld CRM export3,440 of 3,800Client spreadsheet750 of 900Matched onemaildomainrecord ID

Migration and dashboards

We take your old CRM export and spreadsheets, match on email, company domain or record ID, merge the duplicates and import the rest. Then we build the dashboards your owner reads. You receive: an import log, the dashboards and a short guide for your team.

How it runs

Blueprint the portal, build it, move the data in

You approve the scope before work begins, then each stage before the next, and each one hands you a document to keep.

portal-blueprint.csv

Portal blueprint

Sample · Sample Northfield Accounting
AreaDecisionReason
HubSales Hub, ProfessionalSequences and workflows are in Professional
Seats4 Sales seats, 1 View-OnlyThe bookkeeper reads reports and edits nothing
FormsExisting site forms, tracking code addedNo new hub needed to capture inquiries
DataContacts, companies, dealsMatches how the firm sells today
Left outMarketing Hub, Service HubRevisit when a second team needs them
Five users in total, four with Sales seats and one View-Only. The portal belongs to the firm.

Our stack

The tools we connect to HubSpot

The apps we connect to your HubSpot portal, each of which touches customer data.

HubSpot
Why HubSpot

HubSpot is a CRM with hubs for marketing, sales, service, content and data work, sold in Starter, Professional and Enterprise editions.

How we use it

We work inside your own account, in the hubs and edition you choose, and tell you where an edition limit would get in the way.

CRMMarketing automationAttribution
HubSpotYes
MarketoYes
ZohoYes
SpreadsheetNo

Questions

HubSpot implementation, answered

Start here

Get a HubSpot portal your team will open

Tell us where HubSpot stands today. A written scope and its price come back to you before you commit to anything.