Press Cmd/Ctrl + P to export: choose Landscape, set Margins to None, and enable Background graphics to preserve the full visual design.
Back to Deck
Physical Space Intelligence — enabling AI to understand what is happening inside a space
Investor Deck · 2026 · PhysenseAI
Text has LLMs. Images have Vision AI. The physical world still lacks an intelligence layer.
We are building the intelligence layer for physical space.
Sensor events ≠ real-world events. The missing step is understanding.
Discrete, unconnected and memoryless — able to trigger only isolated rule-based alerts
Continuous, contextual and time-aware — enabling meaningful risk assessment
What is missing is not more sensors, but the layer that turns signals into events.
Mature sensors, accessible compute and rising Physical AI demand make this layer possible now.
Millimeter-wave radar, infrared, door contacts, pressure and environmental sensors are mass-produced and affordable enough for room-level deployment. Spaces no longer lack signals.
Edge NPUs make continuous local inference practical. Raw data no longer needs to leave the premises, unlocking privacy-sensitive environments.
Robots, embodied AI and intelligent buildings all need shared spatial context to act. This layer has yet to become infrastructure.
The window is open: signals are abundant, but understanding is still missing.
We build the intelligence layer every spatial application needs — not sensors, not a single application.
Care · Robotics · Buildings · Security
Event reconstruction · Spatial state · Behavioral baseline
Gateways · Protocols · Time sync
Radar · Infrared · Door contact · Environment
| IoT Platform | PhysenseAI | |
|---|---|---|
| Data form | Individual device readings | Continuously updated spatial state |
| Time dimension | A value at one moment | Continuous events and history |
| Decision logic | Threshold-based alerts | Comparison with historical baseline |
| Output | Raw data / reports | Events, states and anticipation |
Build the layer once, reuse it across every spatial application.
The intelligence lives in the model and reasoning engine — independent of any hardware stack.
Any combination of sensors
Denoising and timestamp alignment
Entities + space + time
Discrete signals → continuous events
Who / where / doing what
Activity changes over time
Compared with personal history
Risk level + actionable response
The output is not a data point, but a continuously updated state of the space.
We do not call a rules engine a foundation model. This is where we are today — and where we are going.
The path is clear: use the engine to access real spaces, then use real spaces to train the model.
Not one threshold for everyone, but each person compared with their own historical norm.
One bed exit, one bathroom entry, one door opening
Bed exit → bathroom → return to bed, with duration for each stage
How often this person rises at night, for how long, and how far
Tonight deviates sharply from personal norms, triggering a risk level and recommended action
Note: The system outputs spatial states and risk signals to support alerts and response workflows. It is not used for medical diagnosis.
The same event can be normal for one person and a risk signal for another.
Everything below is verified on real devices. Nothing is claimed before it happens.
Simulated data validates reasoning logic only; it does not represent field performance.
The engine works. This round is about continuous operation data from real spaces.
Swap sensors on the input side or applications on the output side without changing the core.
Any device; protocol and time alignment
Entity · Space · Time · State
Events · Baseline · Deviation · Anticipation
Events, states, risk levels and recommended actions
Hardware and applications will change. The spatial intelligence layer compounds over time.
Not because care is our only market, but because it proves the value of spatial intelligence fastest.
Nighttime falls and bathroom overstays carry severe human and liability costs
The workflow runs every day and night, making value continuously visible
Cameras are unsuitable in bedrooms and bathrooms; non-visual sensing is essential
Whether a signal indicates risk depends entirely on the person’s normal behavior
Capabilities proven here transfer directly to other spaces.
Customers are not buying sensors. They are buying a clear, live understanding of what is happening across the building.
Night bathroom stay > 15m → Watch; > 30m → Alert
Notification path: Staff dashboard → Mobile push → SMS escalation after 5m without response · Sense → Understand → Alert → Respond
Prove the overnight response loop on one floor, then expand by building and portfolio.
The buyer is clear. This round is about securing the first referenceable pilots.
Use projects to access real spaces, turn capabilities into a product, then build a platform.
Each stage compounds the data and reusable capabilities needed for the next.
Scenarios and thresholds change. The core remains: events, states, baselines and deviations.
Night bed exits and bathroom overstays · Fall-risk alerts and care-round dispatch · Long-term mobility changes
Adjust HVAC and lighting to actual occupancy · Space utilization and workstation analytics · Reduce energy automatically in vacant areas
Loitering in restricted areas · Worker safety state in operating zones · Abnormal routes and timing
More spaces make the same core stronger — that is what defines a platform.
The business flywheel wins spaces; the intelligence flywheel turns spaces into capability. Both drive More Real Spaces.
Data use: customer data improves models only with explicit authorization and data minimization; raw signals remain on premises by default.
Spaces create the model. The model makes it easier to win more spaces.
We do not build robots. We provide the environmental context they lack.

Spatial context will become shared infrastructure for embodied intelligence.
No speculative bottom-up TAM. Only directional anchors supported by public data.
Room-based care systems
Align multi-vendor signals into usable event streams.
One core, adapted by scenario
Real-world data cannot be bought; it must be earned through deployment.
Used by robots and embodied AI
Once systems depend on the context layer, switching costs are substantial.
The moat is not one algorithm. It is the number of real spaces.
This round has one clear goal: turn the engine into a system that runs continuously in real spaces.
Product definition, spatial intelligence solution and commercialization
Technical leader in spatial perception, heterogeneous sensor fusion and temporal intelligence; responsible for the core system from multi-source physical signals to event reconstruction, spatial state and behavioral reasoning, advancing it from prototype to real-world deployment and learned models
Engine operational; real-device data ingestion verified
First facility-floor pilots; overnight response loop live
Self-learning baselines live; false-positive rate and response time become delivery metrics
Standardize the product; validate a second vertical in buildings or security
Reasoning engine, baseline learning and edge deployment
Pilot rollout, field refinement and delivery engineering
Complete the core technical and delivery team
This round will deliver the first systems that run continuously in real spaces and can be formally accepted.
We are not adding more sensors. We are building the capability for AI to understand physical space.