Who decides on implementation and support
Implementation and automation purchases rarely have one decision-maker. In smaller businesses, budget ownership often sits with the founder or commercial director, while technical evaluation is handled internally. In larger organisations, the IT director is usually the first relevant contact: they carry responsibility for system failures and look for outside support when the internal team cannot cover the task.
For 1C partners, the decision map is different. Configuration purchases and support commonly involve the finance director or chief accountant: they feel reporting, labelling, and document-exchange problems first, even if final approval sits elsewhere. Their message must be easy to forward upward—one problem, one timeframe, one concrete outcome, without technical jargon.
That is why we segment by recipient as well as industry. The same service needs different outreach for an IT director and a finance leader; a universal email usually fits neither.
Building a relevant prospect list
- Company registries. Businesses in wholesale, manufacturing, logistics, and services can be filtered by region, revenue profile, and operating scale.
- Hiring signals. A company looking for an ERP developer, implementation specialist, or systems administrator may have an active need that internal hiring has not resolved.
- Procurement activity. Requests for implementation, customisation, and system support reveal buyers with a defined need, as well as contractors who may need subcontracting capacity.
- Software ecosystems and regional partners. These are useful maps for partnership offers and subcontract work.
- Professional Telegram communities. Finance leaders, chief accountants, and IT managers often use Telegram as a working business channel, including people who are less reachable by email alone.
We do not treat a purchased directory as a campaign-ready list. Every list is checked and deduplicated before launch. Across our campaigns, 811,200 companies have received a contact and the bounce rate was 2.3%; that outcome comes from list quality, not chance. Learn more about lead list building.
Offers that get attention
A narrow offer with a defined task works: bringing reporting onto a current release before a filing deadline, setting up a required data exchange, support with a stated response commitment, or a fixed-scope infrastructure audit. For integrators, a pilot automation area or subcontracting support for an overloaded project stage can also be a credible entry point.
Broad claims such as “end-to-end business automation” or “we implement any system” do not help. Technical buyers recognise vague marketing quickly. The first message should state one service for one segment with one measurable outcome and finish with one question that is easy to answer.
Email is the primary channel. Telegram is especially useful for finance directors and chief accountants in the 1C segment, because it is a normal business channel in Russia and the CIS and is often read more consistently than email. We can coordinate channels through multichannel outreach.
Common objections and how to handle them
- “We have an in-house developer.” Do not argue. Start with a task one person may not be able to cover, such as a migration, a reporting deadline, or a complex update.
- “Another firm supports us.” Offer an entry point rather than an immediate replacement: an independent review, a second opinion on scope, or help with a task the current contractor does not take on.
- “Send a proposal.” A generic document is often a deferred refusal. A short relevant summary, a price range where appropriate, and a focused question create a better next step.
- “Not now.” This may be genuine. Record the timing and return when the reporting cycle or project window makes the conversation relevant.
Reply handling needs structure and speed. In implementation work, buyers often look for a contractor when a problem is already urgent, so a warm reply left unanswered can disappear quickly. See reply handling and lead qualification.
What to expect from launch and sales timing
A campaign needs preparation: defining the segment and recipient, building and checking the list, and writing messages for each decision-maker. Replies can appear early in the outreach cycle, while revenue from implementation work usually follows a longer B2B buying process.
Across our campaigns, 3,224,000 emails have been sent to 811,200 companies. Of those companies, 48,100 replied, or 5.93%, and 6,500 gave a clear yes by requesting details, a proposal, or a meeting. These are portfolio-wide figures, not a promise for a specific campaign; in this segment, timing and relevance to a live business trigger matter greatly.
We count only explicit requests as results. Opens, clicks, and “interesting, contact us later” are not qualified leads; see our lead guarantees.
When outreach is not the right fit
- You have no completed implementation that can be described concretely. Build a credible offer and proof of delivery before approaching a cold audience.
- Your average deal cannot support the time needed to develop and close a lead. You may need a larger project scope or a different acquisition channel.
- Your team is fully booked with referrals and tenders, or nobody can respond to incoming interest during the working day.
- You want to contact every company using 1C. Without one initial segment and one reason to talk, the campaign becomes noise rather than prospecting.
Entering a new region or an adjacent client segment is a separate scenario. It requires a list and message built for that market from the start; see B2B outreach across Russia and CIS.