AI for web agencies that ships to your clients' repositories

One project per client, with its apps and its repositories: developer agents pick up tickets, open a merge request with a preview build, and every task shows its cost. You review, you show the preview to the client, you merge.

Create my space Book a demo

GitHub, GitLab, Vercel and Upsun
A preview for every change
The cost of every task in euros

Aurore StudioSearch or ask ERHA

Maison Delorme redesign

BoardBacklogVersions

To do2

Pricing page with three plansLanding

Multi-step quote formWebsite

In progress2

Responsive headerWebsite

Booking endpointAPI

In review2

Site chat on the landing pagePreview

Checkout flow reviewWebsite

What slows a web agency down

An agency sells strategy and design, yet much of its week goes into short requests spread across dozens of projects.

Small tickets

Fixes, tweaks, one more page: the stream of client requests keeps developers busy on low-stakes work.

Sites under maintenance

Dozens of sites to look after, each with its own stack, host and history.

Margin you cannot see

It is hard to know what a request actually cost, so it is hard to bill it back properly.

What agents do on your clients' projects

The agents in the ERHA catalogue are developers: web front ends, APIs, mobile, landing pages, code review. They work in each app's repository, following your rules.

Development tickets

Nora, Julien or Marc take a ticket, code in an isolated session, then open a merge request or push to the branch.

Client previews

Every change gets its own preview build. You send the link to the client before merging.

Code review

Hugo reviews the changes and flags what needs rework before your team looks at it.

Site chat and audience

An agent adds the site chat or cookieless audience tracking to the app's code, through a task you review.

Docs, blog and Storybook

Agents write documentation and blog posts in the repository. Storybook is shared through a console link.

Cost per task

Every task shows its cost in euros. You know what each client request consumed.

How your agency gets started

You keep your tools: your repositories, your hosting, your own way of reviewing and shipping.

01One project per clientYou create a project for each client and add its apps: landing page, website, API, mobile app, library.
02You connect the repositoriesEach app points to its GitHub or GitLab repository, its branch and its Vercel or Upsun hosting.
03You start tasksA ticket on the board, the Start button, and the right agents split the work. The task moves to review once everything is done.

An example: a client request on a Friday

An eight-person studio maintains around thirty sites. A client asks for a new section on the home page and a contact form.

The project manager creates the task in the client's project and clicks Start.
Nora builds the section and Julien wires the form, each in an isolated session.
Hugo reviews the changes and a merge request opens with its preview build.
The client approves the preview, a studio developer reviews the merge request and merges it.

Outcome

The developer's job becomes a review, and the cost of the request is shown on the task, ready to bill back.

The ERHA building blocks involved

Projects and appsOne project per client, with its apps, repositories and hosting in one place, plus the tools agents install.AgentsThe developer agents from the catalogue, with your agency's rules: conventions, tone of messages, budget.SkillsYour repetitive non-code work, such as client meeting notes, built by the ERHA team and run on demand.

Frequently asked questions

Do agents push straight to production?

Delivery is set per app: a merge request to review, or a push to a branch. With a merge request, nothing reaches production until your team merges it.

Is our clients' code safe?

Agents code in an isolated environment, separate for each job. No platform secret goes in, and your agency's space is isolated from every other ERHA space.

Do we have to move our repositories or hosting?

No. ERHA connects to GitHub or GitLab and to Vercel or Upsun. For a client with nothing set up, ERHA can also host the repository and the site.

How do we bill the agents' work back to clients?

Every task shows its cost in euros, based on actual usage. You also set spending caps for your agency's space.

How is this different from ChatGPT or a coding assistant?

An assistant answers in a chat window. Here, the agent takes a task from the board, works in the right project's repository, opens a merge request with a preview and reports back on the task. If it needs a decision, it asks, and the task is marked as blocked.

Keep reading

SolutionsWebsite developmentLanding pages and websites built and updated by your agents, approved by you.SolutionsWebsite maintenanceBug fixes, updates and small improvements handled by your agents.SolutionsAI website chatA chat on your site that answers from your documents and hands over to your team.TeamsTech and ITDevelopment, maintenance and documentation handed to agents on your repositories.

Hand over your first piece of work this week

Open your space in a few minutes, or book a demo to scope a first use case with the ERHA team.

Create my space Book a demo