For AI product content studios
AI product content, briefed by SKU and approved by the client.
Clients say which scenes, how many variants, and what must not appear. You approve the request, share the work, and they decide variant by variant.
Lenso keeps the brief, the review, and the files. It does not generate the content.
Where AI content projects get stuck
- Clients do not say which scenes, how many variants, or what must not appear.
- Approvals get lost in chat, so nobody can tell which variant was accepted.
- The next round starts from scratch because the last brief is not with the files.
How an AI content project runs
- The client picks AI content on your Start a project page.
- They fill the AI brief: scenes, variants per product, source photos, and brand rules.
- You approve the request and share the work in the same project.
- They sign off on each variant and download the files.
What the AI product content brief asks
These are the fields on the built-in AI product content brief.
- Brand name
- Needed by
- Where will it run?
- Content types
- Scenes and mood
- Variants per product
- Aspect ratios
- Product images to start from
- Brand rules (colors, logo use, must avoid)
- People, faces, or likenesses that must not appear
- Products and scenes, with SKU, product, scene, variants, and notes
- File format
- Output resolution
- Do you need AI-generated content labeled?
- What should we deliver?
- Reference links
How clients give feedback
- Clients approve a variant or request changes on that variant.
- Per-item invoicing lets them select the files they want and pay per item.
What Lenso does not do for AI content
- Lenso does not generate images or video. Your tools do.
- Lenso does not decide which variant the client accepted. That decision stays on the file.