Brief and decisions
Scope, open questions and decisions stay with the project.
Projects Flow Further
Keep every project’s work and handoffs in one place.
Baton holds the brief, build, review and delivery record together, so the next person can continue without chasing context.
A project, at a glance
Build in progress
Website launch
DefineBuildHandoff
Delivery checklist
3 of 4 completeScope agreed
Repository connected
Preview ready
·Client review
Next: share the preview with your client.
What Baton keeps together
One shared record for the work.
Review in context
A focused review space keeps feedback close to the preview.
Handoff with history
Repository context, QA and delivery notes are ready for the next owner.
Inside one project
Start with the brief. End with a useful handoff.
Each phase leaves the next person with the information they need.
- 01
Set the scope
Record the brief, requirements and open questions.
- 02
Connect the work
Link the repository and give the right people access.
- 03
Review together
Share the preview and resolve feedback in context.
- 04
Leave a clear handoff
Keep QA and delivery notes ready for what comes next.
Different roles. Shared direction.
Built around the people
behind the project.
For independent builders & technical teams
Keep building. Keep everyone in the loop.
Turn a brief into scoped work. Keep the repository, open questions and QA beside the project so the next step is easy to find.
- Keep scope and decisions together
- Connect a repository you already own
- Hand over the project with its history
Build in progress
Website launch
DefineBuildHandoff
Delivery checklist
3 of 4 completeScope agreed
Repository connected
Preview ready
·Client review
Next: share the preview with your client.
Your tools, connected to the project
Bring the tools.
Leave the copy-paste.
Choose GitHub repositories from your connected account. Keep provider connections and deployment references beside the work they support.
GitHubConvexVercelCloudflare
Available operations vary by provider and the permissions you grant.
RepositoryProvider accounts
BatonYour projectScope · access · evidence
Your teamAI via MCP
For AI-assisted delivery
Your assistant can pick up the thread.
Connect a compatible MCP client to work with project context and supported repository operations. Project roles and provider grants define what it can do.
Connect an AI assistant
Review and handoff
Make the final pass easy to follow.
Share a client preview, gather feedback, work through QA and leave the delivery notes with the project.
See a project walkthroughA few useful answers
Before you
pick up the baton.
Who is Baton for?
Independent developers, agencies and technical teams delivering projects with clients. Clients use a focused review experience, while builders keep the delivery work in their workspace.
Does Baton replace GitHub or my hosting provider?
Your repository and hosting stay where they are. Baton connects provider accounts to projects and brings supported operations and project context together. Available actions depend on the provider and the permissions you grant.
Can my AI assistant use Baton?
Yes. Compatible MCP clients can discover Baton’s project tools. An authorized assistant can work with project records and supported repository or provider operations. Each call remains limited by the connected identity, project role and provider permissions.
How are connected accounts handled?
Each user can add personal provider connections through a private form. Credentials are encrypted server-side and are not returned in normal project or MCP responses. Shared workspace connections require workspace administration.
Can I look around before setting up a project?
Yes. Choose “Explore read-only walkthrough” on the sign-in page to open sample projects. The walkthrough is read-only and does not connect your repository or spend on AI.
Baton