I build systems that keepbusinesses moving.

Problem

Most internal systems collect activity, documents, notes, approvals, and user actions, but teams still spend hours manually checking what matters. The real problem is not lack of data. It is the lack of system intelligence that can explain what is happening, what needs attention, and what should happen next.

Problem

Important business data often hides inside documents, emails, notes, and scattered records. Teams waste time finding it, reading it, and moving it into the right workflow.

Problem

The business relied on a large, production CRM/ERP platform with lines of code powering daily operations across sales, leasing, listings, deals, compliance, HR, finance, call center operations, dashboards, automations, and integrations. I worked closest to the platform, helping keep it stable, improving legacy workflows, debugging production issues, building new internal tools, and supporting multiple departments without disrupting daily operations.

Problem

Regional cloud instability created serious risk for core platform availability, storage access, and day-to-day business operations. I helped move and stabilise critical infrastructure across AWS regions, using Frankfurt as the recovery target while validating EC2, RDS, S3, VPC, DNS, AWS DataSync, and multi-AZ resilience to keep production workflows usable during the disruption.

Problem

Most legacy CRM and ERP systems do not fail loudly. They drift over time. Years of urgent fixes and shifting business needs can slowly turn a working system into something heavy, confusing, and risky to touch. A full rebuild may sound like the answer, but in a live business, it often creates more risk than it removes.

Problem

Sales teams lacked a reliable way to prioritise leads, leading to inconsistent follow-ups and missed opportunities. There was no clear signal to identify which leads required immediate attention.