ZQ Zaid Qayyum

Automating repetitive business work

This is a normal operations Tuesday, suspended mid-air. Scroll to run it through a system designed to take reconciliation from 6 hours a week to about 30 minutes.

Tuesday, processed8 of 8

  1. Stripe payouts → QuickBooks, daily

    matched line by line, no CSV in sight

  2. Disputes flagged the day they open

    used to surface a week late

  3. "Where's my order?" → answered before it's a ticket

    order status SMS flow, Twilio + SendGrid

  4. Missed call → answered, qualified, booked

    voice agent, straight into the calendar

  5. Every finished job asks for its review at T+24h

    every job, not just on slow days

  6. Renewal call → job history attached

    synced from the ops system overnight

  7. Refunds land in POS and the books together

  8. Brief → drafted, tone-checked, queued

    human review in Slack before anything ships

design target 6h/wk → 30min reconciliation effort, Stripe to QuickBooks
design target, roughly 60% fewer "where's my order" tickets, month one

Same Tuesday, running itself.

Book a discovery call or read the cases first

The Tuesday upstairs is a composite. These three are the builds underneath it.

Sample builds, not client engagements: representative scenarios with the architecture worked through in full. Each case keeps the machine's shape: the mess as modeled, the system designed to replace it, the target it is built to hit.

Case 01Revenue Operations2024Sample build Representative scenario: B2B SaaS company, Canada

Stripe + QuickBooks reconciliation for a Canadian SaaS

The scenario: finance spends around 6 hours a week exporting Stripe CSVs, splitting subscriptions from one-off charges and pasting the lot into QuickBooks. Reconciliation lags by a week, disputes age before anyone sees them, and the CFO has no live view of MRR.

what replaces it:

  1. Stripe webhookcharge, refund, dispute, payout: every event mapped
  2. n8n normaliseidempotent, re-runnable on any time window
  3. QuickBooks postsales receipt, credit memo or journal entry
  4. Slack alertfailed payments surface within 60 seconds
design target

  • Month-end close from T+7 to T+1

    revenue books the moment Stripe confirms it

  • Disputes caught the day they open

    resolved inside the chargeback window, not a week late

  • Year-end accountant export in one click

    every entry traces back to its Stripe event

design target 6h/wk → 30min reconciliation effort, Stripe to QuickBooks
Open case 01

the first stamp upstairs, filed at source

Case 06AI Content Ops2025Sample build Representative scenario: 12-person marketing agency, US

n8n + Claude content production pipeline for a marketing agency

The scenario: about 80 pieces a month across 14 client accounts, and the bottleneck is never the writing. It is everything around it: outlines, tone of voice per client, review, formatting, tracking what shipped where. Senior editors rubber-stamp work just to keep the pipeline moving.

the queue as modeled: briefs stacking in faster than the desk can clear them

what replaces it:

  1. Notion briefpicked up on trigger
  2. Claude outlineloose brief becomes structure
  3. First draftClaude or OpenAI, by content type
  4. Tone passvoice cards hold each client's sound
  5. Slack reviewa human accepts, rejects or edits
  6. PublishCMS, ESP, scheduler or Drive
design target, roughly 80 → 240 pieces a month, without hiring

If a model times out or comes back low-confidence, the brief routes to a human writer with the partial draft attached. Every piece carries provenance: which model, which prompt version, which reviewer approved.

Open case 06
Case 02Field Service Operations2024Sample build Representative scenario: plumbing & heating contractor, UK, 10 vans

Jobber + Zapier dispatch automation for a UK plumbing co

The scenario: jobs get booked, completed and invoiced, but review requests go out by hand, on slow days, and get forgotten on busy ones. Five-star Google reviews sit flat for a year despite genuinely happy customers.

what replaces it:

  • booked
    Booking confirmation
  • T-24h
    Reminder: named technician, ETA window
  • en route
    Mike is on his way.

    the message as built: name pulled from Jobber's assigned-to field, never "your engineer"

  • T+0
    Completion summary
  • T+24h
    Review request

    no review by day 5: a softer nudge, from the technician's name, not the company's

  • T+90d
    Seasonal check-in

