Taking over a CRM in trouble

Taking over a CRM in trouble

In April 2026 I was asked to take over the CRM module of the Keyfinder ERP. It was unstable, behind schedule, and the knowledge of how it was supposed to work wasn't written down anywhere.

Before changing anything, I read through the code and documented the module's business logic: what each part does, how records move through it and which rules apply. That gave me, and everyone after me, a map of the module.

Then I audited the property-matching feature, the part that matches clients' requests with available properties, since it was the most important and least understood part of the module.

With the logic documented and the matching feature checked, I fixed what was blocking the release.

The CRM was released within a week of me taking it over, and the documentation I wrote stayed behind for the next developer who touches it.