Skip to content

BlogCraft

ERP or CRM for an IT consulting firm: which one do you need?

A CRM is enough for an IT consulting firm while each fact lives in one place. You need an ERP once availability, rates and timesheets are copied between tools.

13 min read

An IT consulting firm needs a CRM from its first client, and an ERP from the day a single fact has to serve several parts of the business at once. Think of a consultant’s availability, which sales and staffing both need, an engagement’s day rate, which sales and invoicing both read, or the days on a timesheet, which feed invoicing as well as payroll. As long as each of those facts is written in one place only, a CRM and an invoicing tool are enough. Once it is typed in twice, the question is no longer which software to buy, but which one to believe.

It is the rule we apply to our own systems and to those of the firms Balt works in: the number of tools matters little, the number of copies of the same fact matters a great deal. It has a very practical merit. It replaces a catalogue question, answered by every vendor with a product sheet, with a question only you can answer: how many times, in your firm, is a consultant’s end-of-assignment date typed in by hand?

What does an IT consulting firm’s software have to hold?

The software of an IT consulting firm has to hold six families of facts, and what makes the trade unusual is that none of them serves a single department.

Family of facts What it contains Who uses it
Clients and requirements accounts, contacts, open requirements, proposals sales
Candidates and consultants skills, availability, skills dossier sales, recruitment, staffing
Staffing positionings, current assignments, end dates staffing, sales, management
Time timesheets, absences, leave invoicing, payroll, managers
Invoicing purchase orders, invoices, payments received finance, management
Margin per engagement day rate sold, consultant’s daily cost, margin management, account managers

Follow a single fact from one end to the other and the software question changes shape. An engagement’s day rate is negotiated in the opportunity, written on the purchase order, multiplied every month by the days on the timesheet to produce the invoice, then compared with the consultant’s daily cost to give the margin. That is four uses of the same figure, and sometimes four entries. Availability travels the same road: declared by the consultant or their manager, it is read by the account manager answering a requirement, by the recruiter wondering whether to source, and by whoever forecasts the quarter’s revenue. The skills dossier behaves the same way, since it is a sales document rewritten for each engagement and every rewrite starts from the last version someone managed to find.

That is why “ERP or CRM” is hard to settle from a product sheet. A CRM handles the first row of the table very well, an invoicing tool the fifth, and an IT consulting ERP such as BoondManager or VSA is built to connect them all. The real question is how many of those rows you are prepared to see written in two places.

When is a CRM enough for an IT consulting firm?

A CRM is enough for an IT consulting firm as long as every copy goes through the same head. Take a small firm where the founder places, staffs and invoices. The CRM holds the clients and the requirements, a spreadsheet holds the staffing, the timesheet arrives by email at the end of the month and the invoice is made from it in an invoicing tool. The copies exist, but one person reconciles them, every month and from memory, and knows which one to believe when two of them disagree.

There is nothing amateurish about this setup, and it deserves defending against the urge to buy software too early. A CRM such as HubSpot, Salesforce or Sellsy does very well what it was designed for: tracking accounts, contacts, opportunities and follow-ups. An industry ERP is paid for in per-user licences, in weeks of configuration and in adoption, which is never a given. If it is slower than the spreadsheet, the team will reopen the spreadsheet next to it, and you will have paid for software in order to get one more copy.

Three conditions make the setup viable, and they take a minute to check. Everything is sold on time and materials, so every invoice is a plain multiplication of approved days by the day rate on the purchase order. Engagements are long, so staffing moves little from one month to the next. And one person handles both staffing and invoicing, which makes them, without anyone having decided it, the company’s synchronisation system.

The general-purpose CRM hits one specific limit, which is worth knowing before asking more of it: it has no native notion of a consultant, nor of the engagement that ties that consultant to a client with a day rate, dates and billed days. These objects can be built, at a price; in HubSpot, for instance, custom objects require an Enterprise subscription. Without them the engagement becomes a property of the won opportunity, and availability a text field with no entry date, even though it is the most perishable field in the whole database and the most expensive one when it is wrong.

At what point does a CRM stop being enough?

A CRM stops being enough on the day reconciliation no longer fits in one head, which happens more often through a change of organisation than through a number of consultants. There is no serious headcount threshold, and we would rather not invent one. There are, on the other hand, four signs that do not mislead, and any one of them is enough to reopen the question.

A second person reconciles. A second account manager joins, or an assistant takes over invoicing. Each holds their share of the copies and corrects them on their own side, so that nobody knows which one to believe on the day they disagree.

