Paper sculpture of a profile with lines flowing into several green spheres, representing AI agents

    How do I hand off my AI agents so someone else can run them?

    Short answer

    Package them with a one-page Start Here document, a master index, one folder marked CURRENT per system, and a dated, versioned final package. I handed three working agents to another operator this way. An AI system becomes a business asset the day someone else can run it without calling you.

    Yesterday I zipped up seven months of AI work, wrote a one-page document called Start Here, and handed the whole system to another operator.

    The kit held three working agents: one answers customer email, one runs social, one supports training. Until yesterday, every one of them lived in my chat history, my folders, and my head.

    The zip took five minutes. Making it runnable by someone else took the whole day.

    When does an AI system become a business asset?

    An AI system only you can run is a personal productivity trick. It becomes a business asset the day someone else can run it without calling you.

    That sentence decided how I spent the day. The agents already worked. What they lacked was a way in for anyone who wasn't me. The packaging has no glamour, and it is the part that creates the value.

    What went in the handoff kit?

    • A one-page Start Here doc: what exists, what order to read it in, who owns what.
    • A master index that names every file and its job in one line.
    • Exactly one folder marked CURRENT for each system, so nobody guesses which version is live.
    • A folder labeled for review and deletion, holding every superseded draft. I moved them there instead of deleting them, because ambiguity kills handoffs and marking removes it.
    • A date and version on the final package, staged in a repo so every future change stays traceable.

    The Start Here page carries the most weight. A new operator opening an unfamiliar set of folders needs the reading order before anything else. Without it, they open whatever file looks newest and start guessing.

    The CURRENT folder does similar work. Any system built over months collects drafts, forks, and abandoned versions. One label removes the question of which one is live, and the review folder keeps the old material close by without letting it compete.

    Why does this matter for founders right now?

    Founders are building agents faster than they are documenting them. I keep seeing the same pattern in companies of every size: real AI capability that exists only in one person's account. Capability like that behaves like folklore. It disappears with a departure, a vacation, or a forgotten password.

    The stakes rise if you ever plan to sell, raise, or hire an operator. A buyer values what transfers. A system that performs only in a demo you have to run yourself carries little weight in that room. The Start Here page, the index, and the CURRENT folder are what let someone outside your head confirm the system exists and keep it running.

    Do this today

    1. Pick the one AI workflow your business would miss most.
    2. Write its Start Here page: what it does, where it lives, how to run it, which version is current.
    3. Give yourself ten minutes.
    4. If you finish inside ten minutes, you have an asset. If you cannot, you just found the system that lives only in your head. Package that one first.

    Meredith's rule

    An AI system becomes a business asset the day someone else can run it.

    Questions

    What should an AI agent handoff document include?

    Start with a one-page Start Here doc covering what exists, the reading order, and who owns what. Add a master index naming every file and its job, one folder marked CURRENT per system, and a dated, versioned final package stored in a repo.

    Why does documenting AI workflows matter if I plan to sell my company?

    A buyer values what transfers. AI capability that lives only in one person's account disappears with a departure, a vacation, or a forgotten password. Documented, versioned systems that someone else can run are the ones that count as assets.

    Should I delete old versions of AI prompts and workflows?

    Move superseded drafts into a folder clearly labeled for review and deletion, then mark one folder CURRENT for each system. That removes the guesswork about which version is live without destroying anything you may need to check later.

    Related service

    Agentic System Install

    Paper sculpture of an ivory profile on a dark background facing a green sphere and brass arc

    Want this worked out for your business?

    Bring the real problem to a working session and leave with a plan.

    Book a session

    More Field Notes