An AI chief of staff for a biotech founder
Most founders at this size cannot justify hiring one, and are doing the job themselves badly. Here is which parts of it software can take, and which parts it cannot take at all.
A chief of staff exists because a founder becomes the integration layer between everyone else's heads, and that is a poor use of the one person who has to make the decisions. At a twenty-five person biotech the founder is simultaneously the business development lead, the program sponsor, the person the board asks about the filing date, and the only one who has spoken to all three of the contract organizations this quarter. Nothing is written down in one place because the person who holds it is too busy holding it.
The role has a recognizable shape. Hold the whole picture so the founder does not have to. Chase what was promised, in both directions. Make sure the founder walks into every room already prepared. Keep the number in the board deck and the number in the internal tracker from drifting apart. Notice the thing that is quietly slipping before it becomes the thing that blew up.
Which parts of the job transfer
| What a chief of staff does | Can an agent take it? |
|---|---|
| Keep the record of every project current | Yes, from the mail and meetings already happening |
| Track what you owe and what you are owed | Yes, including promises made verbally on a call |
| Prepare you for the room you are walking into | Yes, assembled overnight from your own threads |
| Keep the board number and the internal number the same | Yes, by making them the same file with two views |
| Draft the reply, the update, the summary | Yes, and it stops there until you approve it |
| Read the room and tell you an uncomfortable truth | No |
| Manage people, or carry authority on your behalf | No |
| Decide what matters this quarter | No |
The top half of that table is roughly the whole administrative load and roughly none of the judgment. That split is why the analogy holds and also why it is limited: what you get is the part of a chief of staff that is a records-and-chasing function, run on a scheduled pass rather than by you, and none of the part that is a second brain in a hard conversation.
The biotech version of the daily load
The generic version of this pitch is about meetings and follow-ups. The biotech version is specific and it is worse, because most of a founder's operating surface is external. The tox study sits at a contract research organization with its own schedule. The analytical work sits at a second vendor. Manufacturing is a booked slot at a third. A partner has a joint committee that meets quarterly and makes decisions out loud. Each of those parties tells you when something changes by emailing one person, at an unpredictable hour, in a thread with eleven other things in it.
So the founder's real job between board meetings is to hold five external timelines in their head and notice when one of them moves the filing date. That is exactly the work that decays first when the week gets hard, and it is the work an agent that reads your mail and writes the record does well: the date moves in the record when the email moves it, the downstream items shift, and the commitment you made to an investor that depended on it gets flagged as at risk rather than discovered later.
The other half is relationship memory. Which partner went quiet and how long ago. What was actually said in the last diligence call rather than what you remember. Which comp you quoted from memory that you should check before repeating. That is the load treated function by function in AI for business development in biotech, and as a tooling decision in build or buy deal tracking software.
What it will not do. It does not send anything on its own. It does not assign work to your team, because it is installed for one person and has one mail identity. It does not do discovery science, it is not a lab notebook, and it does not go anywhere near patient data. If your problem is analysis rather than threads and promises, this is the wrong purchase and it is better to know that now.
Why this category is appearing now
The idea is not proprietary and it is worth saying so. In July 2026, AI Fund, Andrew Ng's venture studio, posted a residency to build an AI chief of staff, described as taking the post-meeting work managers dislike: extracting action items, sorting them to the right project, and chasing the follow-ups. Its own stated validation question was whether the automatic sorting, rather than flat capture, is what makes a single manager use it daily before any team adopts it. That is category evidence that the problem is real and that other serious people are working on it. It is not a customer story and nothing here should be read as one.
What differs between approaches is where the record lives and who can read it. The version described across this site keeps everything as plain files on the founder's own machine, so the record survives the tool. The platform-specific setup, including what running it on Claude actually involves, is Claude as an AI chief of staff, set up in a biotech. The daily-use view from the chief executive's own seat rather than the role analogy is an AI agent for biotech CEOs.
If you want the underlying definition first, it is what an AI company brain is, and the knowledge-management framing of the same machinery is AI knowledge management for a drug development team.
The records-and-chasing half, run by software
This is a built app holding five external timelines at once: a vendor moves a date in an email, the filing date and every promise resting on it move with it, and the chasing in both directions comes back drafted for your approval. Go and see that half running; the judgment half stays yours.
See the demo