Enterprise SAP.
Without the
enterprise bill.

With a consultancy, part of what you pay covers people you'll never actually work with — account managers relaying requirements, partners signing off on scope, bench consultants the firm needs to keep billable. None of that touches your project directly. With me, you're working with the person who designs the solution, writes the code, and debugs it in production — nothing gets diluted passing through a chain of people. That means faster decisions, fewer miscommunications, and a rate that reflects the actual work, not the structure around it.

Yes. I'm open to contract, freelance, contract-to-hire, and full-time positions — whatever model fits how you need to bring someone in. If you're testing fit on a project first before committing long-term, contract-to-hire works well. If you know from day one you need someone embedded in your team for the long run, that's equally on the table. The model matters less to me than doing good work — let's talk about what fits your process and budget cycle.

Those 2 years weren't spread across small, disconnected projects — they were spent fully embedded in a live, large-scale S/4HANA engagement for a major aviation client. That meant handling production incidents under real pressure, writing and reviewing ABAP development that had to hold up in a regulated, high-availability environment, fixing CPI integration flows connecting systems across regions, and delivering Fiori apps end users depended on daily. That density teaches you things slower-paced work doesn't. I'd rather be evaluated on what I've actually shipped and fixed than on tenure alone.

Big 4 SAP consultancies typically bill RM 800–1,500 per day once partner overhead, account management, and bench-time markup are baked in. A meaningful chunk of that never touches your project's actual delivery. My rate is significantly lower, but the delivery standard isn't — same technical rigor, same certifications backing the work, just without paying for a firm's internal structure. You also get faster turnaround, since there's no internal approval chain slowing decisions, and direct communication with the person actually building your solution.

Yes. I'm based in Kuala Lumpur and work remote-first by default — async communication, clear documentation, minimal friction across time zones. I've coordinated daily across Malaysia and Singapore time zones throughout my current engagement, so distributed work isn't new to me. I'm also open to engagements with clients in Europe — remote collaboration works the same regardless of distance, and I'm comfortable adjusting my schedule for overlap windows when needed. On-site travel can be arranged where required.

English and Malay fluently, with German in active development — useful context for engagements with DACH-region clients, and a signal I'm building toward working across Europe, not just staying where it's convenient.

Usually with a short call to understand the problem you're trying to solve — not a sales pitch, just enough context to tell you honestly whether I'm the right fit. From there I'll scope the work, propose a rate and timeline based on the engagement model that suits you (contract, project-based, or embedded), and we go from there. No lengthy procurement process required on my end.

Yes. Given the nature of the systems I've worked on — production S/4HANA landscapes handling real operational and financial data — confidentiality isn't optional. I'm comfortable signing NDAs, working within client security policies, and limiting access to only what's needed for the engagement.