02
Problem
Robots that don’t match the work
- Operators need safe, predictable robots for confined, repeatable jobs.
- Most options are either risky “general” autonomy or one‑off custom builds.
- That leads to stalled pilots, compliance risk, and weak unit economics.
03
Why Now
Labor, RaaS, and ROS‑2
- Labor gaps in agriculture, logistics, and industrial operations keep growing.
- RaaS has matured as a low‑risk way to adopt automation.[web:92][web:104]
- ROS‑2 and sim tooling enable reusable, safety‑aware robotics stacks.
04
Solution
Canonical core for captive robots
- ROS‑2‑native RaaS platform for bounded‑intelligence, “captive” machines.
- Each robot is tied to one role and envelope—no open‑ended behavior.
- Partners adapt the core to domains; shared features and data improve all deployments.
05
Technology
Bipartite platform
- Canonical Assets: Control stack, safety layer, sim worlds, RL training, logging.
- Partner Implementations: Domain‑specific form factors and workflows on top.
- Data and policies feed a loop that shrinks sim‑to‑real gaps across captive roles.
06
Product & Use Cases
Captive roles in the field and indoors
- Agri‑companions: Low‑speed units for crop monitoring and gentle livestock patrol.
- Facility Stewards: Zone‑limited inspection and light logistics in labs and plants.
- Urban & Yard Helpers: Route‑constrained cleaners and inspectors in sites and yards.
07
Market & Model
RaaS for controlled environments
Agriculture
RaaS
Per‑robot + per‑hectare
Facilities
RaaS
Per‑site + per‑robot tiers
Construction & Inspection
RaaS + Projects
Per‑robot + usage bundles
- Focus on mid‑market and enterprise operators with repeatable workflows.
- Mix of recurring subscriptions, per‑robot fees, and partner integrations.
08
Traction
Early captive validation
- Design‑partner talks underway in agriculture and light industrial facilities.
- First captive roles scoped: field patrol, indoor inspection, and yard helper.
- Simulation demos show zone‑limited behavior and safety stop layers.
09
Go‑To‑Market
Design partners → templates → ecosystem
- Phase 1: 2–3 paid design‑partner pilots in agriculture and facilities.
- Phase 2: Launch captive role templates (field patrol, inspection, yard helper).
- Phase 3: Work with OEMs/integrators to ship white‑label captive machines.
10
Team
Robotics, safety, and platforms
- Founder / CEO: Robotics platform and safety‑critical systems background.
- Founding Engineer(s): ROS‑2, controls, and field robotics deployments.
- Advisors with deep‑tech, RaaS, and regulated‑industry experience.
11
Roadmap
18–24 months of captive milestones
- 0–9 months: Ship MVP core; secure 2–3 paid pilots and first captive roles.
- 9–18 months: Expand role library; run multi‑site pilots; refine unit economics.
- 18–24 months: Standardize RaaS contracts and grow the partner ecosystem.
12
The Ask
Build the core for captive robots
$3.5M Seed
- 40% Platform & safety: ROS‑2 core, captive‑role studio, safety tooling.
- 30% Domain pilots: agriculture, facilities, and inspection deployments.
- 30% Engineering & GTM: robotics, integrations, and founder‑led sales.
- Milestones: 3+ live captive deployments and validated RaaS model.