Digimetrics.ai — Internal Plan

Apollo.io — Lead Gen & Marketing Plan

Grounded in your team's live, connected Apollo account — not generic product docs. Includes what's actually configured today, a live fix already shipped, and the volume/customer math across pricing tiers.

Prepared 2026-09-01 · Updated same day: the Context Center rewrite in §2 has been written live to the connected Apollo account and published. §1's audit table describes the before state for context — the account itself now reflects Digimetrics.ai, not MediaOne, at the company level.

⭳ Download the plan as Markdown

TL;DR

Your Apollo account is real and funded — 20,000 AI credits, 570 lead credits sitting unused this cycle — but it was configured to sell MediaOne's agency services, not Digimetrics.ai. A campaign literally named "Digimetrics.ai – AI Marketing Tools Outreach" already existed, but empty, inactive, no contacts, no connected mailbox, and personalizing against the wrong ICP. Nothing had gone out yet, so nothing needed undoing — just a build. The Context Center has since been rewritten live to Digimetrics.ai (§2) — the remaining blocker is connecting a sending mailbox (§4.1).

1. What's actually in the account (live audit, before state)

ItemState at time of audit
Context Center company name"MediaOne" — described the agency, not a SaaS product
Product profiles configured5: Branding, Paid Ads, SEO, Social Media Marketing, Website Design — all MediaOne service engagements. Two even reference "Uses Digimetrics.ai to inform bid, audience, and budget adjustments" — Digimetrics as MediaOne's internal tool, not the thing being sold
Digimetrics.ai product profileDid not exist
Existing campaign"Digimetrics.ai – AI Marketing Tools Outreach" — 3 steps (Day 0/+3/+3), all manual_email, inactive, 0 contacts, 0 sent, AI-assistant-generated
Connected sending mailboxesZero — nothing can send regardless of campaign state
Website visitor trackerTracker exists (domain_limit: 3) but no confirmed tracked domain — treat as not installed
Saved lists/labelsNone
Waterfall enrichmentOff (waterfall_email_enabled: false, waterfall_phone_enabled: false) — confirm this matches your plan tier

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

Credit typeAvailableGates
Lead credits570Revealing a verified email (≈1 credit each) — your outbound volume ceiling
AI credits20,000AI-personalized messaging, AI Research — essentially unconstrained
Broadcast credits50,000Sending itself — not your bottleneck
Inbound website visitor credits20Identifying anonymous visitors — a hard constraint, see §5.2
Direct dial credits0 left (160/160 used)Phone/dialer — already exhausted this cycle
Export credits0CSV export currently unavailable
Plenty of runway to find and email new leads (570 lead credits, 50,000 broadcast credits) and almost unlimited AI personalization — but only 20 credits/month for website-visitor ID. That idea still works, it just needs to aim at your highest-intent page, not the whole site (§5.2).

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)Digimetrics.ai (SaaS)
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 pointRetainer, likely $2k–10k+/mo$39+/mo self-serve, or free trial
Sales motionConsultative, needs a callSelf-serve signup, PLG

Running both out of one undifferentiated Context Center produces messaging that's wrong for whichever one it wasn't written for.

Product name: Digimetrics.ai 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 SEO and AI/GEO visibility in one place; starts free. CTA: Start your free audit at platform.digimetrics.ai — see what's holding your site back in 90 seconds.
Live since 2026-09-01

Written and published to the account. Company name, domain, overview, pain points, value prop, customer profile, CTA, and social proof all now describe Digimetrics.ai — every AI-generated email personalizes against this from here on. Social proof was deliberately left as an honest placeholder rather than reusing MediaOne's three agency testimonials, since those describe hiring MediaOne, not using this tool.
Not touched: the 5 existing product profiles (Branding, Paid Ads, SEO, Social, Website Design) still describe MediaOne's services word-for-word and now sit under the renamed "Digimetrics.ai" header — inconsistent if anyone opens the Context Center. Rewriting/removing them is a separate decision, flagged not acted on.

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

SegmentApollo targeting angleFit
AgenciesAccount Director, SEO Lead, Head of Digital, Founder/GM at 1–50-person agencies; keywords: marketing/digital/SEO agencyBest fit
Marketing teams (in-house)Marketing Manager, Head of Marketing, Growth Marketing Manager; 51–500 employeesStrong fit
EcommerceRetail/ecommerce NAICS codes; Ecommerce Manager, DTC Growth LeadStrong fit
Independent marketersFreelance Marketer, Marketing Consultant; 1–10 employeesModerate
Business ownersOwner/founder seniority, no dedicated marketing hireHarder cold — better as warm/visitor-ID
Local servicesLocation + industry keywords (contractors, clinics, law firms)Hardest cold
Start on Agencies and Marketing Teams only. 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 before sending anything

  1. 4.1 Connect a sending mailbox (blocking). Zero connected today — nothing sends regardless of campaign state.
  2. 4.2 Build the Digimetrics.ai product profiledone, live
  3. 4.3 Rebuild vs. archive the existing campaign. Reasonable skeleton (3 touches, sensible spacing, manual-review sends) but drafted against the wrong ICP — regenerate its copy against the new product profile, or archive and build fresh.
  4. 4.4 Confirm the waterfall enrichment setting is expected for your plan tier — it materially improves email-find rates on harder contacts if available on a higher tier.
  5. 4.5 Install the website visitor tracker on platform.digimetrics.ai, scoped to /pricing and /account — not the whole site, given only 20 credits/month.

