Start a Project
Structure and deliver a controlled-environment agriculture project.
Crop Urbanis combines its Platform with optional agronomic and implementation support to help organisations define, compare and deliver vertical-farm and hydroponic-greenhouse projects.
What to include in the first message
Use concise, non-confidential information so Crop Urbanis can identify the appropriate delivery scope and specialist input.
-
01
Project situation
New vertical farm, hydroponic greenhouse, retrofit, existing-farm improvement, supplier collaboration or research context.
-
02
Decision and stage
The decision required now, project geography, expected timeline and what information is already available.
-
03
People and responsibilities
The project owner, operating team and any engineering, supplier, research or delivery partners involved.
-
04
Production and constraints
The crop or production intent, market/use channel, quality considerations and known site or utility constraints.
-
05
Economics and decision criteria
An optional high-level investment range, approval stage and the trade-off or blocker that needs to be resolved. Detailed financial models are not requested through the public route.
-
06
Evidence available later
Only the categories of information that may exist, such as a project brief, site context or supplier context. Do not upload documents or private links; a controlled route is agreed only if needed.
-
07
Delivery need and desired next step
The project definition, delivery, agronomy, training or partner discussion you want to explore, and the high-level next conversation that would help. Product and private-beta scope are confirmed separately where relevant.
What happens next
Do not submit confidential project material through this public form
The public contact route is for high-level qualification only. Do not submit confidential project files, supplier documents, personal data or regulated information. Project work may use the Crop Urbanis Platform where appropriate. A project enquiry does not automatically create private-beta access; the relevant scope is confirmed separately.
Other routes
Technology or research collaboration
For a potential technology, research or validation collaboration, use the partnership route and state the permitted evidence and intended role.
Training or a general question
Use general contact for a course, media enquiry or a question that does not need project qualification.
The form starts a high-level qualification. Project work and private-beta access are separately scoped with the relevant organisation and qualified parties.