Founder's operating manual

I build applied technology across several ventures—not a single product brand. The common thread is practical systems: data that can be labeled and reviewed, devices that survive field conditions, and delivery that teams can actually operate.

I prefer transparent status over polished abstraction. If something is a prototype, I will say so. If a claim needs evidence, I would rather link a receipt than invent a metric.

Start with the problem and the constraint, not a slide deck of solutions. A short note with context beats a long pitch.

Good partners bring domain knowledge, access to a real operating environment, or capital and mentorship that respects builder time.

I work well with people who can iterate in public: share what failed, adjust, and keep going.

Athena OS and assisted labeling workflows (audio + vision) with human review.

Industrial and energy-adjacent products under Stratetics Experts (including solar inspection adjacency).

Agritech experiments tied to Farm Optix and TUAI Ventures' smallholder mission.

Keeping this Field Guide honest so introductions do not require a private deck to understand the shape of the work.

You can name the problem you're trying to solve in one or two sentences.

You know whether you want a pilot, a partnership, investment/mentorship dialogue, or a technical compare-notes session.

You're comfortable if the answer is 'not now' or 'wrong fit'—clarity saves both sides time.

I'm a Sarawakian founder based in Kuala Lumpur. The through-line from Sarawak to KL is the same: build tools that respect local context—language, field conditions, and operators who are not sitting in a lab.

The portfolio spans industries on purpose. Shared capabilities (labeling, sensing, delivery) travel; company names stay distinct so nobody confuses a social enterprise with a consultancy product line.