What a Fixed-Fee Database Engagement Actually Includes
"How much will this cost" is genuinely unanswerable before scoping the work — and "fixed fee" only means something if both sides agree on exactly what's inside it. Here's how that scoping actually works.
1. It starts with discovery, not a quote
A fixed-fee number that's quoted before anyone has actually looked at the environment is a guess wearing a number. A short discovery step — reviewing the current setup, the actual problem, and any constraints — comes first, so the fee is based on what's really there rather than assumptions. For a well-defined problem this can be quick; for something more open-ended (an unfamiliar environment, an unclear root cause) it's worth treating as its own small step before committing to a fixed price for the main engagement.
2. What's typically included
- A written scope — specific deliverables, not vague intentions. "Migrate database X to Azure SQL Managed Instance, validated against Y test cases" rather than "help with the migration."
- The actual work — scoped against what discovery found, not what was assumed at the start.
- A validation step — confirming the deliverable actually works before calling it done, not just that the work was performed.
- Handoff — documentation of what changed, why, and what the client's team needs to know to operate it going forward.
3. What's usually not included by default
- Work outside the agreed scope — if discovery mid-engagement turns up something bigger than originally scoped (a separate performance problem, a security gap unrelated to the original ask), that becomes a documented, separately-estimated change request rather than either silently absorbed or silently ignored.
- Ongoing support after handoff — a fixed-fee engagement has an end state. Continued monitoring or maintenance afterward is normally a separate, ongoing arrangement (retainer or as-needed), not an assumed extension of the original fee.
- Infrastructure and licensing costs — the engagement fee covers the work; any Azure consumption, SQL Server licensing, or third-party tooling costs are the client's own, not bundled in.
4. Scope creep is the actual risk on fixed-fee work — here's how it's handled
The honest failure mode of fixed-fee pricing isn't the client asking for more — it's not having a clean process for when that happens. A well-run engagement documents anything discovered outside the original scope, gives a straight estimate for addressing it, and lets the client decide whether it's in-scope-now, a follow-up engagement, or something they handle themselves. What doesn't happen: quietly expanding the work to "make it right" and eating the cost (unsustainable), or refusing to acknowledge something material that was found along the way (a bad way to build trust with a first client).
5. What "done" looks like
A fixed-fee engagement ends with a defined deliverable, validated, and handed off with documentation — not an open-ended relationship that quietly continues. If ongoing help makes sense afterward, that's a new, separate conversation, priced and scoped on its own terms (see our fractional DBA vs. full-time comparison for what that ongoing arrangement can look like).
The clients who feel good about a fixed-fee engagement afterward aren't the ones who got the most extra work for free — they're the ones who always knew exactly what was in scope, and what wasn't.
Have a specific problem that needs a scoped fix?
Free 20-minute fit call — describe what you're dealing with, get a straight read on what a scoped engagement would look like.
Book a free fit call