Ahmad Tahir, Lahore, PakistanSince 2017 · 9 years building for the web

Ahmad Tahir, Full-StackEngineer.

I build web applications, SaaS products and AI-powered systems, from database schema and queue workers to the interface people use.

  • NowEngineering with Cart Compound and Titan Dev Agency
  • LabBuilding agentic RAG systems with LlamaIndex and local models
  • 9 years
    Shipping software since 2017
  • Laravel · React
    Primary stack
  • Python · LLMs
    Current frontier
  • GMT+5
    Lahore, remote-first
OutreachFlow dashboard showing available credits, on-hold credits and outreach activity

FeaturedSaaS platform

OutreachFlow: one engineer, one Filament panel, five queues and a credit ledger that can’t be overspent.

Every paid action, whether finding a website, finding an email, pulling metrics or sending a message, is metered in credits that users get through Stripe subscriptions.

Role
Solo build: architecture, planning and all of the development
Timeline
MVP delivered in about four months
Stack
Laravel 11, FilamentPHP, Livewire, MySQL, Stripe & Cashier

The model is the easy part. Billing, retries, background work and honest failure states are the product.

02Technical identity

A deep foundation,
an open frontier.

Nine years in PHP and JavaScript, and a growing share of my time in Python and AI engineering. Footnotes point to the work where each one shows up.

FoundationWhere most of my work lives
  • Laravel1
  • PHP1,2
  • MySQL1
  • JavaScript
  • React3
  • WordPress & WooCommerce2,4
ToolkitWhat I reach for regularly
  • FilamentPHP
  • Livewire
  • TypeScript
  • Tailwind CSS
  • REST APIs & webhooks
  • Stripe & Cashier
  • Queues & scheduled jobs
  • PostgreSQL
  • Linux, Nginx & systemd
  • GitHub Actions
  • AWS
  • Google APIs & BigQuery
FrontierWhat I'm exploring now
  • Python3,5
  • LLM integrations1
  • RAG3
  • AI agents & tool use3
  • Local models (Ollama)3
  • Workflow automation

Seen in — 1 OutreachFlow 2 UnderFit 3 RAG Support Agent 4 B2B Mint 5 Email Verifier

03Approach

How I like to build.

Habits that came out of real production incidents, not slogans. Most were learned the slow way.

  1. Plan the structure in writing

    Before the code multiplies, I write down the architecture, the conventions and the edge cases. It feels slow on day one and pays for itself every week after.

  2. Conventions are architecture

    Thin jobs, focused services, enums that own their labels, one class that owns every rate. Small rules applied consistently are what keep a codebase workable for one person or for ten.

  3. Boring infrastructure, deliberate seams

    A database queue and a modest server can launch a product. What matters is that nothing in the design blocks the move to Redis or bigger hardware when usage asks for it.

  4. Fix the cause, not the symptom

    Problems get investigated rather than hidden behind patches. A production incident should leave behind a rule that prevents the next one.

  5. Be honest about the edges

    Known gaps get documented, not buried. A system you can reason about includes the parts that don't work yet.

04Journey

From themes to systems.

I started as a WordPress intern in 2017. The work kept pulling me deeper into the backend. The longer version.

  1. 2026 — NowCart CompoundWordPress, WooCommerce & Laravel Engineer
  2. 2022 — NowTitan Dev AgencyFull-Stack PHP Developer
  3. 2019 — NowIndependentWordPress & WooCommerce Developer
  4. 2017 — 2021Designs ValleyWordPress Developer
Full history on LinkedIn

→Get in touch

Building something
interesting?

hi@ahmadthedev.com