# Why do data programs ask how many people you employ? https://licensethedata.com/blog/why-company-size-criteria-matter/ Headcount is a program filter, not a valuation formula. Understand what it can signal and what it cannot prove. Published 2026-10-13. 4 minute read. ## Two real filters, not a universal market minimum micro1’s Enterprise Data Partnership targets operationally mature businesses with 30+ employees and established documentation. Handshake’s intake seeks 20+ full-time employees and at least three years of operation. The qualifiers matter: workforce size and operating history are different requirements, and employee definitions are not identical. Do not convert either program’s criteria into a statement that smaller businesses have no useful records. Conversely, do not treat the lack of a published threshold at another provider as confirmation that it accepts a smaller team. Eligibility remains a question until that program confirms fit. Source: micro1: Enterprise Data Partnerships — https://www.micro1.ai/data-partnerships Source: Handshake AI: Data Partnership Intake — https://joinhandshake.com/ai/data-partnerships/license ## What headcount may be standing in for micro1 couples its employee target with mature operations, documentation and workflow quality. Appen describes demand for approval chains, exceptions and the reasoning behind decisions. Taken together, those public descriptions support a narrower observation: buyers are interested in organizational work patterns, not just the number of names on a payroll. Our analysis is that headcount can be a convenient screening proxy for the chance of finding multi-person workflows and substantial records. That is an interpretation, not a provider’s published causal model. It should not be used to multiply a team size into a price estimate. - A larger team may have more recorded hand-offs, but documentation still needs checking. - An established business may have long histories, but history can have gaps. - A specialized smaller team may have distinctive workflows, but buyer demand remains unconfirmed. Source: micro1: Enterprise Data Partnerships — https://www.micro1.ai/data-partnerships Source: Appen: Enterprise Data — https://www.appen.com/enterprise-data ## Workforce size cannot prove rights or readiness A company meeting the numeric filter still has to define what it controls and what it can disclose. The payroll count says nothing about whether client work belongs to the client, contractor IP has been assigned or employee records can be used for the proposed purpose. These are independent diligence questions. Use the employee threshold as an early fit check, not a substitute for legal, privacy or technical assessment. If you pass the threshold, the next useful description is your workflow and available history. If you do not pass it, avoid investing in exports for that particular program unless it confirms a relevant alternative. ## A 20–29-person business needs a precise question For a hypothetical business with 25 full-time employees and four years of operation, Handshake’s published intake criteria fit those two facts. That is not approval: data quality, rights, demand and other diligence still matter. The same business does not meet micro1’s published 30+ employee enterprise target. This is why an owner-facing comparison should show the actual criteria instead of a generic “small businesses welcome” label. Ask a program whether the relevant count is current full-time staff, historical workforce, contractors or another definition. Do not inflate the number or silently substitute one category for another. Source: micro1: Enterprise Data Partnerships — https://www.micro1.ai/data-partnerships Source: Handshake AI: Data Partnership Intake — https://joinhandshake.com/ai/data-partnerships/license ## Country and language are separate from size micro1 says it prioritizes US companies followed by other Western markets, and its inspected program FAQ primarily seeks English operations and documentation. Company representatives must be able to communicate with its team in English. A company meeting the headcount filter can still be outside present demand. A global referral route is not the same as global seller acceptance. For a business outside the program’s priority markets, ask about processing locations, allowed seller countries and the languages actually needed for the buyer’s use case. Do not infer a country whitelist from a calculator menu. Keep geographic eligibility and cross-border privacy review as separate decisions. Source: micro1: Enterprise Data Partnerships — https://www.micro1.ai/data-partnerships ## Describe evidence of maturity instead of chasing a bigger number Prepare a concise account of operational history: which recurring tasks are documented, which systems link decisions to outcomes and which periods are complete. As an editorial proposal, this is more useful than claiming your company is “data rich” without explaining the records. The practical result is a better qualification conversation. You can establish that a particular program is a poor fit without concluding your records are worthless, or meet its numeric criteria without assuming an offer is coming. No workforce band supplies an expected income figure. - State staff count honestly and identify the counting basis. - Give the operating-history period and known record gaps. - Name the workflow, not just the industry. - Ask which current buyer requirement your company might satisfy.