Cultivation execution
Know more.
Do it the same way every time.
Cultiv8IQ pairs live room data with the SOPs your crew actually follows — so nothing is guessed, nothing is re-typed, and the operation gets tighter every cycle.
Flower 3
Day 38 · Gelato 41In rangeTemp
78.4°F
RH
58%
VPD
1.24kPa
CO₂
1,150ppm
Light
100%
PPFD
920µmol
Product illustration — sample data.
In daily production use by commercial cultivators — built on the floor, with the crew.
The problem
The work gets done. The knowledge doesn't stick.
Most facilities aren't short on effort — they're short on repeatability. What the best grower knows never becomes what the room does, and the numbers that would prove it out are scattered across paper, spreadsheets and someone's phone.
Every grower runs the room a little differently, and the good version lives in one person's head.
One published SOP, the same steps every time — in hand at the bench.
Numbers on a clipboard, typed up later, never charted against anything.
Captured where the work happens, and read against the plants that produced them.
The same information re-entered into a spreadsheet, a binder and the state system.
Entered once by the crew, and reused everywhere it's needed.
What you get
Live data and standard work, in the same system.
Not a dashboard bolted onto a document folder. The SOP a grower opens at the bench and the reading they take thirty seconds later belong to the same room, the same cycle and the same record.
Rooms that show the whole picture
Every room has one page: what's planted where on an interactive map, its environment graph, the crew's to-dos and its irrigation — instead of four screens that don't know about each other.
The numbers, where the work happens
Walk the zones and log runoff on a phone. Dryback, substrate EC read at field capacity, and your recipe's weekly setpoints charted against what the room actually did — so a steering decision is a reading, not a hunch.
SOPs that leave the binder
Build a procedure step by step, publish it, and it's on every phone on the floor. Editing a published SOP bumps its version, so the crew can only ever be following the current one — not a printout from two seasons ago.
Environment on autopilot
Aroya, TrolMaster and Rhythm feed climate and fertigation in on their own. When a room sits out of range, the people responsible for that room get a push notification.
Standard work, on schedule
Recurring tasks land on the right room on the right day, a message board keeps an issue open until it's resolved, and a morning review puts what needs attention in front of whoever opens the app first.
METRC without the re-typing
Plant batches, moves, destructions and transfer manifests are pushed from the records your crew already filled in — with a review queue for anything that needs a human.
Runoff & crop steering
Read the room off its own numbers.
Every zone walk lands here. The dryback sawtooth, the EC stack, and the flush that pulled it back — against the recipe's target band, not a gut call.
Out of range
Catch it while it's still a nuisance.
When a room drifts outside its setpoints, the people responsible for that room are notified — and a to-do is raised against it automatically, assigned and dated. Nobody has to be watching a dashboard at 2am for a stuck valve to get caught on the same shift it started, instead of on the morning walk when it's already a crop emergency.
VPD 1.62 kPa — above the 1.35 setpoint
Sustained, not a spike. RH has been falling since the lights came on.
Pushed to 3 people
Everyone assigned to Flower 2 — on their phones, not buried in an inbox.
To-do raised
Check Flower 2 dehu + RH setpoint
Flower 2 · due today · unassigned
The cycle
Every stage hands off to the next.
Clone batches become veg batches become a flower cycle, and every reading, photo and note stays with that group the whole way. Nothing is re-keyed between stages and nothing is orphaned at the end of one — a harvested group moves out of the room's live workspace into its own history, with the full record intact and comparable to the last run.
- 01
Clone
Batches cut and tracked from the mother they came off.
- 02
Veg
Counts, culls and moves — with the compliance side kept in step.
- 03
Flower
Flip, per-zone genetics, runoff, environment, crop steering.
- 04
Harvest
Wet weights by zone, into a dry room the whole crew can see.
- 05
Dry & trim
Retention on a wet basis, trim output, then packaged.
The room, mapped
Know what's on every bench.
Genetics per zone, plant counts per bench, and a pin anyone can drop when something's wrong — which becomes a to-do for that room, assigned and dated.
Flagged
Z2 · bench 2 — emitter clog, 6 plants dry. Now a to-do.
Plant photos
A photographic record you can actually trust.
Designate a few index plants per room and the app hands the crew a daily checklist — six shot types on a schedule anchored to cycle day one, with the previous shot ghosted over the viewfinder so the frame lines up. Every photo files itself against the room's cycle, recipe week, strain and light. Then put this week beside the same week of a previous cycle. And because coverage is derived from the photos themselves rather than someone ticking a box, you can see exactly which shots were missed — the morning digest names yesterday's gaps by room.
Wk 5 · 12 Aug · LED · marker A
Wk 5 · 04 May · LED · marker A
Same capture point, same light, same recipe week — so the difference you are looking at is the plants, not the photograph.
3 index plants · 6 shot types · schedule anchored to cycle day 1. The morning digest names yesterday’s gaps by room — and only when there are any.
Integrations
It plugs into the hardware and software you already use.
Readings arrive on a schedule — nobody exports a CSV on Friday. Not listed? Anything that can post a reading or hand over a file feeds the same tables.
Aroya
Substrate and climate sensors
TrolMaster
Room climate control
Rhythm
Fertigation — feed EC, pH, volume
OpenSprinkler
Irrigation control — run and schedule shots
METRC
State compliance, both directions
Airtable
Existing bases kept in sync
Google Sheets
Existing trackers imported, not re-typed
More on the way
New hardware and software integrations land regularly.
Maintenance
Raise it, assign it, know what it cost.
A flagged pin or a failed room check becomes a work order against the actual unit — serial, warranty, photo. Assign it to your repair crew and they're notified; log the vendor, cost and invoice as it moves open → completed → paid. When it's fixed, everyone working that room sees it — no more 'didn't someone already fix that?'
Dehu #2 short-cycling
Quest 506 · SN 4471
Notified
Replace bench 4 emitter line
Netafim 16mm
Notified
Rebalance zone 3 manifold
Dosatron D25RE2
Cascade Mech.
Quarterly filter change
AHU-1
Paid · INV-2214
For the crew
If the crew won't use it, it isn't data.
Phone-first, installable
It installs from the browser onto a home screen — no app store, no reinstalls. The bench work is designed for a phone in a bright room with gloves on.
Eight languages
English, Spanish, Chinese, Thai, Russian, Armenian, German and Dutch — the whole app, not just the menus. Each person picks their own.
Access that fits the org
Roles from viewer to admin, optional per-room scoping, and multiple facilities under one company — each one separate, the way each crew actually works.
Questions
What operators ask first.
If yours isn't here, put it in the demo request and we'll answer it directly.
What is cultivation execution software?
It is the system the floor actually runs on. Cultivation execution software pairs the live data coming off a grow — substrate moisture, runoff EC, room climate, irrigation — with the standard work a crew performs against it, so the reading and the procedure it should trigger live in the same place. It is distinct from an analytics or reporting tool: the point is not only to show an owner a chart after the fact, but to make the right task appear in front of the right grower while the cycle is still running.
Does Cultiv8IQ integrate with METRC?
Yes. Plant batches, moves, destructions and transfer manifests are pushed to METRC from the records your crew already filled in, rather than being re-typed into the state system days later. Anything that needs a human decision lands in a review queue instead of failing silently.
Which hardware and software does it work with?
Aroya for substrate and climate sensors, TrolMaster for room climate and lighting, Rhythm for fertigation, OpenSprinkler for irrigation control, METRC for state compliance, and Airtable or Google Sheets for trackers you already keep. Anything that can post a reading or hand over a file can feed the same tables, and more integrations are added regularly.
Can I control irrigation from the app?
Yes — irrigation is controllable through the OpenSprinkler integration, so shots can be run and scheduled from the same place the runoff data lands.
What happens when a room drifts out of range?
The people responsible for that room are notified on their phones, and a to-do is raised against the room automatically, assigned and dated. That means a drift gets handled on the shift it started rather than being discovered on the next morning walk, when it has usually become a crop emergency.
Can my crew use it in their own language?
The whole application — not just the menus — is available in eight languages: English, Spanish, Chinese, Thai, Russian, Armenian, German and Dutch. Each person chooses their own, so a mixed crew can work side by side in the same rooms.
Does it work on a phone?
It installs onto a phone's home screen straight from the browser, with no app store and no reinstalls when it updates. The bench work — logging runoff, walking zones, following an SOP, closing out a task — is designed for a phone used in a bright room with gloves on.
Can I track the crop with photos?
Yes. Shoot the canopy from named capture points — the same vantage spot each week — and the photo is stamped automatically with the room's active cycle, its recipe week, and the light and fixture it was taken under. You can then put this week beside the same week of an earlier cycle. If the two shots differ on capture point, camera or lighting, the comparison says so rather than letting you draw a false conclusion, and originals are kept full-resolution and are never deleted automatically.
How do we know the crew actually took the photos?
Coverage is derived from the photos themselves, not from anyone confirming they did it. The app knows which index plants and which shot types were due on a given day, checks what actually arrived, and shows a grid of captured, missed and not-scheduled per room. A morning digest names yesterday's gaps by room, and only sends when there are gaps. Photos backfilled later are recorded but never counted as same-day, so the record cannot be quietly tidied up after the fact.
Can it replace the spreadsheets we run now?
That is what it is for. Runoff logs, room checks, SOPs, tasks, harvest records and equipment maintenance stop living in separate files and get tied to the rooms and plant groups they belong to. Existing Google Sheets and Airtable trackers can be brought in rather than re-typed.
See it against your own rooms.
The fastest way to judge this is to walk one of your cycles through it. Tell us how your facility is laid out and we'll set up a demo around it.
Already have an account? Log in