Remote contract engineer · IEEE-published

AI automations and custom internal tools that save service businesses 20+ hours a week.

Fixed-scope sprints. CRMs, n8n workflows, and Android AI shipped for travel, ops, and product teams. Booking from $3,500.

Share your scope See client work

Commercial proof

CRM, automation, Android AI UX, and multi-surface delivery kept at the center of the portfolio.

  • 1

    Custom CRM replaced 3 separate spreadsheets — pipeline review cycle cut from ~2 days to ~15 minutes.

  • 2

    Inbound order + lead automation eliminated an estimated 60–80 hours/month of manual logging for a multi-branch operator.

  • 3

    Shipped Android AI chat-to-search UX in a live media app — stabilized state sync across the discovery flow.

How I help

Outcome-first engagement options for teams that need delivery, not generic freelance coverage.

AI Workflow & Internal Tool Sprint

From $5,000 · fixed-scope

Design and ship the system that removes manual steps, clarifies ownership, and gives teams a cleaner operating baseline. Most engagements recover 15–30 hours of weekly ops time within the first delivery cycle.

Typical sprint: 2–6 weeks

Best for: internal workflow cleanup, ops tooling, team visibility

  • Workflow mapping, data shape, and role-aware delivery plan
  • Implementation across backend, dashboard, and supporting product surfaces
  • Handoff notes for rollout, maintenance, and next-step iteration

Relevant proof

Enterprise CRM - Sales Pipeline & Performance SystemInbound Order & Lead Ops AutomationMulti-Surface Platform Monorepo

Automation & Ops Clarity Sprint

From $3,500 · fixed-scope

Build n8n + Apps Script + API automation layers that move data between tools, eliminate repetitive logging, and make operational state easier to trust. Past engagements have removed 60–80 hours/month of manual work.

Typical sprint: 1–3 weeks

Best for: lead routing, reporting handoffs, manual admin reduction

  • Workflow implementation across APIs, n8n, Apps Script, and operational sheets
  • Validation, fallback handling, and traceability checks
  • Lightweight operating notes for non-technical team members

Relevant proof

Inbound Order & Lead Ops AutomationEnterprise CRM - Sales Pipeline & Performance System

Android + AI Product Delivery

From $4,500 · fixed-scope

Ship Android features and AI-assisted product flows that need careful state handling, usability work, and production-minded implementation. IEEE-published research background in real-time computer vision (YOLO model evaluation).

Typical sprint: 2–4 weeks

Best for: AI chat/search UX, offline-first flows, on-device CV (TFLite/YOLO/ONNX)

  • Flow review for user entry points, state changes, and edge cases
  • Implementation inside the existing Android architecture
  • Release-ready notes for QA, follow-up fixes, and future iteration

Relevant proof

Media Android App - AI Chat + Search UXOffScan AI
See engagement options Share your scope

Selected systems and product delivery

Highest-fit proof for internal tools, automation, platform delivery, and Android + AI execution.

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.

  • Problem

    Pipeline updates and performance reporting were split across 3 separate spreadsheets, making weekly reviews take days and ownership hard to trust.

  • My scope

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

  • Result

    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
  • Prisma
  • Docker
Read case study

Automation Systems

Client delivery

Inbound Order & Lead Ops Automation

Automation Engineer2-week delivery sprint

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.

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

  • n8n
  • Google Apps Script
  • Google Sheets
  • Google Calendar
  • Notion
Read 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.

  • 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

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

  • Android
  • Kotlin
  • WebView
  • Search UX
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
  • TypeScript
Read case study
Review relevant work Share your scope

What clients say

Verified delivery — full client context shared on call. Returning clients across multiple verticals.

Rifki mapped the whole workflow before writing a single line of code. The CRM fit exactly how our team operates — we stopped reconciling spreadsheets every Monday. Clean handoff, well documented, ready to hand to whoever maintains it next.

Co-founder — Multi-vertical operator (travel + service businesses), Indonesia

Engagement #1 — Enterprise CRM build

Brought him back for a totally different vertical after the CRM. Automation cut our daily reporting and booking work from hours to minutes across multiple branches. Edge cases flagged before they became problems.

Same operator — Returning engagement — different vertical (service operations)

Engagement #2 — AI ops automation

Why teams bring me in

  • Shipped production systems across CRM, automation, Android AI UX, and multi-surface platform delivery.
  • Published research in IEEE Xplore — real-time computer vision (YOLO model evaluation for on-device classification).
  • Returning clients across multiple verticals — operators come back for second and third engagements after first delivery.
  • Direct stakeholder collaboration on scope, milestones, and rollout context. Full client references available on request.

Good fit

  • Service businesses (travel, salons, clinics, agencies, multi-branch ops) losing 20+ hrs/week to manual workflows
  • Founders or operators who need fixed-scope sprints, not hourly dev time
  • Product teams that need Android + AI delivery (TFLite, YOLO, on-device CV) alongside backend or web work

Working style

  • Scopes are broken into milestones with clear delivery order and acceptance criteria.
  • I work comfortably inside existing products, not just greenfield builds.
  • Handoff quality matters as much as implementation speed.

Core stack

  • Laravel
  • Next.js
  • NestJS
  • Android
  • Kotlin
  • PostgreSQL
  • Docker
  • n8n
  • Google Apps Script

Profiles

GitHubLinkedIn

Remote contract engineering

Ready to stop patching the same workflow every quarter?

Share the current process, blockers, and timeline. I will reply with the best starting scope within 24 hours.

Share your scope Email project brief