What a One-Person AI Org Looks Like at 90 Days

A one-person AI org is a structured team of AI agents, skills, workflows, hooks and memory that a single person can operate. The purpose of this article is to share how powerful Claude Code is beyond what's previously been primarily an engineering conversation, and what 90 days of effort spent after hours can translate into. I will be sharing exactly what that looks like, what value that's created for me personally and professionally, and where I see the next 90 days taking me. For those that have not taken the plunge into this space, my aim is to inspire and show what can be done beyond a generic ChatGPT interaction.

How to Get Started

What I'm about to share might come across as seemingly out of reach, but looking back, I believe anyone can take this journey too.

Like any journey it starts with taking that first step. Unlike linear journeys, this one is defined by 'the exponential', meaning the steps you take might've been fixed stride lengths in the past but now with AI those steps become leaps and bounds, and even then there are some 'steps' I've reflected on and can only describe as superhuman.

That first step, get Claude Code. Yes there are other options out there, for example ChatGPT codex, but this article is not about comparing frontier models. You can't go too wrong investing the next 90 days in Claude Code and much of your learnings will be transferable.

If you're starting from scratch Anthropic Academy have a range of free courses to get you going.

What a one-person AI org contains

Here is what mine looks like at 90 days, laid out across the dimensions of capability stack, infrastructure, projects, output, volume, velocity. This shape is not prescriptive, yours will be different based on your objectives, and it's something that changes daily.

Value created, the "so what?"

The inventory above is what a one-person AI org looks like at 90 days, but ultimately, so what?

Compounding knowledge. The AI org gets better at my specific work the longer I run it. Nothing resets between sessions. Last week's rejected phrasings, the briefs that landed, the shortcuts I take when I am tired, the AI org has all of it on file. Each session starts further forward than the one before.

Always-on operating environment. The platform runs when I do not. The market intel digest is already in my inbox by the time I have made coffee on Monday, with the overnight reports underneath it and the resources scout's proposed new entries underneath that.

The foundations to scale AI agent teams. Adding agents takes a fraction of the time of what adding the first one did. Voice rules, brief templates, the memory layer, the verification pass, the lint, the deploy gates, all there on day one for new agents to inherit. The focus now moves on how to do more work, more quickly and with higher quality and autonomy.

The ability to automate and parallelise work. Inside a single session I might have a research agent working one part of a brief while a peer-reviewer scrutinises another. Scheduled jobs pull the reports I used to forget to run. Briefs draft themselves while I am doing something else. Work that used to wait for me does not wait anymore.

The learnings and perspectives gained along the journey. The hands on execution has taken my knowledge to another level. The journey has also radically changed how I think about creating and delivering value and the future ways of working, spoiler alert, it does not involve adding AI to what we currently do, but letting AI re-imagine how we can more effectively do it.

Examples of work (screenshots)

The following 7 projects represent a small selection of work completed over the 90 days. Each is working capability I regularly use.

AI Org memory. An engram index is the routing layer for every memory the platform carries between sessions. Each entry is a one-line pointer into an extracted learning, a feedback rule, a reference fact, or a project state. This is what compounding knowledge across interactions looks like at an organisational scale.

Orchestration workflow. An agent dynamically designs each workflow, assigns the relevant agent, and renders the workflow in a human readable format. Each stage shows its owner and each verification gate shows the condition that has to be true before the work moves on. The diagram is what the human sees when reviewing and verifying, and what a new agent inherits when it joins.

Next best action modeller. A customer-base dashboard organised around the DIKW pyramid: data, information, knowledge, wisdom, with cross-cutting graph and query layers. One scaffold carries churn propensity, retention scoring, incentive targeting and next-best-offer. Non-analysts can ask the dataset in natural language and get back tangible AI powered insights to execute.

