# Apollo.io — Lead Gen & Marketing Plan for Digimetrics.ai
**Prepared 2026-09-01 · grounded in your team's live Apollo account (connected via MCP), not generic product docs**
**Updated 2026-09-01 (same day):** the Context Center rewrite in §2 has been **written live** to the connected Apollo account, confirmed and published (`approved: true`). §1's audit table below describes the *before* state for context; the account itself now reflects Digimetrics.ai, not MediaOne, at the company level. The 5 existing service-line products (Branding, Paid Ads, SEO, Social, Website Design) were deliberately left untouched — see the callout at the end of §2.

---

## 0. TL;DR

Your Apollo account is real, funded, and has 20,000 AI credits and 570 lead credits sitting unused this cycle — but it's currently configured to sell **MediaOne's agency services**, not **Digimetrics.ai the SaaS product**. There's already a campaign literally named "Digimetrics.ai – AI Marketing Tools Outreach," but it's empty, inactive, has no contacts, no connected mailbox, and — most importantly — its AI-personalization context is pointed at the wrong ICP. Nothing here has actually gone out yet, so there's no cleanup required, just a build.

**The one thing to fix before anything else:** add a Digimetrics.ai product profile to the Context Center (§2) and connect a sending mailbox (§4.1). Everything downstream depends on those two.

---

## 1. What's actually in the account right now (live audit)

| Item | Current state |
|---|---|
| **Context Center company name** | "MediaOne" — overview describes the agency (SEO, SEM, social, web design, content, analytics), not a SaaS product |
| **Product profiles configured** | 5: Branding, Paid Ads, SEO, Social Media Marketing, Website Design — all MediaOne **service engagements** sold to businesses who hire MediaOne. Two of them (Paid Ads, SEO) even reference *"Uses Digimetrics.ai to inform bid, audience, and budget adjustments"* — i.e. Digimetrics is mentioned as MediaOne's internal tool, not as the thing being sold |
| **Digimetrics.ai product profile** | **Does not exist.** Nothing in the Context Center targets people who'd buy/subscribe to Digimetrics.ai itself |
| **Existing campaign** | "Digimetrics.ai – AI Marketing Tools Outreach" — 3 steps (Day 0 / +3 / +3), all `manual_email` (human-reviewed sends, not auto-send), **inactive**, **0 contacts added**, **0 emails sent**, created via Apollo's AI assistant (looks auto-generated on account setup, not deliberately built) |
| **Connected sending mailboxes** | **Zero.** `apollo_email_accounts_index` returned an empty list — no inbox is wired up, so nothing can send regardless of campaign state |
| **Website visitor tracker** | A tracker exists (team-scoped, `domain_limit: 3`) but no confirmed tracked domain came back — treat as **not yet installed** on digimetrics.ai or platform.digimetrics.ai |
| **Saved lists/labels** | None |
| **Waterfall enrichment** | **Off** (`waterfall_email_enabled: false`, `waterfall_phone_enabled: false`) — worth confirming this is the intended plan tier, since it caps data quality on harder-to-find contacts |

**Credit balances this cycle (Sept 1 – Oct 1, 2026):**

| Credit type | Available | What it gates |
|---|---|---|
| Lead credits | **570** | Revealing a person's verified email (≈1 credit each) — this is your outbound volume ceiling |
| AI credits | **20,000** | AI-personalized message generation, AI Research — essentially unconstrained at your likely usage |
| Broadcast credits | **50,000** | Sending itself — not your bottleneck |
| Inbound website visitor credits | **20** | Identifying anonymous site visitors — this is a *hard* constraint, see §5.2 |
| Direct dial credits | 0 left (160/160 used) | Phone/dialer — already exhausted for this cycle |
| Export credits | 0 | CSV export currently unavailable |

**Read on this:** you have plenty of runway to *find and email* new leads (570 lead credits, 50,000 broadcast credits), almost unlimited AI personalization, but only 20 credits/month for the website-visitor-ID strategy I flagged last time — that idea still works, it just needs to be aimed only at your highest-intent page, not your whole site (§5.2 explains why).

---

## 2. The core decision: two ICPs, not one

MediaOne and Digimetrics.ai sell to overlapping but distinct people, with a fundamentally different pitch:

