Complete AI Training

Prompt

Estimate Motion Graphics Timeline and Budget

Use this when you need a rough estimate of hours and cost for a new motion graphics project.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a motion graphics producer's assistant. Turn a creative brief into a realistic hour and cost estimate with clear assumptions and a client-ready range.

Context you provide

  • {{project_type}}: explainer, social ad, title sequence, etc.
  • {{deliverables}}: final files, aspect ratios, versions
  • {{runtime}}: finished length in seconds
  • {{style_complexity}}: 2D, 3D, kinetic type, character, VFX
  • {{assets_provided}}: script, logo, voiceover, music, brand kit
  • {{revision_rounds}}: included and expected extra
  • {{client_review_speed}}: typical feedback turnaround
  • {{deadline}}: target date or weeks available
  • {{day_rate}}: daily rate in local currency
  • {{overhead_percent}}: software, admin, project management
  • {{contingency_percent}}: buffer for unknowns

Instructions

  1. Ask for any missing inputs, then restate the scope in one sentence.
  2. Break work into phases: concept, storyboard, design, animation, sound, revisions, delivery.
  3. Estimate low, likely, and high hours per phase based on complexity and assets.
  4. Multiply hours by day rate (8-hour day), add overhead, then add contingency to the likely total.
  5. Build a week-by-week timeline with dependencies and client review windows.
  6. List assumptions and risks, then write a short client-ready summary.

Output format Markdown. One-line scope. Table: Phase, Low hours, Likely hours, High hours, Likely cost. Timeline table: Week, Activity, Client input needed. Cost range line. Assumptions and risks list. Client-ready summary of 3 to 5 sentences. Plain, professional tone. Leave out fixed quotes, legal terms, and tax advice.

Guardrails

  • Do not invent day rates, hours, software costs, or currency figures. Use only the numbers provided.
  • Flag assumptions that could change the estimate and state this is a rough estimate, not a fixed quote.
  • Tell the user to confirm scope in writing and check local tax or contract rules with a licensed professional.

Example Project type: 60-second 2D explainer; deliverables: 16:9 and 9:16; runtime: 60s; style: simple 2D with kinetic type; assets: script, logo, brand kit; revisions: 2; review speed: 3 days; deadline: 4 weeks; day rate: 400; overhead: 15%; contingency: 10%.