Where you stand
Today.
12345or arrow keys
Consumed
286k/ 310k
92.3% of quarterly budget
Remaining
24kcredits
13 days to refresh
Avg pace YTQ
3,714/ day
vs 3,370 plan
Bridge pace
1,850/ day
through May 28
Where credits went this quarter
The May 8 conversation surfaced four major credit lines. The biggest pull came from international dialing, especially Middle East voicemails. The second-largest came from enriching contact data for sequences that didn't convert because of email infrastructure issues.
| International dialing | Heavy use of mobile waterfall + voicemails, primarily in the Middle East. Nordic dialing paused to preserve runway. Largest credit line |
| Voicemail handling | International voicemails consumed credits without producing connects. We'll fix this with dialer-side VM controls in Week 1. |
| Email enrichment | 50,000+ emails enriched and sent across sequences. Reply rates near zero, indicating an email infrastructure issue rather than a credit issue. |
| Waterfall enrichment | Active on lists. Powerful when used surgically. Expensive when run broadly. |
Note on data sources. Quarterly credit consumption figures referenced here come from your team's reports on the May 8 call. We're validating these against Apollo's product analytics before locking in the per-line breakdown above. If the validated numbers differ, we'll update the plan together.
The pace that works
Target.
A 310,000 credit quarter, run on a steady weekly cadence, gives your team three full months of outreach without late-quarter scrambles. The math is simple. The discipline is the change.
Quarter base
310kcredits
92 days
Daily pace
3,370/ day
total team
Weekly ceiling
24k/ week
includes weekend pad
Monthly target
103k/ month
~33% of quarter
Per-user math
With 8 enabled users, the team-level numbers break down to a manageable per-rep allocation. Reps see the budget in terms of a week, not a quarter.
Per user · daily
421credits
Across 8 users
Per user · weekly
3,000credits
The number reps track
Per user · monthly
12,900credits
Rolls up to team plan
How to split the budget
A starting allocation across your four main credit lines, sized for an outbound-heavy team that runs sequences, workflows, waterfall, and dialer in parallel. We refine these percentages in Week 1 based on your actual usage.
Mobile waterfall
35%
~36k / mo
Email enrichment
25%
~26k / mo
Direct dials & general phones
20%
~21k / mo
Targeted full waterfall
15%
~15k / mo
Buffer for the unexpected
5%
~5k / mo
Top-off buffer. Apollo is finalizing a credit refresh of approximately 50,000 credits to land alongside your May 28 quarterly reset. This plan holds that top-off as a protective reserve, not Month 1 spend. If a week runs hot, we draw from the reserve. If the quarter holds steady, the reserve rolls forward as expansion runway.
May 28 to Aug 28
Three months, three milestones.
Each month has a single job. Stabilize. Optimize. Sustain. By the August renewal, your team has a quarter of clean data to point to and a rhythm worth keeping.
Month 01
Stabilize
May 28 → Jun 27
≤ 103k credits
Daily ceiling 4,500 · Weekly ceiling 25k
This month we:
- Run pre-launch DNC scrub on every new sequence.
- Fix mailbox infrastructure: connect parked domains, complete warmup on any new mailboxes.
- Configure dialer to skip voicemails on international mobiles.
- Set per-user weekly budget visible to each rep.
- Hold weekly 30-min check-in with Apollo.
Success looks like
Under 100k consumed. DNC scrub in workflow. Mailbox bounce rate under 3%.
Month 02
Optimize
Jun 28 → Jul 27
≤ 103k credits
Daily ceiling 4,000 · Weekly ceiling 24k
This month we:
- Tune the allocation percentages based on Month 1 actuals.
- Activate AI messaging in your Content Center for sequence content quality.
- Restrict waterfall to validated, engaged lists only.
- Double down on the channel returning the best reply or connect rate.
- Shift to bi-weekly check-ins with Apollo.
Success looks like
Pattern proven. Apollo-sourced meetings reappearing. Allocation tuned to actuals.
Month 03
Sustain
Jul 28 → Aug 27
≤ 103k credits
Daily ceiling 3,800 · Weekly ceiling 23.5k
This month we:
- Lock in the rhythms that work. Document what changed.
- Build the renewal value story from a full quarter of clean data.
- Identify expansion plays the team has earned.
- Hold a final review meeting one week before renewal.
Success looks like
Clean quarter. No surprise burn events. Strong story going into Aug 28.
What your team runs
Playbook.
Five plays the team owns. Each one prevents a specific credit drain we identified together. Each one becomes part of the weekly rhythm.
Play 01
Pre-sequence checklist
Run before launching any new sequence.
Steps
- Scrub the contact list against your DNC list.
- Confirm minimum 200 validated emails before launch.
- Verify mailbox warmup status: minimum two weeks active before send.
- Cap sends to 50 per mailbox per day.
- Set A/B subject lines on the first two steps.
Why it saves credits: prevents enrichment spend on un-mailable contacts and avoids spam-trap mailbox blocks that waste future sends.
Play 02
Dialer hygiene
Configure once. Audit weekly.
Steps
- Set voicemail handling on international mobiles to skip or no-credit-charge.
- Use phone-only filtered views before pulling mobile waterfall enrichment.
- Cap max attempts per contact at 3.
- Tag and exclude HQ-only numbers from outbound cadences.
- Run a weekly audit of dial outcomes vs credits spent.
Why it saves credits: international voicemails were the highest unit-cost drain on the prior quarter. Dialer-side controls cut this at the source.
Play 03
Waterfall enrichment, used surgically
For high-priority targets only.
Steps
- Run first-pass enrichment first. Waterfall only the no-result contacts.
- Set a credit cap per list run (suggested: 1,000 credits max).
- Reserve full waterfall for accounts with an active engagement signal or pipeline tag.
- Review monthly: cost per qualified contact added.
Why it saves credits: waterfall is your most powerful enrichment path and your most expensive. Used surgically, it returns pipeline. Used broadly, it consumes a quarter in weeks.
Play 04
Mailbox health protocol
Continuous. The deliverability work.
Steps
- Connect parked domains to active sequences. Spread send volume across them.
- Warm up any mailbox under 14 days old before live sends.
- Check inactive-reason flags weekly. Resolve any flagged accounts.
- Bounce rate above 3% on a mailbox: pause that mailbox, run audit, fix infra before resuming.
- Target: reply rate climbs from near-zero toward the 20% range achievable on healthy infrastructure.
Why it saves credits: dead or spammy mailboxes are why your 50k-email campaign returned zero replies. Fix the infrastructure and replies follow, which means every enriched contact does work.
Play 05
Weekly cadence
Every week. Same days. Same numbers.
Rhythm
- Monday morning: pull last week's credit consumption report. Compare actual to plan.
- Wednesday: mid-week pace check. Adjust if running hot.
- Friday afternoon: post next week's per-user budget to the team.
- Bi-weekly: Apollo touchpoint.
- Monthly: retune allocations based on actuals.
Why it saves credits: visibility equals control. Without a weekly rhythm, quarters slip silently. With it, problems surface on Monday, not on day 77.
How we'll know it's working
Tracking + tuning.
Weekly metrics
Credits consumed
≤ 24,000 / wk
Monday
Daily burn (7-day rolling)
≤ 3,400 / day
Daily
Sequence reply rate
trending toward 20%
Weekly
Mailbox bounce rate
< 3% per mailbox
Weekly
DNC scrub coverage
100% of new sequences
Weekly
Cost per qualified contact
tracked, trending down
Monthly
Mobile waterfall yield
contacts per 1k credits
Monthly
Escalation triggers
Three lines that, when crossed, change what we do that week.
-
Daily burn above 4,500 for three days running. Pause non-priority sequences. Audit waterfall use.Same week
-
Weekly burn above 28,000. Tap the protective reserve. Apollo + WalkingTree review the week before continuing.Same week
-
Mailbox bounce rate above 3%. Pause that mailbox. Run a deliverability audit. Resume only after a clean check.Same day
What each side does
Apollo brings
Implementation, audit, weekly support
- 60-minute implementation session inside Week 1: deliverability fixes, DNC SOP walkthrough, sequence review.
- Deliverability audit and DNC scrubbing SOP, packaged and shared.
- Credit usage audit findings, refined against your actual usage in Week 1.
- Weekly check-in for Month 1. Bi-weekly through Month 2 and 3.
- Pace tracker view updated weekly.
- Renewal value review in the last week of Month 3.
WalkingTree brings
Owner, rhythm, execution
- A named credit/pace owner on your side. The person who runs the Monday/Friday cadence.
- Pre-launch DNC scrub on every new sequence.
- Parked domains connected and used for sequence sends.
- Dialer voicemail settings updated in Week 1.
- Weekly pace report posted to your team.
- Attendance at the weekly Apollo check-in.
The renewal moment
By the last week of August, the conversation is different. Three months of clean burn, traceable reply rates, and a documented rhythm change what the renewal looks like. The data does the talking.