Scaling a Cricket Farm: From 10 Bins to 100 and Beyond

Farms that track FCR per bin reduce feed costs by an average of 18%. That number gets a lot more important when you're running 100 bins instead of 10. Feed cost per bin doesn't change. Multiply it by 90 more bins and the savings on a 0.3-point FCR improvement become substantial.

Scaling a cricket farm is straightforward in theory: more bins, more output, more revenue. In practice, the constraints that didn't matter at 10 bins, tracking gaps, manual labor time, environmental inconsistencies, start costing real money as your bin count grows. This guide covers what actually changes at each tier and how to manage the transition without losing quality or margin.

TL;DR

Farms that track FCR per bin reduce feed costs by an average of 18%.
Multiply it by 90 more bins and the savings on a 0.3-point FCR improvement become substantial.
In practice, the constraints that didn't matter at 10 bins, tracking gaps, manual labor time, environmental inconsistencies, start costing real money as your bin count grows.
With 25+ bins cycling at different stages, keeping track of what each bin needs today becomes a full-time cognitive load.
At 30 bins, daily rounds take 2–3 hours if you're doing it right.
If you're above 2.0 consistently, you have identifiable underperforming bins.
Without task management and routing, 4–5 people still feel stretched.

FCR target at this tier: 1.7 or below.

FCR target at this tier: 1.7–1.9.

Tier 1: 10–25 Bins (Startup to Early Commercial)

At this stage you're figuring out your operation. You're probably still hand-entering data, doing daily checks manually, and getting comfortable with your grow-out cycle.

What works at this scale: spreadsheets for bin tracking, manual temperature checks, a thermometer in each room or zone, visual mortality assessment.

What starts breaking down: inconsistent data entry when you're busy, missed harvest windows when a bin gets crowded out of your mental priority list, no early warning on temperature drops unless you happen to be there.

FCR benchmark at this tier: 1.8–2.2 is typical. Farms in their first year often run above 2.0 because feed schedules aren't optimized and pinhead feeding frequency is irregular.

What to fix before moving to the next tier:

Stable hatch-to-harvest cycle documented for at least 3 consecutive batches
FCR per bin tracked (even in a spreadsheet) for at least 2 grow-out cycles
Temperature monitoring in place with at least one overnight alert

Tier 2: 25–60 Bins (Growing Commercial)

This is where manual systems fail. With 25+ bins cycling at different stages, keeping track of what each bin needs today becomes a full-time cognitive load. You start forgetting harvest windows. You notice your FCR has drifted but you're not sure which bins are causing it.

Labor is the first constraint you hit. At 30 bins, daily rounds take 2–3 hours if you're doing it right. At 50, you either hire help or cut corners.

What you need at this tier:

Bin-level lifecycle tracking software, this is when CricketOps pays for itself
Automated temperature and humidity alerts, one overnight crash can kill a bin's worth of product
Daily plan generation, knowing exactly what needs feeding, checking, or harvesting each morning
At least one part-time worker who knows your protocols

Labor reality check: Labor costs typically triple between 20 and 60 bins without a tracking system routing daily tasks. That's not inefficiency, it's the natural result of more bins, more complexity, and more data to hold in someone's head. A tracking system doesn't replace the labor; it makes it manageable.

FCR target at this tier: 1.7–1.9. If you're above 2.0 consistently, you have identifiable underperforming bins. Bin-level FCR data will show you which ones.

Tier 3: 60–150 Bins (Full Commercial)

At this scale, you're running a business with real fixed costs, probable employees, and regulatory requirements if you're producing for food-grade markets.

The operational challenges shift. It's less about managing individual bins and more about managing systems, staffing consistency, supply chain reliability, production planning against customer commitments.

Key scaling investments at this tier:

Commercial HVAC with redundant heating, can't afford a full-room temperature crash at this scale
Drum separator or mechanical harvest equipment, manual harvesting at 100+ bins is economically unsustainable
Multi-user farm management platform with team permissions, you need your team entering data consistently, not each person using their own system
Full food safety documentation if selling flour or food ingredients, retail buyers at this scale will ask for it

Staffing: A 100-bin operation typically requires 2–3 FTE equivalents when properly systematized. Without task management and routing, 4–5 people still feel stretched.

FCR target at this tier: 1.7 or below. At this scale, a 0.1-point improvement in FCR across 100 bins saves hundreds of dollars per month in feed cost.

What Equipment Changes at Scale

|---|---|---|---|---|

FCR Benchmarks by Scale

Your FCR should improve as you scale, more data, better protocols, more consistent feed sourcing. If your FCR gets worse as you add bins, that's a signal that your tracking and protocols aren't scaling with your bin count.

