Updated 4 November 2026
A company with 2,000 employees might hire 20 people a month. Another company of the same size might hire 200. Their headcounts match, but the workload for their recruiting teams does not. If you're choosing an AI interview platform, start with the number of candidates you need to interview each month. Then check whether the platform can handle that volume, fit into your hiring workflow and meet your organisation's security requirements.
The short answer
50 hires a month is an illustration, not an enterprise threshold.
There is no universal definition of enterprise hiring. Start with the interview volume and operational requirements your team actually has.
The 50-hires example below is only a way to show how hiring volume and headcount can differ. It is not a definition of enterprise hiring. Your own monthly interview volume is the number that matters when you choose a plan.
An Enterprise label on a pricing page does not tell you how many interviews are included or which features come with the plan. Check the monthly capacity, ATS integration, security documentation, access controls and support you will actually receive.
Start with the hiring workload, not the employee count
Consider two companies with 2,000 employees. If one hires 20 people a month and the other hires 200, the second team may need to screen and interview ten times as many candidates. The platform decision should reflect that workload, not the number of people on the payroll.
Estimate how many interviews you run each month
The latest US workforce benchmark can provide context, but it is not a substitute for your own hiring data. The US hires rate was 3.4% in September 2026, with 5.4 million hires (preliminary BLS Job Openings and Labor Turnover Survey, released 3 November 2026). This is a broad US figure, not a benchmark for your company or for Indian employers.
For a rough headcount estimate, divide monthly hires by 0.034. But do not use that estimate to choose your AI interview plan. For that, use your actual interview-to-hire ratio and count how many candidates your team interviews in a typical month.
Hires a month, and the company size that hires that many
Implied headcount = hires a month ÷ 0.034. US total nonfarm average, September 2026 (preliminary).
| Hires a month | Hires a year | Implied company size |
|---|---|---|
| 10 | 120 | about 290 |
| 25 | 300 | about 740 |
| 50 | 600 | about 1,470 |
| 100 | 1,200 | about 2,940 |
| 250 | 3,000 | about 7,350 |
The example is useful for showing why headcount can mislead. It cannot tell you how many interviews your team runs. That depends on the roles you hire for, how many candidates reach interview and how many interview stages you use.
A team hiring for high-turnover roles may interview far more candidates per hire than a team recruiting for a small number of specialist positions. Use your own recent numbers rather than assuming every company has the same hiring rate.
Once you know your monthly interview volume, you have a much more useful basis for comparing AI interview plans.
Find your own hires rate
The starting numbers are examples. Replace them with yours.
Turn your hiring target into monthly interview volume
Start with the number of people you hire each month, then multiply it by your interview-to-hire ratio. If your team conducts eight interviews for every hire and makes 30 hires a month, that is about 240 interviews a month. Use your own ratio from the last quarter; eight is only an illustration.
Use that monthly figure to check plan capacity. For example, if you expect around 240 interviews a month, a 50-interview Pilot plan will not cover the workload. Check what happens when you exceed included volume, whether unused interviews roll over and how many recruiters need access. AI Interview plans start at $250/month and scale with volume and requirements. Ask for the included interview volume, seats and overage terms for the plan you are considering; book a plan walkthrough.
Check the requirements that can affect an enterprise rollout
Interview volume is only part of the decision. A large hiring operation may also need security reviews, access controls, data-processing terms and an integration with its applicant tracking system. Find out which of these your organisation requires before you choose a plan, so the platform does not become a bottleneck during procurement.
Before choosing a platform, get clear answers to five practical questions: where candidate recordings and transcripts are stored; how they are protected; how long they are retained; which ATS workflows are supported; and what your security and procurement teams need to review. The checklist below gives you a starting point. Ask each provider for the relevant documents and confirm that the answers apply to the plan you are considering.
The enterprise review checklist
Tick each row once you have the document or the answer in hand.
of 8 ticked
If you hire in India, include the Digital Personal Data Protection Act and Rules in your review. Check which provisions are in force when you sign, what will apply during the contract and how candidate data is handled. Your legal team should assess your organisation's obligations; a platform's statement about compliance is not a substitute for that review.
India's Digital Personal Data Protection Rules were notified in the Gazette of India on 13 November 2025 (G.S.R. 846(E)). They switch on in phases. Rules 3, 5–16, 22 and 23 take effect 18 months after Gazette publication. The Gazette is dated 13 November, while the PIB summary describes the Rules as notified on 14 November. That creates a one-day difference in the calculated start date: 13 or 14 May 2027. These rules cover notice to people whose data you hold, security safeguards, breach reporting, retention and transfers abroad. For a plain-language explanation, see SCC Online's summary. Read the official Gazette notification and the PIB summary; also check the December 2025 corrigendum before treating the calculated date as a settled compliance deadline.
Before signing, agree on what candidate data the platform processes, where it is stored, how long it is retained, whether it is used to train models and how it is deleted. Put the agreed terms in the data-processing contract and check that they match your organisation's policies.
The 13/14 May 2027 dates are calculations from the 18-month commencement rule, not a calendar date printed in the Rules. Confirm the applicable date with counsel before setting compliance milestones. This is general information, not legal advice.
When a high headcount does not mean you need an enterprise plan
A company with 2,500 employees that hires 15 people a month may need less interview capacity than a smaller company hiring 100 people a month. Do not choose a plan based on headcount or the word Enterprise. Choose it based on the interviews your team actually runs and the requirements your organisation must meet.
The decision comes down to two things: the monthly interview volume you need to support and the operational requirements the platform must meet. If a lower plan covers both, you do not need to pay for an Enterprise tier simply because your company is large.
A lower-volume team may still need enterprise-level controls if its industry is regulated, a client contract requires specific certifications or candidate data crosses borders. In that case, check those requirements directly rather than assuming a higher interview-volume plan automatically includes them.
If you're comparing AI interview platforms, start with the capabilities your hiring process needs: interview volume, candidate experience, evaluation, ATS workflow and the security controls your organisation requires. See Fabric's comparison of AI interview platforms to understand how the options differ.
Where Fabric fits
Fabric's Enterprise plan is designed for teams running 500 or more interviews a month. It is custom-priced based on volume and requirements. AI Interview plans start at $250/month and scale with your needs. If your team runs fewer than 500 interviews, compare the plan that covers your monthly volume before assuming you need Enterprise.
Fabric supports high-volume interview operations, with up to 500 interviews running concurrently. Enterprise is designed for teams running 500+ interviews a month, with monthly capacity tailored to the contract. Per-client branding is available on Scale and Enterprise; two-way ATS integration is Enterprise-only. Confirm the specific integration and workflow you need with the Fabric team before making a decision.
For teams whose security review is part of the buying decision, Fabric lists the following controls and certifications:
- Fabric lists SOC 2 and ISO 27001 certifications. Request the current documentation and confirm the scope, reporting period and legal entity covered.
- Encryption: Ask for the current at-rest and in-transit encryption standards and the evidence that applies to the systems in scope. Do not infer a specific cipher or protocol from a certification badge.
- Data hosting: Fabric has confirmed hosting in India and the US. Ask which region will host your account and whether any residency restriction can be included in the contract.
- These controls can help your security team assess Fabric, but they do not replace your own privacy, legal or procurement review. Ask for the current reports and certificates, confirm the hosting arrangement for your account and check which integrations and controls are included in your plan.
- Fabric's integration directory lists 31+ connections across the hiring stack. Its ATS & HRIS section includes Workday, Keka, Lever, Greenhouse, iCIMS, Bullhorn, Darwinbox, JobDiva, Ceipal and Zoho Recruit. Two-way ATS integration for AI Interviews is Enterprise-only. Confirm that your ATS and the specific data flow you need are supported on your plan.
See the Fabric enterprise page for details on the rollout, security and integration requirements.
FAQ
How many hires a month counts as enterprise hiring?
There is no universal number. This article uses 50 hires a month as an illustration. At the US average hires rate of 3.4% a month (BLS JOLTS, September 2026), that would correspond to a company of roughly 1,470 employees. It is a calculation, not an official standard.
We have 2,500 employees but hire 15 people a month. Are we enterprise?
Not necessarily. Headcount alone does not determine whether you need an enterprise AI interview plan. Estimate your monthly interview volume, then check whether your required integrations, security controls and support are included in a lower tier.
What should an Indian company check before choosing an AI interview platform?
Check the DPDP Act and Rules with your legal team before signing. Agree on the platform's data-processing terms, retention period, deletion process, hosting location and whether candidate data is used to train models.
See whether Fabric can handle your interview volume
If your team is assessing hundreds of candidates each month, book a Fabric demo. We'll show you how the platform handles high-volume AI interviews, how results fit into your hiring workflow and which plan supports the volume and controls you need.