Rifki Rosada | Automation Systems

Inbound Order & Lead Ops Automation

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, bookings, and chat updates were copied manually into spreadsheets across multiple branches, producing inconsistent records, delayed follow-up, and zero operational visibility for management.

  • My scope

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

  • Result

    Eliminated an estimated 60–80 hours/month of manual data entry across multi-branch operations. Booking + reporting now flow automatically into a single source of truth.

Project walkthrough

Watch the delivered workflow.

A walkthrough of the multi-branch automation, showing bookings, reporting, and staff KPI flows.

Open on Loom

Problem

Inbound orders, bookings, and chat updates were copied manually into spreadsheets across multiple branches, producing inconsistent records, delayed follow-up, and zero operational visibility for management.

Constraints

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

System workflow

  • 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

  • Estimated 60–80 hours/month of manual logging eliminated across branches.
  • Daily Telegram digests for branch + staff KPIs now generated automatically — management visibility went from weekly to daily.
  • Reusable n8n + Apps Script patterns shipped so the team can extend new automations without engineering involvement.

Tech stack

  • n8n
  • Google Apps Script
  • Google Sheets
  • Google Calendar
  • Notion
  • Telegram Bot API
  • OpenAI

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

Cut the weekly pipeline review cycle from ~2 days of spreadsheet reconciliation to ~15 minutes — single source of truth across sales, ops, and management.

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

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

Android + AI

Client delivery

Media Android App - AI Chat + Search UX

Android AI UX Engineer3-week delivery sprint

Stabilized AI chat-to-search state sync in production — eliminated mismatch issues that broke the discovery flow for end users.

  • Android
  • Kotlin
  • WebView
Read the case study

Have a similar workflow?

Share what your team needs to improve. I can help define the first useful milestone.

Discuss a project See services & pricing