Who to contact when several roles approve an IT project
There is no universal decision-maker for custom development. At companies without a strong internal IT function, the owner or commercial director may be the first contact: they care about launch timing and a manageable budget. In product companies, a CTO, Head of Product or engineering leader is more likely to begin a substantive discussion. HR matters when you sell staff augmentation, but rarely chooses the supplier alone.
| Role | Likely constraint | How to open the email |
|---|---|---|
| Owner | A new feature is waiting, while expanding the permanent team feels risky | “I noticed you are developing a customer portal. Is there a feature you need released before expanding the team?” |
| CTO | A specific capability or team capacity is missing | “Is the more pressing need mobile development, backend capacity, or QA?” |
| CPO / Head of Product | A product hypothesis is waiting for development | “Do you bring in an external team to validate product hypotheses in a separate sprint?” |
| HR director / recruiter | Open roles remain unfilled while workload grows | “Would temporary team reinforcement be relevant until permanent engineers join?” |
Research starts with the role, not a job title exported from a database. If a company is hiring both backend developers and a product manager, approach the technical or product leader. If it is launching a new service without hiring, begin with the product owner. Agree lead definitions with sales in advance so the sender and the person taking the conversation share the same qualification criteria.
Signals that show an upcoming development need
A list for software-development outreach cannot be built from one industry code. It will include studios, end customers and companies with no current need. Look for observable events instead. For staff augmentation, that may be several vacancies in one technical specialism, a new technology leader or a growing engineering team. For custom development, it may be a new portal, app, marketplace, loyalty programme or regional launch.
- Select sectors where a digital product affects revenue: finance, logistics, e-commerce, education, and manufacturing with dealer networks.
- Review company sites, vacancies, product announcements, app-store pages and partner sections.
- Record the evidence in the account: not “an IT company,” but “hiring three Kotlin engineers” or “launched a B2B portal.”
- Identify two roles: the owner of the task and the technical approver. One recipient should not be the only entry point.
Useful public sources include career pages, industry rankings, accredited-organisation registers, event sites, tender notices, app listings and hiring news. Lead research can be separated into a dedicated lead-list-building process, with addresses checked before sending through list verification.
Why an offer of available developers usually gets no reply
“We can provide experienced developers at a competitive rate” gives the recipient no reason to reply now. It names neither the bottleneck nor a low-risk way to assess the fit. A better opening combines a specific task, relevant specialism and a question that can be answered in a few words.
Weak: “We are a full-service studio building websites and apps. We would be glad to discuss cooperation.” It has no recipient-specific reason or next step. Better for a company with open roles: “We saw you are hiring two Go developers. While you recruit, would you consider an external team for a separate service, or only permanent hires?” It does not promise to solve everything; it clarifies the current constraint.
- For an MVP, offer to assess one user journey or disputed module rather than “build the whole product.”
- For staff augmentation, name the stack and engagement format; do not attach anonymous CVs in the first email.
- For modernisation, ask about a specific area: integrations, mobile app, customer portal, QA or support.
- For agency partners, offer reserve capacity for a client project with a clear area of responsibility.
When a studio sells design, development, operations, marketing and analytics all at once, the email becomes a price list without prices. Choose one task for the first wave. Partner outreach needs a separate scenario because the buyer’s motive and sales cycle differ from those of an end customer; see white-label outreach for agencies.
How to respond to “we have an in-house team” and “send a proposal”
“We have an in-house team” does not necessarily rule out external support. It often marks a boundary of responsibility: the recipient may not want to change suppliers or acknowledge a capacity gap. Do not argue. Ask whether there are tasks the internal team has postponed because of priorities, a rare stack or limited testing capacity.
The exchange can be simple: “We build internally.” — “Understood. Do you avoid external suppliers entirely, or bring them in selectively when a separate workstream needs to be taken off the team?” If they name a workstream, the conversation is now specific. If they say they are not looking, record the refusal and do not send a sequence of proof points.
Do not answer “send a proposal” with a generic deck. Return a question first: “So I do not send something irrelevant, which is closer to your current need: a dedicated team, a module build, or reinforcement in a specific stack?” Once they choose, send a short relevant document and invite the technical lead into the conversation. Consistent handling of these replies is part of reply handling and lead qualification.
How to assess a campaign without promising meetings
A software-development deal rarely comes from one email. The buyer checks the stack, portfolio, availability and supplier-security requirements. Assess the campaign as a sequence: did the address accept the email, did the recipient answer the question, did they confirm a task, and did they agree to a next conversation? Across our campaigns, 3,224,000 emails have been sent; 811,200 companies received outreach and 48,100 companies replied.
- Before launch: define one ICP, one first-wave service and a stop-list of unsuitable companies.
- After the first wave: review reasons for replies and refusals, not just sending volume.
- After conversations: record which roles reply and which tasks they name.
- Before scaling: change one element only — the segment, signal or wording of the question.
Preparation takes time for account research, contact checks and sending setup. The earliest useful report is not a sales promise but an analysis of the first replies: whether the company list matches the offer and whether recipients understand what you are proposing. If you need email, Telegram and professional-network outreach in one process, choose channels by decision-maker availability rather than fashion; see multi-channel outreach.
When software-development outreach is not for you
Do not launch the channel if you sell “development in general” and cannot name the first deal’s concrete result: an MVP within a defined sprint, migration of a specific service, or reinforcement in a particular stack. It is also unsuitable for a studio without proven cases, available specialists, a clear start date and an accountable manager. Emails will then create questions your team cannot answer quickly.
Outreach is weak where supplier selection happens only through a closed tender, mandatory accreditation, security review or an existing supplier’s recommendation. Do not rely on cold outreach in regulated fields such as healthcare, finance, industrial automation or the public sector if you lack the required certifications, approvals and relevant work. The channel cannot create budget, urgency or an internal sponsor where none exists.
It is not suitable for staff augmentation if you cannot confirm the stack, start date, management model, replacement terms and difference from ordinary hiring. For custom development, outreach is premature when estimation takes weeks, technical presales is absent, or you cannot define the result’s boundaries. Remove these constraints first and test the hypothesis on a small manual sample.