Short answer: Decide which engineering leader actually owns your buying decision, find them on LinkedIn and company sources, confirm they are current, then use a contact data tool for a verified work email and mobile number. Reach out with a short, specific message about a technical or delivery problem they care about, and follow up politely.
Why engineering leaders matter for B2B sales
If you sell developer tools, cloud or infrastructure, cybersecurity, data platforms, API products, QA tooling or engineering services, the CTO or VP Engineering is often a key buyer or strong influencer. In India, many mid-sized product and IT services companies still have a single senior engineering leader who sets stack choices and vendor shortlists.
They get a lot of outreach, so vague "we help engineering teams scale" messages are easy to ignore. Relevance and a clear ask matter more than volume.
Step 1: Pick the right engineering role
Titles and ownership vary by company size and type in India.
- Product and SaaS companies: Chief Technology Officer, VP Engineering, Head of Engineering, Head of Platform, or Engineering Manager for a specific domain.
- IT services and digital agencies: Delivery heads, practice heads, CTO or Head of Technology for the relevant vertical.
- Large enterprises: Separate leaders for infrastructure, application development, security and data. Your product may sit with one of them, not the group CTO.
- Startups: Early on, a technical co-founder often owns everything. Later there may be a Head of Engineering before a full CTO title appears.
- Family-run and traditional businesses: Technology decisions may sit with a CIO, IT head or even an operations leader who manages vendors.
Match the title to who feels the pain you solve. A security product may need the CISO or security head. A CI/CD tool may start with a platform or DevOps lead.
Step 2: Build your target list
- Define your accounts. Industry, company size, city, tech stack signals and any triggers such as funding, hiring spikes or a new product launch.
- Search LinkedIn or Sales Navigator with title keywords such as
CTO,"chief technology officer","VP engineering","head of engineering","head of technology","engineering director"and"head of platform", filtered to India and your target industries. - Use company sources. Leadership pages, careers pages (they often show hiring for reports), GitHub organisations, engineering blogs and conference speaker lists.
- Confirm the person is current. Check that the role shows as present, and watch for recent job moves common in Indian tech.
Step 3: Get verified contact details
Most CTOs and VPs of Engineering do not publish a public email or phone number.
- Use a B2B contact data tool with a LinkedIn Chrome extension to find a work email and mobile number while you view the profile.
- Verify the email before sending, so bounces do not hurt your domain.
- Check a sample of phone numbers to confirm they reach the right person.
- Skip generic inboxes such as info@ or careers@ for first outreach.
- Record the source of each contact and honour opt-out requests.
Step 4: Write outreach an engineering leader will read
Engineering leaders respond to clarity and technical relevance.
- Lead with a concrete problem: deployment risk, release speed, reliability, security exposure, hiring bottlenecks or cost of tooling.
- Be specific to their company. Mention a real signal such as a new product line, a hiring surge for engineers or a public tech choice, without overclaiming.
- Keep it short. Three or four sentences for a first email is enough.
- Make the ask small, such as a 15-minute call or permission to share a short example.
- Avoid buzzword-heavy pitches. Show you understand their stack or workflow in plain language.
A simple structure:
- One line on why you are writing to them specifically.
- One line on the problem you help solve.
- One line on how you help, in plain words.
- A clear, easy next step.
Step 5: Use phone and WhatsApp carefully
Many Indian engineering leaders are reachable on mobile. If you call or message:
- Prefer working hours and avoid major release or outage windows when you can tell they are busy.
- Introduce yourself and the reason in the first few seconds.
- Ask if it is a good time, and offer to send a short email instead.
- For WhatsApp, keep the first message brief and professional; do not send long decks unsolicited.
- Respect a "no" and note it in your CRM.
Step 6: Follow up without pushing
Send two or three polite follow-ups spaced several days apart. Each one should add something new, such as a short technical example or a relevant question. If there is no reply, try another engineering contact at the same company or pause and revisit later.
Common mistakes to avoid
- Writing to the group CTO when a platform or security head owns the decision.
- Sending long emails full of feature lists.
- Using stale titles after someone has moved to a new company.
- Ignoring opt-out requests.
- Pitching "AI" or "transformation" with no link to their actual work.
Where PeakAI fits
Getting a working email and mobile number for the right engineering leader is often the bottleneck. PeakAI is a B2B contact data tool focused on India that finds verified emails and mobile numbers for decision-makers, including from LinkedIn profiles through its Chrome extension. Check thepeakai.com for current features and pricing, and test it on a sample of your own CTO and VP Engineering targets.
FAQ
Should I contact the CTO or a director-level engineering manager?
It depends on deal size and company structure. At large firms, a director or head of platform may own the evaluation. At smaller product companies, the CTO or technical founder often decides.
How do I find the CTO name if it is not on the website?
Search LinkedIn with the company name and title filters, check annual reports for listed companies, and look at recent press or conference speaker bios. Always confirm the role is current.
Is it okay to call a CTO on their mobile in India?
It can work if you are brief, call at sensible times and respect a refusal. Follow applicable privacy laws, get consent where required and honour any request not to be contacted.
What subject lines work for engineering leaders?
Short, specific ones tied to a real problem or their company context beat generic "quick chat" lines. Test a few and keep what gets replies.
How many follow-ups should I send?
Two or three, spaced several days apart, each adding something useful. After that, try another contact or come back later.