Skip to content
All case studies

Case study

Taking over a live platform after a one-month handover

Independently resolved 150+ production issues, cut a long-loading service-creation flow to seconds, and fixed a cross-timezone scheduling bug, working daily with Australian stakeholders.

Intergy Consulting · Full-Stack Developer · Aug 2025 – Present

  • Django
  • PostgreSQL
  • Python
Production issues resolved
150+
Handover before I took ownership
1 month
Long-loading process now completes in
Seconds
Work with Australian stakeholders
Daily

The same live care-sector platform, used by 50+ organizations, 300+ clinicians and 2,000+ users, reached me as an inherited production codebase after a one-month handover.

Service time zone
Sydney (AEST)
10:00 AM
Viewer's device
India (IST)
5:30 AM
Shown to the viewer
Wrong: device time
5:30 AM
Example: a 10:00 AM appointment in Sydney, viewed on a device set to India time.

The challenge

A live system with real users arrived with a one-month handover. From then on I resolved production issues independently and shipped hotfixes directly to the client, from code change to deployment.

Two problems stood out: a service-creation workflow that took a long time to load, and appointments that showed the wrong time depending on the viewer's device.

The approach

  1. Take ownership of the inherited codebase

    Took ownership of the inherited production codebase after a one-month handover.

  2. Resolve issues and ship hotfixes

    Independently resolved 150+ production issues, shipping hotfixes directly to the client from code change to deployment.

  3. Speed up service creation

    Optimized PostgreSQL queries and API logic in the service-creation workflow, reducing a long-loading process to completion within seconds.

  4. Fix cross-timezone scheduling

    Fixed a scheduling defect so appointments display in each service's own time zone rather than the viewer's device time.

  5. Work with stakeholders every day

    Worked directly with Australian stakeholders every day on requirements gathering and live support.

The outcome

  • 150+ production issues resolved.
  • A long-loading service-creation process now completes within seconds.
  • Appointments display in each service's own time zone, whatever the viewer's device says.

Same platform: Moving a live care platform off Salesforce with zero data loss