Bhaskar DubeyAI Architect

Department of One

I build the coworkers you don't have to hire.

AI automation · Workflow automation · Web development · Dashboards · Private AI

01 — The usual way

Most companies solve a problem by posting a job.

It works. It's just slow, expensive, and the thing you needed doing is still not being done while you do it.

  1. 01Write the job specTwo weeks of arguing about seniority.
  2. 02Post itA flood of applications, and a week of sorting them.
  3. 03InterviewEveryone's calendar, for a month.
  4. 04OfferThey accept, or they don't and you start again.
  5. 05Notice periodYou wait.
  6. 06OnboardMonth six, if it works out. The work waits.

And in a year, when the next gap opens, you do all of it again.

02 — The other way

So I stopped posting jobs and started building colleagues.

At an international services business, seven roles came up that a growing company would normally advertise for. Instead of adding headcount, I built the systems — and the team stopped covering those jobs off the side of their desks.

Here's the building that came out of it.

03 — The roster

Seven roles. Nobody hired.

Each was a real gap with a real cost. Each is now a system that runs whether or not anyone remembers to run it — which leaves the people for the work that needs people.

H.01 · Filled

Head of Lead Generation

Full-time · Remote · Started 2026

Reads every alert before the team's first coffee.

A lead engine that reads every news alert and job feed each morning, scores every prospect on how ready it actually looks to buy, and hands the team one ranked list with the evidence attached.

Replaced — An hour every morning of someone hired to sell, spent scanning alerts and listings by hand instead.

Manual monitoring is gone. The team opens one screen and starts with the warmest name on it.

  • Next.js
  • OpenAI
  • Feed ingestion
  • Intent scoring

an international services business

H.02 · Filled

Sales Engineer

Client-facing · No login required

Available at 2am. Does not negotiate.

A calculator that models a prospect's own numbers live — their gaps in, the cost of doing nothing out. One link, no sign-up, works on a phone in a meeting.

Replaced — A cost conversation that ran on assertion, and a spreadsheet nobody could safely send outside the building.

Sales conversations start from the prospect's own figures instead of a rate card.

  • Next.js
  • Live modelling
  • Zero backend

an international services business

H.03 · Filled

Knowledge Manager

Full-time · Institutional memory

When someone leaves, what they knew stays.

A knowledge base with a submit → review → approve pipeline, so every procedure has an owner and exactly one current version. Search-first, and new entries get summarised and categorised on the way in.

Replaced — Process knowledge living in chat threads and long-tenured memory, with three versions of the same answer in circulation.

One trusted source of operating truth. Procedures get found instead of re-asked.

  • Next.js
  • Upstash Redis
  • OpenAI
  • Review workflow

an international services business

H.04 · Filled

BI Analyst

Full-time · Reports on time, always

The numbers are ready before anyone asks for them.

A dashboard wired straight into the system of record, tracking the live pipeline across every stage with AI-written summaries on top.

Replaced — A weekly deck assembled by hand, out of date by the time it was presented.

The weekly numbers assemble themselves. The meeting argues about the pipeline instead of about the spreadsheet.

  • React
  • TypeScript
  • Live API
  • Gemini

an international services business

H.05 · Filled

Content Team

Full-time · Multi-channel

Headcount of one, output of several.

A publishing dashboard that plans, drafts with AI assistance and tracks the pipeline across channels, plus a renderer that turns brand templates into finished graphics headlessly.

Replaced — Sporadic posting, unmeasured, and a design bottleneck for every single asset.

One operator runs the entire cadence, and the pipeline is never empty.

  • Next.js
  • OpenAI
  • Apify
  • Headless Chrome

an international services business

H.06 · Filled

Video Producer

Per-project · Turnaround measured in minutes

No lighting setup, no reshoots, no 'can we get it by Friday'.

A programmatic video pipeline: raw phone footage in, English-dubbed vertical reels out, with the edit driven by a beat file rather than a timeline someone drags by hand.

Replaced — Outsourced editing, or nothing at all — which is what usually happened.

Footage becomes a publishable reel the same day it's shot, and the edit is reproducible.

  • Remotion
  • React
  • AI dubbing
  • FFmpeg

