Handing the project to the client's team
Agencies and freelancersAgency finishing a build
At handover, the client's developers got a README and a call. Months of decisions stayed with the agency.
How do I hand a project's decision history to the client's developers and their AI agents?
Give the client's developers access to the project in ArcRoom, where its decisions and rules already live. Their agents then get them from day one. A clean export or transfer of a project between accounts isn't a feature yet.
Also asked as: At handover, months of project decisions stay with the agency. How do we pass them on? · How do I onboard a client's team so their AI agents know the project history? · Can a client's AI agents see the decisions we made while building their app?
The project's decisions and rules are in its room.
- Decision
[client dev, day 1] Code map + 23 decisions loaded for this project.
Step by step
- The project's decisions and rules are in its room.
- The client's developers are given access to the project.
- Their agents get the history from day one.
What the agent sees
[client dev, day 1] Code map + 23 decisions loaded for this project.Compared with today's tools
README + decision records (ADRs) in the repo
The agency writes a short record for each decision and a detailed README during the build, and the client's agents read them from the repo.
- Setup
- a few hours to start
- Ongoing
- write a record per decision, ~15 min each
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min, plus giving the client access
- Ongoing
- None
Records in the repo transfer cleanly, which ArcRoom can't do yet without an export; ArcRoom's edge is putting the right decisions in the prompt without anyone writing them up.
Where it stops
A clean export or transfer of a project between accounts isn't a feature yet.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.