From instantly-pack
Optimize Instantly costs through tier selection, sampling, and usage monitoring. Use when analyzing Instantly billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "instantly cost", "instantly billing", "reduce instantly costs", "instantly pricing", "instantly expensive", "instantly budget".
How this skill is triggered — by the user, by Claude, or both
Slash command
/instantly-pack:instantly-cost-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Optimize Instantly email outreach costs by managing sending account count, right-sizing your plan tier, and maximizing deliverability (which is the core ROI metric). Instantly pricing combines per-seat costs with sending volume tiers (Growth: 5K leads/month, Hypergrowth: 25K leads/month, Light Speed: 100K leads/month).
Optimize Instantly email outreach costs by managing sending account count, right-sizing your plan tier, and maximizing deliverability (which is the core ROI metric). Instantly pricing combines per-seat costs with sending volume tiers (Growth: 5K leads/month, Hypergrowth: 25K leads/month, Light Speed: 100K leads/month).
set -euo pipefail
# Check per-account performance
curl "https://api.instantly.ai/api/v1/account/status" \
-H "Authorization: Bearer $INSTANTLY_API_KEY" | \
jq '.accounts[] | {
email, daily_limit, sent_today,
reputation_score, warmup_status,
effective_sends: (.sent_today * .reputation_score / 100)
}' | jq -s 'sort_by(-.effective_sends)'
# Accounts with low reputation are wasting sends (emails go to spam)
# Before: 10 accounts, each sending 30 emails/day = 300 sends/day
# Problem: 4 accounts have <50 reputation score (emails going to spam)
current:
accounts: 10
effective_sends_per_day: 180 # Only 6 accounts delivering well
monthly_cost: "$97/month per account subscription"
optimized:
accounts: 6 # Remove low-reputation accounts
effective_sends_per_day: 180 # Same effective volume
monthly_cost: "58% of original"
# Proper warmup maximizes deliverability, which maximizes ROI
warmup_best_practices:
new_account:
week_1: 5 emails/day # Start very low
week_2: 15 emails/day
week_3: 30 emails/day
week_4: 50 emails/day # Full sending capacity
total_warmup: 28 days
# Don't rush warmup to save time -- a burnt account costs more to replace
# than 4 weeks of gradual warmup
monitoring:
check_daily: reputation_score
pause_if: reputation_score < 60
reduce_volume_if: bounce_rate > 3%
# Plan selection based on actual sending needs
growth_plan:
leads: 5000/month # 5000: 5 seconds in ms
best_for: "Small team, 1-2 SDRs, testing campaigns"
cost: "$37/month"
hypergrowth_plan:
leads: 25000/month # 25000 = configured value
best_for: "Active outbound team, 3-5 SDRs"
cost: "$97/month"
tip: "Only upgrade when Growth plan consistently hits >80% lead capacity"
# Calculate: if you're on Hypergrowth but only importing 3K leads/month,
# switch to Growth and save $60/month
# The highest ROI optimization is improving reply rate, not sending more emails
optimization_priority:
1_clean_lead_lists:
action: "Verify emails before importing"
impact: "Reduces bounces, protects reputation, fewer wasted sends"
2_personalize_sequences:
action: "Use merge tags and custom variables"
impact: "2-3x reply rate improvement"
3_optimize_sending_schedule:
action: "Send Tuesday-Thursday 9-11am recipient timezone"
impact: "20-30% better open rates"
4_a_b_test_subject_lines:
action: "Test 2-3 variants per campaign"
impact: "10-20% open rate improvement"
| Issue | Cause | Solution |
|---|---|---|
| Paying for unused sending capacity | Plan oversized for actual volume | Downgrade plan tier |
| Low ROI per dollar spent | Poor deliverability | Fix warmup, clean lists, improve personalization |
| Account costs without results | Account reputation too low | Pause account, rewarm or replace domain |
| High bounce rate | Unverified lead lists | Use email verification before import |
Basic usage: Apply instantly cost tuning to a standard project setup with default configuration options.
Advanced scenario: Customize instantly cost tuning for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin instantly-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026