Skip to content
AR

What I can build for you.

From an AI agent that answers your customers to a full store in Arabic and English: designed, built, tested and deployed by one person.

AI workers for your business

An AI worker owns one job, like review replies, email campaigns or support, and does it every day on its own. It follows your rules, and a person approves anything risky before it goes out.

  • Review replies, campaigns, support
  • Runs daily on its own
  • Human approves risky steps

AI agents & automations

Assistants, copilots and workflows built with the OpenAI Agents SDK, Claude and MCP: tools that read your data, take actions and hand off to a human when they should.

  • Custom AI agents & tools
  • MCP servers & integrations
  • Multi-model fallback

Next.js SaaS & web apps

Production apps with auth, billing, dashboards, admin panels and a real database, deployed on Vercel and built to keep running.

  • Auth, billing & roles
  • Postgres / Neon / Supabase
  • Tested & monitored

E-commerce stores

Fast, good-looking stores with checkout, admin, WhatsApp ordering, local payments and multi-language or Arabic RTL support.

  • Catalogue, cart & checkout
  • EN / AR / UR, full RTL
  • Local payment methods

WordPress websites

Business and restaurant sites on WordPress with Elementor or Divi, plus a custom child theme so the owner can edit everything.

  • Elementor & Divi
  • Custom child themes
  • Owner-editable content

Agents answer. Workers do the job.

AI agent

Does a task when you ask.

You open it, give it a task, and it does that task: write a reply, turn a voice note into a report, answer a question.

AI worker

Owns one job and does it every day.

It runs on its own, follows your rules, and stops for a person to approve anything risky. Under the hood, a worker is built from agents.

AI agents vs AI workers
AI agentAI worker
StartsWhen you askOn its own, on a schedule or trigger
ScopeOne taskOne whole job, every day
RulesYour promptWritten rules it always follows
Risky stepsYou check the answerWaits for a person to approve

The simple test. If you have to open a chat and ask every time, it's an agent. If the work gets done while you sleep, it's a worker.

From first message to live URL.

  1. 01

    Understand

    A short call or chat to learn the business, the users and what success looks like. I write it down as a clear brief.

  2. 02

    Prototype fast

    You see a working version early, on a real URL, so feedback is about the actual product, not a mock-up.

  3. 03

    Build & test

    Production code with types, tests and proper auth and data handling. Nothing invented: real content or clear placeholders.

  4. 04

    Launch & support

    Domain, deploy, analytics and handover, with a guide you can follow. I stay around for fixes and the next feature.

Let's build something people use.

Have a project in mind?