Making it easier for customers to connect their existing systems to an external HRIS or EOR

Problem statement

• Every connector is built like it's the first one — ten systems need 45 point-to-point connections, and only the common few are ever worth a bespoke build.
• Most connections run on a schedule — without native webhooks, a raise or an offboarding needs manual attention, which delays everything downstream.
• What's synced is shallower than it looks — standard syncs cover common fields across platforms, but custom fields never make it across.
• Not a data problem: it's how connections get built, when they update, and what they actually show.

Who feels it

• The HR/People Ops Lead can't tell which fields are actually syncing until one goes missing — for them, the gap shows up as drift.
• The IT/Systems Admin owns a fix nobody else can read, so every vendor API update risks silently breaking it — for them, the gap shows up as debt.

The solution

• A reusable mapping template, not a bespoke build — a new system starts from the closest existing template instead of zero.
• Frequent diffing, not a weekly file drop — a raise or an offboarding shows up in hours, not a pay cycle.
• A visible completeness score, not a silent gap — shows exactly what's covered, and flags what isn't, before it becomes a problem.
• None of this needs new data from the EOR's API. It changes how a connection gets built, how often it updates, and what it shows.

Where this leads

Connect is the first chapter, not the whole story. Build gets sharper, not busier: what's left in the queue is a genuinely new template, not a repeat of one that exists. And Compound is Connect run in reverse — every new mapping template raises the match rate for the next similar system. One loop: Connect builds the templates, and Compound is those templates getting reused.

Value for customers

• Uncommon systems don't get skipped — a closer template match means even a less common system is worth connecting quickly.
• Changes show up in hours, not pay cycles — frequent diff-checks catch a raise or an offboarding before the next payroll run.
• You can see exactly what's synced — a completeness score shows what's covered, and what still needs a human look.

Impact

• Lower build cost per new system, since reused mapping templates mean less bespoke engineering per connector.
• Fewer payroll errors from stale data, since diff-based sync catches a change before the next pay run, not after.
• Fewer compliance scrambles before deadlines, since visible completeness catches a gap weeks early, not three weeks before a filing.

What I'd watch

Read from how these integrations typically fail across the category, not internal data. Next step: instrument these three before and after launch to see which one actually moves.