Resource Planning and Profitability for Cross-Border Consulting Firms

When consulting firms operate as one team across multiple entities, reporting usually breaks – eventually

Many engineering and AI consulting firms grow internationally before their operations stack is ready for it. Teams are staffed across borders, projects are delivered as one unit, but the business is still split into legal entities for finance, payroll, and compliance.

On paper, this looks manageable. In practice, it creates blind spots in resource planning, project profitability, and forecasting that only show up once the firm reaches 30 to 50 to 70 people (it's hard to say exactly when this will happen. People have different tolerances for this)

This article breaks down a real operational setup common in cross-border consulting firms, where delivery works well, but tooling and reporting struggle to keep up.

A common structure: one delivery team, multiple entities

The firm in this example operates with roughly 30 consultants across:

• A US subsidiary
• A Canadian subsidiary
• Additional consultants based in Europe, assigned to either US or Canada

From a delivery perspective, the firm operates as one team. Canadian consultants regularly staff US projects and vice versa. Leadership wants to see consolidated delivery performance, but still needs clean reporting by legal entity for margins, cost, and profitability.

This is where most traditional tools start to break down.

The typical consulting tech stack and where it fails

Like many consulting firms, tooling has grown organically:

• CRM: HubSpot or Salesforce, used for sales pipeline and opportunities
• High-level resource planning: Spreadsheets or point solution application not connected to CRM or finances
• Time tracking: Point solution system or within the finance tool like QuickBooks
• Contractor payroll and expenses: external platform
• Accounting: NetSuite or QuickBooks for both entities, with manual reconciliation in Excel

Each tool works well in isolation. The problems appear in the gaps between them.

The biggest operational gaps

1. Planned vs. actuals is fragmented

High-level staffing happens in a Salesforce app or spreadsheets. Actual hours live in Harvest. Finance reconciles in Excel.

There is no reliable way to:

• Compare planned hours to actuals by project or role
• Track burn-down against plan early, before margins slip
• See which projects are drifting until it is too late

Delivery managers end up maintaining their own spreadsheets, each with slightly different logic. That's not really efficient.

2. No consistent project planning or burn-down tracking

Project planning is not standardized. Some projects are tightly planned, others loosely estimated. Burn-down is tracked manually, if at all.

This makes it difficult to:

• Spot scope creep early
• Understand whether a project is burning faster than expected
• Separate delivery issues from staffing or estimation issues

Utilization and margin reports lag behind reality.

3. Cross-entity staffing with unclear profitability

Resources can be assigned across entities, but reporting does not clearly show:

• Which entity carries the cost
• Which entity earns the revenue
• How margins look per project, per entity

Leadership sees averages. The underlying picture stays blurry.

4. Skills-based forecasting is missing

While basic utilization forecasting exists, there is no reliable way to:

• Forecast demand by skill or role
• See future gaps in capability
• Make bench visible outside of utilization percentages

Bench often gets buried inside “healthy” utilization averages.

5. Agentic workflows break down with a splintered tool stack

As firms look to automate more operational work using AI and agentic workflows, fragmented tooling becomes a hard blocker.

When CRM data, resource plans, time tracking, and financials live in separate systems with inconsistent structures, it is difficult to automate anything beyond simple alerts. Agents cannot reliably answer questions like whether a project is at risk, who should be staffed next, or whether margins are tracking to plan without pulling data from multiple sources and reconciling it manually.

Instead of enabling automation, teams end up building brittle workflows that depend on exports, custom scripts, or human intervention. This limits the ability to automate staffing decisions, forecasting updates, or month-end processes in a meaningful way.

A connected operating layer is a prerequisite for agentic workflows that actually reduce operational effort rather than adding more complexity.

What a better operating model looks like

For cross-border consulting firms, the goal is not to replace every system. It is to connect planning, staffing, time tracking, and financials into one operational layer.

A modern resource planning platform should support:

• Cross-entity resource allocation for opportunities and projects
• Clear separation of cost and margin by legal entity
• Planned vs. actual hours in one place
• Project-level burn-down and profitability tracking
• Visibility into billable vs. non-billable work by resource
• Skills-based forecasting tied to real project demand
• AI-enabled insights to help people cut down time working with manual workflows

This allows delivery, finance, and leadership to work from the same data without manual exports.

What firms typically validate first in a trial

When firms with this setup evaluate a resource planning platform, they usually start by validating a few critical workflows:

• Can consultants from one entity be staffed on projects owned by another entity?
• Do costs and margins stay correctly separated by entity?
• Can project burn-down be tracked against plan in real time?
• Is billable vs. non-billable work clearly visible by project and by resource?

If these basics work, everything else compounds from there.

Why this matters at 30 to 50 to 70 people and up (again, it's hard estimating when exactly!)

At smaller team sizes, operational gaps can be patched with spreadsheets and goodwill. The gaps you start seeing are as follows:

• Revenue leakage: T&M projects run on low billing, project overrages in fixed price work
• Late margin surprises: No proactive project health insights
• Overworked delivery managers: Instead of being empowered by the tooling and AI that enables smooth collaboration with the team
• Leadership decisions based on incomplete data: costly hiring decisions, investments in the wrong service offering areas

Fixing this is about having one system that ties capacity planning, staffing, time, and financials together in a way that matches how consulting firms actually operate.

Final thought

Cross-border consulting firms struggle because their operational tooling was never designed for shared teams across multiple entities. Getting resource planning, planned vs. actuals, and profitability into one connected system gives leadership clarity without slowing delivery down.

If your firm operates as one team but reports as many, this is the point where your tooling needs to catch up.

Frequently Asked Questions

How do consulting firms manage resource planning across multiple entities?

Consulting firms centralize resource planning while keeping reporting separated by legal entity. This supports cross-border staffing while maintaining accurate cost, margin, and profitability reporting per entity.

What challenges do cross-border consulting firms face with planned vs actual hours?

Planned work is often tracked in one system while actual hours are logged elsewhere. Without a unified view, it is hard to spot project burn early, explain variance, or prevent revenue leakage.

Why is project burn-down tracking important for consulting firms?

Burn-down tracking shows whether a project is consuming budget faster than planned. It helps teams catch scope creep and staffing issues early, before margins or timelines are impacted.

Can resource planning tools support cross-entity project staffing?

Yes. Modern resource planning tools support cross-entity staffing while keeping costs and margins correctly attributed to each legal entity, which is essential for multi-country delivery teams.

Why do fragmented tool stacks make agentic workflows difficult to build?

Agentic workflows require consistent, connected data across CRM, staffing, time tracking, and financials. When systems are fragmented, agents cannot reliably assess project health, staffing needs, or margin risk without manual reconciliation, which makes automation brittle.