23 jobs run by AI agents, 5 by me, 1 by nobody: the org chart of a one-person studio

A solo founder running 14 ventures has published a live org chart mapping every function a small company needs to an owner: 23 run by AI agents or scripts, 5 reserved as human gates, and 1 deliberately unstaffed. The founder reports that the first pass left several functions with no owner at all, and argues that a duty only counts if it appears in an agent's own written instructions rather than on a chart.

I run 14 ventures with no employees. That claim is cheap. What is less cheap is writing down every job a company needs and putting a name next to each one. So I did. The table below is generated from the system map of my studio every time the site builds. It lists the functions a small company needs, and who runs each one today. There are three possible answers: an AI agent with a written contract, me, or nobody. The count as served today: 23 automated · 5 human gates · 0 not covered · 1 not pursued. | Area | Function | Run by | |---|---|---| | Strategy | Opportunity research and prioritisation | Opportunity Strategist agent | | Strategy | Brand and marketing strategy | Brand & Marketing Strategist agent | | Strategy | Market and competitor research | Research Organ agent | | Strategy | App teardowns | App Teardown Daily agent | | Strategy | Pricing | Opportunity Strategist agent | | Build | Product build | Product Builder agent | | Build | Design and brand identity | Art Director agent | | Build | Release and deploy | Distribution Engineer script | | Growth | SEO | Head of SEO agent | | Growth | Growth execution and distribution | Growth Operator agent | | Growth | Inbound and conversion | Convertor agent | | Growth | Outbound drafting | Convertor agent | | Growth | Customer support | Convertor agent | | Growth | Contacts and relationship graph | Network Graph script | | Measure | Analytics and user behaviour | Behavior Intelligence Engineer agent | | Measure | Monitoring service runs | Monitor Night Shift agent | | Operate | Portfolio state and nightly self-heal | Nightly Reconcile agent | | Operate | The founder's daily brief | Morning Action Card agent | | Operate | Organisational learning | OS Organization Developer agent | | Operate | Systems maintenance | OS Plumber agent | | Operate | Backups | OS Backup script | | Operate | Finance and bookkeeping | Kirjuri Builder agent | | Operate | Legal preparation counsel decides | Research Organ agent | | Human gate | External sends | Me | | Human gate | Money go-live | Me | | Human gate | Secrets and access | Me | | Human gate | Signing and accepting terms | Me | | Human gate | Key personal relationships | Me | | Not pursued | Fundraising and investor relations | Nobody, by choice | The live version is at jukkablomberg.com/ai https://jukkablomberg.com/ai?utm source=devto&utm medium=post&utm campaign=jb-org-chart-devto . 1. "0 not covered" is the number that matters, and it was not always zero. The useful exercise is not counting agents. It is listing the functions first, from the point of view of a company, and only then asking who does each. When I first did that, several rows had no owner. One agent was producing an output nobody read. Another job had been "assigned" in a note that the responsible agent never saw. A function with no named owner does not fail loudly. It just stops happening. 2. One agent can hold several jobs, and that is fine as long as it is written down. The Convertor answers inbound, drafts outbound and handles customer support, because all three are the same skill: reply to a real person within a day with something finished. The Opportunity Strategist also owns pricing. Collapsing jobs onto fewer agents is cheaper than one agent per box. The rule that keeps it honest: a duty is only real if it is in that agent's own instructions. Putting it in an org chart does not count. 3. The human rows are not "the things AI is bad at". They are the things where a mistake is expensive or hard to undo: money going live, credentials, anything that contacts a third party in my name, signing terms, and the relationships that matter most to me. Agents do the preparation; the decision stays a human click. Where an exception exists some routine email replies, for example , its edges are written down: who, which address, how many a day. The gates are narrow on purpose. A system that has to ask about everything gets ignored, and one that asks about nothing will eventually spend your money. These are the counts the same site serves, each with its source and an "as of" date: None of these mean the work is good. They mean the work is counted, and that a reader can check the counting. The full method, including where each number comes from, is on the Portfolio OS page https://jukkablomberg.com/operating-system?utm source=devto&utm medium=post&utm campaign=jb-org-chart-devto . You do not need agents to get value from this. Take a blank sheet and do it in this order: Step 4 is where most of my gaps were. I'm Jukka Blomberg, ex-CMO at two crypto exchanges and before that at Nokia and Microsoft. I now help leadership teams decide what to do with AI, and then build it. The org chart above is generated from my own system map; the numbers are as served on 28 October 2026.