|---|---|---|---|

| 10–25 bins | 1.8–2.2 | 1.6 | Above 2.5 |

| 25–60 bins | 1.7–2.0 | 1.6 | Above 2.2 |

| 60–150 bins | 1.7–1.9 | 1.5 | Above 2.0 |

| 150+ bins | 1.5–1.8 | 1.4 | Above 1.9 |

Managing Quality Control at Scale

Quality control at 10 bins is visual. You look at each bin, you notice problems, you fix them. At 100 bins, visual inspection is insufficient, there are too many bins to catch early-stage issues before they become losses.

Systematic quality control at scale requires:

Mortality cause tracking: Log every significant die-off event with its apparent cause. After 60 days of data, patterns emerge, specific bins, specific times of day, specific temperature ranges. Without cause data, you're reacting. With it, you're preventing.

Size consistency checks: Random sample 10–15% of bins weekly for size distribution. If bins are diverging significantly in size at the same stage, something in your protocol is inconsistent, feed, temperature, or density.

Batch documentation: At the food-grade scale, every production batch needs a paper trail. This is both a compliance requirement and a quality tool. If a batch tests poorly or a customer reports a problem, batch records let you trace it back to specific bins, specific grow-out conditions.

Common Scaling Mistakes

Expanding too fast before FCR and mortality are stable. Adding bins before your protocol is consistent just gives you more instances of the same problems. Get your existing bins to benchmark FCR before scaling.

Skipping monitoring hardware. At 10 bins, you can check temperature manually twice a day. At 50, you're not checking every bin twice a day. Environmental monitoring with automated alerts isn't a luxury at scale, it's risk management for your most expensive failures.

Understaffing the transition period. The gap between your current capacity and your new capacity is a stressful period. Plan for more labor during setup and early operation at each new tier, then systematize down once protocols are stable.

Not upgrading software with your bin count. Spreadsheets that worked at 15 bins become a liability at 50. The time cost of manual tracking at scale is real and compounding.

FAQ

At what point does a cricket farm become profitable at scale?

A feeder cricket operation typically reaches break-even at 20–30 bins at full capacity, assuming good FCR and consistent sales. A cricket flour operation has higher compliance costs and often takes 12–18 months to reach profitability. The faster route to profitability at any scale is improving FCR and reducing mortality, both of which require data you can only get from bin-level tracking.

What equipment is needed to scale beyond 50 bins?

Beyond 50 bins you need zone-level HVAC with at least one redundant heating system, IoT temperature and humidity sensors with automated alerts, a drum separator for harvest, and a farm management platform with team task assignment. The monitoring and tracking investments typically pay back within 3–6 months at that scale through reduced die-off events alone.

How do you manage quality control across hundreds of cricket bins?

Systematic quality control at scale requires three things: bin-level FCR tracking (so you identify underperformers before they become chronic), mortality cause logging (so patterns become visible and preventable), and batch documentation (so you can trace any quality issue back to its source). Manual visual inspection isn't sufficient above 50 bins.

How does CricketOps help track the metrics described in this article?

CricketOps provides bin-level logging for the variables that drive production outcomes -- feed inputs, environmental conditions, mortality events, and harvest results. Rather than maintaining these records in separate spreadsheets, you can view performance trends across bins and over time to identify which operational variables correlate with better outcomes in your specific facility.

Where can I find industry benchmarks to compare my operation's performance?

The North American Coalition for Insect Agriculture (NACIA) publishes periodic industry reports with production benchmarks. University extension programs in agricultural states, including the University of Georgia and University of Florida IFAS, occasionally publish insect farming production data. Industry conferences hosted by the Entomological Society of America and the Insects to Feed the World symposium series are additional sources of peer benchmarking data.

What is the biggest operational mistake cricket farmers make in their first year?

Expanding bin count before achieving consistent FCR and mortality targets in existing bins is the most common and costly first-year mistake. At 5-10 bins, problems are manageable. At 30-50 bins, the same proportional problems represent much larger financial losses. Most experienced cricket farmers recommend holding expansion until you have three consecutive production cycles hitting your FCR and mortality targets.

Sources

Food and Agriculture Organization of the United Nations (FAO) -- Edible Insects: Future Prospects for Food and Feed Security
North American Coalition for Insect Agriculture (NACIA)
Entomological Society of America
University of Georgia Cooperative Extension
Journal of Insects as Food and Feed (Wageningen Academic Publishers)

Get Started with CricketOps

The practices covered in this article are easier to apply consistently when they are supported by organized production data. CricketOps gives cricket farmers the tools to track what matters -- by bin, by batch, and over time. Start your next production cycle in CricketOps and see how organized data changes the way you manage your operation.