Your forecast is in
Production-music shop spinning up royalty-free tracks on demand. Marketer types a brief (tempo, mood, genre, target length), the agent drafts a Suno prompt + style cue, generates the track, and queues it for review. ~20…
How PitCrew gets you to $36/mo
Each recommendation below is one change you make at design time, with the dollars it shaves and the running total saved before you ship.
Action plan
The full reasoning behind each recommendation — copy into your build doc.
M2.7 from minimax runs the same workload at lower cost (budget tier, same quality bucket). Spec lists it as good for: agentic, productivity. Verify quality on a sample of your traffic before fully switching.
Considered, didn’t apply
PitCrew checks every lever — model fit, prompt caching, batch lanes, prompt trimming. Here’s why the rest didn’t make the cut on this build.
- Prompt cachingYour system prompt is 86 tokens; caching needs ≥1,024 tokens to amortize the cache-write cost.
- Trim system promptNo redundancy detected — your 86-token prompt is already tight.
- Batch APIThis is a real-time agent (0% async traffic). No work to route to a batch lane.
Alternative music models
Same modality, your wizard’s output settings. Click Try as default to re-render this report with that generation model as the new baseline.
| Model | Unit cost | Resolution | Monthly cost | vs default | Try as default |
|---|---|---|---|---|---|
sunoSuno v3.5 Defaultsongwritingvocals + lyrics | $0.04/song | — | $36/mo | — | |
stabilityStable Audio 2 instrumentalsound effectsshort loops | $0.000833/sec | — | $45/mo | +$9/mo | Try as default → |
udioUdio v2 remixhigh-quality covers | $0.05/song | — | $45/mo | +$9/mo | Try as default → |
What we assumed
These are the inputs we used. If anything looks off, re-run the audit with better numbers.
- Call volume is your guess — typical pre-deploy estimates land within ±50% of actual.
- Conversation length is a coarse bucket — actual tokens vary by ±40% per call.
What’s not included
PitCrew forecasts steady-state AI API spend — the dollars the LLM / embedding provider bills for the deterministic workload your wizard described. A production bill carries two kinds of cost on top that PitCrew doesn’t model:
1. Inference overhead — proportional (20–50% on top of steady-state)
- Dev / eval loops (often 10-30% of total spend)
- Retries, error recovery, idempotency replays
- Background batch jobs (summaries, classification of past data)
- A/B traffic on alternate models
- Embeddings + fine-tunes that ride alongside the agent
| Scenario | Steady-state (PitCrew) | With inference overhead |
|---|---|---|
| Default build | $37/mo | $45–$56/mo |
| PitCrew plan | $36/mo | $44–$55/mo |
2. Hosting & infra — flat (workload-dependent, typically $10–80/mo)
- Cloud hosting (Vercel / Render / Fly / AWS / etc.)
- Database (Supabase / Postgres / Mongo / etc.)
- Managed vector DB or search — Pinecone, Weaviate, OpenSearch typically $25–100/mo (if not already entered in Step 5)
- CDN, scraping APIs, telephony minutes, transport (Twilio, LiveKit, Zyte, etc.)
- Vendor SaaS margin if going through a wrapper (Cursor, Vapi, Evee, etc.) instead of direct API
The 20-50% inference multiplier comes from public engineering postmortems and the validation cases in docs/accuracy-validation.md. If your team has tight eval loops and minimal retry traffic, target the low end. The hosting/infra range is highly workload-dependent — small RAG bots may spend nothing extra, voice agents add telephony costs on top.
How sensitive is this forecast?
Pre-deploy estimates are guesses. Here’s how the savings shift if the volume or conversation length you guessed turns out to be off.
Run another audit
for a different build
Tweak inputs, swap the model, see how the forecast moves.
New audit