AgentSee
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 / No clients / No case studies / Nothing to sell you yet
01 — The premise
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
03 — How we're going about it
Streams and a podcast 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 with you rather than delivered to you — in the room while it's made, not on the far side of a statement of work. That means partners bought into the approach and clear-eyed that it's a risk, with a share of the reward that reflects having taken it.
The discovery isn't a formality we're hurrying through to get to the selling. When we're clearer, we'll start with a small number of partners — and we'll publish what we charge and how we arrived at it. 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 no proven model, no client list and no product. We have two engineers, a domain name and a strong suspicion.
04 — The register
05 — Contributors
Lead Software Engineer, agentic engineering · Hove
James isn't theorising about agentic engineering. He's been doing it in production and counting: 874 commits across three production codebases in six months, around a quarter of his team's total output, and he wrote the AI agent guidelines the rest of the team now works to.
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.
Lead Software Architect · Co-founder & CTO, GradeDrive
Abrar has spent nine years working on the seams where software actually fails: ownership, architecture and the client conversation. Seven of them architecting a global retail commerce platform — point of sale, payments, transaction flows, inventory, and ERP and OMS integrations. The systems where being wrong costs money in public, instantly.
He led distributed teams and walked clients through high-stakes technical decisions, which is precisely the role this whole thesis puts under the most pressure. He rebuilt that platform around modular patterns that cut running costs and raised deployment velocity, and got environment onboarding down by eighty per cent.
He is currently co-founder and CTO of GradeDrive, an AI marking platform he took from zero into real classrooms in UK secondary schools. So he has already had to answer "what is this worth, and who is accountable when it's wrong" for money, not in theory.
He cares about clean system design, clear ownership, and creating leverage through good engineering — the three things an agency built this way will either get right or die of.
06 — Classifieds