Every transition fires off a Jobber event. Zapier wires it, Twilio carries the SMS, SendGrid the email; review traffic splits between Google and Trustpilot.

The target at sixty days: about 5 hours a week back for the office team, and fewer reschedules and no-shows, because the on-the-way SMS makes the schedule feel real.

design target 4 → 14 five-star reviews a month, first 60 days
Open case 02

Five more cases in the archive, including the one the second stamp upstairs came from.

Works →

Capability manifest

What I build between the tools you already run.

Every engagement assembles from this catalogue. Each line names the platforms it runs on and what lands in your hands at the end.

  1. 01

    Custom CRMs & internal tools

    Lead pipelines, client records, job history and role-based portals in one system. Built on PHP + MySQL, or fitted into the GoHighLevel or Salesforce seats you already pay for. Ships as a hosted app with an admin login and a written runbook.

  2. 02

    API integrations between business tools

    Stripe into QuickBooks, Jobber into Twilio, Salesforce into whatever holds the job history. Idempotent, re-runnable on any time window, an audit row on every sync. Lands as n8n or Zapier flows, or custom endpoints where those run out.

  3. 03

    AI-assisted internal utilities

    Claude or OpenAI drafting, tagging and triaging inside the workflow, with a human approve step in Slack before anything ships. Vapi.ai answers the phones after hours. Prompts are versioned; every output carries provenance.

  4. 04

    Dashboards & operational reporting

    KPI tracking, inventory counts, job status and revenue against target, pulled live from MySQL and the APIs underneath. Delivered as one dashboard URL behind your own login: the screen an operator checks each morning.

  5. 05

    Full-stack web applications

    Booking systems, POS, customer portals: the tool that does not exist off the shelf. PHP, JavaScript and MySQL with authentication and roles from day one. Handed over deployed, with source in your repo.

One operator, end to end.

I'm Zaid Qayyum, automation and internal tools engineer: 4+ years building the systems that replace manual operations. CRMs, dashboards, API integrations and AI workflows, for founders and agencies that have outgrown spreadsheets.

The person who scopes the call is the person who builds the system and writes the runbook. Nothing gets handed between departments, because there are none.

4+ years building · freelance and full-time product work

Zaid Qayyum, duotone print portrait

Career log

  1. Feb 2023 - nowlog 01

    Full Stack Developer

    Rank Genics

    Custom web systems, dashboards and operational tools for client businesses: integrations, backends, admin panels. Currently shipping features on an enterprise multi-tenant React/Node platform (2M+ lines of code, under NDA).

  2. 2021 - nowlog 02

    Freelance Developer & Systems Builder

    independent

    CRMs, business tools, admin systems and automation builds, managed from planning to deployment.

  3. 2021 - 2025log 03

    BS Information Technology

    Riphah International University

    Final-year work focused on software systems and web applications.

  4. 2019 - 2021log 04

    Full Stack Web Development

    TechnoLangs

    "Emerging Student of Web Development" award.

How an engagement runs.

Three stages. Each one ends with something concrete in your hands.

  1. 01

    The discovery call

    30 minutes, no slide deck, no pricing pitch. We map the bottleneck and agree what the smallest useful first ship looks like; you decide fit before any contract goes out.

  2. 02

    The build

    Short cycles against that scoped first ship. You watch the working surface come up, the actual workflow inside n8n, GoHighLevel or the repo, not status decks. Scope stays pinned to the bottleneck we named.

  3. 03

    The handoff

    Every system ships with a Loom walk-through, a written runbook and credentials in an account you own. You own it on day one; I stay on call for the first 30 days at no extra cost while your team learns the surface.

The 30 minutes cost nothing either way: worst case, you leave with the bottleneck named. Book it below ↓

Got a workflow bottleneck?

Tell me about your operational pain. A short message is enough to start; I usually reply within a working day.

Loading the booking calendar...

Opens in Google Calendar

Book directly: calendar link