Kombo's pitch is coverage, and a buyer comparing unified APIs counts integrations first. Six job posts give three different numbers and the homepage avoids giving one.
First action
Count systems live in the catalog today and agree with the CRO which number sales will use.
How to measure it
Public surfaces with a mismatched integration count
- Now
- –
- Target
- zero
- By
- 1 week
Steps
Count from the catalog
Systems live in production, by category (HRIS, ATS, payroll, LMS, assessment).
Head of Growth 2 hours
Agree the rule
What counts: live, read and write, at least one customer connected.
CRO 30 minutes
Put it in the hero
Replace "hundreds" with the number and the category split.
Head of Growth 1 hour
Fix the job posts
One "About Kombo" paragraph shared by every post.
Head of Growth 1 hour
Update the deck
The same number on the title slide and coverage slide.
Pre-Sales Engineer 30 minutes
Automate it
Serve the count from the catalog so pages never drift.
Head of Growth 1 day
Why it works
Pick the number you can defend (systems live with read and write), put it in the homepage hero, every job post and the sales deck, and generate it from the integration catalog so it updates itself.
Merge and Finch both lead with integration counts, and the Senior Enterprise BDR and Field Marketer will quote a number in every first touch. One defensible number makes Kombo look precise in a category where precision is the product.
Risks and how to handle them
A precise number looks smaller than "hundreds"
Show the category split and the "deepest read and write" claim next to it.
Evidence
- HiringThe integration count differs by page: the Senior Enterprise BDR and Field Marketer posts say 100+ systems, the Pre-Sales post 200+, the Enterprise AE, business development and RevOps posts 250+, and the homepage "hundreds".Source
- Your websiteHomepage: "All your integrations with one API" for HRIS, ATS, assessment, payroll and LMS; "hundreds" of integrations, 99.9% uptime, SOC 2 Type 2, ISO 27001, HIPAA and GDPR; logos include Indeed, Greenhouse, Paychex, Experian, Gem, Factorial, TestGorilla and Wellhub; Jobteaser: "Within just weeks we could connect all of our customers' ATSs and HRISs!"Source
- programmable.infoThe site has 267 integration pages, 15 case studies, 17 blog posts, 11 solution pages and 4 use-case pages. There are no live comparison pages: kombo.dev/vs/merge, which still appears in search results, returns a 404.Source
- Competitor researchComparisons describe Merge as a multi-category unified API, Finch as the US payroll-depth specialist and Kombo as the HR and Europe specialist (Personio, PayFit, Softgarden, Factorial). Unified.to, Knit and Truto publish "Kombo vs" and "Kombo alternatives" pages. One review reports a $25M Series A led by Volition Capital in February 2026.Source