Understanding needs
I studied international trade and started with campus and small business projects, learning to listen for real needs and see work through to delivery.
ABOUT / ETHANYEANGSHENZHEN, CHINA
Curious enough
to build it.
WHO I AM
I’m ethanyeang. I work on product definition and business, and I stay hands-on with web development, AI agents, robotics and hardware alongside a technical team in Shenzhen.
WHAT I’M EXPLORING
I’m interested in the moment when software touches the real world: models reading an actual scene, robots taking action and prototypes turning into tools people can use. I work between open source, product design and the workshop.
AN UNUSUAL ROUTETrade → software → physical AI
Making systems useful
I led product and delivery work across SaaS, ERP and custom software, learning to coordinate requirements, product design and technical teams. Interfaces, permissions, data and collaboration matter long after a demo is over.
Moving into the physical world
At MetaHub in Shenzhen, I work on enterprise AI products and delivery. Outside that product work, I keep bringing agents, robotics and hardware into the same workshop to test what works in a real setting.
HOW I BUILDPrototype, meet feedback, repeat
Get one path working.
Start with the smallest flow that can test an idea. A real run teaches more than a larger plan on paper.
Let the use case guide the stack.
A product is for people doing real work. If they don’t want to use it, the demo still has work to do.
Put tools back in the community.
Clear, reproducible experience helps the next builder avoid repeating the same debugging session.
05 / FOR TEAMSPRODUCT × ENGINEERING · SHENZHEN / REMOTE
What we can build,
and how it starts.
For teams with a clear goal that want custom AI or robotics work. I lead product definition and business, take part in technical validation, and deliver with an engineering team. Shenzhen projects can include on-site testing; elsewhere we work remotely.
01
ENTERPRISE AI / AGENTSAI agents &
↗AI agents &
private deployment
Start from a real business goal. Evaluate retrieval, workflow design, tool integration and deployment boundaries. Agree on test criteria before sizing a prototype and delivery scope.
Business workflowsKnowledge systemsPrivate deploymentIntegration
02
PHYSICAL AI / ROBOTICSRobot integration
↗Robot integration
& VLA validation
Connect hardware, teleoperation, real robot data, model inference and field demonstration in one project plan. Depending on platform support, explore SO-101, B601, Reachy Mini, LeKiwi and open VLA workflows.
VLA / LeRobotTeleoperationRobot dataReal-world evaluation
03
PRODUCT / CUSTOM BUILDProduct prototypes
↗Product prototypes
& custom software
For teams validating a problem and ready to try a real workflow: agree on users and scope, build a usable prototype, then work with an engineering team to implement and iterate.
Product definitionWeb toolsInteraction designAI applications
HOW WE WORKSTART WITH THE PROBLEM
Start with the goal
Who is the user, and which real workflow should change?
Set a testable scope
Agree on hardware, data, system boundaries and acceptance criteria.
Try a real prototype
Test it with people and use field observations to guide the next step.
Ship with the team
Clarify development, integration, deployment and ongoing support.
FAQBEFORE WE START
A few things to settle
before we begin.
What kinds of projects do you take on?
Three main areas: enterprise agents and private deployment, robot integration and real-world VLA validation, and product prototypes with custom software. We start from the business goal and existing constraints, then decide whether an assessment, a prototype or a full delivery is the right scope.
Do you work remotely?
Yes. In Shenzhen we can meet and test on site; elsewhere the work is mostly remote, with an on-site phase if the project needs one. We can communicate in Chinese or English.
How does a project usually start?
Send an email with the context, goal, existing hardware or data, expected timeline and budget range. The first conversation tests whether the problem is worth solving and where the boundary is; if it fits, we agree on stages and deliverables.
How do you scope and price the work?
Based on scope, hardware, data readiness and delivery format. Exploration, prototype and full delivery are usually quoted as separate stages, each confirmed before the next, so the scope does not lock in too early.
Which robot platforms are supported?
SO-101, B601, Reachy Mini, LeKiwi and common LeRobot / VLA workflows can be evaluated. Actual support depends on the hardware, firmware, drivers and site conditions. Where something is uncertain, we run a small validation first instead of promising an outcome.
Do you guarantee model performance or success rates?
No promises about unverified metrics. We define testable acceptance criteria first and rely on real data and field results. The demos on this site document specific experiments, not guaranteed reproduction in every setting.
HAVE A SPECIFIC PROJECT IN MIND?Share the context, goals and timeline.
Share the context, goals and timeline.
We’ll start with the real problem.
Chinese / English · In person in Shenzhen or remote collaboration.