The Builder
William, Weelau Cheong
Most weeks I am the architect, the engineer, and the person explaining to a stakeholder why the estimate was wrong. Not because the team is small — because the problem doesn’t split cleanly. Specialisation helps until it creates blind spots: the architect who has never read the production logs, the engineer who doesn’t realise they’re negotiating scope. Those gaps surface in the product.
What I’ve found, across banks and insurance platforms and startups, is that wearing multiple hats isn’t the problem. Wearing them without knowing you’ve switched is. The decision that makes sense in architect mode often breaks things in engineer mode. Knowing which context you’re in — and making the call that context actually requires — is the discipline. Simple to describe, hard to do consistently under pressure.
DivineForge is where I document that — not the cleaned-up version, but the actual one, with the constraints, the legacy systems, and the timelines that were never realistic.
Track record
Embedded in the enterprise architecture team as a technology catalyst — exploring solution patterns, evaluating emerging approaches, and helping build the case for change with the teams that had to live with it.
Contributed to the architecture and delivery of a mobile-first roadside assistance app in the insurance space, from early design through to production release.
Currently building AI pipelines and workflow automation systems — iterating on what the technology can actually hold up in practice, and what still needs work.