HubSpot Agency Partner Certification cheat sheet

Inbound methodology has four stages: Attract, Engage, Delight; the flywheel replaces the funnel because customer momentum drives referrals and word of mouth.

Buyer's journey stages are Awareness, Consideration, Decision; content is mapped to each stage, not to the sales pipeline.

A buyer persona is a semi-fictional representation of the ideal customer built from research, not a demographic guess.

Lead = contact who converted on a form; MQL = marketing qualified lead by fit and engagement; SQL = sales accepted and qualified.

Content offers should be gated only when the value justifies friction; top-of-funnel blog content is typically ungated.

Inbound success is measured with lifecycle-stage conversion rates, not raw traffic; a common funnel check is visitor-to-lead, lead-to-MQL, MQL-to-customer.

A call-to-action (CTA) is a single specific next step; a landing page should have one conversion goal and minimal navigation.

Lead nurturing is a sequence of relevant touches that moves a contact toward the next lifecycle stage; it is not a mass newsletter.

Attribution matters: first-touch credits discovery, last-touch credits conversion, multi-touch distributes credit; choose a model and state it explicitly.

Core hubs: Marketing Hub, Sales Hub, Service Hub, Content Hub (CMS), Operations Hub; each has tiered editions (Starter/Professional/Enterprise).

Objects: Contacts, Companies, Deals, Tickets, Products, Line Items, plus custom objects available at higher tiers.

Properties have a type (string, number, date, enumeration, etc.) and a field type; property history and calculated properties are edition-gated.

Workflows automate actions on objects based on enrollment triggers and filters; sequences are one-to-one sales email automation limited to Sales Hub seats.

Lists are static or active; active lists recalculate on membership criteria and power segmentation and workflow enrollment.

Forms, CTAs, landing pages, and emails live in Marketing Hub; email send limits and A/B testing depend on edition and contact tier.

Pipelines and deal stages are configurable per object; stage properties and required fields control data quality at each stage.

The API and integrations use OAuth for apps and private app tokens for single-account access; sync behavior differs between native integrations and custom builds.

Sandbox accounts are available on Enterprise tiers for testing workflows and integrations without touching production data.

A standard onboarding sequence: kickoff, access and audit, goal alignment, technical setup, campaign launch, review cadence.

Access checklist: Super Admin or equivalent, portal ID, domain/DNS control, analytics access, ad accounts, and CRM data export.

Technical audit items: tracking code, forms, email authentication (SPF, DKIM, DMARC), domain configuration, and duplicate records.

Data migration requires field mapping, deduplication rules, and a documented decision on which lifecycle stages and owners carry over.

Define success metrics before launch; baseline historical performance so post-launch reporting has a comparison point.

Roles must be explicit: who owns content, who owns workflows, who approves sends, and who holds billing and admin rights.

A launch checklist gates go-live: tracking verified, unsubscribe and consent settings correct, test sends, and rollback plan.

Onboarding documentation should include an access matrix, a RACI-style ownership list, and a change log for configuration.

Scope categories: strategy, implementation/build, content production, campaign management, reporting, and training.

Retainer models: hours-based, deliverable-based, and performance-based; each shifts risk between agency and client.

A scope of work should state deliverables, cadence, exclusions, revision limits, and client responsibilities.

Change control: out-of-scope requests are logged, estimated, and approved before work begins.

Hourly retainers require time tracking and a rollover policy; unused hours either expire or roll over per the contract.

Project vs retainer: projects have a defined end state; retainers fund ongoing capacity and continuous optimization.

Pricing inputs include hours, blended rate, tooling costs, and margin target; the blended rate is total cost divided by billable hours.

Reporting cadence and KPIs belong in the contract so performance reviews do not become scope disputes.

Offboarding terms should cover asset ownership, account transfer, and data export obligations.

The Solutions Partner Program is HubSpot's partner network; tiers reflect demonstrated client results and platform usage.

Tier progression generally runs from entry level upward through higher tiers; each tier unlocks benefits such as listings, support, and margin.

Tier criteria are based on metrics such as managed client count, software attach, and customer retention or satisfaction, not on tenure alone.

Partner benefits commonly include revenue share or margin on sold software, lead referrals, and access to partner enablement resources.

Program requirements and tier thresholds change; verify current criteria in the partner portal rather than relying on memorized numbers.

App Partner and Solutions Partner designations differ; app partners build integrations, solutions partners deliver services.

Partner directory listings and badges are earned through tier status and can be used in marketing within program brand guidelines.

Co-selling with HubSpot sales requires registering deals and meeting program eligibility rules.