How to Write a Custom 3D Gift Design Brief

A useful custom gift brief describes both the visual idea and the place where it will run. “Make a premium animation” leaves many decisions open. “A short birthday celebration above an audio-room speaker tile, using our colours and remaining readable on a small phone” gives the conversation a concrete starting point.

You can send a custom gift enquiry to VoltKit without placing an order. Use the prepared sales form and fill in the requirements you already know. Unknowns are fine when they are identified clearly.

Explain the moment and the audience

Start with the app, the audience and the event that triggers the gift. Describe where the artwork appears, how much space it has and what must remain visible. Include whether the moment should feel playful, celebratory, formal or tied to a regional event.

Give the team a few references you have permission to share. Explain the part you like in each reference, such as colour, timing or silhouette. Do not assume that a reference gives permission to copy a character, logo or another creator's artwork.

Name the deliverable

Specify a still image or animation, the required format, intended dimensions and approximate duration. If your app already uses a player, include its name and the target platforms. Add any file-size or decoded-memory budget established by your engineers.

Say explicitly if you need editable source files, multiple language variants, transparent output or a runtime 3D model. These requirements affect scope and should not be inferred from the phrase “3D gift”. See the format comparison if you are deciding between SVGA, animated WebP and still artwork.

Make review and timing practical

List the number of gifts and any variants. Identify who can approve the visual concept and who can approve playback in the app. Give a desired date and explain whether it is a fixed event or a preference. Agree review milestones before production, including what counts as approval and how revisions are handled.

For an animation, a useful acceptance example describes the opening state, main action, end state and loop behaviour. Include a still or text fallback if your application supports reduced motion.

Discuss licensing before proceeding

Record whether the intended use is inside one app, across products or for a wider campaign. Mention any request for exclusivity or source-file ownership. Custom terms need separate agreement; do not assume the catalogue licence answers every commissioning question.

The custom gift page links to a sales ticket with a brief template. Sending it opens a discussion so availability, feasibility, scope and terms can be confirmed before work starts.

Before starting a custom project, compare the ready-made gift gallery. An existing asset may already suit your experience, and its gift ID can help describe the visual direction you like.