Case Study: Improving FCR from 2.4 to 1.7 on a 50-Bin Cricket Farm

Bin-level FCR tracking revealed 3 underperforming bins responsible for 40% of wasted feed. Before CricketOps, the farm had been averaging FCR 2.4 across 50 bins and attributing the poor performance to their feed supplier. After 90 days of bin-level data, the problem turned out to be three bins in a corner with a ventilation dead spot, and fixing it took two hours.

This is how they got from 2.4 to 1.7 and what the $680/month feed cost savings looked like.

TL;DR

• Bin-level FCR tracking revealed 3 underperforming bins responsible for 40% of wasted feed.
• Before CricketOps, the farm had been averaging FCR 2.4 across 50 bins and attributing the poor performance to their feed supplier.
• After 90 days of bin-level data, the problem turned out to be three bins in a corner with a ventilation dead spot, and fixing it took two hours.
• This is how they got from 2.4 to 1.7 and what the $680/month feed cost savings looked like.
• Feed spend had been creeping up, they were spending approximately $2,350/month on feed.
• Three bins, numbers 31, 32, and 33, were running at FCR 2.8, 3.1, and 2.7 respectively.
• The operator placed a temporary sensor in that corner: ammonia smell was noticeable, temperature was 2–3°F warmer than the rest of the room (from poor air circulation), and humidity was 15% higher than the room average.

Background: A 50-Bin Operation Running on Batch Averages

The farm was an established Acheta domesticus feeder cricket operation selling to a regional pet store chain and an online reptile keeper subscription service. They'd been operating for three years with consistent sales but declining margins.

Feed spend had been creeping up, they were spending approximately $2,350/month on feed. The operator knew their FCR wasn't great but had been calculating it at a batch level: total feed delivered to the room divided by total weight harvested from the room. That gave them an average of 2.4. They assumed their feed source was the issue and had tried three different suppliers with no improvement.

When they moved to CricketOps and started logging feed per bin, the picture changed immediately.

Month 1: The Discovery

Within the first three weeks of bin-level logging, the FCR dashboard showed a clear pattern. Out of 50 bins, 47 were running between FCR 1.7 and 2.0. Three bins, numbers 31, 32, and 33, were running at FCR 2.8, 3.1, and 2.7 respectively.

Those three bins were adjacent, occupying the corner of the grow-out room farthest from the ventilation intake. The operator placed a temporary sensor in that corner: ammonia smell was noticeable, temperature was 2–3°F warmer than the rest of the room (from poor air circulation), and humidity was 15% higher than the room average.

The high-FCR bins weren't being managed differently from the others. They were in a worse environment: higher ammonia, more heat stress, higher humidity. Crickets in those bins were spending metabolic energy on stress response rather than growth.

Month 1 FCR data:

• Bins 1–30 (good zone): average FCR 1.85
• Bins 31–33 (problem corner): average FCR 2.87
• Farm average: 2.4 (contaminated by the 3 outliers)

If the farm had 50 bins all at 1.85, their monthly feed cost would have been $1,670. The three outlier bins at 2.87 were consuming feed at a rate equivalent to 7 normal bins producing the same output.

Month 2: The Fix

The operator added a small oscillating fan on a shelf in the corner aimed at the ceiling, improving air circulation to the problem zone. They also added a second ventilation cut-out to the lids on bins 31–33 and reduced the stocking density in those bins by 15% (from 1,100 to 940 crickets per bin).

These were simple, cheap changes. Total cost: $0 (used an existing fan) plus 2 hours of time.

Month 2 FCR data (after changes):

• Bins 31–33: average FCR 2.1 (down from 2.87)
• Farm average: 1.95

Better, but still above the 1.85 target. A second investigation identified that those bins were also receiving slightly more feed per feeding than adjacent bins, a legacy of an old ad-hoc practice where the corner bins got a "little extra" because they always looked like they were eating it all. With FCR tracking showing those bins were still above average, the feed quantity was equalized.

