Muhammad Haris

Muhammad Haris

Tech Lead

I lead delivery on systems, not just write the code in them. That means the first client conversation, the shape of the thing, the team that builds it, and being the one accountable when it ships. 5+ years across PHP, JavaScript and Python.

What follows is one of those systems, drawn rather than described.

haris@muhammadharis.dev

Architecture of a multi-tenant commerce platformA storefront rendered at the Cloudflare edge and an authenticated merchant dashboard both write to one Laravel core spanning 38 modules. Every outside system is reached through a single integration manager with one driver per courier, payment gateway and messaging provider, so adding a provider is one class and a configuration entry rather than a change across the domain.ordersStorefrontAstro, edgeCommerce coreLaravel, 38 moduleswritesMerchant dashboardNext.jsdispatchIntegration managerone contractshipchargenotifyCourier driversper operatorGateway driversper gatewayMessaging driversper provider

Tyveno: multi-tenant commerce platform, in development.

How I run a project

The code is the part I enjoy. It is rarely the part that decides whether a project lands.

  • Before the build

    Most of my work starts as a conversation, not a specification. That means running discovery myself, working out what a client actually needs as opposed to what they first asked for, and being honest early about what a budget will and will not buy. The uncomfortable version of that conversation is much cheaper in week one than in month four.

  • Leading the build

    Setting the architecture, splitting the work so people can move without colliding, and reviewing what comes back. I stay close enough to the code to know when an estimate is wrong, because a lead who has stopped reading the diff is guessing along with everyone else.

  • Closing it out

    Delivery is the job, not the handover. Getting a thing live, keeping it live, and staying answerable for it afterwards is the part clients actually remember, and it is the reason the work below spans repeat engagements rather than one-off builds.

Delivered for clients in Angola, Vietnam, Sri Lanka, South Africa, Australia, Germany, the United States, the United Kingdom and Pakistan.

Selected work

Sorted by what is worth your time, not by whether it is still running. Status is stated on every entry.

All work

A US college sports NIL platform

Running endorsement deals between college athletes, their schools and brands

College athletes in the US can now be paid for endorsements, but the money has to clear their school's compliance office before it moves, and getting that wrong can cost an athlete their eligibility. This platform runs those deals end to end. I was lead developer, building athlete onboarding, identity verification on the payout path, compliance reporting for schools, and a refund workflow that stays auditable when a reversal touches three parties at once.

This work shipped under a white-label arrangement. The client name, the live URL and all interface screenshots are withheld here. The architecture and the decisions below are mine and are described in full.

Status
Status: Live
2026
Role
Lead developer
Stack
  • Laravel
  • Vue.js
  • MySQL

A German B2B industrial machinery marketplace

B2B machinery marketplace and consultant management, German market

A German-market platform covering two sides of industrial machinery: a marketplace catalogue fed by an assisted ingestion pipeline, and management of the consultants who work the deals. Ingestion runs from an allowlist-driven source registry with a per-supplier state machine, and AI-normalised records are held for human review before they can publish.

Built under a client confidentiality arrangement. The client, the product name, the live URL and all interface screenshots are withheld. The architecture and the decisions below are my work and are described in full. Happy to go deeper in conversation.

Status
Status: Live
2025
Role
Lead developer
Stack
  • Laravel

An AI-assisted finance and reconciliation platform

AI-assisted invoice ingestion

A finance platform that takes invoices, receipts and statements in whatever form they arrive, turns them into reconciled positions, and settles them. Documents enter through five paths including a forwarding mailbox and Gmail sync behind a keyword gate. AI extraction runs against versioned prompts, bills are matched to bank and card transactions through a FIFO allocation, and payment runs on Stripe Connect with no custody: card in, verified bank debit out, settled directly to the receiving party.

Built under a client confidentiality arrangement. The client, the product name, the live URL and all interface screenshots are withheld. The architecture and the decisions below are my work and are described in full. Happy to go deeper in conversation.

