44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# Executive Summary
|
||
|
||
## Product
|
||
|
||
A specialized bikepacking planner and riding companion for multi-day trips. It should combine route planning, daily stages, route-corridor logistics, local rules, offline use, and bikepacking-specific route suitability.
|
||
|
||
## Positioning
|
||
|
||
**BikepackPilot** is for riders who need answers beyond “which road/path connects A to B?”
|
||
|
||
It answers:
|
||
|
||
- Can I ride this with a loaded bike?
|
||
- Where can I sleep tonight?
|
||
- How far to the next reliable water?
|
||
- Is there food before shops close?
|
||
- What if this forest road is closed?
|
||
- Where is the nearest bike shop or bailout train?
|
||
- Can the plan still work offline?
|
||
|
||
## Primary users
|
||
|
||
1. **Weekend bikepacker**: 2–3 days, wants low stress, legal sleep options, reliable water/food.
|
||
2. **Long-distance tourer**: multi-week trip, needs offline maps, resupply, device export, budget sleep.
|
||
3. **Gravel/adventure rider**: wants maximum dirt but still rideable on a loaded bike.
|
||
4. **Remote-route rider**: needs dry-stretch warnings, bailout options, weather exposure, repair planning.
|
||
5. **E-bikepacker**: needs charging points, range-aware stages, charger-friendly overnight stops.
|
||
|
||
## Differentiation from general route planners
|
||
|
||
The differentiator is not access to a secret map dataset. Major outdoor planners often use OpenStreetMap as a foundation. The differentiator is the proprietary layer built on top:
|
||
|
||
- bikepacking suitability score,
|
||
- rideability with loaded bike,
|
||
- water/food/sleep gaps,
|
||
- local rules confidence,
|
||
- trusted local reports,
|
||
- offline route-corridor intelligence,
|
||
- multi-day staging optimized around logistics.
|
||
|
||
## MVP outcome
|
||
|
||
A user should be able to plan a 3–7 day trip, inspect stage cards, see critical POIs, export a route, and save an offline pack.
|