Skip to content
GullySales
← All articles

Notes for owners · Industry playbooks

What a CTO checks before shortlisting a DevOps partner

Before a CTO calls a cloud or DevOps firm, they check who will do the work, whether the firm fixed something like theirs, and who answers at night.

The GullySales team · Updated 13 Nov 2026 · 5 min read

Editorial illustration for What a CTO checks before shortlisting a DevOps partner
On this page
  1. Who will do the work?
  2. Have you fixed something like mine?
  3. What does it cost, and against what?
  4. Who answers at night?
  5. A checklist a CTO would build in their head
  6. Why the checks happen before the call
  7. What a first call should settle
  8. Access and security
  9. Handing over at the end
  10. Making the engagement shape clear
  11. Reference calls and how to prepare for them
  12. Showing how you work day to day
  13. Team size and capacity
  14. What to do next

A CTO checks three things before putting a firm on a shortlist: who exactly will touch the production environment, whether the firm has fixed something that looks like their problem, and what happens at two in the morning when it breaks. A firm that can answer all three in writing, in plain words, gets a call. The rest are filtered out before anyone has read their service list.

Who will do the work?

Buyers have been burned by a senior name on the pitch and a junior on the project. So the first thing a CTO looks for is a named engineer, with a role and a visible record, such as a technical post, a talk or a repository.

A page that says "our certified experts" says nothing. A page that says the migration lead is Priya, that Priya has run data-centre exits and that Priya will be on the calls after kick-off gives the CTO something to check on LinkedIn. Name the person who will do the work, not only the person who sells it. Where the architect is also the only seller, say so, and say who covers the project while the architect is on a sales call.

Have you fixed something like mine?

This is where careful firms lose. The client agreements forbid naming anyone, so the case notes shrink to "a leading financial services company". That is true and useless.

For example, a CTO at a Bengaluru logistics start-up has just seen a cloud invoice where data transfer costs more than servers. The CTO is looking for a firm that has dealt with that exact line. A case note that reads "a mid-sized logistics platform, three services moved from one region to another, the reporting database moved next to the application that reads it" is something the CTO can believe, even without the client's name. The detail is the proof. The name is only decoration.

Write each case note as five lines: the situation, the stack, what you changed, what the client's team does differently now, and what you would do differently. The last line is what makes it read as written by an engineer.

What does it cost, and against what?

A CTO compares you with three things at once: a freelancer who will log in this weekend, the salary of a senior engineer, and the cloud vendor's own partner team. Your price will not beat the first, so do not argue with it.

Say what the fixed-scope assessment covers, what it hands over and what it leaves for the buyer to decide. Before the call, the buyer should know whether the assessment is paid. Who signs the scope? What does the next step cost to scope? Pricing differs by project, so do not publish a rate card, but do publish the shape of the engagement. A CTO who can see that you scope in writing and put the fee in writing relaxes. The page on content marketing for cloud and DevOps service companies goes into how to write these pages.

Who answers at night?

This is the question the sales deck skips. A managed cloud retainer is sold on what happens during an outage, so write it down: who is on call, how they are reached, what counts as an incident, and what the client's own team keeps. A firm that has written that paragraph looks like it has lived through an outage.

A checklist a CTO would build in their head

What they checkWhere they lookWhat a good answer looks like
Is the work realTechnical posts, case notes, LinkedIn profilesA described project on a stack like theirs
Who does itTeam page, the first callA named engineer who speaks on the call
Can I verify itPartner directory, Clutch, GoodFirms, a referenceA reference they may call after the buyer is serious
What breaks the budgetThe proposalFee, scope and exclusions written in plain lines
Who is on callThe support termsA paragraph, not a badge

Why the checks happen before the call

Most of this checking is invisible to you. It happens on a Sunday evening, after an engineer's recommendation in a WhatsApp group, with the firm's website open in one tab and LinkedIn in the other. If the site cannot answer, the CTO moves to the next name.

That is also why SEO for cloud and DevOps service companies is less about ranking for "cloud" and more about being found for the specific problem the buyer typed: a migration, a cost review, a data-residency question. And the referral page covers the group chats where the first names are given.

