Overview
A private site where clients follow project progress and submit change requests in one place, instead of email and phone. Clients sign in with a passwordless link and can always see the progress timeline, how many revisions remain under the limit agreed for the build or maintenance phase, and the status of each request. Requests are sorted into changes, bug reports and questions; anything beyond the contracted limit is accepted only after recorded consent to the fee. On the admin side, an inbox handles acceptance, rejection and how many revisions a request consumes, with per-project limits and pricing, and notification emails go out automatically. Data is separated per company at the database layer, ready to be offered to other studios.
Design decisions
Counted only when accepted
A revision is consumed when Ebla accepts the request, not when the client posts it, and bug reports and questions are never counted. Clients post without hesitation, and the judgement stays with the studio.
Consent log as the basis for billing
Requests beyond the limit are never blocked. Consent is recorded together with the exact fee text shown before the request is accepted, so there is no dispute later.
Isolation in the database, not the UI
Every table carries the company identifier, and separation is enforced at the database layer rather than in the screens. Built from the start to be offered to other studios.
- Client
- In-house system
- Launched
- 2026
- Category
- System
- Scope
- RequirementsData designUI/UX designSystem developmentAuth & notificationsOperations design
- Stack
- Next.jsSupabaseResendVercel
Let's talk first.
Consultation and estimates are free. A “wouldn't it be nice if…” is all you need to bring.
contact@ebla.jp