From project definition to controlled handover.

The operational internal-MVP Platform connects six stages into one traceable workflow for vertical-farm and hydroponic-greenhouse projects.

One project record, from the brief to delivery. The workflow keeps sources, requirements, alternatives, calculations, reviews, decisions and delivery outputs connected instead of dispersing them across separate files and handovers.

Discuss a CEA Project Request private-beta consideration

The delivery model

01 Define

02 Structure

03 Compare

04 Calculate

05 Decide

06 Deliver

Customer

Frame the organisation, objective, decision, site, stakeholders and project scope before detailed work begins.

Make requirements, constraints, responsibilities and unresolved questions explicit before alternatives are compared.

Compare crop, system, supplier, equipment, delivery and operating alternatives against a shared project record.

Test capacity, production, utilities, compatibility and economics through explicit assumptions before selecting a direction.

Record the selected option, rationale, risks, dependencies, approvals and unresolved items at each project gate.

Confirm readiness, delivery dependencies, commissioning inputs, training and handover conditions before operation starts.

Crop Urbanis

Frame agronomic, commercial and project context; assess evidence quality; coordinate the required expert input.

Develop the agronomic and project framing needed to test options under explicit assumptions and review boundaries.

Coordinate agronomic and project comparison inputs, clarification logs and decision preparation.

Develop agronomic configurations, production assumptions and feasibility reasoning under expert review.

Prepare decisions, review checkpoints and controlled outputs within the agreed project scope.

Coordinate agreed delivery inputs, agronomic readiness, operating protocols and training within the defined engagement.

Qualified partners

Provide scoped site, utility, regulatory, engineering or market evidence where those responsibilities sit with qualified parties.

Validate specialist utility, structural, electrical, HVAC, regulatory and supplier assumptions within each responsible scope.

Confirm equipment performance, warranties, compliance, commercial terms and contractual obligations within each specialist scope.

Review inputs that require specialist engineering, supplier or regulated confirmation before they inform a project decision.

Approve or validate the regulated, engineered, supplier-specific or contractual elements that sit within the responsible party’s duties.

Execute and accept construction, installation, safety, engineering and commissioning work where qualified and contractually responsible.

Platform

Capture the project brief, source register, known constraints, unknowns and first review questions in one structured record.

Map requirements, constraints, units, missing information, conflicts, responsibilities and review questions into a controlled model.

Create comparable configuration and supplier options, retaining source references, exclusions, missing information and dependencies.

Run deterministic scenarios for capacity, production, utilities, compatibility, CAPEX/OPEX and sensitivities with versioned assumptions.

Maintain the reviewer, option, rationale, risk, dependency, approval and unresolved-item record as controlled project history.

Assemble controlled delivery outputs: specification inputs, procurement clarification, dependencies, readiness, commissioning and handover. The later Operations Feedback Layer remains a roadmap module unless separately operational.

01 Define

Customer: Frame the organisation, objective, decision, site, stakeholders and project scope before detailed work begins.
Crop Urbanis: Frame agronomic, commercial and project context; assess evidence quality; coordinate the required expert input.
Qualified partners: Provide scoped site, utility, regulatory, engineering or market evidence where those responsibilities sit with qualified parties.
Platform: Capture the project brief, source register, known constraints, unknowns and first review questions in one structured record.

02 Structure

Customer: Make requirements, constraints, responsibilities and unresolved questions explicit before alternatives are compared.
Crop Urbanis: Develop the agronomic and project framing needed to test options under explicit assumptions and review boundaries.
Qualified partners: Validate specialist utility, structural, electrical, HVAC, regulatory and supplier assumptions within each responsible scope.
Platform: Map requirements, constraints, units, missing information, conflicts, responsibilities and review questions into a controlled model.

03 Compare

Customer: Compare crop, system, supplier, equipment, delivery and operating alternatives against a shared project record.
Crop Urbanis: Coordinate agronomic and project comparison inputs, clarification logs and decision preparation.
Qualified partners: Confirm equipment performance, warranties, compliance, commercial terms and contractual obligations within each specialist scope.
Platform: Create comparable configuration and supplier options, retaining source references, exclusions, missing information and dependencies.

04 Calculate

Customer: Test capacity, production, utilities, compatibility and economics through explicit assumptions before selecting a direction.
Crop Urbanis: Develop agronomic configurations, production assumptions and feasibility reasoning under expert review.
Qualified partners: Review inputs that require specialist engineering, supplier or regulated confirmation before they inform a project decision.
Platform: Run deterministic scenarios for capacity, production, utilities, compatibility, CAPEX/OPEX and sensitivities with versioned assumptions.

05 Decide

Customer: Record the selected option, rationale, risks, dependencies, approvals and unresolved items at each project gate.
Crop Urbanis: Prepare decisions, review checkpoints and controlled outputs within the agreed project scope.
Qualified partners: Approve or validate the regulated, engineered, supplier-specific or contractual elements that sit within the responsible party’s duties.
Platform: Maintain the reviewer, option, rationale, risk, dependency, approval and unresolved-item record as controlled project history.