What a first call should settle

The CTO's first call with a firm is a screening. They want to hear the engineer who would do the work describe, without notes, a past problem on a stack like theirs. They listen for trade-offs, a mistake corrected and a sense of what was left unfinished. They ask what the firm would not take on. A firm that says no to the wrong work earns more trust than one that says yes to everything.

Prepare for the call by reading what the buyer has published, and ask them to describe their present set-up in their own words. Write down their terms for things, and use the same terms in your reply.

Access and security

A CTO will think about what you can touch. Be ready to explain how you handle credentials, how access is granted and removed, how changes are reviewed and recorded, and who else sees the environment. Offer a written note on access, set up so that each engineer has an individual login and the client can see what was changed. Say what you will not do, such as keep copies of data or work from shared accounts.

Describe your approach to rollback. A CTO wants to know how a change is undone before it is made.

Handing over at the end

Buyers worry about being locked in. Explain what you hand over at the end of an engagement: the code, the documentation, the runbooks and the knowledge. Offer a handover session with the client's team and keep the notes in a place the client owns. A firm that makes itself replaceable on paper is the easier firm to keep.

Making the engagement shape clear

Describe in writing the steps of a typical engagement: a first assessment, a written scope, the work, a review and a decision on what comes next. Say what the client does at each step and what the firm does. Put the fee and the term in writing, agreed with the client, and avoid vague promises about speed or results. A CTO reading such a page can picture the work and judge the fit.

Add a short list of what the client should prepare before the first call: access to the cloud account in read mode, the architecture diagram if there is one, recent bills, and the incident history. Such a list shows how you work, and it saves the first meeting for the real problem.

Reference calls and how to prepare for them

A serious CTO will ask to speak to a client. Choose references who can describe a similar problem and who agreed in writing. Brief them on what the CTO is likely to ask, such as how the engagement started, what went wrong and how it was handled, and let them speak for themselves. Tell the CTO beforehand who the reference is and what they did.

Offer a reference only when the buyer is serious, as you owe your clients their time. Keep a record of who has been called and when.

Showing how you work day to day

CTOs want a picture of working with you. Describe how the work is tracked, how changes are proposed and reviewed, how the client is told what is happening and through which channel. Explain who the client calls with a question. Avoid claims about speed, and let the description show the habit. A short page headed "how we work with your team" turns a vague worry into a concrete answer.

Team size and capacity

A small firm should say so. A CTO prefers an honest account of who is available to a promise of unlimited capacity. State how many engagements the firm takes at one time, who covers during leave and what happens if an engineer leaves mid-project. Buyers forgive size; they do not forgive surprise.

What to do next

Open your own site as a CTO would, with a stopwatch of five minutes. Can you find who will do the work, one project like theirs and the support arrangement? If any of the three is missing, write that page before you spend on anything else.

If you would like the check done properly, tell us what you need, including how enquiries reach you and what happens to them, and we will read it before we call. Start from the industry overview for cloud and DevOps service companies if you want the wider view first.

Put the reading to work

Try this with your own records.

Map existing partners, their territories, and the customers they serve. Review active selling and repeat orders separately from the number of partners signed up.

How to review the result

Follow a partner enquiry through to an order and the next purchase. Check whether the partner has the product knowledge and material needed to sell without repeated intervention.

Questions

Questions owners ask.

Do partner badges from AWS, Azure or Google Cloud matter to a CTO?
They matter as a filter, and little more. A badge tells the buyer you passed the vendor's checks. It does not tell them whether you have moved a system like theirs. Put the badge in the footer and put the described project above it.
How do we show work we cannot name?
Describe the situation, the stack and what changed, and hide only the name. Say the client was a lender with an on-premises core, or a logistics start-up with a runaway data transfer bill. Offer a reference call once the buyer is serious and the client agrees.
Should the engineer who will do the work join the first call?
Yes, when you can manage it. A CTO's first doubt is whether the person selling is the person doing. An engineer on the call who answers a technical question in plain words settles that doubt faster than any slide.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design. One written way to sell, from first enquiry to repeat order.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.