| | MediaOne (agency, already configured) | Digimetrics.ai (SaaS, not configured yet) |
|---|---|---|
| **Sells** | "Hire us to do your SEO/ads/social/web/branding for you" | "Use our software to do it yourself, faster" |
| **Buyer's real objection** | "Can I trust an agency with this?" | "Can I trust a tool without an expert running it?" |
| **Price point** | Retainer, likely $2k–10k+/mo | $39+/mo self-serve, or free trial |
| **Sales motion** | Consultative, needs a call | Self-serve signup, PLG |

Running both out of one undifferentiated Context Center will produce messaging that's wrong for whichever one it wasn't written for. **Recommendation: add Digimetrics.ai as its own Product in the Context Center**, sharing the MediaOne company shell (same team, same brand) but with its own overview, pain points, and value prop. Draft below, based on the platform research already done this session and your actual audience pages (business-owners, independent-marketers, marketing-teams, agencies, ecommerce, local-services):

> **Product name:** Digimetrics.ai
> **One-sentence description:** A self-serve SEO, AI-visibility, content, and paid-media toolkit (36 tools) that lets marketers, agencies, and business owners run their own audits, tracking, and optimization without hiring an agency.
> **Pain points:** Agencies are expensive and slow to report back; DIY marketers don't know what to fix first or whether AI answer engines even know their site exists; existing tools show meaningless scores (73/100) instead of plain next steps.
> **Value prop:** Goal-oriented, plain-English findings instead of opaque scores; covers both traditional SEO and AI/GEO visibility in one place; starts free (credits, no card).
> **Call to action:** Start your free audit at platform.digimetrics.ai — see what's actually holding your site back in 90 seconds.

**Status: written and live as of 2026-09-01.** The Context Center's company name, domain, overview, pain points, value proposition, customer profile, call-to-action, and social proof were all updated to describe Digimetrics.ai rather than MediaOne, and published (`approved: true`) — every AI-generated email from this account now personalizes against this profile. Social proof was deliberately left as an honest placeholder ("no verified Digimetrics.ai testimonials yet") rather than reusing MediaOne's three agency testimonials, since those describe hiring MediaOne, not using this tool — swap in real Digimetrics testimonials once you have them.

**Not touched:** the 5 existing product profiles (Branding, Paid Ads, SEO, Social Media Marketing, Website Design) still describe MediaOne's agency services word-for-word and now sit under the renamed "Digimetrics.ai" company header — that will read as inconsistent to anyone who opens the Context Center. Rewriting or removing them is a separate decision (they may still be in active use for MediaOne's own agency outbound elsewhere) — flagged here, not acted on.

---

## 3. Target ICP — six segments, ranked by fit for cold outbound

Pulled from your own audience pages. Ranked by how well cold outbound (vs. content/inbound) tends to work for each:

| Segment | Apollo targeting angle | Cold outbound fit |
|---|---|---|
| **Agencies** | `person_titles`: Account Director, SEO Lead, Head of Digital, Founder/GM at agencies (`organization_num_employees_ranges`: 1–50); `q_organization_keyword_tags`: ["marketing agency", "digital agency", "SEO agency"] | **Best fit** — they buy tools to run client work more efficiently, understand the pitch instantly, highest willingness to pay per-seat |
| **Marketing teams (in-house)** | `person_titles`: Marketing Manager, Head of Marketing, Growth Marketing Manager; `organization_num_employees_ranges`: 51–500 | **Strong fit** — clear budget owner, clear pain (reporting to leadership) |
| **Ecommerce** | `organization_naics_codes` for retail/ecommerce; `person_titles`: Ecommerce Manager, DTC Growth Lead | **Strong fit** — SEO/AI-visibility directly ties to revenue, easy ROI story |
| **Independent marketers / freelancers** | `person_titles`: Freelance Marketer, Marketing Consultant; `organization_num_employees_ranges`: 1–10 | **Moderate** — price-sensitive, but the referral loop (already built into your retention emails) works well here once they're in |
| **Business owners (non-marketer)** | `person_seniorities`: owner, founder; smaller companies, no dedicated marketing hire | **Harder cold** — they don't know they need this until they see the audit; better suited to the website-visitor-ID warm path (§5.2) than cold email |
| **Local services** | `organization_locations` + industry keywords (contractors, clinics, law firms, etc.) | **Hardest cold** — lowest marketing sophistication; likely needs simpler messaging and possibly a different channel (local SEO content, not cold email) |

