Skip to main content
Serhii Panchyshyn

For B2B SaaS teams with AI in production and a five-figure monthly AI bill

I cut a client’s AI bill from $100K to $8K a month. 
Same product. Same traffic.

The AI Spend Audit: one week inside your production AI. I find at least 10% of your AI spend in itemised annual savings — or you pay nothing. That is a floor, not a forecast. You keep the plan either way.

Book a 30-minute call (opens in new tab)
  • Now booking August — 1 audit slot
  • $9,500 · one week · fixed fee
  • 10% found or it’s free
10% or free
The guarantee: at least 10% of your AI spend identified in itemised annual savings, or the audit costs nothing — a floor, not a forecast.
See the audit ↓
35%
Projected AI infrastructure cost cut at a SaaS company via model routing analysis.
7 yrs
Building software. The last 3 on production LLM systems, retrieval, and multi-agent orchestration.
Serhii Panchyshyn

Serhii Panchyshyn
ex‑PwC compliance · production AI engineer

Meet Serhii

I did not start in code. I started in tax compliance at PwC: filings, audits, and rooms where someone senior asks why a number is wrong and “the system did it” is not an answer.

Then seven years of software. Junior to senior at a logistics SaaS handling thousands of transactions a day, backend architecture, and the testing strategy that stopped regressions from reaching customers. The last three years have been production LLM systems: retrieval, multi‑agent orchestration, evals, and cost work.

Since going independent in 2025, I keep walking into the same scene. An AI feature shipped in a hurry. A bill climbing quietly. No one who can prove the thing still works. Everyone built. Nobody is keeping it alive.

That is the job I do now. Engineer enough to fix your system. Compliance enough to defend it.

When your AI gets it wrong, you should hear it from a dashboard, not a customer.

On working with me

Pulled from my public LinkedIn recommendations. Every name links to the source.

“Serhii is one of those rare engineers who not only delivers great results but also raises the standard for everyone around him. I’d gladly work with him again anytime.”

Alexey Novak · Senior Software Engineer

“Consistently one of the most talented and reliable engineers I’ve had the pleasure of working with. He can take full ownership of large projects and see them through to production reliably.”

Valentyn Vasylenko · CTO, Curtis

“He embraces and leans into the unknown, picking up new concepts and ideas incredibly quickly. One of the most productive engineers I know.”

Alicia Chin · ex-Snowflake, ex-IBM

“One of the most driven and impressive people I’ve ever met. An incredible collaborator, always willing to go above and beyond to get results.”

Derek Santos · AI Builder

“Grit, hustle, and total comfort in ambiguity. When something has to ship, Serhii is who I count on to get it done.”

Alexander Luksidadi · CTO & Co-Founder, Rose Rocket (YC S16)

The problem

Five ways production AI quietly fails

You already shipped the feature. These are the failure modes that follow it into production. If even two feel familiar, keep reading.

  • Silent drift

    Your product breaks, and a customer tells you

    The provider ships a new model version behind the same endpoint. Same name, same API call, slightly different behaviour. Nothing throws an error. Quality decays for weeks until a customer emails to complain. You learn about your own product from the outside.

  • Runaway cost

    The bill nobody can break down

    It went from $3K a month to $30K. Every single increase looked small, so nobody flagged it. Now a board member is asking about the line item. Nobody can answer “what does one user cost us?”

  • No owner

    Shipped in a hurry, held by hope

    Someone built the AI feature fast, shipped it, and moved on. Now a production system runs with no evals, no cost ceiling, no runbook, and no one responsible. Everyone is quietly hoping it holds.

  • No evidence

    “How do we know it’s still accurate?”

    There were evaluation tests once. They ran once. The person who wrote them is gone. If someone senior asks how you know the AI still works, the honest answer is: you don’t. In a regulated company, that is not an inconvenience. It is a liability.

  • The compliance gap

    Consequences with no regulatory cover

    You are in healthcare or finance. An AI output has consequences someone can be fined or sued over. The people who built it have zero regulatory background. Nobody in the building can say the system is defensible.

None of these throw an error. That is the whole problem. Your monitoring watches for crashes. AI systems don’t crash. They rot.

After the audit: assurance, running weekly

The audit is the front door. If you want what it finds run for you, this is the ongoing service — not vague advice. Five concrete things, running every week.

Evaluation suites on a schedule

Quality checks that run weekly, not once. Drift shows up on a dashboard before it shows up in a customer email.

Cost instrumentation and reduction

Every request tagged and attributed. You can finally answer what one user costs. Then we cut the number.

Model migration handling

When a provider deprecates a model, I run the migration and prove the replacement performs before it ships.

Incident response

When the AI breaks, someone owns it. Triage, fix, and a postmortem you can show your board.

The audit trail

The evidence file that proves outputs are correct. Built for the day a regulator, auditor, or enterprise customer asks.

Proof

The numbers hold up

$100K/mo down to $8K/mo

