Rifki Rosada | Client Systems

Enterprise CRM - Sales Pipeline & Performance System

Designed and shipped a custom CRM that turned fragmented sales tracking and reporting into one shared operating workflow.

Lead Full-Stack Engineer 6-week delivery sprint Remote contract delivery
  • Problem

    Pipeline updates and performance reporting were split across separate files, making weekly reviews slow and ownership hard to trust.

  • My scope

    Mapped sales stages, reporting rules, and operator roles before touching schema or UI.

  • Result

    Gave the team one place to review pipeline movement, ownership, and performance snapshots without spreadsheet reconciliation.

Problem

Pipeline updates and performance reporting were split across separate files, making weekly reviews slow and ownership hard to trust.

Constraints

  • Had to fit active sales operations with minimal disruption
  • Needed role-based access for contributors and managers
  • Deployment target required Docker + Nginx with predictable recovery

Delivery

  • Mapped sales stages, reporting rules, and operator roles before touching schema or UI.
  • Built Laravel + PostgreSQL services for pipeline events, rollups, and role-based access.
  • Implemented a focused Next.js operator interface for updates, reviews, and manager visibility.
  • Delivered Docker + Nginx deployment structure so the handoff was stable and recoverable.

Result

  • Replaced spreadsheet sprawl with a shared CRM workflow for sales operations.
  • Removed manual reconciliation from regular pipeline reviews.
  • Created a base system that could support future sales ops features without restarting the architecture.

Tech stack

  • Laravel
  • Next.js
  • PostgreSQL
  • Docker
  • Nginx

Related delivery proof across internal tools, automation, Android + AI, and supporting product systems.

Automation Systems

Client delivery

Automation Workflows

Automation Engineer2-week delivery sprint

Reduced repetitive copy-paste work and improved visibility across inbound operations.

  • Problem

    Inbound orders and chat updates were copied manually into spreadsheets, producing inconsistent records and delayed follow-up.

  • My scope

    Implemented web-order-to-sheet automation with validation and normalization.

  • Result

    Reduced repetitive copy-paste work and improved visibility across inbound operations.

  • n8n
  • Google Apps Script
  • REST APIs
Read case study

Platform Delivery

Client delivery

Multi-Surface Platform Monorepo

Monorepo Platform Engineer4-week delivery sprint

Reduced release friction and dependency drift across the platform.

  • Problem

    Separate repositories for related surfaces caused dependency drift and slowed coordinated releases.

  • My scope

    Structured the repository with npm workspaces and clearer package boundaries.

  • Result

    Reduced release friction and dependency drift across the platform.

  • npm workspaces
  • Next.js
  • NestJS
Read case study

Android + AI

Client delivery

Media Android App - AI Chat + Search UX

Android AI UX Engineer3-week delivery sprint

Made the AI-assisted discovery flow clearer and more reliable from chat prompt to search result.

  • Problem

    Users lacked a clear transition from AI chat prompts to meaningful search actions, and state sync issues reduced UX reliability.

  • My scope

    Worked inside the existing WebView-based AI entry path so the feature fit the live app architecture.

  • Result

    Made the AI-assisted discovery flow clearer and more reliable from chat prompt to search result.

  • Android
  • Kotlin
  • WebView
Read case study

Planning a similar build?

Share the workflow, delivery risk, and timeline. I will reply with the best starting scope.