One Week Without.
One Week With.
One Clear Answer.
After 19 years of running pilots, we've learned that the simplest protocol is also the most scientific. Two weeks. Your equipment. Your data. Your decision.
Request a Pilot19 Years Taught Us Something Counterintuitive
Long Enough to Be Real
One week captures a full business cycle: weekday deliveries, weekend traffic, the normal rhythm of your operation. It's long enough to produce a statistically meaningful baseline — and short enough to avoid the weather shifts that bias longer studies.
Short Enough to Be Fair
Stretch a pilot across 30 or 60 days, and ambient conditions shift: outside temperature, humidity, kitchen load. Those variables cloud the before-and-after comparison. Two tight weeks — one without eTemp, one with — isolates the effect of the sensor itself.
This isn't a marketing shortcut. It's the methodology we landed on after nearly two decades of measuring real refrigeration systems under real operating conditions.
How the Pilot Works
You run it. We guide you. The entire pilot takes two weeks from start to finish — with zero downtime and zero risk to your operation. Your refrigeration keeps running the whole time. The only thing that changes is your data: less run time, fewer compressor cycles, and food temperatures that stay just as stable or improve.
The key to a valid comparison is operational symmetry: pick two weeks that look alike. If one falls during a holiday rush and the next is a normal week, the comparison won't be meaningful. Same deliveries, same traffic, same kitchen load. We'll help you choose the right windows.
Baseline: Run Without eTemp
Your refrigeration operates exactly as it does today. Data loggers record the baseline:
- Compressor run time and cycle frequency
- Food temperature throughout the cooling cycle
- Air temperature at key points
You use your own data loggers. If you need a recommendation, we can point you to reliable options. At the end of the week, download the data — plug the logger into a computer and export.
Install eTemp
Install the eTemp sensor on each unit. Installation takes under an hour per unit — no refrigerant lines opened, no existing components modified, no disruption to your operation. Most customers handle this with their existing maintenance staff using our guidance.
Install as soon as possible after the baseline week ends. The goal is to minimize any change in ambient conditions between the before and after periods — tight timing keeps the comparison accurate.
Measure With eTemp
The same units, the same data loggers, the same metrics. The only difference: eTemp is installed. After the week, download the data again.
See the Difference
Upload your before-and-after data. We produce a side-by-side comparison showing exactly what changed — compressor run time, cycle frequency, food temperature, and energy draw. The numbers speak for themselves.
What's Measured — and Why Each Metric Matters
Four metrics. No black boxes. Everything we measure is something you can verify with your own equipment.
How many minutes per hour your compressor is actively drawing power. This is your direct energy cost.
How often the compressor starts and stops. Fewer cycles means longer equipment life and lower maintenance.
The critical safety metric. Our average client sees food temperatures that are more stable — and if anything, slightly lower — with eTemp installed.
Ambient temperature inside the unit. Confirms that performance improvements aren't coming at the expense of cooling quality.
Food temperature is the one most efficiency pitches leave out. We lead with it — because if your savings come at the cost of food safety, they aren't savings. Our data shows eTemp maintains or improves temperature stability across every deployment.
For Stadiums & Event-Driven Venues
If your operation runs on an event calendar rather than a weekly business cycle, the standard one-week protocol isn't the right fit. A week with three home games isn't comparable to a week with none. For stadiums, arenas, and convention centers, we structure the pilot around three home games without eTemp versus three home games with it — ensuring each measurement period captures the same level of operational activity. The protocol and the metrics are identical. Only the time window adapts to your schedule.
You Run the Pilot. We Provide the Protocol.
As a small, focused company, we've designed the pilot to be run by your team — not ours. You receive a clear, step-by-step protocol that covers logger placement, data collection intervals, and what to look for. We're available to consult throughout. The result is a pilot that scales: you can run it across one location or twenty, and we don't become the bottleneck.
You use your own data loggers. We can recommend models if you need them. At the end of each measurement week, you plug the logger into a computer, download the data, and upload it. We handle the comparison.
Get the ProtocolSatisfaction Guaranteed — No Questions Asked
We've spent 19 years refining this technology and this protocol. We're confident in the results. If you complete the pilot and aren't satisfied with what the data shows, we refund your pilot package in full. No fine print. No justification required.
Common Questions
How many units should we include in a pilot?
We recommend a minimum of two units — that eliminates the possibility of a single-unit operational anomaly skewing the results. Two or three units is typical. For larger organizations, it's common to start with a test kitchen, then expand to a regional rollout before going chainwide.
Do we need to have data loggers already?
You'll need data loggers to record compressor run time, cycles, and temperatures. If you already have loggers as part of your operations, those will work. If not, we can recommend models that are well-suited to the protocol. The loggers connect via USB — at the end of each measurement week, you plug them into a computer, download the data files, and upload them for analysis.
What does the pilot package cost?
Self-serve pilots are $799 per sensor (recommended 2-sensor package $1,598), up to 10 units online. That includes the eTemp sensors, measurement protocol, installation guidance, and before-and-after comparison. Larger scopes are quoted offline. And if the pilot doesn't deliver — for any reason — we refund the full package.
Can we run the pilot on our own?
Yes — that's how we've designed it. You receive a detailed protocol covering logger placement, measurement intervals, and data handling. We're available for consultation throughout the process. The pilot is built to be run by your facilities or operations team, without requiring eTemp staff on site for the measurement periods.
Will eTemp affect food temperature or safety?
No — and this is one of the four metrics we measure during every pilot, specifically so you don't have to take our word for it. Across our client base, food temperatures with eTemp installed are consistently as stable or more stable than the baseline period. The sensor extends compressor off-cycles without letting internal temperatures drift outside your existing operating range.
Does eTemp work with our existing refrigeration equipment?
Yes. eTemp is compatible with both electronic and mechanical thermostats and integrates with all major commercial refrigeration brands — walk-ins, reach-ins, prep coolers, beverage merchandisers, and under-counter units. Installation is non-invasive: no refrigerant lines are opened and no existing components are modified.
Two Weeks to a Verifiable Decision
Start with a savings estimate, or go straight to a pilot. Either way, you'll be working from your own equipment and your own data — not industry averages.