How to Evaluate a Cloud Advisory Firm:
Questions That Reveal Quality

Most cloud consulting firms describe themselves the same way: experienced, trusted, results-driven. Those words do not differentiate anyone, because every firm uses them. The way to evaluate a prospective advisory partner is not to read their marketing. It is to ask questions specific enough that a firm without genuine depth cannot answer them convincingly.

Questions About Their Actual Work

"Walk me through a specific engagement where your initial recommendation was wrong."

Every firm that has done real work has had a recommendation that did not pan out as expected. A firm that cannot describe one, honestly and specifically, is either inexperienced or unwilling to be candid with you. Either answer is useful information.

"What did you recommend against, and why?"

Firms that only ever recommend the more complex, more billable option are optimizing for their own revenue, not your outcome. A firm worth working with can describe a time it advised a client not to migrate, not to adopt Kubernetes, or not to pursue a multi-cloud strategy, because the client's situation did not justify it.

"How do you price engagements, and what happens if scope changes?"

Time-and-materials pricing with no defined scope creates an incentive misalignment: the firm benefits from the engagement taking longer. Fixed-fee or outcome-based pricing, with a clear change process for scope shifts, aligns incentives more closely with your actual goals.

Questions About Technical Depth

"Who specifically will work on our engagement, and what have they built before?"

Sales conversations are frequently led by the firm's most experienced people, who then hand the actual work to more junior staff. Ask directly who will be doing the work, and ask for their specific, verifiable experience, not just years at the firm.

"What AWS services have you implemented in production, not just in a proof of concept?"

There is a meaningful gap between having configured a service in a demo environment and having operated it in production under real load, real failure conditions, and real cost pressure. A firm with genuine depth can speak specifically about operational lessons, not just feature capabilities.

Questions That Reveal How They Think

"What would you need to see before recommending we do nothing?"

A firm that always has a project to sell you, regardless of your actual situation, is optimizing for its own pipeline. A firm confident enough to tell a prospective client that their infrastructure does not need intervention right now, or that a smaller engagement would serve them better than a larger one, has demonstrated something marketing copy cannot.

"How do you measure whether an engagement succeeded?"

Vague answers ("client satisfaction," "successful delivery") suggest the firm has not defined success rigorously for its own work. Specific answers (cost reduction percentage against an agreed baseline, deployment frequency improvement, defined SLA achievement) suggest a firm that holds itself accountable to outcomes.

What Good Answers Sound Like

Firms worth engaging tend to answer these questions with specifics: named services, actual numbers, honest descriptions of what did not work. They are comfortable being told no, and comfortable telling you no when your situation warrants it. They can describe their pricing model without hedging, and they can name the people who will actually do the work.

The absence of specificity, generic language, deflected pricing questions, an inability to describe a failure or a "no" recommendation, is itself the most reliable signal available to you before you sign an engagement.