The first fixed-price project is signed. On time and materials, the invoice is a multiplication; on a fixed price, it follows a schedule of milestones, and the margin depends on the days actually consumed against the days sold. Every timesheet then has to be tied to a project budget, the remaining work tracked, and what has been delivered but not yet invoiced known. No CRM holds those facts, and a spreadsheet holds them badly as soon as two people write in it.

The monthly invoice needs three tools. The CRM for the day rate, the spreadsheet for the dates, the inbox for the approved timesheets: the time spent gathering them is visible, but it is the smallest cost of this way of working.

The same date is typed in twice. It is the simplest test on the list. Take a recent end of assignment and count the places where someone entered it by hand: beyond one, divergence is no longer a risk, it is a matter of time.

What does a fact copied into two tools cost?

A copied fact costs money in both directions, but not in the same way: the error that favours your firm is reported by the client, while the one that costs it is reported by nobody. That is what makes copies so durable, since they almost never produce a visible incident.

Take the day rate. An engagement is renewed with a twenty-euro increase per day, won at the precise moment when margin is usually lost for want of renegotiation. The new price is on the purchase order, but the invoicing tool keeps reusing last month’s rate. With the 205 billed days a year of the example we use there, that comes to €4,100 a year per consultant that will never be invoiced, and the client, who did sign the increase, has no reason to tell you. Had the error gone the other way, it would have been disputed on the first invoice.

Take availability. A consultant comes off an assignment earlier than planned; their manager notes it in the staffing spreadsheet, but the CRM record, the one account managers look at when a requirement comes in, still shows them on assignment. The match between that requirement and that consultant is never made. Every working day they spend on the bench then becomes a day without billing, about €520 of revenue in the example we use to work out a day rate, while salary and employer contributions keep running. The reverse error is more awkward still: a consultant presented as available who no longer is, and a client from whom you have to withdraw a profile they had picked.

Take, finally, the timesheet. A day of absence is added after approval when the invoice has already gone out, and there is a credit note to issue, a new invoice to justify and an explanation to give a buyer who does not like corrections.

None of these incidents looks like a software problem, which is exactly why they last: they get fixed one at a time, as slips, without ever removing the copy that produces them. The rule that prevents them fits in one sentence: a fact has a single owning system, and every other copy is read-only and flows in one direction only. The choice of owner matters less than people think; what matters is having settled it, and having written it down somewhere new joiners will read it.

How do you choose without ending up with a ranking?

You choose by first writing down, fact by fact, which system owns it, then checking that the setup you are considering respects that split. The league table of software comes last and matters less than this split, because an excellent ERP that half the team never types into does worse than a well-kept CRM.

Here is a split that works. It is not the only possible one, and what matters is that each row has a single owner, whichever it is.

Fact Owning system Read it without writing
Client, contacts, requirement until signature CRM or sales module ERP, invoicing
Signed engagement: day rate, dates, purchase order ERP (engagement management) CRM, invoicing
Candidate until hired ATS or recruitment module ERP
A consultant’s availability and end of assignment ERP (staffing) CRM, ATS
Days worked: timesheets, absences ERP or time-tracking tool invoicing, payroll
Invoice and payment invoicing tool or accounting ERP, CRM

Signature is the natural border between the two worlds. Before it, the requirement, its contact and the proposed price belong to sales; after it, the engagement, its day rate and its dates belong to the tool that invoices. A CRM and an ERP live together very well on either side of that line, provided the second does not copy the first by hand and the first never corrects the second. For many firms, that is the honest answer to “ERP or CRM”: both, with a direction of flow written down in black and white.

Then come the questions to put to vendors, or to your current setup if you change nothing:

  • How you sell. Does the software handle both time and materials and fixed price, with purchase orders, billing schedules and progress tracking, or only one of the two?
  • From timesheet to invoice. Do approved days become an invoice without being retyped, and does a timesheet correction carry through before the invoice is sent rather than after?
  • Margin. Is it calculated from the cost payroll knows, or typed by hand into a field nobody updates after a pay rise?
  • E-invoicing. Since 1 September 2026, every company in France has had to be able to receive electronic invoices, and small and medium-sized businesses and micro-businesses will have to issue them from 1 September 2027, through a state-approved platform. The tool that invoices must be compatible, and since the client’s SIREN number is now one of the mandatory mentions, the client record has to be right in that particular tool.
  • Leaving. If you left tomorrow, what would you get back, in what format, and would the history of engagements and timesheets be part of it?

For a vendor-by-vendor comparison, with prices and the firm sizes each one targets, I would rather send you to the comparison of software for IT consulting firms on the blog of Cobalt, which we also publish, than put out a less complete version here.

What does this choice change for automation and AI?

