For agencies with a queue of
small client changes.
Most client work after launch is small. Refinar gives each client a team of their own: they ask for changes in a live preview, and your developer approves them.
One team per client
Every client gets a team of its own
A Refinar account can own many teams, each with its own apps, members and billing, and you switch between them from the team menu. Give every client their own team and nothing crosses over: their apps, requests and credits stay theirs.Invite by email and pick a role
Member lets them ask for changes, viewer lets them look, and billing lets them pay for the team's plan themselves.Clients ask, you keep the final say
Changes need approval first
On each client's app, an owner or admin can switch publishing to Changes need approval first. The client then sends changes for review, and one of your developers, admins or owners approves them before anything goes live. A change made after the approval needs approving again.Rules for the AI
Rules for the AI narrow what the agent may do on that app, in plain words, for example "update text and images only, never pages, layout or sign-in". Anything outside them comes back to your team as a request instead of a change.Who does what
- Ask for a change in the live preview
Your client: Yes, as a member
Your team: Yes
- Put it live
Your client: Sends it for review when approval is required
Your team: Approves and publishes
- Changes the agent stops on (sign-in, payments, deleting data)
Your client: Handed over as a request
Your team: Picked up from the review list
- Rules for the AI and who can publish
Your client: No
Your team: Owners and admins
- Paying for the plan
Your client: Can, with the billing role
Your team: Or your agency pays
| Your client | Your team | |
|---|---|---|
| Ask for a change in the live preview | Yes, as a member | Yes |
| Put it live | Sends it for review when approval is required | Approves and publishes |
| Changes the agent stops on (sign-in, payments, deleting data) | Handed over as a request | Picked up from the review list |
| Rules for the AI and who can publish | No | Owners and admins |
| Paying for the plan | Can, with the billing role | Or your agency pays |
Setting up a client
01
Create a team for them
Choose Create team from the team menu. Each new team comes with trial credits to try it on.
02
Connect their repository
Install Refinar's GitHub App on the client's repository. If it sits in the client's GitHub organisation, one of its owners may need to approve the install (connecting GitHub).
03
Set the rules
On the app's Setup tab, write the Rules for the AI and choose who can publish.
04
Invite the client
Send the invite by email with the member role. They don't need a GitHub account.
05
Pick a plan for the team
Plans are per team, from $50 a month for about 100 requests. Your agency can pay, or the client can, with the billing role.
Questions agencies ask
How many clients can one account run?
Up to 50 client teams per account.
Can clients see each other's work?
No. Teams are separate, and a client only sees the teams they've been invited to.
What if a client's site isn't on GitHub?
Then Refinar can't work on it. It needs the code in a GitHub repository, so sites built in Webflow, WordPress or Framer aren't a fit.
How much can run at once?
Each team can run three chats at the same time, so a client's requests don't queue behind another client's.
Product details are from Refinar's app and documentation, checked on 7 October 2026.