Status
Status: Live
2026
Role
Developer, in a team
Stack
  • Laravel
  • Livewire
  • Flux UI
  • Tailwind
  • MySQL
  • Redis
  • Horizon
  • Gemini
  • Plaid
  • Stripe

Stack in production

Counted from the work below, not from a list of things I have read about.

  • Laravel14 projects
  • MySQL10 projects
  • PHP3 projects
  • Vue.js3 projects
  • WordPress2 projects
  • Flux UI1 project
  • Gemini1 project
  • GitLab CI/CD1 project
  • Horizon1 project
  • Livewire1 project
  • Next.js1 project
  • Phalcon1 project
  • Plaid1 project
  • React Native1 project
  • Redis1 project
  • Stripe1 project
  • Tailwind1 project

Experience

5+ years across marketplaces, hospitality distribution, commerce and payments.

  1. Feb 2025 to Present

    Tech Lead at Hybrid MediaWorks

    Islamabad, Pakistan

    Leading delivery rather than only building it. I sit in the client conversations myself, run the discovery, turn what a client describes into something a team can actually build, and stay accountable for it through to launch. Being the person in both the requirements call and the code review is the whole point: a lead who has stopped reading the diff is guessing along with everyone else about what an estimate means. Technically the work spans Laravel with Vue and Livewire, Next.js and Tailwind on the front, and AI and MCP integrations, where most of the engineering turns out to be deciding what a model is allowed to touch and what a human still has to sign off.

    • Laravel
    • Vue.js
    • Livewire
    • Flux UI
    • Next.js
    • Tailwind
    • AI integrations
    • MCP
    • JavaScript

  2. Oct 2024 to Feb 2025

    L3 Software Engineer (Remote) at Creative Networks

    Rochdale, United Kingdom

    L3 engineer on a support and delivery team that absorbed the client books of several web development companies the business acquired. Each acquisition arrived as a set of live sites, unfamiliar codebases and clients who expected no interruption in service, so the work was to pick up other people's builds at speed and keep them running. Everything routed through DeskPro. Client requests came in as tickets and each one was a different problem: a new requirement on a site I had not seen before, a plugin conflict after an upgrade, a broken integration, a change to something a previous agency had built and not documented. L3 meant the tickets that reached me were the ones the earlier tiers could not close. Alongside the ticket queue, I handled version upgrades and plugin work across the estate. WordPress and Joomla core upgrades, plugin updates, replacements where something had been abandoned upstream, and the regression work that follows any of those on a site that is live and earning. The value was in breadth and turnaround rather than depth on one system. Reading an unfamiliar codebase quickly, working out what a client actually needed from a short ticket, and shipping without breaking a site that someone else's business depends on.

    • WordPress
    • Joomla
    • PHP
    • MySQL
    • DeskPro

  3. Jun 2023 to Apr 2024

    Software Engineer at Ibex Pakistan

    Lahore, Pakistan

    Built the Unilever and Pepsico internal ticketing systems in Laravel and Vue.js, and contributed to several BPO dashboards and enterprise applications. Enterprise ticketing is rarely a feature problem: the requirement is almost always the workflow and the audit trail wrapped around it, and the interesting constraints come from who is allowed to see what.

    • Laravel
    • Vue.js
    • Angular
    • MySQL

  4. Dec 2021 to May 2023

    Backend Developer (PHP) at Horizon Web Solutions / Tossdown

    Lahore, Pakistan

    Built B2B and B2C portals with role-based access control, and integrated the long tail of systems those portals depend on: QuickBooks, Odoo, Sendgrid, Shipstation, Bykea and PandaGo. Real-time notifications and chat ran over WebSocket pushers. Payments spanned Stripe and PayPal alongside PayFast, Bank Alfalah, HBL and UBL, where the local gateways each define their own idea of a callback and none of them agree.

    • PHP
    • Laravel
    • MySQL
    • Pusher
    • Stripe
    • PayPal
    • QuickBooks
    • Odoo

Contact

If something above lines up with what you are building, the fastest route is email.

haris@muhammadharis.dev