It decides what an agent will be able to do for you, but not through the criterion people usually look at. Whether a piece of software “has AI built in” says almost nothing; what counts is what it lets a third party do. We have set out the five properties an agent needs from an ATS or a CRM: an API that exposes the business objects for writing, events that can be replayed, rights expressed per person, an exportable history and reachable custom fields.

In an IT consulting firm, the business objects have precise names: requirements, positionings, consultants, timesheets, invoices. The public documentation of BoondManager’s API, to take a piece of software we know well, allows requirements, positionings, consultants, candidates and timesheets to be created, describes for each object the rights that apply to it and offers webhooks. It also accepts OAuth2 connections restricted to the users the application has been opened to, and limited to the APIs it declares. Those lines of documentation, far more than a demo, tell you what an agent will be able to do in your ERP.

Rights are the point people look at least and the one that costs the most. An agent has to act with the rights of the person talking to it and never with an account of its own, otherwise it opens a path that bypasses all your permissions. We have explained why an agent should not have an identity of its own. Software that can only express profiles, rather than people, forces a choice between a technical account that sees everything and a reimplementation of the visibility rules, which is to say one more copy.

The split between owners matters as much as access. An agent connected to a CRM and to a staffing spreadsheet that contradict each other does not settle the matter: it picks one of the two availabilities and presents it with confidence, and the better the agent, the less the error shows. The work described above, deciding which system owns which fact, is therefore the real preparation for an automation project, well before choosing an AI tool.

That is how Balt works in an IT consulting firm. It connects to BoondManager, reads the consultants, their assignments, the open requirements and the candidates there, and fetches each fact from the system that owns it instead of keeping a copy. It acts with the rights of the person talking to it, prepares updates and asks before changing a record. Everything that leaves the company, a proposal to a client as much as an invoice reminder, waits until a person has read it. The details are on our page for IT services companies.

One question remains, and this split makes it pressing: are the facts you are about to name as owners actually right? An availability with no entry date is worth nothing, whatever software holds it, and the state of your data is worth checking before you connect an agent, starting with what the agent will touch first.

Frequently asked questions

  • What is the best ERP for an IT consulting firm?

    There is no best one in the abstract, and a ranking answers the question badly. The right software is the one that handles the way you sell, time and materials and fixed price, turns an approved timesheet into an invoice without retyping, calculates margin from real cost, issues e-invoices through an approved platform and opens a write API with rights per person. The rest comes down to adoption: an ERP nobody types into does worse than a well-kept CRM.

  • Can a CRM such as HubSpot or Salesforce replace an IT consulting ERP?

    It handles clients, contacts and opportunities very well. Consultants, engagements and timesheets need objects a general CRM does not have out of the box, HubSpot for instance keeping custom objects for its Enterprise plans, and invoicing stays in another tool. The setup works for a small time-and-materials firm as long as one person reconciles the copies, and stops working once the same fact is typed in by two people.

  • How many consultants does a firm need before it needs an ERP?

    No headcount threshold is reliable, because the trigger is the organisation rather than the size. The signs that matter are a second person reconciling the tools, the first fixed-price project to track in days consumed, a monthly invoice run that means opening three pieces of software, and the same end-of-assignment date typed in two places.

  • Does e-invoicing change the choice of software?

    It adds a criterion that is not up for negotiation. Since 1 September 2026, every company in France has had to be able to receive electronic invoices, and small and medium-sized businesses and micro-businesses will have to issue them from 1 September 2027, through a state-approved platform. The tool that invoices must be compatible with those platforms, and the client record it uses must carry the right SIREN number, which is now a mandatory mention.

  • Do you have to change your ERP or CRM to use an AI agent?

    Rarely. Check that your software exposes your requirements, positionings, consultants and timesheets for reading and writing, that it can express rights per person and that it signals what changes. If it does, an agent can work in it as it is; if not, start with the tasks that only need reading.

Sources

  1. BoondManager, public documentation of the Boond API (accessed 13 November 2026)doc.boondmanager.com
  2. BoondManager Help Center, OAuth2 Connection (30 April 2026)help.boondmanager.com
  3. HubSpot Knowledge Base, How to use objects for business processes (accessed 13 November 2026)knowledge.hubspot.com
  4. economie.gouv.fr, Tout savoir sur la facturation électronique pour les entreprises (accessed 13 November 2026)economie.gouv.fr
  5. Cobalt, Les meilleurs outils et logiciels pour ESN : comparatif complet (December 2025)cobalt-ia.com

Balt does this work

Read next

Give Balt its first job.

Thirty seconds to add it to Teams and get to work.

Try for free