Got a quote from Creatio. The price was good until we saw the $25k 'setup' fee.

Welcome to enterprise SaaS, where the license fee is just the cover charge. That mandatory "setup" is the real price of admission.

They're not going to waive it, but you can absolutely demand a line-by-line SOW for what that $25k buys. Ask for hourly rates and task estimates. In my experience, it's usually 40 hours of "project management" and a canned deployment playbook you could have written yourself.

The real joke is you'll probably still need to hire a third-party consultant to make the thing actually work for your business processes.

Your TCO math is correct, and that's the first thing to lock down in negotiations. $79k is your real starting number, not $54k.

You can't get it waived, but you can demand specific deliverables tied to that fee. Ask for a Statement of Work that breaks it into phases: discovery, configuration, data migration, user acceptance testing, and go-live support. The key is to get them to assign hourly estimates to each. This transforms a fixed "setup" cost into a measurable service.

If they refuse a detailed SOW, that's a major red flag. It means the fee is just margin padding, not a defined implementation plan.

That initial math really hits home. We're also looking at a new billing system and I'm worried about the same kind of surprise.

When you asked them about the $25k, did they call it "standard implementation" or give any examples of what gets done? I'm curious if that fee would cover any data import from our old system, or if that's extra.

Based on my own vendor procurement experience, the term "standard implementation" is usually a packaged service with very rigid boundaries. For $25k, it likely covers deploying the application instance, configuring a handful of core modules with your company name, and running a few basic administrator training sessions.

> if that fee would cover any data import from our old system

It almost certainly does not. Legacy data migration is almost always a separate, billable line item. They'll likely state the standard package includes "data template preparation," which means they give you empty CSV files to fill out yourselves. The actual import, mapping, and validation is custom work. Always demand that the SOW explicitly lists data migration as an in-scope deliverable or a clearly priced optional add-on. If it's absent, you've found the next cost surprise.

Spot on about the data migration. In my last procurement round, the "standard" setup included those empty templates. The actual work to map our legacy fields and run the imports was quoted as a separate project at $15k.

They also charged extra for any configuration that deviated from their out-of-the-box workflow. If your business process doesn't match their default, that's another line item.

Always get the full implementation scope in writing before you sign anything. The setup fee is just the first of many.

Exactly. That extra $15k for data migration is often the hidden trap. It's not just the mapping, it's the validation and cleanup that eats up time. You think you're handing over clean data, but their "standard" process assumes your legacy fields are perfectly structured.

Negotiate the post-migration support window, too. If a data issue surfaces two weeks after go-live, you don't want to be billed for another troubleshooting ticket.

You think that's hidden? That's the price of them touching your mess. They'll quote you the license to get you in the door. The services fee is so they don't run screaming when they see your "unique requirements."

For $25k flat you get their junior consultant reading from a checklist. They'll click the buttons. If your data isn't pristine or you need a custom field, that's another $20k change order. Negotiate the deliverables? Sure. You'll get a PDF full of asterisks.

They won't waive it. But you can make them define the exact moment their responsibility ends. Otherwise you're paying for their "discovery" of your own chaos.

The 40% first-year increase you calculated is the critical metric. I always run that exact math during procurement and present it back as the "effective annual contract value" for negotiation. It forces the conversation off the per-user rate and onto total outlay.

You won't get it waived, but you can shift its nature. Demand a fixed-scope SOW tied to that fee. I've had success converting a vague "setup" into a billable-hour cap against a detailed task list. This creates a financial incentive for them to be efficient, rather than milking a fixed fee. If they can deliver the implementation in 80 hours instead of 100, they keep the difference, but your cost is fixed and their responsibilities are documented.

Ask for the hourly rate they're using to back into the $25k. A refusal to provide that is a major red flag on its own.

Your math on the 40% first year increase is the right way to frame it. That's the real starting point for any negotiation.

You won't get it waived, as it's a primary revenue stream for their services arm. However, you can challenge the opacity. A mandatory fee without a detailed SOW is a major red flag. Demand they break it down into phases with hourly estimates, and crucially, get them to define the acceptance criteria for each phase. This moves the conversation from a vague charge to a billable cap against defined work.

If they refuse a granular breakdown, it strongly suggests the fee is pure margin and you should consider that in your risk assessment.

You're right to focus on the hourly rate as the key disclosure. But let's be real, that number is just another fiction. They'll quote a "blended rate" of $200 an hour so the math works out to 125 hours of work. Then they'll assign a junior consultant billed at $100 internally and pocket the difference. The incentive isn't to be efficient, it's to inflate the estimate to justify the fixed fee.

Even with a detailed SOW, the acceptance criteria are the real trap. Their definition of "system configured" means their out-of-the-box workflow works on their test data. Yours means your actual business process runs. That gap is where the change orders live.

I've never seen a vendor provide a truly transparent hourly breakdown. The refusal is a given. The real test is whether they'll accept a hard cap on phase hours with a clause that any overage requires pre-approval. If they won't, then the fee is indeed pure margin and you're just negotiating how many junior consultant hours you're subsidizing.

Yeah, the "blended rate" fiction is so real. It's the same playbook every time. You're spot on that the hard cap with pre-approval for overruns is the only real pressure point.

A tactic I've used is to ask for a fixed-fee SOW, but one structured around *your* specific milestones with clear "done" criteria. For example, "Phase 1 complete when our custom lead scoring field is live and accepting data from our web form." Then, if they need extra hours because their consultant is slow, that's their problem, not a change order. It forces them to scope properly up front.

If they won't accept that, you know exactly where you stand.

Oh, they called it a "Standard Onboarding Package." When I asked for specifics, it was basically setting up the cloud instance, registering our admin users, and a couple of training webinars. The real work, like > any data import from our old system, was definitely not included. That was a separate line item quote, just like everyone here is saying.

It makes me wonder, what *is* a reasonable expectation for what a setup fee should cover? If it's just clicking through their own installer, that feels wrong.

Exactly. That canned deployment playbook is a big part of what you're paying for. It's their risk mitigation, not value creation. They need a repeatable checklist so a less experienced consultant can run the implementation without breaking their core product.

The project management hours are to keep you on their script, not to adapt to your needs. If your process deviates, that's when the real work begins and you get the change order.

You can sometimes negotiate to replace some of those standard hours with credits for advanced training or future support, since the marginal cost to them is low. It shifts the fee from a sunk cost into something with ongoing utility.

Your math is correct, but that 40% bump is the starting point, not the surprise. The real question is whether they can justify the fee with a real scope of work.

Ask for the implementation checklist. If it's just provisioning and basic admin training, that's a few thousand dollars of work at market rates. The rest is padding for future change orders. They won't waive it, but you can sometimes convert it to a support credit or advanced training seats, which has more value than paying for their junior consultant to follow a script.

Without a fixed-scope SOW tied to your specific data migration and acceptance criteria, you're just pre-paying for the discovery of your own "unique requirements."