Skip to content
Hafiz Ahmed ZiaAvailable for work
Start a project

AI-Native Product & Systems Builder

I take your idea all the way to a running system.

Research, PRDs, wireframes and hi-fi design. Then I build it with a team of AI agents, deploy it on servers I run myself, and keep watch with monitoring. One person, the full cycle.

See my work Start a project
  • Based in Pakistan
  • Working worldwide (UTC+5)
  • Written-first, async

An animated ring shows the eight stages I take a project through: idea, research, PRD, wireframes, hi-fi design, build, deploy and monitor.

Scroll

The full cycle

Eight steps. One clear line from idea to production.

  1. 01

    Idea

    Every system starts as one sentence. I turn it into a clear problem: who it is for, what hurts today, and what success looks like.

    NotesQuestions

  2. 02

    Research

    Before anything is built, I look at how people work now, what already exists, and where the real gaps are.

    InterviewsMarket scan

  3. 03

    PRD

    A product spec anyone can build from: users and roles, flows, business rules, edge cases, and what is out of scope.

    MarkdownDecision records

  4. 04

    Wireframes

    Fast, plain layouts to agree on structure before a single pixel is polished.

    Penpot

  5. 05

    Hi-Fi Design

    Finished screens on a real design system: type, colour, states and layouts that work on every screen size.

    PenpotDesign tokens

  6. 06

    Build

    AI coding agents write the code. I run them like a team and review every change before it moves forward.

    Claude CodeCodex

  7. 07

    Deploy

    Docker deployments on servers I run myself, with private admin access and secrets kept out of the code.

    DockerDokployCloudflare

  8. 08

    Monitor

    Metrics, logs, uptime checks and alerts, so I know something broke before your users do.

    GrafanaLokiUptime Kuma

How I build

My team is made of AI agents.
The decisions are mine.

I run AI coding agents like a small engineering team. Each one has a role, and nothing reaches production without passing review and my approval.

MManager agentplans & scopes
DDeveloper agentsbuild & test
GGatekeeper agentindependent review
Meverify & approve
Release
change-log · repeat-safe checkout
  1. ManagerSplit “repeat checkout” into three tasks with acceptance checks.
  2. Developer ATask 1 done: a repeated request returns the first order.
  3. Developer BTask 2 done: stock is re-checked on the server.
  4. GatekeeperMissing a negative test for an expired cart. Sent back.
  5. Developer ANegative test added. All checks passing.
  6. GatekeeperIndependent review passed. Ready for approval.
  7. AhmedRead the diff and the test report. Approved for staging.

An illustration of how one change moves through my workflow.

  1. 01

    Written specs first

    Agents build from a PRD and clear acceptance checks, not from a vague prompt.

  2. 02

    Independent review

    A separate gatekeeper agent checks the work before it can move forward.

  3. 03

    A human signs off

    I read the diff and the test report. Production is always my manual decision.

Selected work

Real projects, at honest stages.

Most of the code is private, so here is what each project does, where it stands today, and what I did on it.

In production

DMRA Student Hub

School operations with a human in control.

Teachers post daily updates in chat. An AI agent turns them into draft records for attendance and Quran progress (Sabaq, Sabqi, Manzil). A person approves before anything is saved, and approves again before a parent hears about it.

What I did

  • Product requirements, roles and data model
  • Two-step approval: save a record, then send a message
  • Backend access rules, built with AI agents
  • Deployment, backups and restore checks
DiscordAI agentSurrealDBDockerWhatsApp (in setup)

Live on staging

Sasta Inverter

A solar marketplace for Pakistan, built end to end.

Buyers compare solar products and seller offers in one place, sellers manage their own prices and stock, and checkout re-checks every price on the server. Planned, designed, built and deployed with a team of AI agents.

What I did

  • Five-part PRD: product, roles, rules, flows, pages
  • Architecture and written decision records
  • Manager, developer and gatekeeper agent workflow
  • Docker deployment through Cloudflare Tunnel
AstroReactRust (Axum)SurrealDBCloudflare R2Flutter

In daily use

Self-hosted platform

The infrastructure all of this runs on.

Three cloud servers for production, staging and a small relay. Deployments, private admin access, central monitoring and alerts, all documented in one shared playbook that my AI agents follow too.

What I did

  • Docker deployments with Dokploy
  • Private management access; no public database ports
  • Central metrics, logs, uptime checks and alerts
  • Secrets in a vault, never in code
DockerDokployTailscaleCloudflareGrafanaInfisical
Also on GitHubHafiz Rust GatewayAn open-source research project on streaming and failure handling for AI traffic. Pre-alpha.
  • 8stages, from idea to monitoring
  • 3servers I run and monitor myself
  • 18services deployed on them
  • 0public database ports
  • Penpot
  • Markdown
  • Decision records
  • User flows
  • Claude Code
  • Codex
  • TypeScript
  • Rust
  • Astro
  • React
  • SurrealDB
  • Flutter
  • Docker
  • Dokploy
  • Cloudflare
  • Tailscale
  • Grafana
  • Loki
  • VictoriaMetrics
  • Infisical
  • n8n

Working together

Three ways I can help right now.

I work best with founders and small teams who want clear scope, written updates and a result they can run without me.

Hafiz Ahmed Zia thinking through a problem

From idea to spec

You have an idea or a rough brief. I turn it into a clear PRD, user flows and wireframes, so any developer or AI agent can build it without guessing.

  • Users, roles and business rules
  • User flows and wireframes
  • Open decisions marked clearly

From prototype to production

You built something with AI and it works on your laptop. I help you deploy it properly, keep secrets safe, back it up and watch it.

  • Docker deployment to staging
  • Backups with a tested restore
  • Monitoring and alerts

From messy repo to clear handover

Your project works, but nobody can explain how. I document the setup, the architecture and the known issues, so the next person can run it.

  • Setup guide that actually works
  • Architecture map
  • Known issues and ownership

How a project runs

  1. 1

    Brief

    You share the problem, the current setup and the outcome you want.

  2. 2

    Scope

    I send back a written scope: what is included, what is not, and how we will check it.

  3. 3

    Build

    Work happens in small, reviewed steps, with short written updates.

  4. 4

    Review

    Every change is checked against the agreed acceptance criteria.

  5. 5

    Handover

    You get the result, the docs and everything needed to run it without me.

From vibe coding to real systems

Your idea deserves a system that keeps running.

Tell me the problem, your current setup and the outcome you want. I reply in writing with how I would approach it.

Start a project
[email protected]

Start a project

Tell me what you need.

I read every message myself and reply by email.

Your details are sent through Cloudflare to my Gmail so I can reply. Please avoid sensitive information. Privacy notice.

Prefer email? [email protected]