Use case
Clip production for agencies
Render client clips from your own system and price the job before you quote it. No seats, and no plan to carry between retainers.
Margin lives in the gap between quote and cost
An agency bills a client for a clip and pays a supplier for it. The business is whatever survives in between, which means two numbers matter more than any feature: what you can promise before the work, and what you actually pay after it.
Clipwright answers both before you commit. A quote endpoint returns the cost of a request, and the run uses that same figure. You can put a real number in a proposal instead of a guess with padding on top.
Volume that does not arrive evenly
Agency work is lumpy. A campaign lands, forty clips are needed in a week, then nothing for a fortnight while the client reviews.
A monthly allowance punishes that shape, because the quiet fortnight was paid for anyway. Credits in a pack do not care. They sit there between campaigns at 30 credits per second whenever you do render.
When a render breaks on a deadline
Billing starts when the vendor accepts the paid render of your clip, and not before. A run that breaks earlier costs nothing, and a run that breaks because of us costs nothing either, even when we have already paid the vendor.
For an agency this is the difference between a retry and a conversation with a client about why a failed render is on their invoice.
Your client never meets us
The file comes back clean, at 1080 by 1920 by default. No badge, no mark of any kind, nothing announcing a supplier. What you wrap around it is your product.
Clips are kept for 30 days and then deleted, so anything a client may want later belongs in your own storage rather than ours.
What you will have to arrange yourself
Publishing. Clipwright renders and returns the file, and does not post to any account, ever. If your service promise includes posting on a client's behalf, that part stays in your stack.
Approvals, revisions, and the client conversation. There is no review editor here, because that is your relationship and not ours.
Start
You cannot price a retainer on a supplier you have not measured. Run one campaign's worth of clips, then put your real cost next to what you charge for them.
Checked on 2026-09-15.
Questions
- Can I put this behind my own interface?
- Yes. Clipwright returns a file. What you build around it, and what your client sees, is entirely yours. There is no badge burned into the clip and nothing that announces where it came from.
- How do I quote a client before I commit?
- Use the quote endpoint. It returns the cost of the request you are about to make, and it is the same figure the run will use, so the number you put in a proposal is the number you pay.
- What if a client cancels mid-campaign?
- Credits sit in a pack and do not expire, so unused budget carries to the next client rather than evaporating at the end of a billing month.
- What happens when a render fails?
- You are charged only once the vendor has accepted the paid render of your clip. A failure before that point costs nothing, and so does a failure caused on our side, even when we have already paid the vendor.
- Do you keep client footage?
- Clips are kept for 30 days after the run finishes and then deleted. If a client needs the file retained longer, store it on your side.
Render a clip and compare the files yourself.