5. Channel plan

5.1 Cold outbound sequences (Agencies + Marketing Teams first)
5.2 Website visitor identification (warm path) — sized to reality

20 inbound-website-visitor credits/month is small. To make it count: don't track the whole site — only /pricing and /account; filter to Apollo's "high" intent tier; treat this as a pilot, not a program, at current credit levels.

5.3 What Apollo doesn't replace

No LinkedIn sequencing or multichannel automation the way Lemlist does — that gap is still covered by Lemlist in the Cold Outbound Stack report if multichannel becomes a priority.

5.4 Sales-assisted layer for larger agency accounts

Deal management, meeting scheduler, and call recording/AI insights are already paid for (600 unused conversation credits) — worth a light pilot once outbound volume justifies it, not a day-one priority.

6. How this fits with what's already built

StageOwnerStatus
Pre-signup, coldApollo 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-backThe 20-email retention series (RETENTION-EMAIL-PLAN.md, digimetrics-retention-emails.pages.dev)Spec'd and templated, pending 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

01
Week 1 — unblock
Connect a mailbox, build the Digimetrics.ai product profile, decide on the existing campaign.
02
Week 1–2 — pilot list
Run a live Apollo people search against Agencies to validate real match counts and data quality before committing lead credits at scale.
03
Week 2–3 — first send
Load 50–100 Agency contacts into the rebuilt campaign, manual-review mode, send.
04
Week 3–4 — read results, expand
If reply/open rates hold up, expand to Marketing Teams, consider auto-send, install the website visitor tracker.
05
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

Follow-up sends — already automatic. Once enrolled, Apollo fires each timed step on its own, if the step type is automatic_email. The current campaign uses manual_email on purpose (a review safety default) — switch once the copy's trusted.

Finding new leads every month — needs a real automation. The connected tools expose atomic actions (search, enrich, add-to-campaign), not a standing "auto-enroll new matches" rule. Two paths:

  1. Check Apollo's web app for a native saved-search auto-add feature — can't be confirmed from the MCP tools alone.
  2. Guaranteed fallback: a scheduled job (monthly or weekly) that runs the saved ICP filters, excludes already-contacted people, bulk-enriches net-new matches, and adds them to the campaign — fully buildable today with the tools already connected.
Prerequisite either way: track "already contacted" in an Apollo List so a monthly re-run pulls net-new people, not the same 570 names every cycle. No lists exist yet — create one before the first automated run.

9. Pricing tiers — volume & a realistic customer estimate

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 as a planning range, replace with real numbers after the Week 2–3 pilot.

1 lead credit reveals 1 new contact's verified email. Follow-ups to an already-revealed contact don't cost more credits — so monthly lead credits ≈ monthly new-leads-fully-sequenced.

PlanCostLead credits/moDaily send capNew leads/mo
Free$0~75250/day~75
Basic$49/seat/mo~2,500250/day (~7,500/mo)~2,500
Professional$79/seat/mo~4,000Unlimited~4,000
Organization$119/seat/mo (min 3 = $357/mo)~6,000Unlimited~6,000

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

Estimated customers/month (0.5%–2% blended sends-to-customer rate)

PlanNew leads/moEst. customers/moTool cost per customer
Free~750.4 – 1.5n/a — too small
Basic~2,50012.5 – 50$0.98 – $3.92
Professional~4,00020 – 80$0.99 – $3.95
Organization (3 seats)~6,00030 – 120$2.98 – $11.90
Even at the pessimistic end, Basic or Professional pays for itself many times over against Digimetrics' own $39+/mo plans — one converted customer covers the entire monthly Apollo seat cost. The real decision is how much of the addressable market (§3) you want to reach per month, not whether this pays for itself.
Recommendation: start the pilot on whatever tier the account is currently on — don't upgrade before real reply-rate data exists.

10. Open decisions for your team lead

  1. Approve the Digimetrics.ai product-profile draft — done, live as of 2026-09-01
  2. What to do with the 5 MediaOne product profiles now sitting under the Digimetrics.ai header — rewrite, remove, or leave as-is.
  3. Which mailbox sends this — a dedicated Digimetrics.ai-branded inbox, or an existing MediaOne one?
  4. Rebuild vs. archive the existing empty campaign.
  5. Confirm the waterfall enrichment gap is expected for your plan, not a misconfiguration.
  6. Budget call: upgrade the 20-credit/month website-visitor pilot if it proves out, or stay cold-outbound-only?
  7. Greenlight the monthly automation build — native Apollo feature (if it exists on your plan) vs. a scheduled job Kenneth builds.
  8. Which pricing tier to run on — stay through the pilot (recommended), or commit to Basic/Professional now on benchmark estimates alone.