Skip to content

I take the data and AI work off your team's plate.

I am Farhan Ahmed Khan. For six years I built the software big companies use to move and report on their data. Now I do that work for businesses directly, and build the AI that sits on top of it.

  • Six yearsbuilding data products at a US data platform company
  • 15 peoplein my team at its largest, across product and pre-sales
  • Four continentsNorth America, Europe, the Middle East and Australia
  • Employee of the Year2023, out of the whole company
  • LUMSBS Electrical Engineering
See what I have builtWhat people bring me
Farhan Ahmed Khan, photographed against a pale grey wall

Data and AI bootcamps for more than 1,500 people, at top universities across Pakistan, among them IBA, NED, LUMS, GIKI and NUST.

  • Speaking at a lectern with a microphone, gesturing mid-sentence, a data modelling tool projected behind
  • A full university auditorium of attendees with laptops open, seen from the front of the room
  • Teaching a bootcamp to a room arranged in a horseshoe, arm out mid-explanation
  • Presenting beside a projected data grid, hand raised mid-point
  • A long training room seen from the back, every seat taken and every laptop open
  • Mid-sentence in front of a seated workshop, hands shaping the point
  • The team on the steps of a university building before a bootcamp
  • Holding the Employee of the Year certificate and trophy at a company town hall

AI should only decide what someone can check.

Put AI somewhere a mistake would go unnoticed and it will fail without telling you. Most of my work is deciding where that line sits.

The AI decides

Messy input, and a person can check the answer.

A person approves

Money moves, or it cannot be taken back.

Code does it, not AI

A mistake here would be costly and easy to miss.

Why it sits there

Messy input, and every guess it makes can be checked against the data before anyone builds on it.

Pick one, or leave it running.

What people bring me

Moving off an old system

Getting your data out of the thing you are leaving, cleaned up and matched, with proof that nothing went missing.

Joining up the systems you run

So orders, stock and invoices move between them on their own, instead of someone retyping the same numbers.

Reports you can trust

Built so the numbers stay right as the business changes, instead of quietly drifting.

AI doing the repetitive part

Agents that take on the work nobody wants to do twice, with a person approving anything that matters.

Things I have built

Talking to a data platform

Enterprise product

I led the work that let customers describe the data setup they wanted in plain English and have the software build it.

The call I made. I led the design and set its limits, so anything it is not allowed to do gets a clear no instead of a confident wrong answer. Engineers built it.

Months to days
for a customer to get up and running
Hours to seconds
to build a working data pipeline
MCPAgent skillsETLData modelling

How I work

Write it down until it is unambiguous

I get the agent to interrogate me about a problem until nothing is left vague. Vague requests are where most of it goes wrong.

Several agents on one problem

Claude Code, Cursor and Codex run together on the hard jobs. Designing how they hand work between them is its own skill.

I read everything they write

I do not hand-write production code. I specify it, direct the agents, then test the result against the job it has to do.

Nothing marks its own homework

Whatever matters gets checked by a different AI than the one that wrote it, and plain facts get checked by code.

If your business runs on work someone does by hand, I would like to see it.

Work with me at Quartate

or write to me, farhan1188@gmail.com