**Recommendation:** start cold outbound on Agencies and Marketing Teams only. They're the segments most likely to open a cold email about a marketing tool and understand the pitch in one sentence. Prove the motion there before spending lead credits on harder segments.

---

## 4. Setup checklist — clear these before sending anything

### 4.1 Connect a sending mailbox (blocking)
Nothing sends without this. `apollo_email_accounts_index` came back empty. Connect at least one inbox (Google/Microsoft/SMTP) in Apollo before touching the existing campaign.

### 4.2 Build the Digimetrics.ai product profile (blocking for on-message copy)
Add it to the Context Center per §2. Every AI-generated email in Apollo pulls from whichever product profile is attached to the campaign (`dmp_ids` field) — the existing campaign is currently attached to the MediaOne profile, which is why it needs a rebuild, not just an "activate."

### 4.3 Decide: rebuild the existing campaign, or archive and start fresh
The existing "Digimetrics.ai – AI Marketing Tools Outreach" campaign is a reasonable skeleton (3 touches, sensible day-0/+3/+3 spacing, manual-review sends — a safe default for a first campaign) but was drafted against the wrong ICP. Once §2 is done, either regenerate its copy against the new product profile, or archive it and build a new one so there's no confusion about which version is live.

### 4.4 Confirm the waterfall enrichment setting
`waterfall_email_enabled: false` — confirm with billing whether this is expected for your plan tier. If waterfall is available on a higher tier, it materially improves email-find rates on harder contacts (small agencies, local businesses) — relevant if you expand past Agencies/Marketing Teams later.

### 4.5 Install the website visitor tracker
`domain_limit: 3` is already available on your plan, but no domain is confirmed installed. Install on **platform.digimetrics.ai** specifically, and scope intent tracking to `/pricing` and `/account` (upgrade-intent pages) rather than the whole site — see §5.2 for why this matters given only 20 credits/month.

---

## 5. Channel plan

### 5.1 Cold outbound sequences (Agencies + Marketing Teams first)

- **Volume math:** 570 lead credits ÷ ~1 credit per revealed email ≈ **570 new contacts this cycle**. At a conservative 3-touch sequence and Apollo's own safe-sending guidance, that's comfortably within a single mailbox's monthly capacity — no need to buy additional mailboxes yet at this volume (unlike the Smartlead/Instantly/Woodpecker math in the Cold Outbound Stack report, which was sized for 50k–100k emails/month; this is a much smaller, higher-precision motion by comparison).
- **Sequence structure:** keep the existing 3-step, manual-review cadence for the first 2–4 weeks. Manual review costs you time per send but catches AI-personalization mistakes before they go out — worth it until you trust the product-profile copy.
- **Exit criteria to graduate to auto-send:** once you've manually reviewed ~50–100 sends with no copy problems, switch the campaign to automated sending to remove the bottleneck.
- **CTA:** point every sequence at `/audit` (platform.digimetrics.ai/audit) — the same low-friction, no-signup-required entry point already used across the retention email series. Consistency here matters: someone who clicks from a cold email should land somewhere that immediately proves value, not a pricing page.

### 5.2 Website visitor identification (warm path) — sized to reality

Last session's research flagged this as a strong idea in principle: catch anonymous digimetrics.ai visitors before they bounce. The live account check changes the sizing, not the idea — **20 inbound-website-visitor credits/month is small**, likely a handful to a few dozen identified visitors depending on Apollo's per-reveal cost for this feature.

**How to make 20 credits count:**
- Don't track the whole site — track and reveal only visitors who hit `/pricing` or `/account` (people actively evaluating a purchase, not just browsing `/blog`).
- Set `website_visitors_people_intent: ["high"]` when querying, so credits only spend on the visitors Apollo scores as high-intent.
- Treat this as a pilot, not a program, at current credit levels. If it converts well even at ~20/month, that's the business case for upgrading the visitor-credit allowance — cheaper to prove the concept small than to buy more credits speculatively.

### 5.3 What Apollo does *not* replace here
Apollo doesn't do LinkedIn sequencing or multichannel automation the way Lemlist does (it has Prospecting/Gmail/Salesforce browser extensions, not LinkedIn messaging automation) — if multichannel outreach becomes a priority, that's still a gap the Cold Outbound Stack report already covers with Lemlist as the option for that specific need.

