Where to start when selling to the IT director
Selling to the IT director means showing that your solution fits what the company already has without opening new risk. If a technical question is left without an answer, they become the influencer who blocks the purchase at the end.
In sales to a large company, the IT director decides purchases of infrastructure or core systems. For other purchases, they run the technical review of what another department requested: they gain little if the project succeeds and lose a lot if it fails. So show that the project has controlled risk and will not become a problem for their team.
What the IT director assesses
The questions vary with segment and size, but six topics show up in almost every technical review:
- Stack. Does the solution coexist with the systems the company already uses, or does it require replacing one of them?
- Integration. How data goes in and out (API, ready-made connector, file, webhook), who builds it and who maintains it.
- Security. Access control, roles, a log of who did what, encryption and what happens in an incident.
- LGPD (Brazil's data protection law). What personal data the solution handles, on what legal basis, where it is stored and how it is deleted.
- Project risk. Implementation time, dependence on the internal team and how to exit if it does not work.
- Cost to maintain. How many people on their team will look after the solution once the vendor leaves.
Read the company's stack before the meeting
The IT director can tell within minutes whether the rep knows the company's systems, and much of that is public: tech job postings name the tools required, the company website shows the platform it runs on, vendor announcements name customers and professional profiles show what the team works with.
With the stack in hand, prepare three answers: where your solution connects to what already exists, where it competes with something the company already pays for and what the company would need to change for the project to work. The IT director values the third most, because almost no rep brings it up.
A stack mapped from the outside is a hypothesis, so bring your doubts as questions: instead of stating that the company uses a certain ERP, ask how the integration with it has been since the last version upgrade.
Security and LGPD: what to have ready
At a large company, the security review often comes as a questionnaire that takes weeks when the vendor did not prepare. Bring ready what is usually requested:
- Where the data is stored and who has access to it.
- How access roles and login work, including with the company's identity provider.
- The privacy policy and each party's role under LGPD: who is the controller and who is the processor.
- The incident response process and the deadline for notifying the customer.
- How data is returned and deleted at the end of the contract.
- Security certifications and reports your company already has, without promising what it does not.
How to handle project risk with the IT director
Technology projects run late for known reasons: integration harder than expected, an internal team busy with another priority, scope that grows midway. The IT director has lived through these delays and will ask how you avoid them.
Answer with a plan in stages, each with its own deliverable and success criteria agreed in advance. Say how much of their team's time each stage requires and what happens if one of them fails. A small pilot, with a start and end date, reduces the risk they see.
Typical objections and how to answer
For each common IT director objection, bring proof of what you claim:
| Objection | What is usually behind it | How to answer |
|---|---|---|
| My team has no time for this | Another priority takes up the same team | Show how much time each stage requires and what stays with the vendor |
| We already have a tool that does this | Fear of a duplicate system | Show where the two coexist and where yours covers what the other does not |
| The integration will be complicated | A bad experience with a previous project | Show the integration method, what comes ready-made and who maintains it |
| What if you go out of business? | Vendor dependence | Explain how the data comes out, and in what format, at any time |
Agenda for the first meeting with the IT director
In the first meeting with the IT director, leave the product demo for later and talk about fit and risk, in five steps:
- Open with the business area's request and say you want to understand the technical side before moving ahead.
- Confirm what you know about the stack, in the form of a question.
- Show how the solution integrates and what it requires from their team, without hiding anything.
- Ask which criteria the technical review will use and who else takes part in it.
- Agree on the next step, with a date: the security questionnaire, a technical session with the team or the pilot design.
How GoSeek helps prepare the technical conversation
The GoSeek dossier has a Stack section, with the technology that shows up in use at the company and the grade of proof for each system (confirmed, likely or indication), and a Complexity section on the operation. The Risks and Objections sections anticipate what can stall the deal and what each decision maker may raise.
The power map shows where the IT director sits in the decision and who else influences the technical review. GoSeek builds the dossier in 7 to 15 minutes from the CNPJ, the Brazilian company tax ID, with 100 to 500 public sources. For the conversation with finance, read how to sell to the CFO; to choose the companies before that, see company intelligence for sales. The prospecting maturity assessment, with 18 questions, shows whether your team already prepares the technical conversation before the meeting.
What comes out about the company
Stack, complexity and risks in the dossier prepare the technical conversation
What people ask about how to sell to the IT director
What does the IT director assess before approving software?
Whether the solution coexists with the current stack, how it integrates, how it protects data, how it handles LGPD, what the project risk is and how much of their team it will take to maintain.
When should IT get involved in a B2B sale?
Early. When IT joins only at the end, it finds a finished project that nobody checked for fit, and the technical review becomes the reason for the delay.
Founder of GoSeek. Specialist in market intelligence and consultative B2B sales for the enterprise market.
Keep reading
How to sell to the CFO
How to sell to the CFO: what the finance chief wants to hear, how to prepare with the company's public numbers, the typical objections and a meeting agenda.
Power map in sales
Power map in B2B sales: economic decision maker, champion, influencer, entry point and user, how to map them and the questions that validate it.
Sales battlecard
Sales battlecard: what goes in it, why most go stale on a slide and how to build one per company, with competitors, objections and ready questions.