Independent product · Your RV
Your RV: connecting the interface to the vehicle.
A mobile app, document-grounded AI assistance and connected-hardware development, validated in a personal RV.
- My role
- Founder & CEO · Product, software & hardware integration
- Period
- Apr 2025 – Present
- Designed for
- RV owners
AI leadership noteConnect a diagnosis to the right manual
Original approach
Lead product strategy, UX, software development and connected-hardware integration. The mobile work includes authentication, data services, document uploads, OCR and retrieval-grounded assistance.
What could change today
Extend document-grounded assistance by checking the installed equipment model before proposing a diagnostic step. Show the cited manual passage, sensor reading and owner confirmation together.
Workflow excerpt. The numbered steps show the same part of the journey in each version. The full project includes work beyond this comparison.
Original workflow
- Review vehicle status
- Inspect the equipment
- Ask Harvey for help
- Review the next action
Proposed workflow with AI
- Check vehicle status and the age of the readings.
- Identify the installed equipment and model year.
- Ask Harvey to retrieve the matching manual passage.
- Confirm the proposed step before operating a device.
How to test the change
Test the wrong model year, missing telemetry and lost connectivity. Require confirmation and a recovery path before a device action.
01 / Customer & problem
The need behind the work.
Who needed this.
Owners need equipment information and guidance in the context of their actual vehicle.
The problem to solve.
RV ownership involves equipment readings, manuals, maintenance and controls spread across different systems. Understanding a problem and knowing the next step requires connecting those sources.
Bring compatible equipment information, useful controls and Harvey’s document-grounded assistance into a coherent mobile experience.
02 / My ownership
Responsibilities.
Own product direction, UX, software implementation and the hardware-integration work, including prototyping, physical fit, release practices and product communication.
The constraint to work through.
Software, documentation and physical hardware have to work together, with compatibility shaping what the product can do.
- Review vehicle status
- Inspect the equipment
- Ask Harvey for help
- Review the next action
03 / Actions & delivery
How the work came together.
Lead product strategy, UX, software development and connected-hardware integration. The mobile work includes authentication, data services, document uploads, OCR and retrieval-grounded assistance.
The dashboard connects power, climate and water context with access to equipment and assistance. The gateway work prototypes read/write CAN and RV-C integration alongside CAD, fit validation and functional 3D printing.
Validate the working system in a personal RV and develop the release, monitoring and design-system practices around it. The public product is in early access, with public launch tied to hardware availability.
04 / Decisions & judgment
What carries through the design.
Connect guidance to equipment context.
A useful explanation needs to relate to the vehicle, its documentation and compatible connected systems, rather than offer an isolated generic answer.
Validate beyond the screen.
Software behavior, physical fit and equipment integration are parts of the same product responsibility. My own RV provides a practical validation environment.
Related interaction states
Equipment context on one mobile dashboard.
The product preview brings power, climate and water into a shared entry point, with access to equipment and Harvey’s assistance. Readings in this preview are examples.
Orient around the vehicle
System context connects to equipment, assistance and the wider ownership experience.
05 / Results & business value
What changed through the work.
A working mobile experience and connected-hardware development effort, with document-grounded assistance and validation in a personal RV. Twelve separate provisional patent applications cover independent connected-vehicle and asset technology, with patent-pending status.
Why it matters.
The work connects a mobile interface to document intelligence and physical equipment integration, demonstrating product responsibility across software and hardware.
06 / Reflection
Lessons for future projects.
Keep physical validation close to product design. A convincing interface still needs to work with the equipment and circumstances it represents.
Let’s talk about your next chapter.
Exploring Senior Director, Head of Design and VP opportunities.