Video summary

【第2回】HubSpotとの戦い方

Main summary

Key takeaways

Business

Overview: “How to deal with HubSpot” (vs. competitors)

The speaker argues that while pricing and features may look similar across tools, the real difference is in operating philosophy and support model—especially around helping customers achieve outcomes (not just using the software).

Key differences (strategy + philosophy)

1) “Support what the customer already did” vs. “support the customer to achieve goals”

HubSpot-style approach (as described)

  • Supports execution based on what the customer asks for (e.g., “make this page/button/image,” “show how to do it with these functions”).
  • Emphasis is on enabling use of features rather than actively steering toward business outcomes.
  • If the requested page doesn’t make sense for the goal, the system may effectively stop helping or won’t drive the right outcome.

Speaker’s preferred approach (as described)

  • Helps customers achieve their business objectives.
  • Supports both implementation and consulting, including decision guidance on what to build and why.
  • Stronger outcomes orientation, framed as leading toward orders by aligning marketing and sales execution.

2) Blog-first inbound vs. B2B site-first positioning

HubSpot-style concept (as described)

  • Leans toward inbound marketing via blogs (blog-focused proposals).

Alternative concept (speaker’s stance)

  • Blog can be included, but the emphasis is on:
    • Proper brand/site creation that promotes the company’s service
    • Producing results through ongoing execution (“running …” appears garbled, but the intent is ongoing operation)

Support model / operations playbook

3) Types of proposals: partner implementation vs. direct enablement + consulting

HubSpot-style (as described)

  • Two main proposal modes:
    • Through a partner (implementation/consulting is limited or varies)
    • Directly from the vendor (described as mostly technical support: migration, “how to use it,” navigation/tree explanations)
  • The speaker claims technical-only support often fails unless the client already has the capability and commitment to implement correctly.

Speaker’s approach (as described)

  • Provides both implementation + consulting.
  • Resolves internal misalignment where the client’s marketing and sales teams are separate by:
    • helping sales/marketing teams “acquire and move in”
    • nurturing leads
    • guiding toward orders (pipeline conversion)

4) Customer enablement limitations (important “when it won’t work” criteria)

The speaker highlights cases where this kind of support won’t work well:

  • If learning content is comprehensive but only in English, non-English-speaking teams may struggle to fully adopt using help pages alone.
  • If success requires WordPress/design/engineering skills (e.g., careful handling and stylesheets), teams without those capabilities may not execute effectively.
  • Fit rule (stated clearly):
    • If objectives are not clearly defined, this support “is not for you,” and teams that don’t know where to start won’t get results.

Concrete operating guidance (actionable recommendations)

  • When migration/replacement is needed

    • If you “go in the wrong direction,” it becomes hard to recover with replacement (the wording is garbled, but the message is that misalignment makes change difficult).
    • If direction is wrong, there are still opportunities to propose improvements—coordinate exploration with marketing stakeholders.

  • Before adopting tools

    • Ensure you have:
      • defined goals
      • the capability to execute (or the right partner/consulting support)
      • sufficient language/enablement access

Metrics / KPIs / targets mentioned

  • No explicit KPI targets (e.g., CAC/LTV/churn) are provided.
  • One cost comparison is mentioned (approximate):
    • Many customers spend ~600,000 yen/month more (compared to the speaker’s referenced option), but the speaker argues the difference is mainly philosophy/support rather than cost.
  • The speaker emphasizes volume of prospects as a driver (“process” and “number of prospects is large”), but without measurable funnel KPIs.

Frameworks / playbooks

No formal named frameworks (e.g., OKRs, SWOT, GTM) are explicitly stated. The talk describes an implied operating model:

  • Outcome-first adoption model

    • Implementation + consulting
    • Marketing/sales alignment
    • Lead nurturing → order conversion

  • Fit-for-capability check

    • Ensure clear objectives + team execution skills + accessible enablement language

Presenters / sources

  • Presenter (implied): The speaker speaking in the subtitles (name not provided; ends with “Pub Spot Patty” / “HubSpot Patty,” which appears to be a label rather than a clearly verified name).

Original video