← Back to showcase

Showcase / Enterprise Platform

erp-web-form

A secure schema-driven web form platform built on Salesforce for Koyu and related ERP workflows. The public story stays disciplined: the stable core ships first, and AI assistance is a phased layer with guardrails.

Active draft Salesforce + Apex React + TypeScript AI roadmap, not AI hype

Why it matters

A bridge project between platform delivery and AI leadership

This case study is strong because it combines secure enterprise delivery, product judgment, and practical AI direction in one story. It proves the core platform value now and leaves room for the future AI layer without overselling what is live today.

What ships today

Stable platform capabilities

  • React 19 and TypeScript frontend deployed as a Salesforce Static Resource through Visualforce.
  • Apex @RemoteAction backend for guest-user compatible form operations.
  • AES-256 encrypted URL tokens for controlled access.
  • JSON-schema-driven forms with conditional logic, repeaters, pre-fill, and draft save or resume.
  • Multi-object creation and update flows with asynchronous processing and transaction rollback.
  • Real workflows such as event registration, targeted health surveys, and enrollment or RFI flows.

AI direction

Phased and guardrail-first

  • AI-augmented engineering workflow using JIRA MCP, validators, and reusable instructions.
  • AI-readable project context through notes, hooks, skills, and documentation hierarchy.
  • Documentation synced into Confluence and NotebookLM so both engineers and non-technical stakeholders can navigate the same source of truth.
  • Prompt-assisted schema generation is positioned as a later layer with strict validation, governance, and human review.
The right public claim today is not “production AI form generation is live.” The accurate story is “secure core platform shipped, AI-assisted generation intentionally phased.”

Constraints

Why the architecture matters

  • Salesforce Sites and Visualforce hosting environment.
  • Guest-user access with strict security constraints.
  • PII-sensitive workflows including health-related data.
  • Need to support both public distribution and targeted contact-specific links.
  • Business pressure to ship the platform before the AI layer.

Proof points

Resume-ready outcomes

  • 3 major releases with zero critical production incidents in the current role.
  • AI-augmented debugging workflow that reduced bug-fix cycle time from about 4 hours to 45 minutes.
  • Documentation operating system syncing 57 pages across Obsidian, Confluence, and NotebookLM.
  • Distributed delivery across Singapore, Japan, Vietnam, and the Philippines.

Next buildout

What this page will grow into

This is the right second showcase page to keep expanding. The next useful additions are an architecture visual, one milestone timeline, screenshots, and tighter before-and-after evidence around debugging flow, documentation sync, and rollout decisions.