Back to Work

Enterprise Sales CRM

A sales CRM brings accounts, contacts, activity, documents, sharing, templates, and history into one controlled workspace. I implemented the schema changes, access controls, health checks, and deployment path behind it.

Full-stack, database, and deployment engineerCase studyFull Stack / Infrastructure
Enterprise Sales CRM interface preview

What I built

Account and document workflows are paired with access controls, change history, database evolution, and reverse-proxy operation.

  • Manages accounts, contacts, activity histories, and documents
  • Applies access controls, sharing, templates, and change history
  • Uses migrations, health checks, and Docker Compose deployment

My role

Full-stack, database, and deployment engineer

How it works

  • React and TypeScript client
  • Node API with secure-cookie authentication
  • Oracle and PostgreSQL schema evolution

Key decisions

  • Use access controls and change logs for shared records
  • Treat migrations and health checks as first-class deployment artifacts

What I tested

  • Container health checks
  • Migration validation
  • Browser login verification

Limitations and next steps

The source is private, so this case study stays focused on product behavior, access controls, and deployment decisions.