an international services business

H.07 · Filled

Web Team

Full-time · Ships on release branches

Rebuilt from the ground up, then swapped in without a freeze.

The company's public site, rebuilt as a modern application and cut over from WordPress in place — plus the release process that lets it ship safely without a staging freeze.

Replaced — A WordPress install that everyone was slightly afraid of, and a change process that meant nothing shipped.

The site is fast, owned in version control, and changes go live the day they're ready.

  • Next.js
  • TypeScript
  • Supabase
  • Release branches

an international services business

04 — The wiring

Then they started talking to each other.

A system on its own is a tool. Systems that hand work to each other — a lead becoming a call becoming a record becoming a number in a report, without anyone retyping any of it — are something closer to staff.

This is the part nobody puts in the job spec, and the part that actually compounds.

05 — The private office

Some coworkers shouldn't phone home.

Not every workload belongs in someone else's data centre. Customer records, salary data, anything under a contract that says it stays put — those can run on a model on your own hardware, in your own building, answering only to you.

It's less convenient. Occasionally it's the only option that's legal.

06 — After hours

Nobody asked for these.

Which is rather the point. Client work shows what I'll build when someone's paying. These show what I'll build when nobody is.

L.01 · Real-time physics

Event Horizon

Someone asked what I could do with three.js. This is the answer.

A rotating black hole, raytraced live in the browser. Every pixel integrates a light ray through curved spacetime, so the lopsided shadow, the photon ring and the frame dragging aren't drawn — they fall out of the physics. Stop moving the camera and the image keeps refining until it's clean.

  • Null geodesics integrated per pixel with RK4, in Boyer–Lindquist coordinates
  • Shadow radius validated against the closed-form solution to within 0.18%
  • Relativistic jet whose power scales with spin squared, after Blandford–Znajek
  • three.js vendored, no node_modules, builds to a single self-contained file
  • three.js
  • GLSL
  • GPGPU
  • Numerical relativity

L.02 · Personal life OS

Atlas

I wanted the dashboard I keep building for other people, for myself.

Tasks, calendar, notes, expenses, net worth, investments and goals in one place, running on my own machine against my own database. The AI layer uses a key I paste in myself, calls typed read-only functions, and never sees a raw transaction or does arithmetic of its own.

  • Local-first: SQLite via Drizzle, authored to stay portable to Postgres
  • Multi-tenant from the first migration, not retrofitted later
  • Bring-your-own-key AI — anyone cloning the repo can run the whole thing
  • Full check suite runs with no API key and no network access
  • Next.js
  • SQLite
  • Drizzle
  • TypeScript

L.03 · Consumer product

Kredity

Comparison sites tell you which card to get. Nothing tells you which one to use.

A mobile web app that answers one question: of the credit cards you already hold, which should you pay with right now? Pick a category, get an answer. No login, no bank connection, nothing leaves the phone.

  • Installable PWA — chosen over native so it works from a link
  • Rules engine and card database run entirely client-side
  • No account, no backend, no transaction data collected
  • Next.js
  • PWA
  • OpenAI
  • Rules engine

07 — The architect

There is, in fact, a person here.

Bhaskar Dubey, AI Architect
Fig. 07Scale 1:1

I'm Bhaskar. I work inside an operating business rather than beside one, which means I've had to live with everything I've built — every shortcut, every clever idea that turned out to need maintenance at 11pm. That's made me a considerably more conservative engineer than I was.

I build things that keep working when I'm not looking at them.

How I work

  1. 01 Find the gapOne conversation about the role you keep meaning to fill.
  2. 02 Watch the workHow it's really done today, not how the process doc says.
  3. 03 Build it liveSmall, in your stack, in production early.
  4. 04 Hand it overDocumented, yours to keep, and your team trained to run it.

08 — Your role

You've seen my building. Here's the empty floor in yours.

Pick the role you keep meaning to fill. It opens a note with your problem already at the top — finish the sentence, and I'll reply myself within a working day with whether I can help and how.

Which coworker are you missing?

The building runs itself. The replies don’t — those come from me.