Rifki Rosada | Automation Systems

Automation Workflows

Built automation pipelines that moved orders and chat updates into a shared ops workflow with less manual logging.

Automation Engineer 2-week delivery sprint Remote contract delivery
  • 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.

Problem

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

Constraints

  • Needed to remain usable for non-technical operations users
  • Third-party payloads could change without notice
  • Logging needed traceability for audits and handovers

Delivery

  • Implemented web-order-to-sheet automation with validation and normalization.
  • Added WhatsApp-to-sheet logging and tagging workflows for shared follow-up visibility.
  • Used n8n + Google Apps Script to balance speed, maintainability, and practical ownership.
  • Defined fallback paths and operating checks for failed runs.

Result

  • Reduced manual logging work in inbound operations.
  • Improved consistency of lead and order records across channels.
  • Provided reusable workflow patterns for future automation extensions.

Tech stack

  • n8n
  • Google Apps Script
  • REST APIs
  • Google Sheets

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

Client Systems

Client delivery

Enterprise CRM - Sales Pipeline & Performance System

Lead Full-Stack Engineer6-week delivery sprint

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.

  • 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.

  • Laravel
  • Next.js
  • PostgreSQL
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.

Share your scope Email project brief