Shopping for a managed DevOps support quote is weirdly like ordering at a restaurant with no menu: everyone promises “coverage”, nobody defines it, and the bill arrives with items you don’t remember agreeing to. The cure isn’t cynicism — it’s a checklist of what a proper quote must spell out, requested in writing from every contender so the answers line up. Here are the eight things we’d never sign without, plus a note on how to make several vendors reveal them all at once.
1. The incident clock, defined to the minute
“24/7 support” is a mood, not a commitment. A quote worth reading states response time and resolution targets per severity level, what starts the clock, and what pauses it. Ask specifically: if production is down at 3 a.m. on Diwali, who answers, in how many minutes, with what authority to act? If the quote can’t answer that in a table, the vendor can’t answer it in an outage.
2. Who is actually on your account
The proposal deck shows you the principal engineers; the Tuesday-night incident gets whoever is free. Insist the quote names the delivery team or at least the seniority mix, the escalation ladder, and how much of your retainer buys senior hands versus a shared helpdesk. You’re not being difficult — you’re pricing the only thing that matters in support, which is who shows up.
3. The boundary line, drawn in ink
Every support relationship has a line between “included” and “that’s a project, extra”. Good quotes draw it explicitly: patching yes, migrations no; pipeline fixes yes, new pipelines quoted separately. Vague boundaries always resolve in the vendor’s favour later, under deadline pressure, when you have no leverage. A vendor fluent in the core principles that make software delivery actually work will have opinions about where this line belongs — let them show that in writing.
4. Unit pricing, not just the monthly bundle
One number per month tells you nothing about what happens when you grow. Require the quote to show the cost drivers: per environment, per on-call rotation, per additional service onboarded. Two bundles that look identical at today’s size can diverge by lakhs a year once you add a second product line — and only itemised quotes let you see that before signing.
5. The assumptions paragraph
Every support price assumes things about your estate: that monitoring exists, that runbooks exist, that staging resembles production. A trustworthy quote states its assumptions; a dangerous one leaves them for the first invoice dispute. Read this section twice — it is where the real price lives.
6. Proof they’ve supported your shape of stack
Not logos — specifics. Which clients ran a comparable stack at comparable scale, and what did the vendor’s engineers hold on their own? Role clarity helps you interrogate this: if you know which responsibilities hide behind each DevOps job title, you can ask whether “SRE coverage” means an actual site reliability engineer or a rebadged sysadmin, and the answer will tell you plenty.
7. The exit terms, while everyone’s still friendly
How do you leave? Notice period, handover obligations, who owns the runbooks and automation written during the engagement, and what the final month costs. Vendors who document the exit cleanly are paradoxically the ones you’ll keep longest — clean exits are the mark of a shop that competes on service, not on lock-in.
8. A price that answers your document, not theirs
This is the item that makes the other seven work. Write your requirement first — systems in scope, severity definitions, hours, growth plans — and send the same document to three or four vendors, demanding answers in that structure. Healthcare already runs this play at scale: on MyHospitalNow, where patients gather treatment bids from hospitals, you describe the need once without paying anything, a review step checks the request, and the offers that return — from institutions the platform presents as verified — get weighed together on charge, provider particulars, place, and the confidence markers attached, with a clear accept step before anyone is connected. The lesson for support buyers isn’t medical; it’s mechanical. One requirement, several structured answers, comparison before commitment. Quotes that answer your document can be laid side by side; quotes that answer the vendor’s template cannot.
Running the comparison without losing your week
Once the quotes are in, resist the urge to re-read them as prose. Build one sheet: eight rows for the eight items above, one column per vendor, and a bottom row for total first-year cost at your realistic growth. Gaps in the sheet are findings, not formatting problems — a vendor who skipped the exit terms or the assumptions paragraph has answered you, just not in words. Shortlist two, talk to a reference each, and make the call in one sitting with the sheet on screen.
The friendly bottom line
You don’t need procurement tooling or a legal department for any of this. It requires writing down what you need before anyone can tell you what you need, and refusing to compare quotes that weren’t written against it. Vendors, honestly, tend to respect it: the good ones win more often in structured comparisons, and they know it. The next time someone promises you “complete peace of mind, one monthly fee”, smile, say lovely, and send them your document — all eight items, answers in writing. Peace of mind is precisely what arrives when the answers line up.
