Lumenden

Portfolio

Saad Fazal

See the work
Saad FazalBackend & automation developer
LD-2026
All areas

Hi, I'm Saad.

Shopify apps, Meta developer apps like Accurate Profit, WhatsApp on Cloud API, GHL (flows, agents, funnels, email), and ElevenLabs / retail voice agents. Client delivery for Disruptive Brain and Flaxen Media; EasyCloudAPI is my own.

The work I get called for is usually the part with no documented path - a reorder flow Shopify does not support, ads profit that has to join three APIs, a voice line that must book into GHL, or a queue that has to hold at 2am.

6+ yearsBuilding backends, integrations and automation for clients
12Systems written up here, with the pipeline for each
6 liveRunning in production rather than sitting in a repo

Experience

  • Shopify DeveloperDisruptive Brain Pvt LtdFeb 2023 - Present
  • Accurate ProfitMeta developer app · Client deliveryCase study
  • Custom product reorderingVulgrco · via Disruptive BrainClient delivery
  • Back End DeveloperFlaxen MediaFeb 2021 - Present

Building now

  • Client Shopify + Meta appsDisruptive Brain / Flaxen - Shopify apps, Accurate Profit (Shopify × FB/Google Ads), Vulgrco reorder.
  • GHL growth systemsFlows, agents, WhatsApp automations, sites, funnels, and email sequences for client delivery.
  • Voice agentsElevenLabs + retail AI voice agents with booking, transcripts, metering, and dashboards.
  • WhatsApp / EasyCloudAPIMulti-tenant inbox and automations; CodeBuddy for my own ops chat.

Contact

Toolkit

Node.jsPythonReactShopifyPostgresMongoDBn8n / MakeGoHighLevelWhatsApp Cloud APIMeta Apps / AdsElevenLabs

Selected systems

Five systems, numbered in the order I would walk you through them. Each one starts with the problem and ends with what shipped.

All 12 projects

How I work

What I do before writing the schema

Find out what actually breaks

Before I design a schema I want the failure cases: the webhook that arrives twice, the token that expires at 2am, the merchant with 400 variants. Those decide the shape far more than the happy path does.

Keep the slow work off the request path

Webhooks get a fast acknowledgement and a queue. Meta gets its 200 in milliseconds, the worker takes as long as it needs, and a retry is a normal event rather than an incident.

Build the ops surface, not just the endpoint

An integration nobody can inspect becomes someone's 3am problem. Inbox, logs, usage, manual retry - the boring screens are what make a system supportable after handover.

Hand it over so it survives me

Config over hardcoding, error paths that say what went wrong, and a merchant or ops person who can run it without opening a terminal.

From the products

Screenshots

Accurate Profit - Shopify × Meta Ads × Google Ads
Accurate Profit - Shopify × Meta Ads × Google Ads
GHL - flows, funnels, WhatsApp & email agents
GHL - flows, funnels, WhatsApp & email agents
Voice agents - ElevenLabs + retail AI ops
Voice agents - ElevenLabs + retail AI ops

Got a messy problem to ship?

I'm strongest when the work spans backend, integrations and the product surface - Shopify, Meta apps, WhatsApp, GHL, voice agents, or retrieval that has to cite sources.