End-Client Campaign — Build Spec

Aim the existing outreach machine at end-clients (companies that need the dashboards themselves), not agencies. Same infrastructure; different list, message, and landing.

1. Apollo ICP filter

The qualification logic inverts from the agency campaign. For agencies you filtered for BI/Power-BI org keywords. End-clients aren’t “Power BI companies” — you can’t see their reporting pain in Apollo tags. So you target by proxy (size + industry + pain-owning role) and let the email do the final qualifying.

person_titles:
  ["head of finance","finance director","cfo","head of operations","coo",
   "controller","head of data","head of analytics","bi manager","managing director"]

person_locations       : ["Netherlands","Sweden","Ireland"]   # legal-for-cold only
organization_locations  : ["Netherlands","Sweden","Ireland"]
# Germany end-clients = LinkedIn, NOT email (UWG §7). Same routing as before — it's
# about the RECIPIENT's country, and that doesn't change because the buyer changed.

organization_num_employees_ranges: ["51,200","201,500"]
# Bigger than the agency filter. Below ~50 employees there's rarely reporting pain or
# budget; above ~500 they usually have an in-house BI team and won't hire a freelancer.

contact_email_status: ["verified"]

Where these titles come from

Not a data source — my judgment about who owns the reporting pain and can authorise spend at a mid-size company with no dedicated BI team. At that size, reporting lives with Finance and Operations, so those leaders feel it and hold budget. “Head of Data / BI Manager” is in for the minority that have one — where they exist, they’re often the buyer.

Fuller title menu (widen or narrow from here)

Apollo matches title strings loosely (partial, case-insensitive), so a short list still catches variants. By function:

  • Finance (primary): CFO, Finance Director, Head of Finance, Financial Controller, Controller, VP Finance, Head of FP&A
  • Operations: COO, Operations Director, Head of Operations, VP Operations
  • Data / analytics (if any): Head of Data, Head of Analytics, BI Manager, Data Manager, Head of BI, Analytics Lead
  • Executive / owner (smaller end): Managing Director, CEO, Founder, Owner, General Manager
  • Sector-specific reporting owners: Head of Commercial, Head of Revenue, Head of Supply Chain (logistics), Head of Category (retail / e-comm)

Keep it 8–10 titles per send — more and the pool balloons with weak fits. Start Finance-led; widen to Ops/Data only if volume runs short.

Buying signals — the real answer to “how do I find pain”

Title + size + geo is only the floor. These Apollo dimensions proxy for active reporting pain and budget, and each roughly doubles relevance. Ranked:

  1. Hiring an analyst. A live posting for “Data Analyst”, “BI Analyst” or “Financial Analyst” is the strongest signal there is — pain and budget, right now. (Apollo organization job-postings filter.)
  2. Recent funding. Freshly raised companies professionalise reporting within months and have cash. (Funding-stage / last-funding-date filter.)
  3. Fast headcount growth. They outgrow Excel reporting; +20–30%/yr is the trigger zone. (Headcount-growth filter.)
  4. Tech stack. Data-heavy systems with no BI tool = greenfield: uses Dynamics / SAP / NetSuite / HubSpot / Salesforce (data sits there, unreported), or Microsoft 365 / Azure (Power BI adopts naturally) — and not already Tableau / Qlik / Looker. (Technographic filter.)
  5. Revenue band as a budget proxy (e.g. €5–100M).

Which of these your account exposes depends on your Apollo plan tier — Basic may gate funding / technographic / job-posting / intent filters. When the API reconnects I’ll check what’s actually available and build the exact query. Highest-yield combination: mid-size + Finance title + hiring-an-analyst — that’s a warm-ish list wearing a cold disguise.

No org-keyword filter. Instead, qualify at reveal-time by excluding the wrong firms — drop anything whose keywords say consulting / agency / BI-services (those are the agency campaign, or competitors), and drop obvious non-fits (pure retail POS, staffing, etc.). Prioritise industries where you already have proof: e-commerce / retail, logistics, manufacturing, financial services, SaaS.

Reality check: end-client precision will be lower than your agency batches (you’re filtering on proxies, not confirmable signals). Expect to disqualify more at reveal. That’s fine — the email names a specific pain, so wrong-fits self-select out by ignoring it.

2. Cold email (end-client)

