IT services and integrators: find companies ready to change tools

For an IT services firm or integrator, the best prospect is the one whose tools are starting to crack. Follow-ups get lost between two spreadsheets, the month-end close takes two weeks, the figures for the leadership team never match. By the time the company issues a tender, it is already late: five of you are bidding on the same project and the discussion is about price. This article lists the signals that appear earlier, and how to turn them into a first message that leads to a meeting.

Why does a company change its tools at a specific moment?

Changing CRM, ERP or a business application is expensive and daunting. Nobody does it out of curiosity. The company makes the call when the pain outweighs the cost of change, and that almost always happens after an event: fast growth, an acquisition, a new leader, a new obligation.

These events leave public traces. A hire, an announced funding round, a sales director’s post asking for others’ experience. Spotting them early lets you arrive while they are still thinking, before the need is written into a specification. For the specific case of ERP, see also the signals that announce an ERP migration.

Which signals show a company is about to change its tools?

Signal	What it points to	Where to see it
Hiring a RevOps lead, IT project manager or CRM administrator	Tool project launched or imminent, budget released	Job postings, LinkedIn
New IT director, finance director or sales director	Review of tools and providers in the first months	LinkedIn (new role)
Funding round	Hiring, new teams, current tools outgrown	Business press, LinkedIn
Acquisition or merger	Two systems to bring together, customer data to merge	Press, press releases
New sales team or entry into a new country	Need for a CRM, territory rules, reporting	Job postings, expansion announcements
Regulatory deadline (e-invoicing, for example)	Finance and invoicing tools to adapt	Official timetable, company size
Public question about a migration or a tool	Active evaluation phase	LinkedIn posts and comments, forums, groups
Negative user reviews of their current tool	Dissatisfaction, search for an alternative	Review platforms, public comments

E-invoicing mandates are rolling out across Europe, and France gives a concrete example of such a deadline: since 1 September 2026, all VAT-registered businesses must be able to receive e-invoices, and large and mid-sized companies must issue them; SMEs follow on 1 September 2027 (economie.gouv.fr). For an integrator of finance and management software working in France, that means a whole year of SMEs having to adapt their tools.

How do you rank these signals?

1. Hiring the person who will own the project. This is the clearest signal: the company has put budget for a person on the problem.
2. A new decision-maker in the area. A newly arrived IT or sales director reviews the tools they inherit. See the job change as a buying signal.
3. A public question about a migration. The person is already comparing options.
4. An acquisition or merger. The project is almost certain, but the timing depends on the integration.
5. A funding round. The need will come, often a few months later, with the new hires.

Two signals on the same account are worth more than a single strong one. A company that has raised funds and is hiring a RevOps lead is right in the middle of it.

What does a good opener look like for an IT services firm or integrator?

The classic mistake is to open with your certifications or the name of the vendor you partner with. The decision-maker doesn’t think in software, they think in problems: lost follow-ups, wrong reports, data entered twice. The opener should start from the change they are going through and end with a simple question.

Illustrative example

Signal: a 120-person manufacturing SME posts a job for a “sales administration and CRM manager”.

Opener that fails: “Hello, we are a Gold partner of several CRM vendors and have completed over a hundred implementations. We would be delighted to present our expertise in a 30-minute call.”

Opener that gets a reply: “Hi Sophie, you’re hiring someone to run sales admin and the CRM: often that’s when you find out quotes still live in three different places. Does the role come with a tool project, or is it first about getting the current setup in order?”

The good version shows you understand what lies behind the job posting. The question lets the prospect describe her project, which naturally opens a conversation. More on this signal in job postings as a buying signal.

Illustrative example

Signal: a distribution group announces the acquisition of a regional competitor.

Opener that fails: “Hello, congratulations on the acquisition! We support companies in their digital transformation. Are you available to discuss?”

Opener that gets a reply: “Hi James, after an acquisition, the question of the two customer databases comes up fast: who keeps which account, which base is the reference for invoicing. Have you already decided whether the acquired teams move onto your tools, or will you keep both systems during the integration?”

The failed version says nothing the prospect doesn’t already know. The good one names a specific problem every acquisition creates, and asks a timing question: exactly what you need to know to suggest a meeting at the right moment.

How do you turn a reply into a meeting?

A reply is not a meeting. For an IT services firm, the meeting is justified when the prospect sees what they will get out of it. Three simple rules:

• Qualify through the conversation. The prospect’s reply tells you whether they have a project, a timeline and who decides. Ask one more question if it isn’t clear.
• Suggest a meeting with a purpose. “30 minutes to look at how other companies handled merging their customer databases” beats “a presentation of our services”.
• Talk about results. Time to close the books, reliability of reporting, how quickly a new salesperson gets up to speed. The software comes after.

The detailed method is in from buying signal to meeting.

What mistakes should you avoid?

• Opening with your vendor partnerships. They reassure later, not in the first line.
• Reacting on the day of a funding round or acquisition. Everyone does. Wait for the consequences to show.
• Writing to the wrong person. The new RevOps lead has no budget yet; the finance director does. Sometimes you need both.
• Confusing interest with a project. A like on a post about CRMs doesn’t mean the company is changing CRM. Stack signals before you write.
• Sending the same sequence to everyone. An integrator sells tailored work: a generic message contradicts its own trade.

How do you track these signals day to day?

The signals that matter to IT services firms are scattered: new roles and questions on LinkedIn, job postings, business press, software reviews. MeetMagnet spots LinkedIn signals every day (decision-makers’ posts and reactions), links them to your offer and suggests an opener written from the signal, reviewed before sending. Job postings, the press and reviews are covered by the multi-source option of the Assisted plan. The details by source are on our signal sources page.