top of page
Business & Enterprise
HR Technology
HRIS/HCM
Humaans
Won modern people-operations teams by making employee data, workflows, and documents fast and API-first, despite Workday, HiBob, Personio, and BambooHR owning broader HR suites and larger distribution.
1
MODEL
BUSINESS MODEL
SaaS
- Sold annual HRIS subscriptions based on employee count, modules, and support level. - Started with a fast, modern employee-data layer, documents, workflows, and integrations for scaling companies. - Added onboarding, absence, compensation, reporting, approval flows, and AI capabilities. - Used API-first design and integrations with payroll, identity, collaboration, and productivity tools to embed the HRIS in the customer stack. - Expanded from startups and scale-ups into larger enterprises requiring security, permissions, and workflow depth.
1. Identify a system of record whose incumbent feels slow, rigid, or poorly designed for a modern operator. 2. Build the smallest data layer that becomes the source of truth for people or operational records. 3. Make integrations and automation first-class so the system connects to the customer’s existing stack. 4. Add workflow depth only after the data layer is trusted. 5. Price by the record that grows with the customer—in this case employees. The common mis-build is building an HR suite before proving that the customer will make the vendor its employee-data system of record.
DISTRIBUTION MODEL
Humaans, founded in London in 2019 by Giovanni Lanzani and Marco Laver, built an API-first HRIS for fast-growing companies. It demonstrated repeat adoption through people teams consolidating employee records, documents, onboarding, absence, reporting, and integrations; it raised a $15 million Series A in 2021 and expanded into AI and enterprise capabilities.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Product-Led Growth, Direct Sales, Partnerships, SEO
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Self-serve trials and product-led onboarding reached people-operations teams at startups and scale-ups. - Direct sales expanded into larger companies needing security, workflow depth, and implementation support. - API-first integrations with Slack, Google Workspace, payroll, identity, and productivity tools created embedded adoption. - SEO targeted HRIS, employee database, onboarding software, HR workflows, and Humaans alternatives. - Customer references from fast-growing technology companies built credibility with people-operations buyers.
What worked: an API-first, modern HRIS attracted operators who wanted employee data to connect cleanly to the rest of the stack. Trap if copied blindly: modern UX alone does not overcome incumbent depth in payroll, compliance, and global employment; the vendor must prove a clear system-of-record wedge before expanding.
| PATTERNS OF THIS MODEL
PATTERNS IN MODERN HRIS SAAS: 1. EMPLOYEE RECORD IS THE SYSTEM-OF-RECORD WEDGE. Once the platform owns people data, adjacent HR workflows become easier to adopt. 2. API-FIRST DESIGN CREATES OPERATIONAL STICKINESS. Integrations make the HRIS part of the customer’s broader systems architecture. 3. EMPLOYEE COUNT IS THE NATURAL PRICING METER. Headcount correlates with data, workflow, and support complexity. THE WEAKNESS: HRIS buyers demand compliance, payroll, and global employment depth that startups often underestimate.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — PEOPLE-OPERATIONS WORKFLOW LAYER. The opportunity is automating onboarding, changes, approvals, documents, and compliance—not merely storing employee records. GOLDMINE 2 — AI HR OPERATIONS. The durable opportunity is answering policy questions, drafting workflows, and surfacing workforce risks while preserving permissions and auditability. GOLDMINE 3 — HR DATA FABRIC. The opportunity is connecting HRIS, payroll, performance, and engagement data into one governed people-data layer. THE PIT — MODERN UI WITHOUT SYSTEM-OF-RECORD DEPTH. A beautiful employee directory does not displace an incumbent HRIS without workflow and compliance depth. THE SECOND PIT — GLOBAL PAYROLL COMPLEXITY. Employment law, payroll, and benefits vary by country and can overwhelm a young platform. MOVE WITH CAUTION — Do not build an HRIS without a clear data-ownership wedge; otherwise the product becomes another employee directory rather than a system of record.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Humaans entered against Workday, BambooHR, Personio, HiBob, and CharlieHR. It differentiated through speed, modern UX, API-first architecture, flexible workflows, and a focus on scaling technology companies.
MARKET TYPE
Red Ocean
ENTRY STRATEGY
Direct Entry
WHY THEY WON
The market is a Red Ocean: HRIS platforms are crowded with global suites, regional leaders, and payroll-centric systems. Humaans’ opening was that fast-growing companies wanted employee data and workflows that were modern, connected, and easy to configure. By making the employee record API-first, it changed the comparison from “which HR suite?” to “which system connects people data to the rest of the stack?” The transferable lesson is that an entrant can differentiate by improving the data layer and developer experience rather than matching incumbent breadth.
EXECUTION
Humaans entered with its own cloud HRIS and self-serve distribution rather than acquiring a customer base or depending on a host platform. The initial bet was that scaling companies would adopt a modern employee-data system if it were fast, flexible, and integrated. This required employee records, documents, workflows, permissions, and integrations. The approach was viable because people teams could replace spreadsheets and legacy HR tools quickly; it would fail if customers needed payroll, compliance, or global employment depth before the core data layer was trusted.
FOOTHOLD STRATEGY
Wedge Strategy
Humaans first targeted people-operations teams at fast-growing technology companies that needed a modern employee-data layer. These users were reachable through product-led trials, SEO, and community channels; they could pay when headcount, workflow complexity, or compliance needs increased. The path outward was into onboarding, absence, compensation, reporting, AI, and enterprise HR operations.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Humaans’ API-first HRIS converts a people team’s data-management pain into a broader people-operations platform relationship. KEY LEARNING: The strongest HRIS wedge is ownership of the employee record, not feature breadth. HOW TO USE: Make the core record fast and connected, then expand into workflows that depend on that record.
KEY LEARNING
THE STANDARD: In a Red Ocean, the entrant must own a distinct buying criterion rather than match incumbent breadth. RULE 1 — OWN THE DATA LAYER: Employee records are the foundation for HR workflows. RULE 2 — SERVE THE MODERN OPERATOR: Fast configuration and integrations create a distinct buying reason. RULE 3 — EXPAND INTO WORKFLOWS: Onboarding, absence, and approvals reuse the same data. RULE 4 — GLOBAL COMPLIANCE IS A MOAT: Payroll and employment law depth are hard to replicate quickly. MARKET TYPE: Red Ocean (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN MODERN VERTICAL SYSTEM-OF-RECORD SAAS: 1. API-FIRST DESIGN CREATES OPERATIONAL STICKINESS. Integrations make the system part of the customer’s architecture. 2. RECORD-BASED PRICING SCALES WITH CUSTOMER GROWTH. Employees, locations, or transactions correlate with value. 3. MODERN UX CREATES INITIAL PREFERENCE BUT NOT DURABLE MOAT. Workflow depth and compliance determine retention. 4. THE WEAKNESS: Incumbents can copy modern UX faster than startups can build compliance depth.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Direct entry is appropriate when the buyer can self-serve and the product delivers a complete system-of-record outcome without implementation. RULE 1 — Make the employee-data layer immediately useful. RULE 2 — Validate repeat usage and data ownership before expanding into workflows. RULE 3 — Design integrations as core product, not afterthought. RULE 4 — Reject direct entry when the buyer requires payroll or global compliance from day one. Example: Personio entered European SMB HR through localized compliance; failure occurs when entrants underestimate payroll and employment-law depth.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A wedge is a narrow data or workflow pain that opens broader HR operations once the customer depends on the record. RULE 1 — Choose teams whose employee data is fragmented across spreadsheets and tools. RULE 2 — Target a segment where speed and integration create a distinct advantage. RULE 3 — Expand into workflows that reuse the same employee record. RULE 4 — A wedge fails when the customer only needs a directory and has no operational complexity. Example: HiBob expanded from modern HRIS into broader people operations; failure occurs when vendors chase enterprise breadth before proving data ownership.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Humaans prices through quote-based Growth and Enterprise plans based on employee count, modules, and support level, with AI modules such as Athena sold as add-ons. Third-party estimates place typical pricing around $5–15 per employee monthly.
REVENUE MODEL
Subscription
PRICING MODEL
Custom Enterprise Pricing, Tiered Pricing, Add-On Pricing
WHY THEY WON
Customers pay recurring subscription fees based on employee count and selected HR modules. Revenue expands as customers add headcount, workflows, documents, reporting, AI, and enterprise capabilities; implementation and support intensity rise with global and compliance complexity.
Humaans uses Custom Enterprise Pricing and Tiered Pricing across Growth and Enterprise plans, priced by employee count and modules. AI capabilities such as Athena are Add-On Pricing, with enterprise agreements shaped by security, workflow, and support requirements.
TARGET AUDIENCE
Scaling technology companies (Growth; employee data, onboarding, and workflows); People-operations teams (Growth/Enterprise; automate HR processes and reporting); Multi-country scale-ups (Enterprise; permissions, compliance, and workflow depth); Enterprises modernizing HR systems (Enterprise; API-first integrations and AI operations).
CUSTOMER BUYING BEHAVIOUR
Headcount growth, HR-tool sprawl, onboarding friction, or reporting gaps trigger evaluation. A people team trials the HRIS, migrates employee data, validates workflows and integrations, then expands into more modules and employees.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Customers are buying a governed employee-data system, not an HR directory. RULE 1 — PRICE THE EMPLOYEE RECORD. Headcount maps to data, workflow, and compliance scope. RULE 2 — PRICE WORKFLOW AUTOMATION. Onboarding, changes, approvals, and documents reduce people-team labor. RULE 3 — SELL INTEGRATION CONTROL. API-first design reduces the cost of connecting HR to the rest of the stack. RULE 4 — VENDOR TRAP: Modern UX without compliance depth creates churn when the customer scales globally. The buyer is really buying a people-operations system budget, proven by employee count, workflows, and module adoption.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Incumbent displacement risk is high because Workday, HiBob, Personio, and BambooHR have deeper payroll, compliance, and global employment capabilities. Payroll complexity risk is structural because global employment law, benefits, and tax rules vary by market. Churn risk arises when customers outgrow the platform or consolidate into a broader HCM suite. Low differentiation risk arises if modern UX and API access are copied by incumbents. Enterprise sales risk arises when security, procurement, and implementation requirements slow adoption. Funding/valuation: Humaans raised a $15 million Series A in 2021; current ARR and valuation are not publicly disclosed.
Where the model can break
4
MOTION
motion ge cs
Humaans used product-led trials and API-first onboarding for startups and scale-ups, while direct sales supported larger customers needing security, workflow depth, and implementation. The dual motion reflected a modern HRIS that could be adopted quickly but required enterprise depth at scale.
GROWTH EXPANSION MODEL
Land & Expand, Product Line Expansion
HOW THEY EXPAND
Humaans landed with employee data and documents, then expanded within accounts through onboarding, absence, compensation, reporting, workflows, and AI. Product-line expansion added enterprise security, permissions, and deeper HR operations. The dependency is that each addition must reinforce the employee-data system of record; disconnected features would dilute the modern HRIS advantage.
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against Workday, BambooHR, Personio, HiBob, and CharlieHR, Humaans used Differentiation through speed, modern UX, API-first architecture, and flexible workflows. Its sequence moved from employee data into broader people operations and enterprise capabilities. The viable resource was a modern data layer; the constraint is that incumbents can copy UX while retaining compliance depth.
GROWTH ENGINE
GTM
Content Flywheel
People teams discover Humaans through trials, SEO, and integrations. A team migrates employee data, configures workflows, and connects payroll or productivity tools; successful use leads to more modules and employees. As headcount grows, the customer expands into enterprise capabilities. The repeatable trigger is headcount growth, HR-tool sprawl, or onboarding friction. The engine requires fast data migration, reliable integrations, and clear workflow value; it breaks when customers need payroll or compliance depth the platform lacks. A founder can reproduce this by owning the system-of-record layer before expanding into workflows.
Humaans runs a hybrid product-led and sales-assisted GTM. Trials and API-first onboarding create adoption among startups and scale-ups; direct sales expand into larger customers needing security and workflow depth; integrations deepen retention. The primary motion is product-led self-serve, with sales-assisted expansion for larger accounts. The transferable components are a system-of-record wedge, API-first distribution, and record-based pricing; they require strong data migration, integrations, and compliance roadmap.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is Switching Costs: once a company stores employee records, documents, workflows, and historical HR data in Humaans, migration creates data, compliance, and operational risk. Integrations with payroll, identity, and productivity tools deepen that dependence.
| MOAT INTELLIGENCE
THE STANDARD: HRIS lock-in lasts when the platform holds the employee record, workflow history, and compliance documentation. RULE 1 — EMPLOYEE DATA DEPTH: Records, documents, and history create migration cost. RULE 2 — WORKFLOW DEPENDENCE: Onboarding, approvals, and changes become interdependent. RULE 3 — INTEGRATION DEPENDENCE: API connections make the HRIS part of the customer’s architecture. THE SIGNAL: Humaans serves scaling companies with employee data, workflows, documents, reporting, and AI capabilities, and raised a $15 million Series A in 2021. The moat does not protect against an incumbent HRIS copying modern UX or a customer consolidating into a broader HCM suite.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — VALIDATE THE MODERN HRIS WEDGE: Founded in 2019, Humaans built an API-first employee-data layer for fast-growing companies. WATCH: Data migration and integration reliability. $1–5M ARR — PROVE PEOPLE-OPS PRODUCT-MARKET FIT: Humaans converted startups and scale-ups into recurring HRIS customers through trials, workflows, and integrations. $5–10M ARR — EXPAND INTO WORKFLOWS AND AI: The platform added onboarding, absence, compensation, reporting, and AI capabilities such as Athena. $10–50M ARR — SCALE INTO ENTERPRISE HR OPERATIONS: Humaans added security, permissions, workflow depth, and larger headcount deployments. $50–100M ARR — NOT REACHED publicly verified; Humaans’ current ARR is not publicly disclosed. $100M+ ARR — NOT REACHED publicly verified. Rule: Own the employee-data system of record first, then expand into the workflows and compliance layers that make it indispensable.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Win the system-of-record layer in a crowded vertical by making the data fast, connected, and easy to operate, then expand into workflows that depend on it. SEQUENCE: 1. First, identify a fragmented record-keeping workflow with an incumbent that feels slow or rigid; prerequisite: a reachable operator segment. 2. Next, build the smallest data layer and validate repeat usage; gate expansion on data ownership and retention. 3. Then, add workflows and compliance only when the record layer is trusted; prerequisite: reliable integrations and migration. WORKED: Humaans’ API-first employee data, modern UX, and workflow expansion created a distinct HRIS position. CAUTION: Do not build an HR suite before proving data ownership; breadth without a system-of-record wedge creates churn. CAUTION: Do not underestimate payroll and global compliance; they determine enterprise readiness. LIMITATION: Humaans does not publicly disclose ARR, churn, gross margin, or customer concentration; its $15 million Series A demonstrates investor conviction but not verified revenue quality.
bottom of page