Hey — welcome to Drift Intel.
Taxes. The only thing that finds you faster than a vendor TOS update.
This week: Vercel's coming for your VAT, AI agents are getting their own terms of service (yes, really), and we've got a side project idea that might actually be worth building.
🔴STACK WATCH
Vercel Adding VAT — Starting April 1st, 2026
Not an April Fools' joke, unfortunately.
Vercel announced they'll start collecting VAT on all invoices starting April 1, 2026. If you're outside the US, your bill is about to get a line item you weren't budgeting for.
Why it matters: If you're on Vercel Pro ($20/month) and you're in a country with 20% VAT, that's an extra $48/year you didn't plan for. Scale that across a team and it adds up fast.
What to do:
Go to Vercel → Settings → Billing → add your VAT ID now
If you're VAT-registered, adding your ID means the correct rate is applied (possibly 0% for B2B in some jurisdictions)
If you haven't added it by April 1st, Vercel will charge the standard rate and you'll be chasing refunds
Detected by StackDrift monitoring.
🟡AI WATCH
The Agent TOS Problem Nobody's Talking About
Here's a fun thought experiment: if your AI agent signs up for a service on your behalf, who agreed to the Terms of Service?
This isn't hypothetical anymore. As agentic AI gets built into everything — from Devin writing code to agents booking travel — there's a growing gap between what TOS require ("you, a human, agree to...") and what's actually happening ("a script running on a cron job agrees to...").
Google's Gemini Workspace terms already have an "AI Agents" definition baked in. Most other vendors haven't caught up yet.
The takeaway: If you're building anything with agents that interact with third-party services, keep an eye on whether those services update their terms to address automated access. Some will embrace it. Others might use it as grounds to terminate your account.
🟢VIBE CHECK
Someone Should Build: A "Vendor Health Score" for Indie Devs
Picture this: you paste in the names of the 5-10 SaaS tools your startup depends on, and you get a score. Not just uptime — but how stable their terms are, how often they change pricing, whether they've had any recent controversy, how responsive their support is.
Think of it like a credit score, but for your vendor stack.
The data exists. Uptime is on status pages. Pricing changes are trackable (hey, that's what we do). Review sentiment is on G2 and Capterra. Support response times get posted on Twitter all the time.
Someone just needs to aggregate it into a single score.
Why it could work:
Every founder evaluating a tool would check this before committing
SaaS companies would want a good score (creates demand from both sides)
Affiliate potential is massive (recommend alternatives to poorly-scored vendors)
If you build this, let us know. We'll be your first integration partner.
This Week in Numbers
Metric | Count |
|---|---|
Vendors scanned | 30 |
Documents monitored | 98 |
Changes detected | 20 |
Stable (no changes) | 24 |
Vendors change the rules constantly. Most of the time it's formatting and typos. But sometimes, it's much more important to your bottom line.
That's why we built StackDrift — so you catch these before they catch you.
Want the full breakdown? Sign up for early access and get severity-scored monitoring across your entire vendor stack.
Found this useful? Forward it to a founder who thinks "I'll read the TOS later" is a viable strategy.
See you soon.
Trish @ StackDrift
