Video summary

How To Get Clients As A Data Analytics Consultant

Main summary

Key takeaways

Business

How data analytics consultants can get clients (business-focused summary)

Main client-acquisition pipelines (where clients come from)

The presenter breaks client sourcing into several repeatable channels, emphasizing you should have at least one (preferably two) reliably full pipelines before obsessing over pricing.

Marketing & branding (content marketing) → inbound

  • Build authority via consistent content (LinkedIn, Substack, YouTube, newsletter).
  • Content helps because it:
    • attracts buyers, and
    • helps you see recurring buyer problems (e.g., Airflow/Data integration pain points).
  • Claim: a small set of content pieces drove ~$500k in sales for the presenter.
  • Practical angle: choose topics that map to recurring buyer problems (e.g., “Airflow is difficult,” “Databricks is difficult”).

Sales (outbound + targeting + scripts)

  • Cold outreach works only with high specificity: target a person + their current tech situation + a tailored story.
  • Example sales messaging:
    • Competing with Fivetran: “reduce your costs,” targeting companies using Fivetran.
    • Poaching/competitive positioning: reaching out when another consulting firm is perceived as expensive/ineffective.
  • Core rule: don’t pitch “I do data consulting.” Instead, lead with something tied to their stack:
    • “I see you use Snowflake—how are your Snowflake costs?”
    • “You use Airflow—do you need an audit/fix?”

Agencies / third-party marketplaces (market-makers)

  • Examples: Upwork (race-to-the-bottom risk) and other higher-paying agency models (typically taking a cut, sometimes ~15%).
  • Strategy note: partner with agents who still meet your rate; otherwise avoid.

Networking (events + follow-up + warm intros)

  • Event networking should be goal-driven:
    • Aim to talk to 5–10 people, then follow up with 3.
  • LinkedIn networking (warm lead approach):
    • If a mutual connection is interacting with your target prospect, ask for an intro.

Vendor partnerships (Snowflake/Databricks/Looker SIs)

  • Vendors often prefer partners/implementation firms; consulting doesn’t align with their core SaaS revenue narrative.
  • Two-way street: you must sometimes help send them business, not just expect referrals.
  • Operational principle: stay top-of-mind with the vendor’s account exec.
    • After closing a deal, keep working with the sales team: co-market, write articles, help expand scope.
  • Tie-in: when the vendor needs an implementation partner, they’ll remember you.

Referrals (after you deliver)

  • Referral flywheel: one client → leads to next client.
  • Concept cited via “McKinsey “way” style” framing; presenter also notes a guest/creator example.

Professional communities (paid communities)

  • Example: a paid professional club/community where members share services and leads (not quantified, but mentioned as another channel).

Sequencing priorities (what to do first)

The presenter recommends an order of operations:

  1. Figure out client acquisition
  2. Deliver value effectively
  3. Then focus heavily on pricing

Why: if your pipeline isn’t generating enough interest, pricing experimentation is premature. Also, once inbound volume supports it, you should be able to occasionally say “no” to small-budget clients.

Target timelines, project sizing, and “minimum viable revenue”

Business goals & time horizons mentioned

  • Long-term aspiration: final goal target of ~$500k (framed as far away but achievable).
  • Concrete year math example:
    • $100k/year ≈ 8.3k/month equivalent (as stated).
  • Pipeline health requirement:
    • For a 3-month minimum runway, the presenter frames the threshold around roughly “10k” (exact unit unclear), while stressing the need to keep pipelines full enough to reach the 3-month minimum.

Engagement models and durations

  • Minimum engagement length: 3 months
  • Common average: ~6 months
  • High-end for larger clients: 6 months to 1 year (or “a year plus”)
  • Discovery projects (foot-in-the-door):
    • Duration: ~1 month
    • Price point: around $10k
    • Purpose: smaller commitment when clients avoid bigger contracts (e.g., avoiding $60k–$200k for 6 months).

Concrete consulting service categories (what to sell)

The presenter lists common data/analytics consulting project types:

  • Migrations
    • On-prem → cloud, and between modern stacks:
      • Snowflake ↔ Databricks
      • Redshift ↔ Databricks
      • Informatica → Airflow (as an example)
  • “Key person dependency” fixes
    • Coverage when a key engineer/team member quits or work becomes fragile over time.
  • Niche tooling problems
    • Helping with Airflow setup/fixes
    • Databricks support after complexity reveals itself
  • Complete data stack setups
    • From raw data → final product, often including dashboards.
  • Dashboarding + BI
    • Positioned as an “easy first sell” and commonly expected even if not in the contract.

KPIs / metrics explicitly mentioned (limited)

No formal KPI framework (e.g., CAC/LTV/churn) is provided. The few concrete sales-related figures/metrics stated include:

  • ~$500k attributed to only 3–4 content pieces (presenter’s newsletter/content).
  • ~15% typical cut for some agency/third-party intermediaries.
  • Cold-email conversion hint:
    • “5%” of times it lands can lead to a sale (presented as a small landing→sale path; not fully defined as CAC, lead-to-opportunity, etc.).
  • Revenue/timing targets:
    • $100k/year math example
    • 3-month minimum and an approximately “10k” threshold (context suggests monthly revenue needed to sustain work).

Actionable recommendations / playbook takeaways

  • Choose a narrow target + situation for outbound
    • Don’t sell “data consulting”; sell a specific problem tied to their stack (Snowflake costs, Airflow audit, etc.).
  • Make content problem-led
    • Write about pain points you see repeatedly while doing the work (Airflow, Databricks difficulty).
  • Build pipeline diversity, but don’t over-diversify early
    • Have at least 1–2 pipelines performing reliably.
  • Use smaller “discovery” engagements to reduce buyer risk
    • ~1-month / ~$10k audit or recommendation projects → larger implementation later.
  • Vendor partnerships require operational follow-through
    • After giving them clients, keep collaborating with their account exec (articles, expanding engagement) to stay top-of-mind.
  • Networking is a numbers-and-follow-up game
    • Talk to 5–10, follow up with 3; don’t passively hope.
  • Don’t ignore low-budget prospects—enforce fit
    • You can only say “no” once inbound volume is sufficient.

Case examples cited

  • Losing a bid due to a client finding a blog article

    • Example: migration from Qlik (Qlik Sense/View) to Tableau.
    • Client chose another firm because they found an article that “100% spoke to the problem,” reducing perceived risk.
    • Lesson: content marketing can either win or lose deals; buyers use it to reduce risk and validate fit.

  • Content/SEO habit

    • Example: when someone searches “best ETL/ELT tool,” the first result is often chosen even if the articles seem generic—buyers default to Google and click early results.

Presenter / sources mentioned

  • Presenter: “the Seattle Data Guy” (also referenced by name as Jeff in places)
  • Sally McKinsey Way (mentioned as “the McKinsey way” as a referral/expansion example)
  • Adam (guest video creator; mentioned as discussing referral flywheel)
  • Chad Sanderson (LinkedIn/content example leading to a startup)
  • Alex the Analyst / Alex Friedberg (LinkedIn content style example)
  • Jeff / Chad / Adam are referenced as separate people throughout (context: guest videos/community examples)

Technical brands referenced

Airflow, Snowflake, Databricks, Looker, Fivetran, Tableau, Qlik, Redshift, Informatica, Power BI, Postgres

Original video