top of page
< Back

How does SubmitHub work and what are best practices (pitch structure, subject lines, credits, common rejection reasons, performance tracking)?

TL;DR - SubmitHub is a pay-per-curator pitching hub: use filters to build a laser-targeted list (25-40 outlets), spend Premium credits for guaranteed 48 h feedback, send a ≤ 90-word pitch with a 35-char subject line, and track approvals, cost-per-share, and downstream saves to decide where to scale.

1 │ How SubmitHub Works in 60 s

Element: Credits
What It Is: • Premium (paid, feedback + 48 h reply) • Standard (free, no guarantee)
Why It Matters: Premium drives decisions; mix both to stretch budget

Element: Filters
What It Is: Genre → Mood → Share-Rate → Engagement Tags
Why It Matters: Surfaces curators who actually share + match your sound

Element: Dashboard
What It Is: Real-time listens, approvals, feedback scores, CTR
Why It Matters: Lets you calculate cost-per-share (CPS) & ROAS

Element: Refunds
What It Is: No response in 48 h = credits back
Why It Matters: De-risks spend

2 │ End-to-End Best-Practice Workflow

Stage: Prep
Action: Final WAV, 2000 px cover, one-page EPK
Pro Tip: Pre-edit a radio cut if intro > 30 s

Stage: Curator Filtering
Action: Genre + Mood → Share-Rate ≥ 5 % → tags like Adds to Spotify
Pro Tip: Export list, aim 25-40 outlets

Stage: Credit Strategy
Action: Budget $30–$120 → split ~70 % Premium / 30 % Standard
Pro Tip: Save Premium for curators ≥ 8 % share-rate

Stage: Pitch Structure
Action: Subject (≤ 35 chars): "Indie-Pop • Neon Night (FFO CHVRCHES)"; Body (≤ 90 words): • 1-sentence hook • 2 quick facts (milestone, gig, stat) • 1 specific ask (Fits your Chill Pop list at 1:18 drop) • Private lyric-video link
Pro Tip: Personalize: greet by name + mention a recent playlist

Stage: Submission Timing
Action: 10–14 days pre-release; schedule staggered batches
Pro Tip: Reply to every feedback (even passes) within 24 h

Stage: Performance Tracking
Action: Use SubmitHub Stats → export CSV → cross-reference Spotify for Artists (saves, followers)
Pro Tip: Kill outlets with share-rate < 3 % next round

3 │ Benchmarks & Traffic-Light Guard-Rails

Metric: Approval Rate
Green (Scale): ≥ 30 %
Yellow (Tweak): 15–29 %
Red (Pull): < 15 %

Metric: Avg. Feedback Score
Green (Scale): ≥ 4.0 / 5
Yellow (Tweak): 3.0–3.9
Red (Pull): < 3.0

Metric: Cost-per-Share (CPS)
Green (Scale): ≤ $0.75
Yellow (Tweak): $0.76–1.25
Red (Pull): > $1.25

Metric: Spotify Saves from Shares
Green (Scale): ≥ 10 %
Yellow (Tweak): 5–9 %
Red (Pull): < 5 %

Scale spend on green, tweak creative/targeting on yellow, pause and fix on red.

4 │ Common Rejection Reasons & Fast Fixes

Reason: Genre / mood mismatch
Quick Remedy: Deep-dive curator playlists before pitching

Reason: Production quality
Quick Remedy: Re-mix / master; reference their top tracks

Reason: Slow intro / weak hook
Quick Remedy: Provide 30-sec radio cut that hits chorus fast

Reason: Generic copy-paste pitch
Quick Remedy: Personalize with curator name + playlist mention

Reason: Artwork / branding clash
Quick Remedy: Align cover art with current genre aesthetics

5 │ Mini Case Study — “AstraMoon — ‘Neon Night’”

Move: 32 curators filtered (Indie-Pop, ≥ 8 % share-rate)
Result: 44 % approval (14 shares)

Move: 90-word pitch, 35-char subject
Result: Avg. feedback 4.7/5

Move: Follow-up tracking
Result: Saves ↑ 11 % WoW; $0.72 CPS

6 │ Quick Cheat Sheet

Do: Keep pitch ≤ 90 words, 3-4 bullets
Don’t: Paste life story or attach files

Do: Mix Premium + Standard credits
Don’t: Burn Premium on low share-rate blogs

Do: Submit 10–14 d pre-release
Don’t: Blast only on release day

Do: Thank curators, repost their coverage
Don’t: Argue over negative feedback

Key Takeaways

Experience – Tight targeting + concise pitch can push approval rates past 40 % and translate to real saves.
Expertise – Optimal list size (25–40), share-rate ≥ 5 %, pitch ≤ 90 words, subject ≤ 35 chars.
Authority – Continuous CPS, save-rate, and feedback tracking turns SubmitHub into a scalable channel.
Trust – Respecting curator time, personalizing asks, and improving with feedback build long-term relationships—and better results—for future releases.

bottom of page