AI-Native Product & Systems Builder
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.
An animated ring shows the eight steps I take a project through: idea, research, PRD, wireframes, hi-fi design, build, deploy and monitor.
The full cycle
Follow one example project, a clinic booking app, through every step.
01
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.
02
Before anything is built, I look at how people work now, what already exists, and where the real gaps are.
03
A product spec anyone can build from: users and roles, flows, business rules, edge cases, and what is out of scope.
04
Fast, plain layouts to agree on structure before a single pixel is polished.
05
Finished screens on a real design system: type, colour, states and layouts that work on every screen size.
06
AI coding agents write the code. I run them like a team and review every change before it moves forward.
07
Docker deployments on servers I run myself, with private admin access and secrets kept out of the code.
08
Metrics, logs, uptime checks and alerts, so I know something broke before your users do.
How I build
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.
An illustration of how one change moves through my workflow.
Agents build from a PRD and clear acceptance checks, not from a vague prompt.
A separate gatekeeper agent checks the work before it can move forward.
I read the diff and the test report. Production is always my manual decision.
~/work ❯ docker compose up ahmed
[+] Running 6/6
researchHealthywho it is for, what already exists
prdHealthya spec anyone can build from
designHealthywireframes to hi-fi in Penpot
buildHealthyAI agents write, I review every change
deployHealthyDocker + Dokploy on my own servers
monitorHealthymetrics, logs and alerts on Discord
ahmed | idea → running system
Requests per minute · last 24 hours
Running on my own servers
Docker
Dokploy
Grafana
VictoriaMetrics
Loki
Uptime Kuma
n8n
PenpotHow I work
One command starts the whole cycle. Everything I build ends up running on servers I manage myself, watched by my own monitoring.
Working together
I work best with founders and small teams who want clear scope, written updates and a result they can run without me.
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.
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.
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.
How a project runs
You share the problem, the current setup and the outcome you want.
I send back a written scope: what is included, what is not, and how we will check it.
Work happens in small, reviewed steps, with short written updates.
Every change is checked against the agreed acceptance criteria.
You get the result, the docs and everything needed to run it without me.
From vibe coding to real systems
Tell me the problem, your current setup and the outcome you want. I reply in writing with how I would approach it.
