Skip to content

About

About Zubair Bin Shaukat

Zubair Bin Shaukat is a software engineer based in Lahore, Pakistan. He builds business automation systems with n8n, custom GoHighLevel dashboards and marketplace apps, web applications with Next.js and React, and cross-platform mobile applications with React Native.

He works directly with founders and white-label for agencies, on fixed-scope engagements. The common thread across the work is process: the systems he builds replace something that was previously done by hand, and they are handed over with a runbook so the client can run them without him.

He also goes by Zubyr, which is where the domain comes from.

Facts

Name
Zubair Bin Shaukat
Role
Software Engineer
Based
Lahore, Pakistan
Timezone
UTC+5
Works with
Founders and agencies
Engagement
Fixed scope
Email
thedevzubair@gmail.com
Zubair Bin Shaukat in a mountain valley

I build systems that run your business without you.

Stack

Stack, by how often it gets used

01

Automation

  • n8n, self-hosted and cloud
  • GoHighLevel workflows
  • Webhook inboxes and queues
  • Postgres as the ledger
  • Retry and idempotency design
02

Platform · GoHighLevel

  • API v2, agency and location scopes
  • Marketplace apps, OAuth 2.0
  • Custom menu-link dashboards
  • Sub-account provisioning
  • Snapshot and template hygiene
03

Web

  • Next.js, App Router
  • React and TypeScript
  • Node.js and AdonisJS
  • Postgres, MongoDB, the MERN stack
  • Tailwind CSS
04

Mobile

  • React Native and Expo
  • Offline-first sync
  • SQLite on device
  • App Store and Play releases
  • Crash reporting and OTA updates

Services

What he takes on

  • 01

    GoHighLevel Development

    The layer under snapshots: custom dashboards mounted inside the platform, marketplace apps with their own OAuth, provisioning that runs on a schedule, and API v2 work that survives a rate limit.

  • 02

    n8n & Workflow Automation

    A manual process, written down until it stops having exceptions, then rebuilt as a pipeline with retries, an exception queue and a log someone can read at 8 a.m.

  • 03

    Web Development

    Client-facing applications where the hard part is the data model, not the pixels. Portals, internal tools, and anything replacing a spreadsheet that six people fight over.

  • 04

    Mobile App Development

    One codebase, both stores, built for the case where the network is not there. Sync conflicts get designed, not discovered.