Available for automation work Lahore, PK — UTC+5

Automation that survives production.

I'm Aqif Ahmed — an automation engineer with a backend foundation in Python, FastAPI, and PostgreSQL. I build AI systems with the parts most demos skip: validation, human gates, audit logs, and monitoring. The boring parts. The parts clients are still paying for a year later.

01 — Selected systems

Three systems, built to
production standard.

Not tutorial workflows. Each one is designed around the failure modes that kill automations in week three — malformed output, silent errors, duplicate writes, unbounded cost.

Document Intelligence Pipeline

Extraction + Human Review

Invoices and purchase orders arrive by email; validated structured data leaves in a database. Every extraction is checked mechanically — do the line items sum to the total, is the date parseable, is the vendor known — and anything below the confidence threshold routes to a human review queue with the original document side-by-side.

  • Validation is arithmetic, not another LLM call — totals must reconcile before a record is written.
  • Idempotent writes: re-running a batch can never create duplicate records.
  • Extraction accuracy is tracked weekly against the review queue's corrections.
n8nClaude VisionPostgreSQLAirtable
Confidence-gated writes

Inbound Voice Agent

Qualification + Booking

Answers the phone, qualifies the caller, checks live calendar availability, books the slot, and sends an SMS confirmation. Built for businesses that lose money on every missed call. The agent's tools are narrow by design — it can check availability and book, nothing else.

  • Sub-800ms response latency budget — beyond that, callers hang up.
  • Hard escalation rules: two failed intents or any complaint transfers to a human line.
  • Every call logged with transcript, outcome, and per-call cost.
VapiTwilion8nGoogle CalendarPostgreSQL
< 800ms latency budget

Automation Infrastructure Layer

Monitored Multi-tenant Ops

The layer that turns workflows into a service: self-hosted n8n in queue mode with worker replicas, a global error workflow that catches every failed execution, retries with backoff, and dead-letters what can't recover. Per-client credential isolation, per-client cost tracking, and a one-page dashboard the client can actually read.

  • Workflows are versioned in git and deployed, not edited live in production.
  • Failures are loud: every dead-lettered execution alerts Slack with full context.
  • Monthly report per client: executions run, hours saved, errors, spend.
Dockern8n queue modePostgreSQLRedisGrafana
Zero silent failures
02 — Method

How I build.

The difference between a demo and a system is invisible in a screenshot. This is what I put into every build anyway.

01

Fail loudly

A workflow that fails loudly costs an hour. One that fails silently — dropping leads, misfiling invoices — costs the client's trust. Every failure path alerts.

02

Humans gate writes

Drafts, not auto-sends. Approval cards before refunds. Read-only for two weeks before anything gets write access. Autonomy is earned, not assumed.

03

Eval before ship

A RAG bot doesn't ship until it's scored against a set of real questions with known answers. Prompt changes get measured, not eyeballed.

04

Idempotent by default

Workflows re-run. Webhooks fire twice. A second execution must never create a second contact, invoice, or email. Deduplication is designed in, not patched on.

05

Treat data as data

Anything an agent reads — a ticket, an email, a scraped page — can contain text trying to instruct it. Retrieved content is never treated as a command.

06

Cap the cost

Hard limits on iterations and tokens. Cost tracked per execution, per client, per month. An unbounded agent loop at 3am is not a surprise I ship.

Orchestration n8n (self-hosted, queue mode) · LangChain · Cron
Models Claude API · OpenAI API · Structured outputs · Prompt caching
Backend Python · FastAPI · PostgreSQL · Celery / Redis · Docker
Retrieval pgvector · Qdrant · Chunking + reranking · Eval sets
Voice & channels Vapi · Twilio · Slack apps · Gmail API
03 — Contact

Have a process worth automating?

aqifarain@gmail.com