Taking on a few consulting projects

I build AI assistants and fix data problems for small businesses.

I'm Abhishek Banerjee, a data and AI architect in Toronto. For nine years I've built data systems and, more recently, AI agents — including one that serves 150+ people at the company where I work. I take on a small number of outside projects each quarter: fixed scope, fixed price, and everything runs in your own accounts.

9+years in data engineering and architecture
150+users on an AI agent I designed and shipped
6+years working with Google Cloud
8professional certifications, including GCP Data Engineer
Services

Four things I'm good at.

Each one is a defined piece of work with a price we agree on before I start. No hourly meter, no open-ended discovery.

Most asked for · about 3 weeks

An AI assistant that knows your business

If your team answers the same questions every day from a wiki, a helpdesk, or old support tickets, I'll build an assistant that reads those sources and drafts the answers. It says where each answer came from, and it hands off to a person when it isn't sure.

  • Connects to your docs, wiki, or ticket history
  • Every answer cites its source
  • A human reviews anything uncertain before it goes out
  • Runs in your own cloud account, not mine
  • You get the code, the docs, and a walkthrough
Fixed quote after a 30-minute call
Quick win · about 2 weeks

A second pair of eyes on your cloud bill

Most small teams on Google Cloud or AWS pay for things they don't use: machines left running, database tiers far bigger than the workload, storage nobody opens. I go through the bill line by line against actual usage and give you a list of fixes, ordered by how much each one saves. I do the easy ones while I'm in there.

  • Full review of billing and real usage
  • Fixes ranked by money saved, with effort noted
  • Quick wins implemented during the audit
  • Spend alerts so the bill doesn't creep back up
Fixed fee, quoted up front
Foundations · 4 to 8 weeks

Pipelines and reporting you can trust

If your numbers live in spreadsheets and nobody quite believes the dashboard, I'll rebuild the shaky parts: automated pipelines into a proper warehouse, tables modeled so each metric means one thing, and checks that catch bad data before anyone sees it.

  • Pipelines built or rebuilt properly (Airflow, dbt, Dataflow)
  • Warehouse modeling on BigQuery, Snowflake, or Postgres
  • Dashboards for the numbers you actually look at
  • Data quality checks and plain-English documentation
Fixed-price project, demoed every week
Ongoing · monthly

A senior data person, a few hours a week

For teams that need experienced judgment but can't hire for it. I review architectures, help you choose between vendors, and sit in on interviews for data hires. Mostly async, with a call when something needs talking through.

  • Architecture and design reviews
  • Build-versus-buy calls, with the trade-offs spelled out
  • Help hiring and interviewing data engineers
  • A regular look at where AI could actually help you
Monthly retainer, a few hours a week
Work

Things I've built.

Client work stays private, so here are two things I can talk about. Happy to go deeper on a call.

An AI agent used by 150+ people

At my day job I designed the retrieval architecture behind a production AI agent: it answers questions from internal documents, shows its sources, and routes the hard ones to people. It's been running in production with monitoring and regular evals — the unglamorous parts that decide whether these systems survive contact with real users.

Vertex AILangGraphMCPGoogle Cloud

Open-source agent skills

I publish reusable skills for building AI agents — including one for deploying retrieval-based agents on Google Cloud — so other teams don't have to start from zero. They're free and MIT-licensed.

Open sourceMIT licensed

github.com/baner29/agent_skills

About

Who you're hiring.

I'm Abhishek Banerjee. By day I'm Sr. Manager of Data Platforms and Architecture at Randstad Enterprise in Toronto. I've spent nine years in data engineering across consulting and industry, and the last few years building AI agents that run in production — not demos.

I work mostly in Python on Google Cloud and AWS, with a lot of hours in Vertex AI, LangChain and LangGraph, and MCP-based agent setups. I'm certified as a Google Cloud Professional Data Engineer and a Google AI Professional, among others.

I write about AI engineering on Medium and publish open-source tooling on GitHub. I take on a few consulting projects at a time and do the work myself — you won't be handed to a junior team.

AB

Abhishek Banerjee

Data and AI architect · Toronto
  • Day job: Sr. Manager, Data Platforms & Architecture, Randstad Enterprise
  • Stack: Python, GCP, AWS, Vertex AI, LangGraph, MCP
  • Certified: GCP Professional Data Engineer, Google AI Professional
  • Writing: AI engineering on Medium
  • Code: open-source agent skills on GitHub
Process

How a project goes.

1.

We talk

Thirty minutes, free. You describe the problem; I tell you honestly whether I'm the right person. If I'm not, I'll say so and point you elsewhere.

2.

You get a proposal

A short written document: what I'll build, how long it takes, what it costs. One fixed price. You approve it before anything starts.

3.

I build, you watch

You see a working demo every week, against your real data. If something's off, we catch it early, not at the end.

4.

You own everything

It goes live in your accounts, with documentation and a walkthrough. I stay available for a support window after handover.

FAQ

Questions people ask.

Why fixed price instead of hourly?
Because hourly billing rewards slow work. With a fixed price, my incentive is to finish well and finish on time — same as yours.
Who is this actually for?
Small and mid-sized businesses, roughly 10 to 500 people, with a concrete problem: a support team drowning in repeat questions, reporting nobody trusts, a cloud bill that keeps growing, or an AI idea with nobody to build it. If you just want someone to "do AI," I'm probably not your person.
Where are you, and how do we work together?
Toronto, working remotely. Most of the work is async; you'll need about an hour or two a week for demos and decisions.
What about our data? Do you sign NDAs?
Yes, happy to sign one before we discuss anything sensitive. Everything is built in your cloud accounts and your repositories. You own the code, the data, and the IP from day one.
When could we start?
I keep the number of active projects small, so it depends on what's on my plate. The scoping call is free — ask and I'll give you a straight answer on timing.

Tell me what you're trying to fix.

A few lines about the problem is enough. If it looks like a fit, we'll set up a call. If it doesn't, I'll tell you that too.