Getting Started with CricketOps: Onboarding Your Cricket Farm in Under an Hour
A lot of farm management software takes days to set up properly. CricketOps was designed differently. The average new user completes their initial setup in under 60 minutes, and new users who complete onboarding in their first session have a 90-day retention rate of 94%. That's not a coincidence. Getting set up properly from the start is what makes the platform stick.
This guide walks you through the CricketOps onboarding process step by step, from account creation to your first alert configured and your first bin entered. Follow this sequence and you'll be fully operational before your next coffee gets cold.
TL;DR
- A lot of farm management software takes days to set up properly
- The average new user completes their initial setup in under 60 minutes, and new users who complete onboarding in their first session have a 90-day retention rate of 94%
- Use whatever labeling system you already have, "B1," "Bin A," "Row 1-Shelf 3", or start fresh with CricketOps's numbering system
- For a farm with 10-20 bins, this process takes 10-15 minutes
- Select your sensor platform, follow the authorization flow (typically an OAuth connection that takes 2-3 minutes), and assign each sensor to a location in your farm
- Most farms complete initial onboarding in under 60 minutes
- For larger farms (50+ bins), batch import via CSV is available, contact CricketOps support for the import template
Step 2: Add Your Bins (15 minutes)
This is the most time-consuming part of onboarding, and only because there's actual data to enter.
- Use whatever labeling system you already have, "B1," "Bin A," "Row 1-Shelf 3", or start fresh with CricketOps's numbering system.
- For a farm with 10-20 bins, this process takes 10-15 minutes.
- Select your sensor platform, follow the authorization flow (typically an OAuth connection that takes 2-3 minutes), and assign each sensor to a location in your farm.
- Enter your feed times (e.g., 7am and 5pm for a twice-daily schedule).
- Most farms complete initial onboarding in under 60 minutes.
Before You Start: What to Have Ready
You'll need the following information to hand before you begin:
- Number of bins currently in production (active bins)
- Species in each bin (Acheta domesticus, Gryllus bimaculatus, etc.)
- Approximate age or hatch date for each active bin
- Current feed type and feeding schedule
- Temperature targets for your production room
- Your preferred alert contact (phone number for push notifications)
If you don't know exact hatch dates, that's fine. Use your best estimate. You can adjust bin records later. Getting something in the system is more important than getting it perfect on day one.
Step 1: Create Your Account and Set Farm Basics (10 minutes)
After signing up, you land on the Farm Setup screen. This is where you configure the basics:
Farm name and location: Enter your farm's name and state. This is used for reporting and compliance documentation.
Primary species: Select your main production species from the dropdown. If you're farming multiple species, select your primary one; you'll add others per-bin later.
Production goal: Select from feeder cricket production, cricket flour production, or both. This setting adjusts which features the platform surfaces prominently, flour producers see food safety templates more prominently, feeder producers see size-grade tracking.
Units: Confirm your preferred units for weight (pounds or grams), temperature (Fahrenheit or Celsius), and volume.
Complete this screen and you've established the foundation. Everything from here builds on these settings.
Step 2: Add Your Bins (15 minutes)
This is the most time-consuming part of onboarding, and only because there's actual data to enter. The process itself is simple.
Navigate to Bins > Add Bin. For each bin, enter:
Bin ID: This is your identifier. Use whatever labeling system you already have, "B1," "Bin A," "Row 1-Shelf 3", or start fresh with CricketOps's numbering system. Consistency matters; pick a format and stick with it.
Species: Select from the dropdown.
Life stage: Choose from egg, pinhead, early nymph, mid nymph, late nymph, or adult. This tells CricketOps where in the production cycle this bin sits.
Hatch/Start date: Enter the date the current batch hatched or was introduced. CricketOps uses this to calculate expected harvest dates.
Location: If you have multiple production rooms or shelf positions, you can tag each bin with a location. This becomes useful when you're using the platform to identify which area of your farm is running at different temperatures.
Feed type: Select your current feed or enter a custom feed if yours isn't in the library.
For a farm with 10-20 bins, this process takes 10-15 minutes. For larger farms (50+ bins), batch import via CSV is available, contact CricketOps support for the import template.
Step 3: Set Your Temperature and Humidity Thresholds (5 minutes)
Navigate to Settings > Alerts. This is where you configure the conditions that trigger push notifications.
Temperature alerts:
- Set your minimum threshold at 70-75°F for Acheta domesticus (5-10 degrees above the critical minimum of 60°F)
- Set your maximum threshold at 95°F (above optimal range for most production stages)
Humidity alerts:
- Set minimum at 40% (below this, you'll see molting problems and dehydration)
- Set maximum at 70% (above this, fungal and bacterial risks increase)
These are conservative starting values. After 2-4 weeks of observing your farm's baseline readings, adjust thresholds to reflect your actual normal range rather than general guidelines.
Notification delivery: Confirm push notifications are enabled on your mobile device. Test the connection by saving your thresholds and checking that the CricketOps app has permission to send notifications in your phone's settings.
Step 4: Connect Your Sensors (10 minutes, if applicable)
If you're using IoT temperature sensors (SensorPush, Govee, Inkbird), connect them now.
Navigate to Settings > Integrations > Sensors. Select your sensor platform, follow the authorization flow (typically an OAuth connection that takes 2-3 minutes), and assign each sensor to a location in your farm.
Once connected, you'll see sensor readings start appearing in your location records automatically. No manual logging needed for environmental data on those zones.
If you're not using sensors yet, skip this step. Manual temperature logging in CricketOps still provides notable value over notebook-based tracking.
Step 5: Set Up Your First Feeding Log (5 minutes)
Establish your feeding schedule in CricketOps to activate feeding reminders.
Navigate to Schedule > Feeding Schedule. Enter your feed times (e.g., 7am and 5pm for a twice-daily schedule). CricketOps will send reminders if a feeding hasn't been logged by your scheduled time.
Then log your first feeding: go to any active bin, tap "Log Feeding," enter the amount fed, and confirm. One done. The timestamp is recorded, and CricketOps now has a baseline feeding record for that bin.
Repeat for all active bins, or use the batch feeding log if multiple bins received the same feed today.
Step 6: Review Your Dashboard (5 minutes)
Once your bins are entered and alerts configured, spend a few minutes reviewing the dashboard.
The dashboard shows:
- All active bins and their current life stage
- Any active alerts
- Next harvest projections by bin
- Current average FCR across the farm
- Recent feeding logs
If something looks wrong, a harvest date seems off, a bin's life stage doesn't match what you see in your production room, adjust the bin record now. The platform is only as accurate as the data you put in.
FAQ
How long does it take to set up CricketOps for my farm?
Most farms complete initial onboarding in under 60 minutes. The bulk of that time is entering your active bins, approximately 1-2 minutes per bin. Account setup, alert configuration, and sensor connection are each 5-10 minutes. For large farms (50+ bins), CSV batch import reduces the bin entry time measurably.
What information do I need to enter for each bin in CricketOps?
Each bin requires: a bin ID, species, current life stage, hatch or start date, and feed type. Location and notes are optional but useful. You don't need exact dates if you don't have them, approximate is fine and can be adjusted as you build up your records.
Can I import my existing cricket farm data into CricketOps?
Yes, for bulk bin data via CSV import (contact support for the template). For historical production data, CricketOps support can assist with data migration from spreadsheets. Manual entry is also straightforward for farms with limited historical records. The cricket farm management guide covers how to structure your records for clean migration. See also the CricketOps review for full feature context.
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)
The Bottom Line
CricketOps onboarding is designed to be completable in a single session. Six steps, under an hour, and you're tracking your bins, monitoring your temperatures, and logging your feedings in a proper system.
The most important thing is to complete setup before you go back to your regular farm routine. The 94% retention rate among users who complete onboarding in their first session tells you something real: the farms that finish setup on day one keep using the platform. The ones who stop halfway through tend not to come back.
Get your bins in. Set your temperature alerts. Log your first feeding. That's all it takes to be fully operational.
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.