Deeptech products, computational systems and engineering ventures.

Selected work across venture building, hardware-software products and technical delivery, grounded in engineering software, scientific machine learning and high-fidelity simulation.

Six selected projectsVenture · Product · Execution · Computation

Different technical problems. One approach spanning product, computation and execution.

From defining the problem and building the technical system to coordinating the work, validating the results and delivering a usable product or capability.

Project archive

Selected work

Explore ventures and products alongside the engineering software, connected systems, scientific machine learning and simulation that give them technical depth.

Minimal network illustration representing Avkalan Labs
Venture · Engineering software · Scientific computing

Building Avkalan Labs

Building a technical venture around simulation software, custom numerical solvers, scientific machine learning, synthetic-data generation and engineering automation.

Role: Co-founder

View project
Minimal illustration of an insole with pressure-sensing points
Product · Hardware-software · Healthcare

EigenSole

An AI-powered smart wearable combining pressure and motion sensing, embedded electronics, gait analytics, dashboard software and customised insole development.

Role: Co-founder and product lead

View project
Illustration of a scientific machine-learning workflow for underground imaging
Geophysical imaging · Electromagnetics · SciML

Underground-imaging SciML workflow

A physics-led workflow combining electromagnetic simulation, synthetic data, scientific machine learning and subsurface interpretation.

Role: Solver and scientific ML lead

View project

Recurring themes

The domain changes. The operating questions remain similar.

01

Problem and user

What decision, workflow, or physical problem needs to improve and who depends on the result?

02

System representation

How should the physics, geometry, data, operating conditions and constraints be represented?

03

Technical trade-offs

What level of fidelity, speed, complexity and cost is appropriate for the intended use?

04

Evidence and trust

What validation, comparison, testing, or feedback is required before the result can be relied on?

05

Product and adoption

How does the technical capability become a repeatable, understandable and usable product or workflow?

06

Execution and delivery

How do teams, dependencies, technical reviews, validation and hand-offs fit together to move from technical possibility to a usable outcome?

Let’s talk about what you’re building.

I’m open to conversations about deeptech ventures, technical products and program delivery across AI/ML, engineering software, simulation and connected hardware.