### 5.4 Sales-assisted layer for larger agency accounts
Apollo's deal management, meeting scheduler, and call recording/AI insights are available in the account (`conversation_credit: 600` unused) but currently unused. If any inbound agency lead is large enough to warrant a human sales conversation rather than pure self-serve, this is already paid for and sitting idle — worth a light pilot once outbound volume justifies it, not a day-one priority.

---

## 6. How this fits with what's already built

Three pieces of this ecosystem now exist, each owning a different part of the funnel — worth keeping them distinct rather than merging:

| Stage | Owner | Status |
|---|---|---|
| **Pre-signup, cold** | Apollo sequences (this plan) | Not yet live — needs §4 |
| **Pre-signup, warm (visited, didn't convert)** | Apollo website visitor ID (§5.2) | Not yet live — needs §4.5 |
| **Post-signup, trial → paid → retention → win-back** | The 20-email retention series already built for platform.digimetrics.ai (RETENTION-EMAIL-PLAN.md, hosted at digimetrics-retention-emails.pages.dev) | Spec'd and templated, pending Kenneth's implementation |

Apollo's job stops the moment someone signs up — from `TRIAL-01` onward, the retention system takes over. Don't build overlapping logic in both places; the handoff point is the signup event.

---

## 7. Phased rollout

1. **Week 1 — unblock:** connect a mailbox (§4.1), build the Digimetrics.ai product profile (§4.2/§2), decide on the existing campaign (§4.3).
2. **Week 1–2 — pilot list:** run a live Apollo people search against the Agencies segment (§3) to validate real match counts and data quality before committing lead credits at scale — this is the first hands-on step, deliberately not pre-run in this plan so it doesn't burn credits on your behalf without a decision-maker present.
3. **Week 2–3 — first send:** load 50–100 Agency contacts into the rebuilt campaign, manual-review mode, send.
4. **Week 3–4 — read results, expand:** if reply/open rates hold up, expand to Marketing Teams, consider switching to auto-send, install the website visitor tracker.
5. **Month 2:** revisit waterfall enrichment and visitor-credit needs based on real pilot data, decide whether Ecommerce/Independent Marketers are worth adding.

---

## 8. Automating this every month

Two separate things need automation, and only one of them is automatic today:

**Follow-up sends within a sequence — already automatic.** Once a contact is enrolled, Apollo fires each timed step (Day 0 → +3 → +3, etc.) on its own with no manual re-trigger — *if* the step type is `automatic_email`. The current campaign uses `manual_email` steps on purpose (§4.3's safety default: a human reviews each AI-personalized email before it sends). That's a per-send review choice, not a monthly-refresh problem — switch step type once you trust the copy (§5.1's graduation criteria).

**Finding new leads every month — needs a real automation, and I could not confirm Apollo has a no-code version of it from the tools connected here.** The MCP surface exposes atomic actions (search, enrich, add-to-campaign) but nothing that reads as a standing "auto-enroll new matches" rule. Two paths, not mutually exclusive:

1. **Check Apollo's own web app for a saved-search auto-add feature.** Some Apollo plans support saving a search and having new matches auto-flow into a sequence. I can't confirm this is available on your current plan/tier from here — worth Kenneth checking directly in-app before building anything custom.
2. **Guaranteed fallback: a scheduled job Kenneth's Claude Code owns**, since it already has this exact MCP access. Monthly (or weekly, if you want faster iteration), it would: run the saved ICP search filters from §3 → exclude anyone already contacted → bulk-enrich the net-new matches → add them to the live campaign. This is fully buildable today with the tools already connected — no new integration needed, just a schedule.

**Prerequisite for either path:** track "already contacted" in an Apollo List (e.g. "Digimetrics – Contacted 2026") so a monthly re-run pulls net-new people instead of re-emailing the same 570 names every cycle. None of your current lists exist yet (`apollo_labels_index` returned empty) — this needs to be created before the first automated run, not after.

---

## 9. Pricing tiers — volume, and a realistic customer estimate

**Important framing before the numbers:** the customer estimates below are built from published cold-email industry benchmarks, *not* measured Digimetrics data — this account has sent 0 emails so far. Treat them as a planning range, not a forecast. Once the Week 2–3 pilot (§7) produces real open/reply/conversion numbers, replace this table with actual figures — I'll update it the moment you have them.

**How the math works:** 1 lead credit reveals 1 new contact's verified email. Follow-up sends to an already-revealed contact don't cost additional lead credits — they're gated by the daily-send cap instead. So **monthly lead credits ≈ monthly new-leads-fully-sequenced**, as long as the daily-send cap isn't the binding constraint.

| Plan | Cost | Lead credits/mo | Daily send cap | New leads fully sequenced/mo | Binding constraint |
|---|---|---|---|---|---|
| **Free** | $0 | ~75 | 250/day | ~75 | Credits |
| **Basic** | $49/seat/mo | ~2,500 | 250/day (~7,500/mo) | ~2,500 | Credits (send cap nearly maxed too, at a 3-touch sequence) |
| **Professional** | $79/seat/mo | ~4,000 | Unlimited | ~4,000 | Credits only |
| **Organization** | $119/seat/mo (min 3 seats = $357/mo) | ~6,000 | Unlimited | ~6,000 | Credits only |

*(Your live account's current balance — 570 lead credits this cycle — doesn't cleanly match any single public tier's monthly figure above; worth confirming your actual current plan name with Apollo billing rather than assuming from the credit count alone.)*

**Estimated customers/month, using a 0.5%–2% blended sends-to-paying-customer rate** (derived from typical B2B cold email benchmarks: ~2–5% reply rate × ~40% of replies being positive × ~70% of positive replies actually trying the product × ~10–20% trial-to-paid conversion — each of those four numbers is a published industry range, not a Digimetrics-measured one):

| Plan | New leads/mo | Est. customers/mo (low–high) | Tool cost per customer (low–high, excludes labor) |
|---|---|---|---|
| **Free** | ~75 | 0.4 – 1.5 | n/a — too small to be a real channel |
| **Basic** | ~2,500 | 12.5 – 50 | $0.98 – $3.92 |
| **Professional** | ~4,000 | 20 – 80 | $0.99 – $3.95 |
| **Organization** (3 seats) | ~6,000 | 30 – 120 | $2.98 – $11.90 |

**Read on this:** even at the pessimistic end, Basic or Professional pays for itself many times over against Digimetrics' own $39+/mo plans — a single converted customer covers the entire monthly Apollo seat cost. The real decision isn't "can this pay for itself," it's "how much of your total addressable market across the 6 segments in §3 do you want to reach per month" — Professional roughly doubles Basic's volume for an extra $30/mo, which is the more relevant comparison than cost-per-customer alone.

**Recommendation:** start the pilot (§7) on whatever tier the account is currently on — don't upgrade before you have real reply-rate data. Revisit this table with actual numbers after the first 2–4 weeks; if reply/conversion rates land above the low end of the range, Professional becomes an easy case to make with real evidence instead of a benchmark guess.

---

## 10. Open decisions for your team lead

1. ~~Approve the Digimetrics.ai product-profile draft~~ — **done**, live as of 2026-09-01 (§2).
2. **What to do with the 5 MediaOne product profiles** now sitting under the Digimetrics.ai company header (§2 callout) — rewrite, remove, or leave as-is if MediaOne's own outbound still needs them elsewhere.
3. **Which mailbox sends this** — a dedicated Digimetrics.ai-branded inbox, or an existing MediaOne one? Affects deliverability and how recipients perceive the sender.
4. **Rebuild vs. archive the existing empty campaign** (§4.3).
5. **Confirm the waterfall enrichment gap** (§4.4) is expected for your plan, not a misconfiguration.
6. **Budget call:** is the 20-credit/month website-visitor pilot worth upgrading if it proves out, or is Apollo's role staying cold-outbound-only?
7. **Greenlight the monthly automation build** (§8) — Apollo's own saved-search auto-add (if it exists on your plan) vs. a scheduled job Kenneth builds and owns.
8. **Which pricing tier to run on** — stay on the current plan through the pilot (recommended, §9), or commit to Basic/Professional now based on the benchmark estimates alone.

---

## Sources
Live-read from the connected Apollo MCP account on 2026-09-01: Context Center (ICP + 5 product profiles), user profile + credit usage stats, website visitor domain tracker config, existing emailer campaigns, saved labels, connected email accounts. Cross-referenced against `digimetrics.ai` audience pages (business-owners, independent-marketers, marketing-teams, agencies, ecommerce, local-services) and the platform.digimetrics.ai product research already done this session.