An IT services company (ESN) doesn't sell products, stock, or bills of materials. It sells billable time. And that's exactly what almost every ERP on the market fails to model.
Hence the paradox many leaders live through: paying for an ERP reputed to be powerful, then discovering it has no idea what a day rate, a bench, or a timesheet is. So you configure it, adapt it, bolt three tools onto it. The real cost is no longer the license: it's the project.
An ERP for IT services companies exists precisely to avoid that. Here's what it must cover, building block by building block, and how to recognise the one that will hold up.
Key takeaways
- An ERP for IT services companies is software designed for firms that sell intellectual services: it connects the sales pipeline, staffing, timesheets, day-rate billing and margin per assignment in a single database.
- A generalist ERP isn't enough: it counts what you sell, but doesn't cross-reference the 3 variables that make up your margin (day rate, utilization rate, consultant cost). Configuring it often costs more than the license itself.
- The 6 essential building blocks: CRM and sales pipeline, consultant pool and staffing, time tracking and timesheets, bench management, day-rate billing and e-invoicing, margin and profitability tracking.
- These building blocks are worth little in isolation: what matters is that they share the same data. Every break between two tools costs margin, cash flow or administrative time.
- Marvin brings these 6 building blocks together in a native-AI suite: our clients replace an average of 5 to 7 tools and free up around 7 hours per week per consultant.
What is an ERP for IT services companies (ESN)?
An ERP for IT services companies is integrated management software designed for firms that sell intellectual services. It connects the sales pipeline, consultant staffing, time tracking (timesheets), day-rate billing and margin per assignment in a single database. Where a classic ERP manages goods flows, an ERP for IT services companies manages flows of skills and billed days.
The difference comes down to the business model. A manufacturer makes money by producing and selling goods: its ERP tracks stock, purchases, bills of materials. An IT services company, on the other hand, makes money by placing the right consultants on the right assignments, at the right day rate, for as long as possible. Its ERP therefore has to track business objects that manufacturing doesn't know:
- The assignment, time-and-materials or fixed-price, with its start date, end date and day rate
- The consultant, with their skills, availability and cost
- The timesheet, which proves days delivered and triggers the invoice
- The bench, that unbilled time that eats into margin
- Margin per assignment, the gap between the sold day rate and the consultant's real cost
You'll also come across the terms IT services software, ESN management software or IT services and engineering company software (the sector's old name, still in use). They all describe the same reality: a tool that natively speaks the language of consulting, rather than a generalist tool bent out of shape to look like it does.
Why a generalist ERP isn't enough for an IT services company
The answer fits in one sentence: a generalist ERP knows how to count what you sell, but not what determines your margin.
In an IT services company, profitability rests on 3 variables that are constantly moving:
- The sold day rate, which varies from one assignment to the next
- Consultant utilization rate, which decides what is billable or not
- Consultant cost, fully loaded salary or subcontractor rate
No generalist ERP cross-references these three variables natively. It will give you signed revenue, not margin per assignment. And it's margin that tells you whether the deal was worth it.
Utilization rate — the indicator your ERP should give you in real time. A healthy TACE (utilization rate excluding leave) for an IT services company sits around 75 to 85%. Below that, profitability drops off. Every point lost is payroll cost paid with no billing to match it. An ERP that doesn't track this indicator continuously leaves you discovering the problem a month too late, on a spreadsheet.
Configuration costs more than the license. This is the classic trap. For a generalist ERP to handle a time-and-materials assignment, you have to create custom objects, bolt on a time-tracking tool, another for billing, and maintain the connectors between the three. You're no longer paying for software: you're funding an integration project, with a dedicated administrator and custom development for every change.
You end up with a fragile system, where data is scattered across several building blocks that have to talk to each other. And every break between them costs margin, cash flow or administrative time. That's exactly what IT services software built for the business avoids from the start.
The 6 building blocks IT services software must cover
Here's the checklist to apply to any solution on the market. If any one of these 6 building blocks is missing or lives in a separate tool, you'll pay for the break somewhere — in margin, in cash flow, or in administrative time.
1. CRM and the sales pipeline
This is the starting point: client accounts, opportunities, commercial proposals. But a CRM for IT services companies can't stop at the signature. It has to know that an opportunity turns into an assignment, staffed by a consultant, at a given day rate.
What breaks if this block is missing: sales sells without seeing who's available, promises unrealistic timelines, and staffing finds out about the need too late. We cover this topic in detail in our dedicated article on ESN CRM.
2. Consultant pool and staffing
Your capital is your consultants. The tool must therefore keep their skills, availability, assignment history and cost up to date. This is what lets you respond quickly to a client need: which profile, available when, at what day rate.
What breaks if this block is missing: it takes you 3 days to respond to a tender while your competitor answers in 3 hours. And you miss deals you could have served.
3. Time tracking and timesheets
The timesheet is the piece of evidence that proves service delivered and triggers the invoice. It must be entered once, validated by the manager and then the client, and automatically feed validated days into billing.
What breaks if this block is missing: your sales administration team spends month-end chasing people, the invoice slips, and your cash flow ends up financing your client's. We covered this point in detail in our article on timesheet software.
4. Bench management
The bench is salary paid with no billing to match it. A good tool doesn't just record it: it anticipates it. An assignment end date known 30 days in advance should trigger an alert on the sales side, so the consultant can be repositioned before the gap hits.
What breaks if this block is missing: you suffer the bench instead of managing it. Every consultant on the bench at a €600 day rate represents roughly €12,000 of unbilled revenue per month.
5. Day-rate billing and e-invoicing
The invoice must be generated from the validated timesheet — days × day rate — with no re-entry. And from 1 September 2026, under French regulation, e-invoicing requires structured invoices transmitted via an authorised platform: a PDF sent by email is no longer sufficient between businesses.
What breaks if this block is missing: double entry between time tracking and accounting, discrepancies, credit notes to issue, and non-compliance that comes with penalties.
6. Margin and profitability tracking
This is where the previous 5 building blocks culminate. Because the sold day rate, consultant cost and days delivered all live in the same system, margin calculates itself, assignment by assignment, client by client, in real time.
What breaks if this block is missing: you steer by looking in the rear-view mirror. You find out an assignment wasn't profitable once it's over — that is, once it's too late to renegotiate.
The rule to remember: these 6 building blocks aren't worth much in isolation. What matters is that they share the same data. An excellent CRM bolted onto a timesheet tool through a temperamental API will always produce discrepancies, re-entries and blind spots. It's continuity that creates value, not stacking.
Monolithic ERP or AI-first suite: the real choice for 2026
Most ERPs for IT services companies on the market were designed 15 to 20 years ago. They get the job done, often well. But they were designed at a time when AI didn't exist inside the product, and profile sourcing was done by hand.
The result: they add AI in successive layers, module after module, onto an architecture that wasn't built for it. An assistant here, some matching there, grafted onto a legacy foundation.
An AI-first suite reasons the other way around: AI isn't a bolted-on feature, it's the foundation. That's the stance we took with Marvin.
One dataset, several apps
With us, the 6 building blocks aren't 6 modules you have to connect. They're apps that share the same data:
- Desk carries the CRM and sales pipeline: accounts, opportunities, assignments
- People holds the consultant pool: skills, real-time availability, assignment history, contracts
- Cash generates day-rate billing from the validated timesheet, with gross margin per assignment
The assignment created by sales feeds the consultant's timesheet, which triggers the invoice, which displays the margin. No connector to maintain, no re-entry, no possible gap between what's sold, delivered and billed.
What native AI actually changes
It's not there to look good in a brochure. It's there to respond faster than a competitor: semantic sourcing to find the right profile in your pool in seconds, autonomous agents that handle repetitive tasks, account prioritisation based on market signals.
Our clients replace an average of 5 to 7 tools with a single platform and free up around 7 hours per week per consultant on administrative tasks.
At a glance:
| Legacy ERP for IT services companies | AI-first suite | |
|---|---|---|
| Architecture | Modules connected by API | A single shared dataset |
| AI's role | Added in successive layers | The foundation of the product |
| Profile sourcing | Keyword and filter search | Semantic, in natural language |
| Timesheet to invoice | Often 2 tools to sync | Continuous, no re-entry |
| Getting started | Integration project, configuration | Business objects already modelled |
| Repetitive tasks | Done by hand | Delegated to agents |
Marvin versus BoondManager and Salesforce
Two names dominate IT services companies' shortlists. Here's what they bring, without detour, and where we position ourselves differently.
BoondManager is the sector's reference ERP in France. What it does better: mature, proven business coverage, refined over more than 15 years, with an open API and a high level of certification. An IT services company looking for a complete, classic ERP will find what it needs there.
Salesforce is the most powerful CRM on the market. What it does better: infinite customisation and functional depth for very large organisations. But it's a generalist: it has no native understanding of day rates, bench, or timesheets. Getting it to speak the language of IT services companies means a configuration project, third-party building blocks and a dedicated administrator.
Our bet is different: a native-AI suite, where the CRM, the pool, timesheets and billing share the same data, with no connector to maintain. For an IT services company that recruits as much as it staffs, this continuity between profile sourcing, staffing and billing changes daily operations.
We break this comparison down feature by feature in our dedicated analysis: Marvin vs BoondManager.
Choosing an ERP for IT services companies means choosing where your data will live
The right ERP for IT services companies isn't the one that ticks the most boxes. It's the one that connects what your business already connects: an opportunity becomes an assignment, the assignment is staffed, the consultant submits their timesheet, the invoice goes out, the margin shows up. This chain exists in your day-to-day operations, whether your tool models it or not.
If your software splits it into separate modules, you'll spend your time gluing the pieces back together: re-entries, discrepancies, endless month-end closes, a bench discovered too late. If your software respects it, steering becomes a consequence, not a project.
This is what we built for IT services companies and consulting firms: a continuous chain, from first commercial contact through to cash collection, in a single platform built for IT services companies.
Want to see what this looks like for your business? Book a demo: we'll show you the complete journey in real conditions, from opportunity to margin, using your own use cases.
Frequently asked questions about ERP for IT services companies
What's the difference between an ERP and a CRM for an IT services company?
The CRM covers pre-sales: accounts, opportunities, proposals, sales pipeline. The ERP covers post-signature: consultant staffing, time tracking, billing, margin per assignment. In practice, this boundary is artificial for an IT services company, whose real chain is continuous: opportunity, staffing, timesheet, invoice, margin. The real question isn't choosing between the two, but avoiding breaks between them. We go deeper on this in our article on ESN CRM.
Can a generalist ERP be configured for an IT services company?
Technically yes, economically that's another story. A generalist ERP knows nothing of day rates, bench, or timesheets: you have to create these business objects, bolt on third-party tools for time tracking and billing, then maintain the connectors with every change. The real cost isn't the license, it's the integration project and the administrator you have to dedicate to it. Software built for IT services companies arrives with these objects already modelled.
What's the best software for an IT services company?
There's no single answer: it depends on your size, your model (time-and-materials, fixed-price, recruitment) and how mature your tooling already is. The right selection criterion isn't the length of the feature list, but the continuity of data between the CRM, staffing, timesheets and billing. Ask yourself a simple question for each solution: how many times will the same piece of information have to be entered? If the answer is more than once, the tool will waste your time.
How much does an ERP for an IT services company cost?
Market pricing generally ranges from a few thousand to several tens of thousands of euros per year depending on company size and the modules chosen. But the sticker price says little about the real cost, which includes configuration, integration with your existing tools, training, and administration time. A cheaper tool that requires 3 third-party building blocks often costs more than a single platform.
Is IT services and engineering company software the same as IT services company software?
Yes. IT services and engineering company (the French acronym is SSII) is the old name for what's now called an IT services company (ESN, "entreprise de services du numérique"). The term is still used, but it describes the same reality and the same needs: managing assignments, consultants, timesheets and day-rate billing. Software built for one covers exactly the same scope as software built for the other.
What software should a small, newly launched IT services company use?
A small structure doesn't need a heavy ERP, but from its very first consultant it needs the same building blocks: tracking deals, staffing, collecting timesheets, billing, knowing its margin. The classic trap is starting on Excel, then stacking tools as you grow, and ending up with scattered data you'll eventually have to migrate. Choosing a platform that covers the whole chain from day one avoids that project. Migrating existing data is handled when you come on board: the best way to judge that is to book a demo.
