7 Questions to Ask a DevOps Provider Before You Hire

Most startups hire a DevOps provider exactly once, with no basis for comparison — which is why the bad ones survive. These seven questions expose the difference in a single call. For each: why it matters, the answer a good provider gives, and the red flag.

1. Who exactly will do the work — and can I meet them before signing?

Agencies routinely sell you a senior architect and deliver a rotating bench of juniors. Good answer: a named engineer, on the call, before you commit. Red flag: “we’ll assign the best available resource” — that sentence is the bench.

2. Where will the code and infrastructure live?

If the provider keeps the Terraform in their repos or builds in their accounts, you haven’t bought infrastructure — you’ve rented a dependency, and leaving them means starting over. Good answer: everything in your repos and your cloud accounts from day one, documented well enough for any engineer to pick up. Red flag: proprietary tooling you can’t take with you, or “we’ll hand it over at the end.”

3. What does it cost — right now, on this call?

A provider who needs three discovery calls to name a number is pricing you, not the work. In our review of 22 competitor sites, only about 1 in 6 published any price. Good answer: a number, or a public pricing page (here’s ours). Red flag: “it depends” with no ranges, or open-ended hourly billing — which structurally rewards slowness.

4. How will I know what you did this week?

Infrastructure work is invisible when done well, which makes it easy to bill for and not do. Good answer: a written cadence — weekly summaries, a visible request board, dashboards you can check yourself. Red flag: “you can always ask” — reporting that only exists when you chase it.

5. What happens when something breaks at 2am?

Match the promise to your actual need — most sub-25-engineer startups need good alerting and fast business-hours response, not a $10K/month NOC. Good answer: honest coverage windows in writing, alerts that page you both, and runbooks so the fix doesn’t depend on one person being awake. Red flag: a solo consultant promising 24/7 (they can’t), or an agency selling you 24/7 you don’t need.

6. When should we STOP working with you?

The most revealing question on the list, because a bad provider has no answer — the plan is forever. Good answer: a specific exit condition. Ours is written on our pricing page: past ~25 engineers you should hire in-house, and everything we build is designed for that handover — the full reasoning is here. Red flag: any answer that amounts to “why would you ever leave?”

7. Can you show me what your deliverable actually looks like?

Anyone can promise “a thorough audit” or “production-grade infrastructure.” Good answer: an artifact — a sample report, a real dashboard, a case study with numbers. We publish a full sample of our $1,900 audit report for exactly this reason. Red flag: logos and adjectives, nothing you can inspect.

The pattern behind all seven

Every question probes the same thing: does this provider make money by finishing, or by staying? Flat prices, your repos, written exit conditions, and inspectable deliverables all point one way; hourly meters, their repos, vague reporting, and forever-contracts point the other. Ask all seven in the first call — a good provider will enjoy answering them.

Want to see how we answer? Book a 15-minute call — or start with the free two-minute health check so you know what to ask about.