Launched this week
Stop losing money on forgotten SaaS subscriptions and "ghost" licenses. Toolspend is the ultimate command center for your stack, designed to give you 100% spend visibility without the manual upkeep. While other tools just list your apps, Toolspend deep-dives into your actual usage and spend patterns. We identify underutilized seats, detect duplicate tools across teams, and alert you before every renewal. Toolspend helps you automate the toil of procurement so you can focus on building!
The visibility problem with AI tooling costs is real — you start with one subscription, then three, then you realize you have overlapping tools doing the same job. Centralizing that view with actual usage data rather than just listing what you're paying for is the key insight here. Congrats on the launch!
Toolspend
@cogotemartinez Love how you framed that — overlapping tools doing the same job is exactly what we keep seeing.
Listing subscriptions is easy.
Connecting actual usage to actual spend is where things get interesting (and uncomfortable ).
Out of curiosity — have you found more waste in seat-based tools or in variable token usage so far?
Toolspend
@jihad_mahmoud Thanks Jihad.
Yes — we focus heavily on usage, especially AI API usage (tokens, requests, model-level consumption), not just the dollar amount on the invoice.
And great question on alerts
Right now we support spend-based alerts, but usage-based alerts (e.g. token thresholds, model spikes, abnormal usage patterns) are very much on the roadmap. Honestly, that’s where things get powerful — catching the spike before it becomes a billing surprise.
If you were setting one today, would it be per model, per project, or per API key?
@visagar That's great, glad to hear you have eyes on the usage alerts in the foreseeable future.
Actually for me it is simple since I'm a solo indie maker, alerts make sense per API key. Nevertheless, teams and other people may have different needs hence doing a more detailed alerting system like the one for budgets would make more sense from my prospect so it serves more users. Thank you and I wish you the best of luck.
This is incredibly timely — AI tool costs can spiral out of control fast, especially when you're using multiple APIs for different tasks. Do you support tracking costs for image generation APIs like Replicate or fal.ai? That's where a lot of hidden spend lives.
Toolspend
@tugay_pala Yes — we support Replicate and several other providers, and we’re actively integrating RunwayML and ElevenLabs.
Beyond tracking spend, we analyze actual usage and surface alternative models inside the same ecosystem so teams can save without changing workflows.
Example (image generation):
A team might be using a high-end SDXL or Flux variant on Replicate for every image. ToolSpend can show that for previews, thumbnails, or internal drafts, a lighter SD 1.5–based model or a faster low-step variant produces near-identical results at a fraction of the cost — and flags when the premium model only makes sense for final exports.
Same API. Same output intent. Less burn.
That’s where most “hidden” AI spend lives.
Congratulations on the launch! You could create an AI agent that connects to email, analyzes messages, and automatically extracts all services and service packages from them.