To sell to a CTO or an IT director, lead with one specific technical problem and one thing they can check in a few minutes, not a pitch about transformation. Then expect the sale to run through other people: the engineer or admin who feels the problem, a security review and a budget owner. A CTO at a 60-person startup decides quickly and wants to see the product; an IT director at a 600-person company decides slowly and wants to see the paperwork. This page is about selling business software and services to those two buyers.
Two buyers with the same title
The startup CTO. Often the first or second engineer, now managing a team and a cloud bill. They have the authority to buy a tool that costs a few hundred dollars a month and the habit of trying it before talking to anyone. They dislike sales calls and respond to a product they can start in an afternoon, a clear price and documentation that answers their question. Their scarce resource is attention.
The IT director. Responsible for systems, support, security and the vendors that touch them, in a company with a procurement process. They will not buy on a first email, and are not meant to. Their job is to avoid the incident that comes from an unvetted vendor. They respond to a seller who understands the process and makes it easier: a security summary, a data-processing agreement, a reference at a similar company.
Decide which one you are writing to before you write. A message that suits one reads wrongly to the other.
Reach the person who feels the problem
The CTO is rarely the first person to feel a problem with backups, deployment, access control or monitoring. A platform engineer, a systems administrator or a team lead is. They are also the person a CTO will ask, "does this look right to you?" So there are two good routes: write to the CTO with a message the engineer would forward, or write to the engineer and make it easy to forward upward. Either way, the person you write to should be able to tell, from the first two lines, whether the problem is theirs. For who owns what at a given company, see how to find decision makers at a company, and for the next step, how to get meetings with decision makers.
What a technical buyer reads in a first email
- The problem in their words. "Backups run but nobody tests a restore" beats "data resilience".
- One checkable fact. A detail from their public footprint, such as the stack in their job posts or an engineering blog post, shows you looked.
- No adjectives they cannot verify. "Industry-leading" tells them you have nothing specific.
- A small next step. A two-page note, a sandbox link or a sample report, not a demo.
- Your name, your address and a way to stop. The CAN-SPAM Act requires a valid physical postal address and an opt-out in a commercial email (15 U.S.C. 7704(a)(5)(A), read 2026-11-15).
Here is a worked message. Dana Whitfield sells a tool that tests database restores for engineering teams. It costs $900 a month.
Subject: Restore testing for your Postgres backups
Hi {{first_name}}, I noticed your team is hiring a second platform engineer and your job post mentions Postgres on a managed cloud service. A nightly backup only helps if the restore works, and the restore is the step that is easy to leave untested. I built a tool that restores last night's backup into a throwaway environment each week and tells you whether it worked and how long it took. Would a sample report from a restore of a database like yours be useful?
Dana Whitfield, [Company Name], [postal address]. If you would rather not hear from me, reply "no" and I will not write again.
It is two short paragraphs, names a real problem and one fact about the reader, and asks for the smallest yes. The tool is described in one sentence, and the claim is about what it reports, not a promise of outcomes.
Price against the incident
A technical buyer will do the arithmetic whether or not you do. Do it for them, with a number they can replace. Suppose, as an assumption, a failed restore during an outage ties up 2 engineers for 6 hours at a loaded cost of $85 an hour: 2 times 6 times $85 is $1,020 for the engineers alone, before the lost sales or the support load. A weekly restore test costs $900 a month, or $10,800 a year. On engineer time alone it breaks even only if it prevents about 11 such incidents a year (10,800 divided by 1,020 is 10.6), which is unlikely, so the case rests on what an outage costs the business, not on the hours. Say that out loud, because telling a CTO where your numbers stop is more credible than stretching them. Then ask what an hour of downtime costs them, and let them fill in the figure that decides it.
Clear the security review before they ask
For the IT director, and for a startup CTO who sells to enterprises themselves, the security review is where a deal can stall. Prepare these before the first call:
- A one-page security summary: where data lives, who can see it, how access is controlled and how you handle an incident.
- Any third-party attestation you hold, with its date. Do not claim one you do not have.
- A data-processing agreement ready to sign.
- A list of the subprocessors you use.
- A named reference at a company of similar size who has been through the review.
If you have none of these, say so and tell the buyer what you have: a short security note and a willingness to answer a questionnaire. A gap you state up front is easier to work through than one the buyer finds later.
The trial and the call
Expect a startup CTO to try the product before agreeing to a call. Make that path short, and make the first useful output arrive in minutes. On the call itself, spend the first part asking about their setup, and the rest answering what they ask. The questions to expect are: how does it connect, what does it need access to, what happens to our data if we stop, and what does it cost when we grow. Have each answer ready in a sentence. For what to do when a buyer pushes back, how to handle sales objections goes through the common ones, and how to sell to CFOs covers the buyer who will ask for the cost case after the technical review passes.
Mistakes that end the thread
- Opening with "I know you are busy". They know.
- Naming their stack wrongly. A wrong detail is worse than none.
- Hiding the price. A technical buyer will look for it on your site; if it is missing, they will assume it is high.
- Asking for the CTO's time when an engineer could answer. Offer something an engineer can try alone.
- Sending the same message to a CTO and an IT director.
Rocketship finds the CTOs and IT directors who fit a description (company size, industry, role), emails them from your own Gmail, follows up, answers replies and books the meeting; plans start at $12 a month, with a 7-day trial, card required. It will not pass a security review or run the demo for you.