What you get
A Mepa8 vendor audit is a five-day pass over every metered service your company pays for, done by the people who built the monitor and run it on their own bills. You hand over read-only keys where the vendor allows them, or forward a month of receipts to a private inbox. We never ask for a password. At the end you have four things: the list, the numbers, the leaks, and the board.
The list is every vendor with its plan, limit and reset date. The numbers are real cost per vendor, by API where one exists and by receipt where it does not. The leaks are written the way our own are in the incident log: the measured figure, the cause, the fix, and the one-line rollback. Our first pass on our own 21 vendors found a $93-a-month database bill against a $50 budget and a voice vendor at 106% of its credits. The board is yours to keep, with budgets and alert thresholds set and kill recipes written for each vendor.
“We built it because the invoices kept winning.”Ryan Bolden, Mepa8, 2026-10-08
Book it
Fill in the form. You get a reply from a person within one business day with a short list of what we need and a time to start. Payment of $750 is taken after that reply, not now, and there is no card field on this page.
How the five days go
- Day 1. Inventory. We read your receipts and keys and list every vendor, including the ones you forgot. In our own case that was 21 vendors across 4 payment methods.
- Day 2. Numbers. Cost by API for vendors that expose it, by receipt for the rest. Each vendor gets a plan, a limit, a reset date and an on-pace figure.
- Day 3. Leaks. Anything that is costing more than it should, with the cause measured, not guessed. A 251-updates-a-minute database churn is a measurement; “the bill seems high” is not.
- Day 4. Fixes and rollbacks. Written so your own team can apply or reverse them. Where we can apply a fix safely and reversibly with your say-so, we do.
- Day 5. Handover. Your board with budgets, thresholds and kill recipes set, plus a 30-day re-check booked.
What we need from you
- Read-only API keys for the vendors that offer them. ElevenLabs, Neon and Railway do, and the catalog says which scope to use for each.
- A month of receipts forwarded to the private inbox we give you, for vendors with no billing API.
- One person who can answer “what is this vendor for?” in a sentence, for about an hour over the week.
Keys are stored encrypted, used only for reads, and deleted at the end of the audit unless you keep the board. The privacy page says exactly what this form stores and for how long. Official vendor pricing pages, such as Neon's, are the only source we use for rates, and each audit page links the page it read.
Questions people ask
Do you need my passwords?
No, never. Read-only API keys where the vendor offers them, and forwarded receipts where it does not. ElevenLabs, Neon and Railway all issue keys we can scope to reads. Anything that needs a dashboard click stays with you, and we write the steps.
What if you find nothing?
Then you have the list and the board, which is still the thing nobody had. In our own first audit on 21 vendors we found 2 leaks and 3 vendors with no cost visibility at all. If we find nothing to fix, we say so in writing.
How fast does it start?
A person replies within one business day of the form. Most audits start within three business days of that reply, once keys or receipts arrive, and finish five business days after they start.
Sources
- Neon pricing — read 2026-10-09
- ElevenLabs pricing — read 2026-10-08
Change log: October 9, 2026 — First published with the booking form.