Month 3: Consolidation

By the end of the third month, all three problem bins were running at FCR 1.7–1.9, consistent with the rest of the farm.

Month 3 FCR data:

• Farm average: 1.73
• No bins above 2.1

The Financial Impact

| Metric | Pre-CricketOps | Month 3 |

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

| Farm average FCR | 2.4 | 1.73 |

| Monthly feed spend | $2,350 | $1,670 |

| Monthly feed savings |, | $680 |

| Annual feed savings |, | $8,160 |

The $680/month in feed savings covers the CricketOps Professional subscription ($129/month) with $551/month in net savings. The subscription paid for itself within the first month of corrective action.

What the Farm Learned About Batch vs. Bin Tracking

The three years this farm spent tracking FCR at the batch level gave them an average that was accurate but useless. 2.4 told them "we have a problem." It didn't tell them where.

Bin-level FCR told them exactly where, three specific bins in a specific corner with specific identifiable causes. The fix took two hours. The problem had been costing them $680/month for an estimated three-plus years.

That's approximately $24,480 in excess feed costs that bin-level tracking would have revealed much earlier.

FAQ

How much can FCR improvement save a cricket farm each month?

In this case, improving farm average FCR from 2.4 to 1.73 saved $680/month on a 50-bin Acheta domesticus farm. The savings scale with bin count and feed cost per pound. For every 0.1-point improvement in FCR on a 50-bin farm paying $0.30/lb for feed, the monthly savings are approximately $45–$65 depending on output weight.

What causes high FCR in cricket farming?

The most common causes of elevated FCR are: poor ventilation causing ammonia buildup and stress response (found in this case study), suboptimal temperature reducing growth efficiency, overcrowding increasing competition and ammonia, insufficient feed protein content (below 22%), and inconsistent feeding frequency especially at the pinhead stage. Bin-level FCR data is the tool that tells you which of these is actually driving your numbers.

How long does it take to improve FCR after switching to bin-level tracking?

In this case, the first actionable data appeared within 3 weeks. Corrective actions were implemented in Week 4. Significant FCR improvement in the problem bins appeared within 2–3 weeks of the fix. Full stabilization at the new farm average (1.73) took about 60 days from the first bin-level data. The time from "identified the problem" to "fixed it" was less than a week.

How do I know if I am harvesting too early or too late?

Harvesting too early means crickets have not reached peak body mass, reducing yield per bin cycle. Harvesting too late means increased mortality from natural die-off and rising ammonia that degrades product quality. Most operations find their optimal harvest window by weighing a sample of 50-100 crickets at multiple points in the grow-out cycle and identifying the window where daily weight gain falls below a meaningful threshold.

Does harvest timing affect the nutritional profile of finished crickets?

Yes. Younger adults harvested earlier tend to show a higher protein-to-fat ratio. Older adults accumulate more fat. If your buyers specify a target protein percentage or fat content, aligning harvest timing to hit those specifications consistently is important. Running periodic proximate analyses on finished product batches helps you verify you are staying within buyer tolerances over time.

What is the best method for humanely killing crickets at harvest?

Freezing is the most widely used commercial method. Placing crickets in a freezer at 0°F or below causes rapid loss of consciousness and death. CO2 stunning prior to freezing is used by some certified-humane operations to reduce the duration before unconsciousness. High-temperature methods (blanching) are also used in some flour production operations. Consult your buyer's specifications and any applicable certification standards for the methods they accept.

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
• Journal of Insects as Food and Feed (Wageningen Academic Publishers)
• USDA Agricultural Research Service

Get Started with CricketOps

Consistent harvest timing and FCR improvement both require historical data on how your specific bins perform across the production cycle. CricketOps tracks growth milestones, logs harvest weights by bin, and builds the record that lets you identify which bins consistently hit your targets and which ones need attention. Try CricketOps on your next production cycle.