Project Brief and Data Room
Create one controlled CEA project record from a brief and permitted source material.
Turn a farm-project brief into a controlled delivery record.
The Crop Urbanis Platform structures site, crop, utility, market, supplier, budget and delivery evidence; compares configuration alternatives; retains assumptions; and prepares controlled outputs under qualified review. The core workflow operates as an internal MVP; private-beta access is considered for selected organisations by contact.
Operational internal MVP · Selective organisational beta
The core workflow is operational inside Crop Urbanis. Selected organisations can be considered for a separately scoped private beta covering data, confidentiality, authorised users, responsibilities, support and evaluation. Public self-service is not offered.
The Platform connects the evidence that drives a CEA decision with the requirements, calculations, reviews and outputs that follow from it.
One project record, not disconnected documents
Project inputs
Project objective, buyer, site and geography
Building, utility, climate and regulatory constraints
Crop targets, production assumptions and operating context
Supplier documents, equipment specifications, budget and delivery dependencies
Core Platform workflow
Capture the brief
Bring project files and facts into a structured evidence record.
Model requirements
Normalise constraints, missing data, responsibilities and validation questions.
Configure alternatives
Compare crop, system and delivery choices against stated assumptions.
Run controlled scenarios
Keep production, economics and sensitivity inputs deterministic and reviewable.
Compare supplier evidence
Retain sources, exclusions, dependencies and open clarification points.
Record decisions and approvals
Make expert review, customer decisions and partner responsibilities auditable.
Assemble delivery outputs
Prepare controlled inputs for delivery, commissioning, handover and operation.
Controlled record
Source links, versions, requirements and constraints
Missing information, conflicts, alternatives and assumptions
Deterministic scenarios, supplier comparison, risks and dependencies
Decisions, approvals, delivery and handover outputs
The core modules are operational in the internal MVP. Their availability in a selected organisational beta depends on scope; the Operations Feedback Layer remains roadmap or scoped validation.
Eight connected Platform modules
Requirements and Constraint Model
Turn project inputs into explicit, source-aware requirements and constraints.
Crop and Production Configuration
Make crop, system and production assumptions comparable before a project direction is selected.
Supplier and Equipment Intelligence
Compare supplier and equipment information against defined project requirements.
Scenario and Economics Engine
Compare production and financial options through controlled assumptions and deterministic calculations.
Delivery and Decision Control
Govern project choices, dependencies, changes and decision gates across a defined delivery scope.
Commissioning and Handover Pack
Turn an approved configuration into controlled readiness, commissioning, training and handover inputs.
Operations Feedback Layer
Feed operating evidence and qualified learning back into later project and protocol decisions.
AI, deterministic models and people have different jobs
AI assistance
Supports document extraction, terminology normalisation, retrieval from permitted knowledge, source-aware comparison, missing-information detection, contradiction detection, controlled drafting and multilingual transformation—not autonomous decisions.
Deterministic services
Handle units and conversions, capacity, crop-cycle scenarios, production assumptions, utility constraints, equipment compatibility, CAPEX/OPEX, sensitivity analysis and project gates with inspectable assumptions.
Qualified review
Named professionals and project owners approve agronomic assumptions, engineering decisions, safety and regulatory matters, supplier confirmation, financial and commercial decisions, and commissioning acceptance.
Private-beta boundary
A selected scope can include an organisation-specific project workspace, agreed project and supplier data, defined modules, named review roles, controlled outputs, feedback against evaluation criteria and export or handover conditions. It does not imply autonomous agronomy, engineering approval, investment advice or guaranteed project performance.
Read the product record in context
These routes explain the operational internal MVP, current module scope, technology, private-beta boundary and public-form data boundary.
Share high-level context about the organisation, project stage, data types, responsible reviewers and desired outcome. Do not submit confidential project files through the public form.