06 Deliver

Customer: Confirm readiness, delivery dependencies, commissioning inputs, training and handover conditions before operation starts.
Crop Urbanis: Coordinate agreed delivery inputs, agronomic readiness, operating protocols and training within the defined engagement.
Qualified partners: Execute and accept construction, installation, safety, engineering and commissioning work where qualified and contractually responsible.
Platform: Assemble controlled delivery outputs: specification inputs, procurement clarification, dependencies, readiness, commissioning and handover. The later Operations Feedback Layer remains a roadmap module unless separately operational.

What you actually receive

Define

Structured project brief
Evidence and source register
Initial constraints and next-step decision

Structure

Requirements and constraint model
Responsibility and review map
Missing-information and conflict register

Compare

Comparable configuration options
Source-aware supplier comparison
Clarification and dependency log

Calculate

Scenario set with explicit assumptions
Sensitivity and compatibility record
Decision-ready comparison

Decide

Decision and project-gate log
Review and approval record
Risk and dependency register

Deliver

Controlled delivery pack
Readiness and commissioning inputs
Training and handover record

Professional responsibility remains clear

The Platform supports information, scenario and decision workflows. Crop Urbanis, the organisation and qualified professionals retain responsibility within their agreed, contracted or professional scope; the software does not replace regulated engineering, agronomic responsibility, supplier confirmation or commissioning acceptance.

Four commercial layers — what each is and who it is for

Operational in internal MVP

Recurring Platform access

Ongoing workspaces for project evidence, requirements, comparisons, scenarios, review histories, decisions and controlled outputs.

Who this is for

Organisations that need a durable, traceable record for defined CEA project workflows.

Decision outcome

A continuing Platform workspace scoped through the selected organisation’s private-beta or commercial agreement.

Selective private beta

Private organisational deployment

Dedicated deployment, data controls and integration for organisations with specific governance or infrastructure requirements.

Who this is for

An organisation whose workflow needs defined user, data, confidentiality, hosting or integration conditions.

Decision outcome

A separately scoped organisation environment with agreed controls, modules, roles and evaluation criteria.

Selective private beta

Fixed-scope onboarding

Initial workspace configuration, source-material structuring, requirements mapping and review-workflow setup.

Who this is for

A selected organisation beginning a defined Platform workflow or moving a project record into a controlled workspace.

Decision outcome

A configured starting point that makes sources, requirements, roles and evaluation conditions explicit.

Current

Optional expert services

Agronomic validation, project delivery, implementation support and customer success where the organisation needs domain specialists around the Platform.

Who this is for

An organisation that needs defined agronomic, project-delivery, implementation or customer-success support alongside a Platform workflow.

Decision outcome

A scoped support engagement around the product; expert services do not replace the Platform as the scalable product.

Four commercial layers — what is in it and what is not

Operational in internal MVP

Recurring Platform access

Standard inclusions

Project evidence, requirements, comparisons, scenarios, review histories, decisions and controlled outputs within the agreed module scope.

Explicit exclusions

Automatic public access, unscoped data processing, professional sign-off or guaranteed project outcomes.

Next step

Request private-beta consideration with the organisation, workflow, data categories and review roles at a high level.

The core workflow is operational internally; selected organisational access is governed through a separate private-beta or commercial scope.

Selective private beta

Private organisational deployment

Standard inclusions

Agreed deployment, organisation scope, data controls, access roles and integration or support requirements.

Explicit exclusions

A generic promise of regional hosting, certification, integration or service level before those terms are agreed.

Next step

Describe the high-level governance, infrastructure and workflow needs through the Private Beta route.

Private organisational deployment is considered case by case through selected private-beta or commercial scopes.

Selective private beta

Fixed-scope onboarding

Standard inclusions

Initial configuration, source-material structure, requirement mapping and review workflow within the agreed scope.

Explicit exclusions

Confidential data intake through public forms, unbounded implementation work or regulated professional approvals.

Next step

Confirm the source rights, data route, responsible reviewers and onboarding scope after initial qualification.

Onboarding is defined individually as part of the selected organisation’s private-beta or commercial scope.

Current

Optional expert services

Standard inclusions

Only the validation, delivery, implementation or customer-success inputs expressly agreed for the engagement.

Explicit exclusions

Regulated engineering sign-off, supplier warranties, automatic private-beta access or guarantees of project performance.

Next step

Use the Project or Partner route to define the decision, scope and qualified responsibilities involved.

Optional expert services are scoped separately and support onboarding, validation, implementation and customer success around the Platform.

Share the high-level situation, decision and parties involved. A controlled data route can be agreed after initial qualification; do not send confidential documents through public forms.

Discuss a CEA Project Request private-beta consideration