HR, Finance, and Sales Should Not Run on Separate Logic

A growing company tends to accumulate departmental software the way a kitchen accumulates appliances. Each function picks its own tool. Each tool has its own data model. Each tool defines “customer” or “employee” or “deal” slightly differently. The friction shows up later, in the form of reports that don’t match, decisions that get delayed, and a lot of cross-functional meetings to reconcile basic facts.

Why this happens

It happens for an understandable reason: each function picks the best tool for itself. Sales picks Salesforce because it’s best for sales. HR picks Workday or BambooHR because it’s best for HR. Finance picks NetSuite because it’s best for finance.

Each choice is locally optimal. Globally, the company has three systems with three definitions of “active customer.” Reconciling them becomes someone’s job.

The cost of separate logic

It compounds across the business:

• Reports that should match don’t (revenue per HR-recognized employee doesn’t tie out to what Sales says is the headcount)
• Decisions get delayed waiting for someone to “verify the data”
• Cross-functional projects spend most of their time arguing about facts before they can discuss strategy
• New hires spend weeks learning which system has the “real” answer to each question

None of this shows up as a line item. It shows up as drag. The drag is real.

What “shared logic” actually means

Shared logic doesn’t mean one big system that does everything. It means the foundational concepts — customer, employee, account, deal, period — are defined in one place and propagate to all the systems that need them.

This is a data architecture decision more than a software decision. Pick a source of truth for each foundational concept. Make sure every other system reads from or syncs with that source.

How custom helps here

Off-the-shelf platforms make this harder than necessary. Each platform wants to be the source of truth. Their data models compete.

Custom integration code (or a custom data layer) can mediate. It enforces consistency without requiring everyone to use the same platform. Sales keeps Salesforce. HR keeps Workday. The shared layer makes sure “active customer” means the same thing in both. (See How to Modernize Operations Without Replacing Everything.)

The cross-functional payoff

When HR, Finance, and Sales share logic on the foundational concepts:

• Reports tie out without manual reconciliation
• Decisions happen faster because everyone is working from the same facts
• New hires learn the business faster because there’s one definition to learn
• Compliance is easier because data lineage is clear

None of these alone justifies the work. Together they make the business significantly easier to run.

What to do

For your next cross-functional report or initiative, notice where the friction lives. It’s almost always at definitional boundaries — where two systems define the same concept differently.

That friction is where shared logic would pay back. Pick one foundational concept. Define it once. Propagate. Most companies find they need shared logic on three or four concepts, not thirty. Start small.