First 1–3 months
Create focus. Clarify core users, priorities, and what not to build. Establish a stable baseline the team can execute against.
Months 3–6
Turn decisions into delivery. Define dev-ready flows, tickets, and cadence. Reduce noise, rework, and second-guessing.
6+ months (as needed)
Continued fractional support as you scale, or a clean handover when you're ready to hire.
Throughout: I use AI tools to prototype flows, test edge cases, and keep documentation current — but the thinking, coordination, and trade-offs stay human.
Connected Mobile & Wearables Applications (NFC, BLE, Sensors)
Core UX flows, scoped MVPs, and pilot delivery for mobile apps where hardware, sensors, or physical interactions are part of the user journey.
Work includes:
Defining core journeys and states
Shaping MVP scope and non-goals
Aligning UX, engineering, and rollout sequencing
Supporting pilot → live progression
IoT Platforms & SDK / API Portals
Product direction for connected systems where hardware, firmware, software, and developer tooling must align.
Work includes:
Developer portal and SDK/API experience definition
Multi-track HW / FW / SW delivery alignment
Integration boundary clarification
Delivery tracking across distributed systems
Enterprise & Platform APIs
Event-driven systems, microservices, and data platforms operating across markets or operational environments.
Work includes:
API logic and integration flow definition
Real-time event stream product shaping
Cross-team coordination (backend, cloud, integration)
Reducing ambiguity between system architecture and product intent
Hardware-Adjacent Operations & Field Systems
Mobile and coordination platforms supporting physical infrastructure, logistics, and field operations.
Work includes:
Discovery through delivery
Vertical coordination and workflow design
Integration with sensors and real-world constraints
Improving operational clarity before scale
These packs are typical starting points. We usually begin with short conversations to understand your product, current focus, and whether outside product support would actually help.
MVP scope & priorities
Core UX flows
View Pack
Product scope & sequencing
UX flows + specs
Ongoing delivery support
View Pack
I’m typically brought in when a connected product has momentum — but decisions, sequencing, or ownership aren’t clear enough for teams to move fast with confidence.
I work with a small number of teams at a time, staying closely involved and accountable for outcomes.
I often step in as the first dedicated product lead — clarifying ownership, scope, and delivery structure.
Experienced across API-led platforms and hardware-connected systems, where UX, engineering, and real-world constraints must align.
I use AI tools pragmatically to pressure-test decisions, explore edge cases, and keep documentation tight as products evolve.
I work alongside founders building complex, connected products — usually at the point where momentum exists, but clarity doesn’t.
I step in when ideas are scattered, UX needs tightening, and delivery needs a buildable path forward.
My focus is simple:
make the problem explicit,
define the right flows,
and turn that into direction engineers can trust.
I value calm communication, clear ownership, and steady momentum — one well-defined step at a time.