Turning scattered information into documentation people actually use, built on years of experience in SaaS enablement and knowledge systems.

I work in strategic enablement at a consumer intelligence SaaS platform operating across Southeast Asia, where I build knowledge bases, write technical documentation, and manage release communications for a fast-moving product team. Before that, I worked in customer success, which means I've seen documentation from both sides: the people writing it and the people desperately trying to find an answer in it at 11pm.

Outside of my day job, I run pen-A, a documentation and knowledge systems practice for teams that need their processes, product docs, or internal wikis to actually make sense. I also build a text-based life simulation game as a side project, which has taught me more about systems thinking than most professional training ever did.

I care about documentation that's structured, findable, and written in plain language, not documentation that exists just to say it exists. If your knowledge base currently makes people's eyes glaze over, that's exactly the kind of problem I like solving.

Work Terms

I typically work Malaysia time (GMT+8), with flexibility for async collaboration across time zones. I prefer clear scoping upfront, an initial call or written brief, then structured milestones rather than open-ended engagement, so both of us know what 'done' looks like.

I prefer SafePay for larger projects, broken into milestones with partial release at each stage rather than one lump sum at the end.

Communication: I favour written updates over calls for most things, but I'm happy to hop on a call for kickoff or scoping. I flag issues and ask clarifying questions early rather than guessing, so expect me to ask a few sharp questions before diving in.