Merge Achieves Codat Parity

The important signal is that Merge is not just adding more logos, it is proving that its core product engine can enter a vertical with an incumbent and catch up fast. In practice that means taking the same unified auth, common data model, sync, and developer workflow it used in HR and CRM, then reusing that machinery in accounting, where Codat has been more focused on small business financial data.

• Merge expanded from HR and ATS into ticketing, accounting, and file storage within its first two years, shipping 150 integrations across categories. That matters because feature catch up is easier when the hard part, auth, normalization, sync, docs, and SDKs, is already built once and reused many times.
  1 sacra 2 sacra
• The product difference is concrete. Merge offers field mappings, remote data, passthrough requests, and custom data, which let customers go beyond the default schema when a buyer needs one extra field or a custom object. That is the same kind of edge case coverage that determines whether an integration is usable in production.
  2 sacra 3 merge 4 merge
• Codat is strongest where small business accounting data is the product, especially for fintech and financial services workflows. Merge is using accounting as one module inside a broader embedded integration stack, so a SaaS company can buy one vendor for HR, CRM, ticketing, and accounting instead of stitching together point solutions.
  1 sacra 5 sacra 6 codat

Going forward, the advantage shifts toward the platform that can keep adding categories without breaking the developer experience. If Merge keeps turning each new category into another reuse of the same integration engine, it can pressure vertical specialists like Codat from above by bundling enough depth with much broader coverage across the SaaS stack.