Message-matched to the dashboards page. Same structure that worked for the UK template, retargeted from “overflow capacity” to “your reporting pain.”

Subject (rotate to test): - Monthly reporting still in Excel? - [Company]'s monthly numbers - One view instead of five spreadsheets

Body:

Hi [Name],

I work with mid-size [industry] companies in the EU that have plenty of data but no
single, reliable view of it — the monthly numbers get rebuilt in Excel, and different
teams end up quoting different figures.

I build one live Power BI view that pulls from your existing systems, so the numbers
are current and everyone works from the same picture. Remote, in English, invoiced
from Germany on a cross-border B2B basis.

A few examples and how I work: frequentist.org/services/business-dashboards?c=ec-dash1

If monthly reporting is eating time you'd rather spend elsewhere, reply with a line
about your current setup and I'll tell you what I'd do with it — no charge.

Aleksei Prishchepo
Freelance BI & Analytics · Power BI · SQL · R
frequentist.org

Notes: - Body link carries ?c=ec-dash1 for attribution (bare link in signature). - The ask is a reply about their setup, not a booked meeting — matched to cold readiness. The free “what I’d do with it” is the cheapest possible yes and doubles as a qualification call. - Confirm the real dashboards-page URL slug and swap it into the link.

3. Dashboards page edits

Ranked by leverage for cold end-client traffic.

(a) Quantified proof — biggest lever, currently missing

Your three reference projects describe features (“An interactive BI dashboard combining customer RFM segmentation, ABC/XYZ…”). Cold visitors care what it did. Rewrite each as an outcome. Structure:

[What it replaced / the before-state] → [the after-state]. One line of method.

Fill the brackets with YOUR REAL figures — do not invent numbers.

Examples of the shape (numbers are placeholders for you to replace or delete):

  • E-Commerce Analytics Dashboard — “Replaced [N] separate spreadsheets with one live view of revenue, cohorts and product mix; the team now sees [daily/weekly] numbers without a manual rebuild. RFM + ABC/XYZ segmentation and R revenue forecasting, embedded in Power BI.”

  • Consumer Financial Complaints Dashboard — “[If a client project: the outcome + a real figure.] [If a public-data demo: say so honestly — ‘A worked example on public CFPB data showing trend forecasting and causal factor analysis in Power BI + R.’]”

  • Credit Risk Simulation Dashboard — “Borrower-level credit-risk calculator with portfolio-level simulation — [what decision it supports / what it replaced].”

Honesty flag: if these three are demos on public data rather than paid client work, frame them as demos (that’s fine and still shows skill) — but then your single highest- value addition is one real, anonymised client outcome (“a Berlin e-commerce company”, one true number you actually delivered). Cold end-clients weight one real result over three polished demos. Only you have that number.

(b) Lead with the outcome, not the category

Keep the <h1> “Business Dashboards & Reporting” (nav/SEO), but sharpen the subhead from a description into a hook. Options:

  • “Stop rebuilding the same reports in Excel every month — one live Power BI view your team actually trusts.”
  • “One live view of the numbers that matter — so decisions rest on current facts, not last month’s snapshot.”

(The second reuses your own strong opening line, which is currently buried below the fold.)

(c) Lighter primary CTA

The current “Request a project & book a meeting” (5 fields + calendar redirect) assumes high intent a first-touch cold visitor rarely has. Add a low-friction path ABOVE the form, keep the form as the high-intent option:

Not ready to scope a project? Send me your current reporting setup — aleksei@frequentist.org — and I’ll tell you what I’d do with it. No charge, no pitch.

This mirrors the email’s ask, so email → page → CTA all say the same thing.

(d) Pricing — keep it, check the order

Unlike the bench page, keep €2,000 / €4,500 visible: end-clients evaluating a project want price signals and it filters tire-kickers. Just make sure the outcome and proof (section a) land above the pricing block, so they’re sold before they see the number.

4. Send allocation (this week, ~250 cap)

  • 50–70 → agencies, strict filter (Power BI in stack; small agencies that can’t justify a permanent senior hire).
  • Remainder (~180) → end-clients, NL/SE/IE, filter above.
  • Ramp the daily rate up gradually (+10/day/week) — don’t jump straight to 50/day on the young domain while its reputation is still building.
  • Germany (both audiences) stays LinkedIn-only.
Back to top