Explainer video agency styles are the named visual and motion directions a studio shows a client so they can pick one before production starts. Instead of describing “clean and modern” in a call, you put 74 styles in front of them as a picker, price each tier, and schedule the finished cuts across every client account from one place.
CLIENT PITCH FLOW
atlas (74 styles)
|
v
picker page --> client picks 3
|
v
tier + add-ons --> quote
|
v
script / storyboard / render
|
v
schedule per client workspace
POST /v1/posts (API key per workspace)
|
v
analytics back into next pitch
What explainer video agency styles actually mean for pitching
An explainer video agency style is a reusable production recipe, not a mood word, and naming them is what lets a client say yes in one meeting.
Most studios pitch three options they invented that morning. The client compares three vague descriptions, asks for “something like Apple but warmer”, and the revision cycle starts before the first frame. A style atlas flips that. Each style is a name plus a fixed set of decisions: how the shapes move, how fast the cuts land, whether text is on screen or spoken, whether the palette is flat or graded. When those decisions are already made, the client is choosing between finished directions instead of inventing one.
Practically, that means your pitch deck stops selling “our process” and starts selling a menu. You still show one hero frame per style, but the client’s job becomes narrow and fast: pick three you like, rank them, and tell us the audience. That single change removes most of the back and forth that eats studio margin.
If you want the source material for this, read the Motion Style Atlas breakdown first. It defines the styles. This post is about turning that list into revenue.
How the Motion Style Atlas becomes a client-facing picker
Turn the atlas into a one-page picker with a thumbnail grid, a short label, and three checkboxes per style, then send it as a link inside the proposal.
A picker that works has four parts:
- A numbered grid. 74 styles is too many to scroll cold. Group them into six or eight families (flat vector, kinetic type, whiteboard, 3D isometric, collage, character led, data driven, hybrid) and number within each family. Style 14 is easier to say on a call than “the one with the geometric people”.
- One still per style. A single hero frame, same 16:9 crop for all. Motion is sold later; the picker sells the look.
- Three slots. Let them pick three, ranked. Two is a coin flip and five is a committee.
- A one-line constraint field. “Must include the founder on camera” or “no stock footage” changes which styles are viable, so ask before the quote, not after.
Keep the picker static HTML or a simple form. It does not need a login. The deliverable is the ranked shortlist plus a screenshot of their picks, and both go into the proposal as evidence you ran a structured selection.
| Picker element | What it does | What to avoid |
|---|---|---|
| Numbered families | Makes 74 options navigable | One long ungrouped wall |
| One still per style | Comparable at a glance | Reels for every style |
| Three ranked picks | Forces a decision | “Send us anything you like” |
| Constraint field | Kills dead-end styles early | Discovering limits in edit |
How to price 74 styles without guessing: tiers, add-ons and revision logic
Price the style tiers, not the style count, so 74 options become three prices and a short add-on list.
Sort the atlas into three production tiers by what it costs you to make, not by how impressive it looks:
- Tier 1, base motion. Flat shapes, simple type animation, one music bed. Lowest render and revision cost.
- Tier 2, layered motion. Character or object rigs, transitions between scenes, custom illustrations.
- Tier 3, heavy motion. 3D, simulation, frame by frame, or voice synced animated boards. Highest cost, longest approval chain.
Then add-ons priced separately: extra scene, script rewrite, voiceover direction, sound design, aspect ratio versions (vertical and square cutdowns are their own line), and rush delivery. Put revisions in the contract as a count with a per-round price after that count, and state which tier each style sits in on the picker itself. The client sees the upgrade cost at the moment they choose, which is the only moment it feels like their idea.
If you want a worked reference for mixing voice and motion in one cut, the voice synced animated boards walkthrough shows the pipeline from audio to finished frames.
Can you run multi-client scheduling through the Creator OS REST API?
Yes. Creator OS issues a scoped API key per client workspace, so one agent or script can publish each client’s videos to that client’s own accounts without cross posting.
A Creator OS API key is pinned to one workspace, which is one set of socials. On Agency plans each client gets their own workspace and their own key. An agent holding client A’s key cannot post to client B. That is the whole security model, and it is what makes multi-client delivery safe to automate.
For an explainer studio the flow looks like this. Render the cut, upload it once, then create the post per workspace:
POST /v1/media (file) -> med_ id
POST /v1/posts
{
"content": "How our scheduling works, in 40 seconds.",
"platforms": ["youtube", "linkedin", "instagram"],
"media": ["med_..."],
"schedule_at": "2026-03-04T14:00:00Z",
"timezone": "America/Toronto"
}Creator OS applies each platform’s own rules from that one call: vertical video becomes a YouTube Short, Instagram gets its Reel treatment, LinkedIn takes the landscape cut. Upload the file once and reuse the same med_ id on every platform. If a client has not connected a network yet, it comes back in missing_platforms and the rest still publish.
With the CLI the same job is one line per asset: creatoros posts:create --text "..." --platforms youtube,linkedin --media med_... --scheduledAt 2026-03-04T14:00:00Z --timezone America/Toronto. Loop it over your client list, one key per workspace.
Read the auth model at the authentication docs and the request shape at the posts API reference. Use the docs for the base URL.
Motion atlas vs motion maxxing: which repo talk clients understand
Lead with the atlas when selling to clients, and save the maxxing and repo material for the build conversation with your own team.
They answer different questions. The atlas answers “what will my video look like and what does it cost”. Motion maxxing answers “how do we produce this faster with an agent”. A marketing director signing a purchase order cares about the first. A technical founder who wants to see the pipeline cares about the second.
So keep two decks. The client deck has the numbered picker, three tiers, and delivery dates. The internal or technical deck shows the tooling: the motion maxing repo walkthrough and the GitHub motion maxxing notes. If a client asks how you turn a raw talking head clip into an animated short, point them at the open source skills in OPEN VIDEO EDIT, which render locally with Python and ffmpeg. That is a credibility move, not a sales move.
What to show in a 10-minute pitch deck with the style picker
Ten minutes holds five slides if you let the picker do the talking, and the picker should be slide three.
- Minute 0 to 1, the outcome. One line: what the video has to make happen. Then the audience. No agency history.
- Minute 1 to 2, the shape. Runtime, where it lives, and the deadline, agreed out loud.
- Minute 2 to 6, the picker. Share the link, walk two families, ask for their three ranked picks live. Let them drive.
- Minute 6 to 8, tier and price. Show the tier their picks land in and the add-ons they will likely want. One number, stated plainly.
- Minute 8 to 10, the schedule. Storyboard date, first cut date, publish date, and who approves each. Say that delivery goes out through Creator OS across their channels from one workspace, and that you will show them the post performance afterwards.
End the call with the picker link resent and a date attached. The next step is a signed scope, not another meeting.
How agencies answer the same five client objections every time
Five objections come up in almost every motion pitch, and each has a short factual answer you can put on a slide.
| Objection | Answer |
|---|---|
| “74 is too many.” | You are not choosing 74. You are choosing three from eight families, ranked. We narrow it with your constraint line. |
| “Why is Tier 3 so much more?” | It is a different production. More scenes, more approval, longer render. The picker shows the tier before you commit. |
| “What if we hate the style after the first cut?” | The style is fixed at pick. Revisions are for execution inside that style, and the contract states how many rounds. |
| “Who posts it?” | We do. Each client gets their own workspace and API key, and the cut publishes to their channels on a schedule. |
| “How do we know it worked?” | Per post analytics and daily account metrics come back through Creator OS, and we review them before the next batch. |
Keep these on one page. An objection answered in fifteen seconds does not become a discount request.
FAQ
How many explainer video styles should an agency pitch to a client?
Show the full library as a grouped picker and ask for three ranked picks. A shortlist of three is fast for the client and gives you enough signal to price. Pitching only three from the start hides your range.
What does an explainer video style picker look like in a client proposal?
It is a single page or link inside the proposal: numbered styles grouped by family, one still per style, three selectable slots, and a short constraint field. The ranked picks get pasted back into the proposal as the agreed direction before production starts.
How do I price motion explainer styles per client?
Group styles into three production tiers by cost to make, then add line items for extra scenes, script work, voiceover, sound, cutdowns and rush. Put the revision count and the per round price after that count in the contract.
Can the Creator OS REST API schedule videos for multiple clients?
Yes. Each client workspace has its own scoped API key, and an agent holding one workspace’s key cannot publish to another. You upload media once, get a med_ id, and create the post per workspace with a schedule time and timezone.
What is the difference between the motion style atlas and motion maxxing?
The atlas is a catalogue of visual directions you can sell to clients. Motion maxxing is production technique, using agents and open source tools to build the cuts faster. One is a sales asset, the other is a workflow.
Get started with Creator OS for your agency
Creator OS gives you one place to publish, schedule, reply and read analytics across 11 platforms plus Skool, with a REST API, a CLI and a hosted MCP server so an agent can run each client’s accounts. Agency 5 covers 5 client workspaces for $49.99/month, and every plan includes API keys, the MCP server and the CLI. Creator plans start at $14.99/month for 11 platforms plus Skool.
Start at https://www.creatoros.ca/sign-up, read the docs for the API and MCP setup, and if you want to see the build approach in practice, watch the walkthroughs on the KevBuildsApps YouTube channel and the launch video.
Get started for $0
Free trial for new subscribers. Cancel anytime.