IMPLEMENT · Chapter 4

The first 30 days. Week by week.

The four-week plan I run for SMB clients. Each week has one goal and a small ship list. Resist the urge to do everything at once — by day 30 you want a working foundation, not 40 percent of a finished product.

Week 1 — Foundation

Goal: HubSpot can identify who a contact is and where they came from.

Connect the corporate domain, set up the tracking code, and verify a test pageview lands in HubSpot.
Import the existing contact list — clean duplicates first, then map company associations.
Define the deal pipeline: stages, probabilities, and the entry/exit criteria for each stage in plain English.
Set the lifecycle stages your team actually uses (Lead, MQL, SQL, Customer). Trim the defaults you do not.

Week 2 — Capture

Goal: Every inbound channel pushes a lead into HubSpot with attribution attached.

Install one form on the highest-traffic page. Use HubSpot's native form, not a marketplace plugin — the attribution chain breaks otherwise.
Wire calendar links (HubSpot Meetings) for the founder and any AE. Replace Calendly links sitewide.
Connect Gmail or Outlook inbox to HubSpot so reply tracking is automatic.
Set up the first lead-routing workflow: new form submission → assign owner → notify in Slack/Teams.

Week 3 — Activate

Goal: First nurture sequence sends, first meeting booked through HubSpot.

Write three nurture emails for the highest-intent form (the demo or contact form, not the newsletter).
Ship the sequence and route enrollment from the form submission workflow.
Build one Sales sequence for outbound that has a real human in step 3, not just AI follow-ups.
Document the contact ownership rules so reps do not poach each other's records.

Week 4 — Measure

Goal: A founder dashboard exists and shows truth on Monday morning.

Build the four-report founder dashboard (pipeline, source, lifecycle conversion, deal velocity). Detail on the reporting page.
Schedule the dashboard for Monday 7 AM delivery to the founder's inbox.
Run a data-quality audit: required properties on contacts, companies, and deals. Fill the gaps.
Document everything in a one-page operations doc the team will actually read.

Best for

Founders setting up HubSpot themselves for the first time.
First marketing hires inheriting an account that was bought but never configured.
Operations leads consolidating Mailchimp + Pipedrive + Calendly into one platform.

Fails when

Nobody is willing to own data quality.
Sales reps refuse to update deal stages in the new pipeline.
Imports happen before the lifecycle stage and required-property model is decided.

Verify before

Day 30 checkpoint: pipeline is populated, one sequence has sent, dashboard delivers Monday morning.
All forms route through HubSpot — no marketplace plugins that break attribution.
Required properties are filled on at least 90 percent of contacts.

When to spend on outside help

Three scenarios where I do recommend bringing in a Solutions Partner or an outside consultant rather than DIY:

Salesforce migration. Data model differences, sync between the two during cutover, and the politics of who controls the source-of-truth contact record make this a multi-week project.
Custom-object data model. If your business needs objects beyond Contact / Company / Deal / Ticket (projects, memberships, equipment), the architecture decision shapes every downstream report and workflow.
Multi-Hub Enterprise rollout. Enterprise permissions, sandboxes, partitioning, and the cross-Hub workflow choices are where outside experience saves quarters.

Frequently asked

Can I onboard HubSpot myself without paying the official fee?

Yes, for the standard 5 to 50 person SMB setup on Starter or Professional. HubSpot Academy, the Knowledge Base, and a disciplined 30-day plan cover what the official onboarding delivers. Pay for outside help (Solutions Partner or a consultant) only when the implementation involves a Salesforce migration, custom-object data model, or multi-Hub Enterprise rollout.

What is the single most common onboarding mistake?

Importing the contact list before defining lifecycle stages, lead-source taxonomy, and required properties. The data goes in dirty, and every report and workflow built on top of it inherits that dirt. Two months later you rebuild the foundation. Spend week one on the data model, not on imports.

Should I migrate from Mailchimp / ActiveCampaign / Pipedrive on day one?

No. Run them in parallel for the first 30 days. Use HubSpot to capture the new pipeline and learn the platform, while the old tools continue to do their job for legacy data. Switching over on day one creates a single-point-of-failure migration with no rollback.

How many people from my team need to be involved?

Three roles, at minimum. An owner (usually a marketer or operations lead) who actually configures the platform. A sales champion who commits to using the new pipeline. A founder/executive who signs off on the deal-stage model and dashboard set. Implementations without an executive sponsor stall by week three.

What about the tracking code, GDPR consent, and analytics?

Install the tracking code in week one and verify a test pageview lands in HubSpot. If you operate in the EU or with EU customers, configure HubSpot's consent banner (or your own CMP) before turning on cookie tracking. In Canada (CASL) and the US, the consent model is lighter but still requires unsubscribe and contact information in every marketing email.