My Vercel Bill Tripled in April. One Setting Fixed It.

TL;DR: Vercel sent me a $60.89 invoice. $35 of it came

from "Build CPU Minutes" — a category I didn't know I
was paying for. One toggle in project settings cut it
to near-zero.

Zero paying users. Four SaaS projects. $60.89/month on
Vercel.

That math wasn't working, so I went looking.

Here's what the invoice broke down to:

Pro subscription: $20.00
Build CPU Minutes: $34.57 ← what?
Build Minutes: $5.96
Observability Events: $0.13
Fluid + ISR + others: $0.36
─────────────────────────
Total: $60.89

The $20 subscription I expected. The $34.57 line for
"Build CPU Minutes" I did not.

Why my bill exploded

Vercel deploys every branch by default. Every time I
push code — feature branch, fix branch, "let me just
try this" branch — Vercel runs a preview build.

For a typical week of solo development:

• ~5-10 pushes per day
• Across 4 projects
• = roughly 20-40 builds per day
• = ~600-1,200 builds per month

Each build burns CPU minutes. The CPU minutes don't
show up on the marketing page next to "Pro plan." They
show up on the invoice.

The setting I missed

Buried in Settings → Build and Deployment → Ignored
Build Step, there's a Behavior dropdown.

Default: "Automatic" — every push gets built.

What I switched to: "Only build production".

Vercel now only runs a build when code hits the main
branch. Feature branches, WIP branches, "trying
something" branches — all skipped.

The tradeoff

You give up automatic preview deployments. For a solo
founder this is mostly fine — I have local dev, and I
have tests. For a team building UI changes that need
visual review, this would hurt.

For me: net positive. I can always trigger a manual
deploy when I genuinely need a preview URL.

What changed in late April

My Build CPU Minutes spiked starting in late April.
Before that, the same workflow was costing me cents per
day. After, it was costing dollars per day.

I don't know exactly what changed. With "Only build
production" toggled on, it doesn't matter — the number
of builds got cut.

What to check on your invoice

If you're on Vercel Pro and you're not actively using
preview deployments:

Diagnose (30 seconds):

1. Open the Usage page
2. Look at "Build CPU Minutes"
3. If it's more than a few dollars, you have a problem

Fix (30 seconds):

1. Settings → Build and Deployment → Ignored Build Step
2. Change Behavior to "Only build production"
3. Save

Could save you $20-50/month per project.

I'll know next month if my fix actually works. The
invoice doesn't lie.

---

This is part of a series of build-in-public posts about
launching OriginBrief, an
AI-powered research monitoring tool, as a solo founder.