ERP Consultant for Consulting

How a consulting engagement flows through the business

Consulting firms differ from broader professional services in one important way: the unit of work is the engagement, and it is staffed from a shared pool of consultants whose time is the firm's entire inventory. The core process map, in words, looks like this:

Opportunity -> scoping and proposal -> statement of work or retainer agreement -> resource request -> staffing and booking -> delivery with time and expenses -> change requests -> invoicing or retainer drawdown -> collection -> engagement review.

Two side flows matter as much as the main one. The first is capacity: who is on the bench, who rolls off next month and whether the pipeline will fill that gap. The second is associates: many consultancies deliver with freelance specialists whose costs arrive later than the client invoice, which distorts margin if the system cannot match them.

When I run business analysis for a consultancy, I map both side flows alongside the engagement cycle, because a system that only handles projects and invoices will not answer the questions partners actually ask.

Pain points I see in consulting firms

Consultancies tend to outgrow their early tools in recognizable ways:

• Staffing in a spreadsheet. Resource managers keep a separate grid, so bookings, actual time and pipeline never reconcile, and bench time is discovered after it has happened.
• Utilization nobody trusts. Each partner calculates it differently: some include internal projects, some exclude leave. Board reports become an argument about definitions.
• Retainers tracked by memory. Monthly retainer hours are consumed, carried over or forfeited by informal agreement, and clients dispute balances at renewal.
• WIP hidden until month end. Time and materials work is billed late because nobody sees unbilled value building up.
• Margin without associate costs. Subcontractor invoices are posted to general cost codes, so engagement profitability looks better than it is.
• Scope creep without change orders. Extra work is delivered but never formally added to the SOW, so it is never billed.

Each of these is a rule problem before it is a software problem. I get definitions agreed first, then make sure the chosen platform enforces them.

Recommended ERP modules for consulting firms

The module set for a consultancy is narrower than for product businesses, but each module needs more depth:

• CRM: opportunities with expected start dates, roles needed and probability, so pipeline informs staffing.
• Engagement or project management: SOW structure, phases, budgets, change requests and status.
• Resource management: skills, availability, bookings and bench, ideally linked to pipeline.
• Timesheets and expenses: with approval by engagement lead and rebillable flags.
• Billing: time and materials, fixed price, milestones and retainers with drawdown balances visible to the client lead.
• Purchasing and payables: associate and subcontractor costs linked to engagements.
• Accounting and reporting: WIP, deferred and accrued revenue, engagement margin and utilization by consultant, grade and practice.

Revenue timing for fixed-price and retainer work is an accounting policy question. I make sure the system can support the method your accountants choose, but the policy itself should be set by them. For the costing side in more depth, see ERP for project costing, and for firms with a broader service mix, ERP for professional services.

Implementation checklist for consultancies

These are the decisions I make sure are settled and written into the BRD before a consulting firm starts configuration:

1. The formula for utilization, including which time counts as available, billable and internal.
2. Grade and role structure, with standard cost and bill rates and who can change them.
3. Every engagement type in use: time and materials, capped, fixed price, milestone and retainer.
4. Retainer rules: drawdown unit, rollover, expiry, overage billing and how balances are shown to clients.
5. Change request process and how approved changes update budget and billing.
6. How associate and subcontractor costs are linked to engagements and approved.
7. Opening balances for WIP, retainer hours and receivables at cutover.
8. The partner dashboard: pipeline coverage, bench forecast, engagement margin and debtor days.

I then write UAT scenarios around real engagements, including a retainer mid-term and a fixed-price project with an approved change, because those are the cases that break generic configurations.

Integrations, data migration and growth

A consultancy's systems landscape is usually light but critical: email and calendars, document collaboration, e-signature for SOWs, payroll and expense apps. I define which system owns client, engagement, time and financial data, then design integrations so each record has one source of truth.

Migration focuses on what is open: active engagements with budget remaining, retainer balances, unbilled time, open invoices and associate commitments. Closed engagements can usually be archived and summarized for reporting rather than migrated line by line.

The growth side is where my second area of work helps. Consulting firms often rely on referrals and partner networks, which makes pipeline lumpy and bench time expensive. Connecting CRM data to B2B lead generation and attribution shows which channels bring engagements worth staffing. The services firm case study describes how that link between CRM structure and lead generation worked in practice. If your firm also delivers managed services or technical work, the IT services page covers that model. To talk through your firm, get in touch.