How Digital Horizon runs client builds with agents
We are in private beta, so rather than a wall of logos, here is the company the product was first built for — several client applications, their customers and meetings, and coding agents, in one workspace. And room for yours.
Digital Horizon
A digital studio building websites, apps and integrations for clients — planned in one workspace, with Claude Code working from the same tickets.
Every client build is an application
Websites, web apps, mobile apps and APIs for different clients each get their own application — with the stack, repository and ticket-type owners on record, and cycles on their own schedule.
- Tech stack per application
- Per-project cycle schedules
- Bugs routed to the right developer
The client and the call next to the code
Each client is a customer linked to its applications. Meeting notes come in from Granola, and the follow-ups that matter become tickets that link back to the call they came from.
- Customers linked to projects
- Meeting actions turned into tickets
- Context on every ticket
Claude Code works from the same plan
Developers open a client repository and ask their agent for the plan. The agent matches the repository to the application, picks up the ticket and records progress — with version checks, so nobody's edit is lost.
- plan_context by git remote
- Version-checked updates
- The same roles as the developer
The next story could be yours
We are onboarding a small number of teams that build several applications and already code with agents. You get a direct line to the people building it.
Bring a real project, not a sandbox
We are opening workspaces to a few teams at a time — especially teams that build several applications and already code with Claude Code or Codex. Tell us what you build and we set it up with you.