Hello, I'm Sokheng Ich — Senior Full-Stack Developer & Solution Architect based in Phnom Penh, Cambodia.Hello.

I specialize in designing and building enterprise-grade business systems that solve real operational problems at scale. My core focus areas include HR ecosystems with multi-branch attendance tracking and payroll automation, FinTech platforms with wallet management and financial workflows, healthcare ERPs with clinical and inventory management, and real estate CMS platforms with built-in SEO and lead capture. I also build B2B commerce platforms and operational dashboards that centralize fragmented business data. Every system I build is designed with clean modular architecture so it remains maintainable as requirements evolve. If your organization is managing complex workflows through spreadsheets or disconnected tools, I specialize in converting that operational friction into integrated, scalable software infrastructure.

I work with both startups and established businesses, adapting my approach to match where each organization is in its growth journey. For early-stage startups, I focus on building scalable architectural foundations that won't require complete rewrites as user volume grows — validating the MVP structure before a single line of production code is written. For established companies, I audit existing workflows to identify operational bottlenecks and digitize complex, often fragmented processes into integrated systems. Whether you are launching your first digital platform or modernizing legacy infrastructure that no longer serves your growth, I bring the same rigor to system design, ensuring your platform is built to last rather than patched together over time.

My approach to system architecture begins before any code is written. I conduct a thorough requirement analysis and operational workflow mapping to understand not just what the system needs to do today, but how it will need to evolve tomorrow. From there, I design normalized database models, define API contracts, and establish modular backend boundaries so each domain — authentication, payroll, inventory, reporting — operates independently without coupling. This separation is critical for long-term maintainability. I then plan deployment architecture with environment parity across staging and production. Only after this architectural blueprint is validated with all stakeholders does development begin, reducing mid-project pivots and the compounding cost of technical debt.

Project timelines vary depending on system complexity, integration requirements, and the number of stakeholders involved. A focused MVP or department-level tool typically takes six to ten weeks. A full-scale enterprise platform with multiple integrated modules — such as HR, payroll, inventory, and reporting — typically runs twelve to twenty weeks. I work in structured milestone-based phases: discovery and architecture first, followed by iterative build cycles with regular progress reviews. Each milestone produces a functional deliverable so you can see and validate progress throughout the project. I maintain transparent communication at every stage, giving you full visibility into timeline, scope, and any risks before they become blockers.

Yes, team leadership is a core part of how I operate. As the technical lead at Cross Technology Cambodia, I regularly architect systems, define technical roadmaps, and coordinate engineering teams across multiple concurrent projects. When a project requires scaling beyond a solo engagement, I can assemble a dedicated team of vetted engineers and designers — managing workload distribution, code quality standards, and architectural consistency across all contributors. I set clear contribution guidelines and review processes so that even as the team grows, the system's integrity is preserved. You work with me as your primary point of contact while the team executes behind a unified technical direction.

Yes. I bridge system design and engineering across the full stack. On the design side, I structure information architecture, define user flows, and ensure that the interface logic directly reflects the underlying data model — so that UX decisions are technically sound, not just visually appealing. On the engineering side, I build the backend APIs, database schemas, and deployment pipelines that power that experience. This end-to-end ownership means there is no translation gap between design intent and technical execution. The result is a product that is cohesive from the database layer to the user interface — consistent, performant, and built to be maintained by a future team without confusion.

Launch is not the finish line — it is the beginning of the system's operational life. After going live, I offer structured post-launch support covering performance monitoring, bug resolution, and infrastructure optimization as traffic and data volume grow. As your business evolves, I can expand the system with new modules, integrations, or capabilities without disrupting what is already working. I also conduct periodic technical reviews to identify bottlenecks before they become critical. For clients running high-stakes operations, I offer ongoing retainer agreements to ensure you always have senior engineering capacity available when you need it most.