One client’s AI bill. Same product, same traffic, same quality bar. The spend was in the routing, the retries, and the models nobody had questioned.

$100K$50K$8Kbeforeafter
monthly AI spend, before and after

35% projected infrastructure cut

ContactMonkey’s AI spend, analysed route by route. Same outputs on cheaper paths. The result: an itemised 35% cut in projected infrastructure cost, documented before anything shipped.

Evals before a single user

Also at ContactMonkey: their first generative AI feature, headed for real customers. I built the evaluation framework that verified output quality first. It launched with evidence, not hope.

The offer

The AI Spend Audit

One week inside your AI stack. You get a complete picture of what it costs, what can fail, and what to do about it. Whether we continue or not, you keep everything.

Waiting is the expensive option: if your AI spend is $40K a month, even the guaranteed 10% floor is about $12,000 a quarter — more than the audit costs — and typical findings run well past the floor.

  1. 30 minutes

    Scope

    A short call. You walk me through the stack, I tell you exactly what the audit will cover.

  2. one week

    Audit

    I go through your AI systems. Cost, eval coverage, model risks, failure modes.

  3. after that

    Decide

    You keep the written plan either way. Run it yourselves, or I stay on and run it for you.

The AI Spend Audit

Five deliverables, in writing, in one week:

    Cost map: where every dollar of your AI bill goesEval coverage report: what is tested, what is hoped forModel risk register: what breaks when providers change thingsFailure mode inventory: how your system fails and who finds outA specific, itemised plan to cut spend

$9,500

One week. Fixed fee.

Credited in full toward whatever comes next. Most clients keep me on afterward — either a fixed-scope build of the monitoring stack, or an ongoing assurance retainer from $10K a month.

I will identify at least 10% of your current AI infrastructure spend in itemised annual savings, or the audit is free.

Ten percent is a floor I can guarantee on any stack that passes the scope call, not a forecast of what I expect to find: one audit documented a projected 35% cut, and the standout case took a $100K month to $8K.

I guarantee what I find and document. Your team decides what to implement. No asterisks beyond that.

Now booking August — 1 audit slot

Book a 30-minute call (opens in new tab) We scope the audit on the call. No obligation.

Not ready for a call? Email me — serhii.panchyshyn@animanovalabs.com

Who this is for

B2B SaaS teams, 50 to 300 people, $5M to $50M revenue. You already shipped an AI feature. Your monthly AI bill has five figures in it and nobody can fully explain it — or an enterprise customer, auditor, or board member just asked a question about your AI that nobody could answer. You have an engineering team ready to execute; you need the plan.

  • fintech
  • healthtech
  • insurance
  • legal
  • logistics

Not for teams still deciding whether to build AI. This is for the ones who built it and now have to live with it.

FAQ

Questions worth asking first

  • What does the $9,500 audit include?

    Five deliverables, in writing, in one week: a cost map of where every dollar of your AI bill goes, an eval coverage report, a model risk register, a failure mode inventory, and a specific, itemised plan to cut spend. It is a fixed fee, credited in full toward anything we do after.

  • Why is the guarantee 10% when your results are higher?

    Because a guarantee should be a certainty, not a bet: 10% is the floor I can stand behind on any stack that passes the scope call. The findings themselves come from going through your AI spend route by route — which model handles which request, where retries and redundant calls pile up, and where a cheaper model produces the same output at the same quality bar. That analysis found a 35% projected cut at one company and took another’s bill from $100K to $8K a month, checked against an evaluation suite so the savings do not cost you quality.

  • Do I need this if we already have SOC 2?

    SOC 2 tests your controls at a point in time. It does not tell you whether your AI’s output quality has drifted, what one user costs you, or who owns the system when it fails. AI systems do not crash, they rot quietly, and that gap matters most when an AI output has real regulatory consequences.

  • Who is this for?

    B2B SaaS teams, 50 to 300 people, roughly $5M to $50M revenue, with AI features already in production — the sharpest fit is fintech, healthtech, insurance, legal, and logistics. Your monthly AI bill has five figures in it, and you have an engineering team that can execute a plan. Not for teams still deciding whether to build AI — this is for the ones who built it and now have to live with it.

  • Do you do the implementation?

    Only as a fixed-scope project after the audit: I build the eval suite, cost instrumentation, and drift monitoring, hand it to your team, and train them to run it. Ongoing implementation is deliberately not the retainer — your team owns the system, and I stay on as the check that keeps it honest.

  • What happens after the audit?

    You keep the written plan either way, no obligation to continue. Most clients go one of two ways from there: a fixed-scope build where I install the monitoring and evaluation stack and hand it over, or an ongoing assurance retainer from $10K a month — the dashboards reviewed, evals signed off before ships, and the next model deprecation handled. The audit fee is credited in full toward either.

The cost is climbing. The quality is unproven. And you are the one who will be asked to explain it.

Thirty minutes. We look at your production AI together and you leave with a straight answer on where you stand.