AgentSee

Hove & London Founded 18 August 2026 Issue No. 1 · Free, obviously

The agents see the work.
Humans make the decisions.

A software agency being built from the ground up — organisationally, not just technically — for a world where engineering stopped being the bottleneck. We know what changed. We don't yet know everything it changes.

Early days / Building out the workflows / Hosting a weekly podcast / Taking the first conversations

Before you build Think of something you want built. Whichever assistant you already use asks twenty questions, guesses what it should be, and writes you a one-page brief. Then it asks the question the pitch never does: who runs this once it exists? Start the twenty questions →

01 — The premise

Every software agency that has ever existed was organised around one scarce thing: engineering time.

The account manager protected it. The delivery manager sequenced it. The business analyst translated into it. The estimate priced it. The change request defended it.

The org chart, the rate card and the statement of work are all scaffolding built around a single constraint — and everything an agency sells is shaped by the cost of the thing it was protecting.

We don't think that makes agencies obsolete. We think it makes most of their structure obsolete, and we would rather find out what replaces it by building one than by writing another post about it.

The constraint moved.

So this is the whole thing, from the ground up: what the roles are, what you buy, what it costs, who is accountable, and what it is actually like to be a person doing this work every day.

We are at the very earliest stage of that. This document is the first thing we have published, and it exists to be argued with rather than agreed with.

02 — What we actually don't know

These are not rhetorical. We don't have the answers, and we are suspicious of anyone currently selling them.

  1. If writing the code is no longer the expensive part, what is the client actually buying?
  2. What replaces the estimate? If you can see the working software before you commit, do you pay to go to production rather than paying for the sprint?
  3. What is a product manager when the specification is executable?
  4. Who is accountable for a system that nobody typed?
  5. How do you run acceptance testing on something produced faster than a person can read it?
  6. Where does the next generation of senior engineers come from, if the junior tier that grew them no longer exists?
  7. What does taste mean when volume is free?
  8. Do engineers still want the job? What is it now — author, reviewer, director, or something we don't yet have a word for?
  9. A year out used to mean catching up; now the whole transition can happen inside it. What does coming back from parental leave or a career break look like, and who is making it possible?
  10. What is the honest rate card, and would you publish yours?

03 — How we're going about it

We keep asking in public. We have started taking the first clients, and the price comes before the pitch.

In public, on the record

The podcast, and streams when we get to them, with people who run agencies, buy from agencies and work inside them — including the ones who think this premise is nonsense. The discovery is the content. It isn't marketing for a thing that already exists.

Built alongside you, then run

Built with you rather than delivered to you — in the room while it's made, not on the far side of a statement of work. Then run by us rather than handed over, on a monthly retainer: the people who built a thing are the ones who can keep it alive. That suits clients who want the thing working in a year, not just finished, and who are clear-eyed that we are early.

Discovery, and the first few clients

The discovery isn't a formality we're hurrying through to get to the selling; the podcast and the register carry on. But the door is open: a small number of clients, one at a time, and we'll publish what we charge and how we arrived at it before anyone hears a pitch. Our own tooling gets run on us first; if it doesn't hold up there, we've no business charging for it.

Radical honesty is an easy thing to put on a landing page, so here is ours: we have an unproven model, no client list and no product. We have two engineers, a domain name and a strong suspicion.

04 — The podcast

Each episode is something we actually did: what it cost, what broke, and which of the questions above it touched.

Two developers building a software agency in public, with agents doing the work, and seeing what changes. The working record rather than the highlights: standing up our own infrastructure with agents, producing the show itself by script, and, as they come, the work for clients.

Every episode has a page here with the player, the chapters, the notes and a transcript, and its video is on YouTube. It is in the directories, and in any podcast app by its feed. Guests who think the premise is nonsense are welcome; see the classifieds.

05 — The register

Everything we publish gets a number and a date, so it can be held against us later.

06 — Contributors

James isn't theorising about agentic engineering. He spent six months doing it on three production codebases at his last job, and wrote the AI agent guidelines the rest of the team now works to. Since then, everything on this site, from the mail server to the podcast and the engine that publishes it, has been built the same way, and the register above says what each piece cost.

Fifteen years in the parts of the industry where shipping badly is expensive and immediate — nearly six years leading development on a cloud live-broadcast platform, iOS for HM Revenue & Customs, and a news app read by five million people.

The side projects are the argument rather than a hobby. A C++ WebTransport real-time audio server, written across two Sundays, so his guitar quartet could rehearse from different rooms. A 52,000-line Go platform with 146 end-to-end tests that runs the fixtures for a Brighton parks tennis league. Both solo, both in real use, both alongside a full-time job.

First-class BEng in Electronic & Electrical Engineering from Leeds, top of his year, holding the only award the department gives to undergraduates — voted by staff rather than calculated from marks.

Abrar has already put AI into work that people depend on, and checked it holds up. GradeDrive, the exam-marking platform he co-founded with a physics teacher, marked more than 750 GCSE and A-Level papers for a single school in one month: 12,000 pages across eleven teachers.

Before that, seven years at an agency building commerce systems for top-tier luxury retail clients: point of sale, payments, inventory, and the ERP and OMS integrations underneath. He led distributed teams, rebuilt the platform around modular patterns, and cut environment onboarding by eighty per cent.

ArticleFM is the side project that proves the point. It's an iPhone app he took from nothing to the App Store, turning written articles into narrated audio for the train, the car and the gym.

It started at ten years old, with a first line of C, and he has been in love with building software ever since. He has now been doing it professionally for almost a decade.

07 — Classifieds

Everything below reaches both of us directly. No sequence, no drip, no CRM.