Senlay · investor deck · 1 November 2026
01 · Origin
Senlay
SmartSurf, an existing prototype/reference application in maritime conditions, revealed the need for local environmental context. It is the product origin, not proof of robotics demand or validated safety outcomes.
02 · Customer hypothesis
Start by testing a workflow with drone software teams.
An operator or integration engineer reviewing available wind evidence for a selected coordinate.
This is the first buyer hypothesis. Robotics demand, willingness to pay and repeatable field value are not yet validated.
03 · Problem to test
Environmental values need context to be reviewable.
For a point-level wind review, an operator may need to see what is measured versus forecast, where a source is from, when it was issued or observed, whether sources disagree, and what information is missing. The usefulness of this workflow is a customer-validation question.
04 · Product
Structure available wind evidence for human or software review.
Request available environmental data for a coordinate.
Receive observations and model values where available.
Inspect source, timestamp, distance, freshness, disagreement and unknowns.
Use the deterministic snapshot explanation and preserve its scope.
05 · Example
A response can expose evidence and limits together.
Available wind speed, gust and direction evidence for one selected point, with source timestamps, distance and disagreement where available.
Aircraft limits, route, altitude, obstacles, visibility, airspace permission and whole-mission suitability are outside this assessment.
Use the demo for current behavior; any synthetic walkthrough must be read as synthetic.
06 · Current state
An evaluation beta with working interfaces and reference tooling.
Spot-level environmental API; provenance and timestamps; distance and source comparison where available.
Deterministic snapshot-based explanation, REST/API access, public MCP gateway, reference adapters and offline synthetic replay.
External robotics usefulness, source representativeness, field performance, customer demand and paid conversion.
07 · Founder
SmartSurf and practical work in wind and water shaped the product question.
Founder and builder of Senlay. The founder story documents water-sports instruction, hands-on prototyping and SmartSurf development.
Experience in a physical environment motivated a product that makes available evidence and limitations easier to inspect. It does not establish the robotics workflow's commercial value.
08 · Pilot hypothesis
Test with a defined partner, workflow and evidence protocol.
- Identify the operator or integration workflow.
- Agree test locations, sources and rights.
- Define measures before collecting results.
- Assess source representativeness and integration effort.
- Check repeatability and reliability under an agreed protocol.
- Discuss commercial terms if evidence supports continued work.
No external pilot result, field validation or willingness to pay is claimed.
09 · Business and next milestones
Earn the case for a commercial model.
Drone software teams may value structured wind evidence in an operator review workflow. Paid subscriptions are planned and unlaunched; provider and commercial source rights require confirmation.
- Evaluate the workflow with prospective users.
- Agree a scoped pilot only if there is a partner and lawful source access.
- Validate field performance, reliability and willingness to pay.
- Consider route/time-window capability only after the point-level case is established.
No funding amount, investor terms, numeric customer target or revenue projection is specified in this brief.
Senlay evaluation beta. This deck describes current product scope and unvalidated hypotheses as of 1 November 2026.