Pilot farms and groups
Define real operating problems, safe test zones, baseline workflows and practical acceptance criteria.
Partners and patient capital wanted
Fund evidence. Supply capability. Challenge the design.
Project Scarecrow has a documented operating concept, a public specification and a working software foundation. It does not yet have selected field hardware, a pilot farm, certified safety evidence or a commercial price. The next partners should help close those exact gaps.
The coalition
A robotics project is a chain of accountable specialists.
Robotics and sensing
Provide supported hardware, truthful specifications, SDK access, emergency-stop evidence, spares and local technical capacity.
Security providers
Design lawful monitoring, verification, escalation and physical response under their registrations and SOPs.
Connectivity and edge
Help prove local operation, rural backhaul, redundant power, secure remote access and recoverable updates.
Legal, privacy and safety
Review the service model, contracts, POPIA roles, worker safety, surveillance boundaries and pilot controls.
Insurers and researchers
Help define evidence that can support risk evaluation without promising premiums or outcomes in advance.
Possible collaboration structures
We are open about the model; no arrangement is pre-sold.
Joint controlled trial
Partners share equipment, expertise or cost for one documented site with agreed ownership, publication and stop rules.
Security-company integration
Scarecrow supplies a technology layer while a suitably registered partner owns monitoring and response services.
Shared farm model
Neighbouring farms may share selected infrastructure or response capacity if routing, service levels, privacy and ownership can be made workable.
OEM and local integrator
Use established platforms and focus JVR effort on adapters, incident logic, evidence, farm integration and support.
Independent validation
A university, laboratory or specialist helps define scenarios, analyse results and expose weaknesses before marketing claims grow.
Milestone-based investment
Capital is released against hardware, integration, safety and pilot evidence gates rather than an unsupported scale forecast.
Use of capital
The first money buys de-risking—not a large sales team.
The source financial documents contain historical hardware anchors and package bands. We do not publish them as current prices. A credible raise must be rebuilt from current vendor quotations, local duties, support, insurance and the chosen pilot configuration.
- Hardware
- One supported non-actuating input, an edge gateway and only the minimum mobile platform needed for the agreed test.
- Integration
- Vendor adapter, secure device identity, health monitoring, evidence storage and operator workflow.
- Safety
- Emergency stops, route/no-go validation, worker briefing, test equipment and independent review.
- Professional work
- Contracts, PSiRA/service analysis, POPIA impact assessment, cyber review and insurance engagement.
- Pilot operations
- Survey, installation, connectivity, maintenance, training, measurement and post-pilot reporting.
- Contingency
- Spares, ruggedisation, weather, import delay and a clear ability to stop or redesign.
Due-diligence room
What serious partners can inspect after fit and confidentiality.
The private vault already preserves 41 source PDFs, implementation specifications, risk notes, evidence and decision records. Access is selective and does not imply that every historical concept remains approved.
| Area | Available material | Current limitation |
|---|---|---|
| Strategy | Business plans, investor narrative, farmer and partner positioning | Needs current market interviews and validated segmentation |
| Commercial | Pricing logic, financial-model structure, lease and cluster concepts | Needs current quotations and a populated scenario model |
| Engineering | Architecture, blueprints, APIs, deployment and maintenance drafts | Vendor interfaces and hardware limits are not selected |
| Safety and cyber | Fail-safe, threat-model, test and incident-response drafts | Not a certified safety case or penetration-test report |
| Legal and privacy | Regulatory map, POPIA assessment, service description and contract outlines | Requires qualified South African review |
| Software | Local gateway, simulator, tests and public interaction demo | No live sensor or robot integration yet |
| Evidence | Source register, hashes, status labels and planned pilot report | No field-performance dataset yet |
Fundable sequence
Four milestones to a defensible pilot result.
Lab control plane implemented
Configuration, device health, notifications, evidence export, audit integrity and ten automated tests. This is software evidence, not field proof.
Prove one real input
Connect a supported non-actuating sensor or camera and measure identity, latency, availability and failure.
Qualify one site
Complete survey, baseline, safety/privacy design, contracts and operator training.
Run and report
Execute controlled scenarios, record limitations and publish a reviewed pilot report.
What we are asking for now: a project conversation with parties who can supply a real capability, a suitable controlled site, qualified review or milestone-based capital.
Request a briefing