Local media creation tool. A custom media platform for image and video generation, built on top of a local ComfyUI stack running open source models such as Flux. The interface lets you pick a render mode, set aspect ratio and stylization, and generate against a styles + recipes library, all running offline on my MacBook. Additional capability includes style creation, asset management and ad format generation.

Prompt tool. A multi-vendor evaluation workbench for authoring a prompt, defining criteria and test cases, then running it across Anthropic, Google and OpenAI models. Per-row scores surface strengths, weaknesses and reasoning, and an auto-iterate loop hands the lowest-scoring rows to a "prompt doctor" that proposes a revised prompt and re-evaluates.

Home automation. The Home dashboard replaces a decommissioned Home Assistant VM with a Vite + TypeScript + SQLite stack purpose-built around the actual telemetry I care about. Battery state, solar generation, weather and switched plugs feed into one view. Claude Code powers wholesale energy buying and selling decisions through Amber.

Trading agents. Autonomous agents execute a strategy on paper accounts, with the Trade Journal dashboard rendering setups, executions and outcomes against the rules they were given. Real-world autonomous execution in a domain where being wrong has a price. The journal is where verification happens after the fact.

Key learnings

The build itself has been the education. Five things stand out as the lessons I would carry forward.

Starting with one agent. The temptation when you see what a platform like this can hold is to design the full org chart upfront and then populate it, or download a bundle from GitHub. I went the other way. The first agent that handled one workstream end-to-end taught me more than ten scaffolded definitions would have. Every working agent since has shaped the org chart more truthfully than any pre-packaged bundle could.

The org chart can run ahead of the work. Most agents were scaffolded but unrouted, meaning they existed as definitions but had not been wired into any workflow. I built faster than I integrated, unwired agents are still valuable, they could just be even more valuable. The fix is unglamorous, wire every new AI agent into a workflow before scaffolding the next one. Workflows also help in delivering more consistent outputs.

The bottleneck flips from generation to verification. AI generates faster than any human can check. Once that happens, the rate-limiter on the platform is no longer "can the AI write this?" but "can I trust what it wrote?". Aside from human review, agent peer-review, lint, deploy preflights and the verification pass are not optional polish. They are the architecture that keeps quality alive at the speed of generation. Skip them and the output becomes a quality crisis.

Memory value only compounds if you build it deliberately. The AI org learns not because it's saving conversations or creating handoff files, but through human-like memory consolidation. The session-capture hook, the consolidation pipeline, the engram index, the per-agent memory files, none of these are defaults. Memory systems are gaining increasing attention. The real question however is whether the system is learning or just recalling.

Workflows provide a safeguard. A deploy curl-check used source filenames instead of frontmatter permalinks, and a dry-run rsync flagged three live articles for deletion before the mismatch was spotted. A LinkedIn scraping job triggered an overnight account restriction and was retired the same day. Neither was an AI failure. Both were workflow gaps. Wire the rules in before you scale the volume.

The next 90 days

Looking back I could never have imagined where I would've ended up and I feel that's going to be the case for the next 90 days too!

I'd like to think this was a discovery phase and next starting to define and develop a direction to take, but with the constant advance of AI it's clear there will always be the need for exploration and discovery.

This is where I feel my attention will be:

Self-evolving agents. Each agent to this point has been carefully crafted. The next step is to extend the capability of my Chief of Staff and their team to not only monitor agent performance, but proactively and automatically evaluate, model and modify agents.

Agent team performance. Current work orchestration includes a human verification component. The next step is to explore increasing autonomy within the team, agents taking on increasing responsibility for other agents, and ways of working and team topologies to optimise performance.

Autonomous learning. Building on the AI org's memory system, and more than a scheduled heartbeat, what does always-on autonomous learning look like, what rate of compounding can be achieved, and what value can be derived and measured from the process.

The exponential. Using AI we often default to how this can help with our existing workflow or process. Agent teams can plan and execute their own workflow, which is a significant paradigm shift. I'm keen to explore what that next paradigm beyond this is.