Why HR integrations should not take 20 weeks.

If someone else controls your integration layer, you inherit their timelines, their costs, and their constraints. Ownership is the variable. Everything else follows.

The quiet frustration in HR

HR leaders share a common, quiet frustration: their systems can't change at the speed their business changes. A new field, a new mapping, a new feed, and the answer is months and tens of thousands of dollars.

Oak View Group lived this for years before changing it.

The industry pattern

The 20-week HR integration is not unusual. It is the default. Across mid-market and enterprise HR teams, the standard pattern looks like this:

• 4 to 7 weeks for vendor scoping (e.g., ADP SQR)
• 10 to 16 weeks of vendor build, plus testing
• Roughly 20 weeks total
• $10,000 to $25,000 per integration
• Visibility limited to a spec document
• Errors surfaced after deployment, sometimes weeks after
• Internal teams filling gaps with Excel and vlookups
• Every out-of-scope change billed as a new project

This is treated as how integrations work. It isn't. It's how vendor-controlled integrations work.

Why faster vendors aren't the answer

Some teams replace ADP-style SQR projects with iPaaS tools or boutique integration shops that promise shorter lead times. The integration still happens at someone else's pace, on someone else's queue, with someone else who doesn't know the data.

As OVG's People Systems team put it directly: alternatives would still build integrations for them with a shorter lead time, but none gave them full control.

That distinction is the one that matters. A faster vendor still requires a request, still requires a change order, and still removes the team accountable for the system from the work that controls it.

The forcing function: a real example

At Oak View Group, hiring scale forced the question. OVG runs high-volume, seasonal, venue-bound hiring across arenas, food and beverage operations, and venue staff. The SQR model couldn't keep up.

Every venue, every change, every new mapping was queueing into a 20-week SQR project at typical industry pricing. New hires were occasionally assigned to the wrong company. Coordinators were stuck in vlookups. Onboarding delays caused venues to leave. Management heard the complaints.

OVG's People Systems team brought integrations in-house on Aragorn. No IT track. No consultants. The same people who designed each workflow now build and operate it.

What becomes possible

Once HR owns the integration layer:

• New integrations go live in days to 1 or 2 weeks
• Changes are made directly by the team, not requested from a vendor
• Errors are seen and fixed in real time, not in postmortems
• Each integration becomes a flat $500 per integration per month with unlimited internal changes, replacing $10,000 to $25,000 SQR projects and per-change fees
• Leadership gets analytics on demand, with new metrics added as needed
• Compliance work belongs to the team that carries the compliance risk
• HR moves at the pace of the business, not the pace of an SQR queue

The proof in numbers

• 64 active integrations live
• 49 published integrations
• 883 configuration changes, all internal. Each would previously have required vendor scoping and cost.
• ~40 changes per month on average across 22 months
• 20 weeks → days time per integration
• Zero IT or consultant dependencies

The test case: a single field change

The simplest test of any HR integration model is a single field change. In the SQR model, that change is a $10,000+ scoping conversation and weeks of waiting.

Inside Aragorn at OVG, the same change is one of the 883 configuration changes the team has already shipped. Typically same-day, often during a single working session.

Multiply that across 64 integrations and the operating model itself changes.

"Other alternatives would still build these integrations for you with a shorter lead time. None gave us full control. The biggest difference is autonomy, paired with the speed, control, and confidence to actually run our processes."

People Systems Team, Oak View Group

The broader takeaway

HR does not need better integrations. HR needs control of the integration layer.

The 20-week timeline isn't a property of integration work. It's a property of integration work that someone else does for you.

When the team accountable for a system controls how that system changes, the timeline goes away. So does the dependency that made it inevitable.

OVG's data, 64 integrations and 883 internal configuration changes, a flat $500 per integration per month with all changes included versus $10,000 to $25,000 per ADP SQR project plus per-change fees, isn't a story about a faster vendor. It's a story about a different operating model.

The next 20-week project on your roadmap doesn't have to be 20 weeks. It just has to belong to you.