Two weeks before the launch, someone asks for the social cut. The 90 second film is finished, approved and beautiful, so the editor trims it to fifteen seconds. The result opens on a logo, the voice-over is gone so the first line of the story is missing, and the product appears at second nine. In a feed, second nine does not exist.

This is the standard order of operations and it is backwards. The launch film gets watched by people who already decided to care: press, investors, your own team, visitors who came to the site on purpose. The teaser is what everyone else gets. It runs in a place you do not control, next to content that is not yours, with the sound off and a thumb already moving.

So the teaser is not a shorter version of the film. It is a different asset with different rules, and it deserves to be designed rather than salvaged.

The teaser has one job: buy three more seconds

Every other format assumes a decision has already been made. A landing page video plays because someone arrived. An explainer plays because someone pressed play. A teaser plays because an algorithm put it in front of a stranger who was looking for something else.

That single difference sets everything. The first frame cannot be abstract, because abstraction reads as an ad. The claim cannot be spoken, because nothing is spoken. The pacing cannot build, because there is nothing to build on. What the teaser has to do in its first second is answer the only question the viewer is actually asking: is this worth three more seconds.

A quick test before you approve a cut. Mute it, play the first two seconds, stop. If you cannot say what the product is, neither can anyone else, and the remaining thirteen seconds will never be watched.

App launches spread the same asset across four or five surfaces, each with its own crop, its own length ceiling and its own audience posture. One build should cover all of them, but only if the ratios were planned before anything was animated.

The row people forget is the app store preview. It is governed by the platform, it gets reviewed, and it is one of the few places where a viewer is already deciding whether to install. A teaser recut for that slot converts better than anything else you will make, and almost nobody briefs it.

What actually goes in the fifteen seconds

Fifteen seconds is roughly four beats. Not four scenes, four beats: things the viewer registers. Spending one of them on a logo animation costs you a quarter of the asset before anything has been said.

Notice what is not on the list: a tagline before the product, a founder speaking, a countdown, a date card that will be wrong in a week. Each of those is a beat spent on something the viewer did not ask for.

The cheapest change you can make to a launch is the order. Build the visual system first: type, motion behavior, color, how the interface is framed, how numbers and states appear on screen. Then cut the teaser from that system, before the long film exists. If the fifteen second version does not hold, the ninety second version was never going to, and you have found that out while it is still cheap to fix.

Working in that order also means the launch film, the store preview and the paid variants are recuts of one build rather than three productions with three different looks. That is the same sequencing behind the four decisions in our post on the [product launch video](/blog/product-launch-video), and it is how our [Launch Sprint](/#service-cards) runs: narrative and visual micro system in the first two days, teaser next, everything else after.

There is also the case where the launch is on Thursday and there is no system to build from. We should be transparent here, because the tool is ours: [ShipTeaser](https://shipteaser.com) was built by the same founder as this studio. It takes a product URL and returns a 15 second 1080p motion graphics teaser made for muted feeds, with an optional music bed and the first one free without a card. What it does not do is give you a narrative spine or a visual system the rest of the launch can inherit, and there is no voice-over, no screen recording and no timeline to edit. For a feed cut you needed yesterday, that trade is usually worth taking. For the launch you have been building toward for a year, it is not the whole job.

The five failures that kill a launch teaser

These come up on almost every project that arrives with an existing cut. None of them are craft problems. They are all decisions made before anyone opened a project file.

The fix for all five is the same and it is not a bigger budget. It is deciding the surfaces before the storyboard, so the frame is designed for the crop it will live in.

The brief that gets you a usable first cut

Before you talk to a studio, a freelancer or your own designer, write these five lines. They take twenty minutes and they settle the arguments that would otherwise happen during revisions, when changes cost real money.

A team that gets that page back delivers something close on the first pass. A team that gets a deck and a launch date delivers a beautiful film in a format nobody can use, two weeks before you need it, and the recut comes out of your budget rather than theirs. If you want to see how this plays out across a full engagement rather than one asset, our [brand video for tech startups](/blog/brand-video-for-tech-startups) post covers the same ground at the level of the whole brand.

We design the teaser as its own asset, built from the same visual system as your launch film, sized for every surface it has to run on.

The teaser is the only asset most people will ever see of your launch, and it is usually cut last, from a film built for a page where the sound was on.

A launch teaser runs 15 seconds, muted, in a feed you do not control. What the format has to show, what to cut, and how to brief it properly.

Teaser Video for App Launch: The 15 Second Cut

Teaser video for app launch: fifteen seconds, sound off

Most crypto community content is an announcement with a background image behind it. A partnership goes live, someone writes three lines, drops a banner made in a hurry, pins it, and the channel goes quiet again. The team calls it content because it was posted.

The problem is not effort. A community manager posting five times a day is working harder than anyone else in the company. The problem is that almost none of it is repostable: text a holder cannot forward, images cropped wrong for the app the holder actually uses, updates written for people who already read every message in the channel.

Community content earns the name when members carry it outward without being asked. That is a production question before it is a marketing one. So this piece covers the formats that travel, the weekly rhythm that survives a quarter, and the kit that stops each post from costing a fresh brief.

Why most community content stops at the announcements channel

A post that stays inside your own server has done nothing your pinned message was not already doing. The reach you want comes from the second hop: a member quoting it, a group forwarding it, a creator building on top of it. Almost all community content fails at that second hop, and usually for the same four reasons.

None of that is fixed by posting more often. It is fixed by changing what gets produced, which means deciding on a small set of formats and building them properly once.

The five formats a community actually reposts

Across crypto projects the same handful of formats do the travelling. They are not exotic, and that is the point: a member has to understand the shape of the thing in half a second to decide it is worth forwarding.

Notice how little of this is announcements. Announcements are necessary and they are not content: they inform people who are already inside. The five formats above are built so that the person receiving them was not in the room.

A weekly rhythm you can hold for a quarter

Volume in crypto is not optional. A quiet week reads as a dead project, and the market has a very short memory. The trick is designing a week that a small team can actually deliver every week, rather than a heroic one that collapses in three.

That is three to five assets a week, which is exactly the load our Growth package is built around, alongside a 48 hour response on hot moments. The cadence is only sustainable because none of it starts from a blank canvas.

If a weekly asset takes a new brief, it will not be weekly by week four. The rhythm is a production decision, not a discipline problem.

Build from a kit, not from a blank canvas

The kit is what separates a project that posts consistently from one that posts when someone has time. It is a small set of locked components that a community manager can fill in without making a single design decision, and without asking anyone for approval on the look.

This is the same system a proper identity gives you, applied to the weekly grind rather than the launch. If none of it exists yet, the kit is the first thing to buy, and our note on [Web3 branding](/blog/web3-branding) covers what that system has to contain before it can carry a weekly cadence.

One gap the kit does not cover: a moment lands today, there is no capture, no components, and nothing worth escalating into a real build. We would rather name something of ours than a competitor for that case. [ShipTeaser](https://shipteaser.com) is a product from the same founder as this studio: you paste a product URL, it returns a 15 second 1080p motion graphics teaser designed for muted feeds, with an optional music bed, and the first video is free without a card. It has no voice over, no timeline to edit and no visual system to inherit, so it fills a slot on a bad week, and it will never be the kit.

Hand the community the tools, not only the output

The strongest crypto community content is not made by the team at all. It is made by members using the pieces the team published, which multiplies output and, more importantly, gives people a reason to make something with your mark on it.

That last point is a habit rather than a campaign, and it compounds. It also connects to the launch calendar: the same kit that carries a quiet week is what a [token launch marketing](/blog/token-launch-marketing) push draws from when the date finally lands.

Member count is the vanity number here, and it can be bought. The signals worth tracking are about circulation: whether the content leaves the server, and whether it comes back changed.

We build this the same way for every project: identity and kit first, then a steady weekly output on top, with creator seeding and lore maintenance in the monthly packages. Recent work across crypto and tech projects is on [the work](/work), and the shape of each engagement is on the [service cards](/#service-cards). What we do not do is moderate your Discord or buy media: the community is yours to run, the material is ours to make.

We build the identity kit and the weekly stream that comes out of it, for crypto projects that need volume without losing the look.

Most community content is an announcement with a background image. Here are the weekly formats members actually carry outward, and the kit that produces them.

The crypto community content that travels: five formats a Discord reposts, a weekly rhythm that holds, and the template kit that keeps the volume cheap.

Crypto Community Content That Gets Reposted

Crypto community content a Discord will actually repost

The pattern is familiar. A feature ships, someone asks for a video, a freelancer is found, three weeks later a nice film arrives. A month passes, a funding round closes, someone asks for a video, and the whole search starts again. Twelve weeks later the company owns four assets that do not look related, cost four separate setups, and cannot be recut into anything.

The money was not wasted on bad work. It was wasted on repetition: four briefs, four onboardings, four sets of brand decisions rediscovered from scratch, four project files nobody can reopen. The output is fine and the strategy is absent, which is why the next quarter will feel exactly as expensive as this one.

A startup video marketing strategy is mostly a scheduling decision, not a creative one. You are choosing whether a quarter of video comes from one build or from twelve requests. Here is what the first option looks like in practice, what a single build should produce, and where buying something separately is still the right call.

Why one-off video requests never compound

Every asset commissioned in isolation carries the full fixed cost of starting: explaining the product, agreeing on a look, approving a direction, waiting for a first cut. That cost is roughly the same whether the deliverable runs fifteen seconds or two minutes, which is why a series of small requests is the most expensive way to buy video.

None of this is an argument for spending more. It is an argument for spending the same amount in one block instead of four, and using the difference to buy a system rather than four setups.

The unit of planning is a build: one pass in which the narrative spine, the visual system and the master material are produced together. Everything shipped over the following twelve weeks is a cut, a variant or an extension of that build. The question stops being what should we make this month, and becomes what do we cut next.

This is the same logic as a [product launch video](/blog/product-launch-video) that ships with its social cuts already planned, applied to a whole quarter rather than a single date. The build is where the expensive thinking happens, and it happens once.

A quarter does not need a content calendar with forty cells in it. It needs four slots, each with a job and a cadence. Fill those and the calendar writes itself, because every entry is a known type produced from material you already own.

The slots also tell you what to decline. A request that fits none of them is either a new build, which means it gets planned, or a distraction, which means it gets dropped. That single filter removes most of the arguments a marketing team has about video.

If a request does not fit one of the four slots, it is not a small ask. It is an unplanned build wearing a small ask as a costume.

The deliverable list is where a strategy becomes checkable. Vague scope is how a build turns into a single film with no descendants, which puts you back to commissioning one-offs by week six.

Point five is the one most often skipped and the one that decides whether the quarter compounds. A studio that keeps the project file is selling you renders; the same reasoning shows up in our note on how to brief a [motion design agency](/blog/motion-design-agency). We hand source files and usage rights over monthly for exactly this reason.

Planning a quarter does not mean routing every asset through the same door. There is one recurring case where buying beats building: a small teaser needed this week, for a feed, when there is no build to cut from yet and no budget conversation worth having about it.

For that gap we can point at something of ours rather than a competitor. [ShipTeaser](https://shipteaser.com) comes from the same founder as this studio: a product URL goes in, a 15 second 1080p motion graphics teaser comes out, built for muted feeds, with an optional music bed and the first video free without a card. It has no voice-over, no timeline to edit and no visual system to inherit, so it will never produce the anchor film or the spine. It covers a week you would otherwise spend sourcing one small asset.

What should not be bought piecemeal is anything that sets a precedent: the anchor film, the identity in motion, the way the product is framed. Those decisions leak into every asset that follows, so making them under deadline pressure, by whoever was available, is how a brand ends up with four looks and no system.

View counts move for reasons that have little to do with the plan, so they are a poor read on it. The signals worth watching are operational, and they show up inside the first quarter.

Our own packages are shaped around this rhythm: the Launch Sprint produces the spine and the first build in two weeks, then Growth or Scale keeps the slots filled, with a cinematic build once a quarter and a steady flow of assets between them. You can see what that produces across projects in [the work](/work), and how the packages differ on the [service cards](/#service-cards).

We plan the quarter first, build once, then keep the slots filled with cuts that stay recognisable, for tech and Web3 teams.

Most startups buy video one launch at a time, then wonder why nothing compounds. Here is how to plan twelve weeks of assets from a single build.

How to plan a quarter of startup video from one production build: the four slots to fill, what a single build yields, and what to buy separately.

Startup Video Marketing Strategy: Plan a Quarter

Startup video marketing strategy: a quarter planned from one build

Most Web3 branding starts with a logo round and ends with a folder of exports. Six months later the project has a mark, three fonts nobody agreed on, a Discord banner made by a community member, and an exchange listing tile built at 2am by whoever was awake.

That is not a taste problem, it is a systems problem. A crypto brand gets used by more people, on more surfaces, faster than a normal startup brand. Your community makes assets. Exchanges crop your mark. Wallets render it at 24 pixels. A chart tool decides what colour sits next to your ticker, and nobody asks you first.

So the useful question is not what the logo looks like on the presentation slide. It is what the identity does when you are not in the room.

Branding here means the whole system, not the mark. The mark is a small part of the work and most of the argument, which is why so many projects spend a month on it and then improvise everything that comes after.

Design for the surfaces you do not control

A startup brand mostly appears where the company puts it. A token appears in places that were designed by other people, with their own rules, their own dark mode and their own crops. That is the real design brief.

Test the mark at 24 pixels, on a dark background, in a list next to two competitors. If it fails there, it fails in the place most people will actually see it.

This is why a monochrome variant and a dedicated coin icon are not optional extras. The full logo carries the story. The icon carries recognition at a size where the story is invisible.

The token is part of the identity, not a badge on top of it

Teams often design the brand first and bolt the token on afterwards. The result is a beautiful identity and a coin icon that looks like a sticker. Treat the ticker, the coin mark and the chart colour as first class parts of the system, decided at the same time as the logo.

Quiet markets do not usually kill a brand with a bad decision. They kill it with attrition. The budget drops, the designer who held the taste leaves, and the person left standing has exports but no source files. Six weeks later everything looks slightly off and nobody can say why.

That last one matters more than it sounds. A system with no owner becomes a suggestion within a month, and the first place the drift shows is the weekly output the system has to feed, which we cover in our piece on [crypto community content](/blog/crypto-community-content). You can see the difference in the projects on our [selected work](/work): the ones that still look coherent a year later are the ones where somebody on the team was allowed to say no.

Crypto communities are attached to marks in a way most industries are not. People put your logo in their display name. A rebrand that ignores that reads as a betrayal, however good the new work is.

Three rules keep it clean. Keep one recognisable constant, usually the colour or the silhouette, so the change reads as growth rather than a new project. Ship the whole surface in one day, because a half migrated brand looks like a hack. And announce it with assets people can immediately reuse, which turns the community into the distribution instead of the opposition.

A rebrand is also the moment to fix the things the first identity never had: the coin icon, the motion language, the announcement templates. If you are rewriting the system anyway, rewrite all of it.

How we build it, and what to do when the date is already set

Our [Launch Sprint](/#service-cards) runs two weeks: a narrative spine and a visual micro system in the first days, then a teaser film, then launch page art direction, then a social starter kit. Two weeks is deliberately short. A protocol brand does not need a year of exploration, it needs a system it can start using on Monday and extend for the next twelve months.

Sometimes the date arrives before the system does. When that happens, we would rather point at something of ours than at a competitor: [ShipTeaser](https://shipteaser.com) is a product from the same founder as this studio. A product URL goes in, a 15 second 1080p motion graphics teaser comes out, sized for muted feeds, with an optional music bed and the first video free without a card. It reads your page, not your brand book, so it will not give you a coin icon, a motion language or the rules described above. It gets you one competent asset while the system is still being built.

Once the identity exists, everything downstream gets cheaper. The [Web3 launch video](/blog/web3-launch-video) inherits the motion language instead of inventing one, and the [token launch marketing](/blog/token-launch-marketing) calendar stops being a series of one off design requests.

If your brand is a logo and a folder of exports, we can turn it into a system your team and your community can both use.

Most crypto brands are a logo and a folder of exports. Here is the identity system that still holds twelve months later, through a quiet market and a rebrand.

What Web3 branding covers beyond the logo: naming, coin mark, type, colour, motion, templates and the rules that hold through a bear market and a rebrand.

Web3 Branding That Survives a Bear Market

Web3 branding that survives a bear market

A marketing lead sends a deck, three links to films they like and a launch date. Four weeks later the first cut arrives and it is not what anyone pictured. Notes go back, the second cut fixes the color and breaks the pacing, the third adds a stakeholder who was never in the room, and the launch date starts to look optimistic.

Almost none of that is a talent problem. The studio built the film it was briefed to build. The brief simply did not contain the decisions that matter, so the studio made them, and it made them differently than you would have. Every revision after that is you buying back a choice you never made out loud.

Hiring a motion design agency is worth doing when you know what you are buying. Below is what to settle before the kickoff call, how to use references without commissioning a copy, and how to read the proposal that comes back.

What a motion design agency actually sells

Freelance marketplaces and template tools sell execution: frames, renders, hours. A studio sells decisions, and the frames are what the decisions look like once they are made. That distinction is the whole reason the price is different, and it is the only sensible basis for choosing between the two.

If you already have all four, a good freelancer will execute against them faster and cheaper than any agency, and you should hire one. If you have none of them, hiring execution means paying a specialist to invent your brand decisions in a project file, at the worst possible moment to be inventing them.

The four decisions that set the first cut

Every brief leaves something open. These four are the ones that decide whether the first pass is a starting point or a restart, because each of them changes the film at a level that notes cannot fix.

Write four short paragraphs, one per row, and you have a better brief than most of what studios receive. The claim is a single checkable sentence a viewer could repeat. The placement is a named page or feed with the length that placement allows. The approval path is a list of names. The reference set is covered next, because it is the one people get wrong on purpose.

How to use references without commissioning a copy

A board of films you admire tells a studio what you like. It does not tell them why, which is the only part they can act on. Worse, an unannotated board reads as an instruction to match the surface, and the surface is the part that belongs to someone else.

A reference with no sentence attached is not a reference, it is a mood. Three annotated links beat a board of thirty every time.

The test of a good reference set is that a studio could work from it without ever seeing the films themselves. If the sentences alone do not describe a film, the board is doing the thinking and nobody has written the brief.

More motion projects go over schedule because of how notes arrive than because of how long rendering takes. This part costs nothing to fix and it is almost always left implicit.

A studio that pushes back on this at the proposal stage is protecting your date, not defending itself. The same discipline is what makes our [Launch Sprint](/#service-cards) fit in two weeks: the decisions happen on day one and day two, and everything after that is production.

The proposal is the first real sample of the work. Not the showreel, which was assembled to look good, but the document that shows how a studio thinks when it is handed your specific problem.

One more thing to check: ask what happens after delivery. Source files, fonts and usage rights should be named in writing. A studio that keeps the project file hostage is selling you a render, not a system, and the next format will cost you the full price again. We hand source files and usage rights over monthly, and the reasoning behind that is the same one in our post on [brand video for tech startups](/blog/brand-video-for-tech-startups): the second asset should be a cut, not a project.

Two cases. The first is the one above: you already own the claim, the system and the references, and you need hands. The second is when the only thing missing is a short cut for a feed, this week, and there is no budget conversation worth having about it.

For that second case we can point at something of ours rather than a competitor. [ShipTeaser](https://shipteaser.com) is a product from the same founder as this studio: a product URL goes in, a 15 second 1080p motion graphics teaser comes out, built for muted feeds, with an optional music bed and the first video free without a card. There is no voice-over, no timeline to edit and no visual system to inherit, so it will not replace the four decisions above. It replaces the week you would have spent finding someone to make one small asset.

Everything else is agency work: a launch that needs a spine, a set of assets that must look related, a category that has to be explained before it can be sold. Those are decision problems first, and the motion is what the decisions look like once they are made. You can see how that plays out across projects in [the work](/work).

We settle the claim, the placement and the visual system first, then build the films and the cuts from it, for tech and Web3 teams.

Most first cuts miss because the brief left the important decisions open. Here is what to write down before a studio opens a project file.

What a motion design agency needs before production starts: the one claim, the placement, the approval path, the references, and how to read the proposal.

Motion Design Agency: How to Brief One Well

Motion design agency: how to brief one so the first cut lands

The exchange confirms on a Tuesday for a Thursday. The audit comes back two days later than promised. A competitor gets exploited over the weekend and every timeline in crypto talks about custody for 48 hours. None of that was on your marketing plan, and all of it lands on the same week.

So the plan collapses into what it always collapses into: one announcement graphic, one thread, one video ordered Monday for Thursday, and a launch that looks like the last forty launches. Not because the team lacked taste, but because by then there was no room left to have any.

The fix is not more assets. It is separating the work that can be finished before the date exists from the work that can only happen once it does. That split is the whole discipline, and almost nobody does it in the right order.

A token launch is five phases, not one day

Treating the listing as the event is the first mistake. It is the loudest phase, not the longest, and it is the only one where nothing can still be changed.

Budgets almost always concentrate on the third row. That is the row where the outcome is already mostly decided: by then the story either reads in one sentence or it does not, and no graphic fixes the difference. The first and the last rows are the ones that compound, and they are the two that get cut first when the date moves.

Build backwards from a date you do not control

Run one exercise before anything else. List every asset you want for the launch, then sort each one into two columns: does this need the date, the ticker, the exchange name, or the price? If the answer is no, it can be finished now, reviewed calmly, and signed off weeks early.

The fifth row is the one worth stealing. A teaser that shows the product and the world of the project, with the final card built as an empty slot, can be approved three weeks early and still ship the hour the date lands. A teaser that says the date out loud cannot, and that single craft decision is what separates a launch film from a disposable one. It is the same reasoning behind the structure we use in our post on the [web3 launch video](/blog/web3-launch-video).

The last row matters for a different reason. Pre written reaction copy always reads as pre written, because it was drafted before the thing it reacts to happened. What you prepare is the container: the frame, the type treatment, the export sizes, the approval path. The words stay live.

This is the part that can be planned properly, because none of it depends on anyone else confirming anything.

A useful gate at week minus two: if the launch date slipped by three weeks tomorrow, how much of what you have built would be wasted? If the answer is most of it, you built the wrong things first.

Where a fast tool fits, and where it does not

Sometimes the four weeks are not there. The date arrives early, a listing appears out of a conversation nobody told marketing about, and the honest question is what can exist by tomorrow rather than what should exist.

For the feed cut specifically, there is a faster route, and we should be clear that it is ours: [ShipTeaser](https://shipteaser.com) is a product built by the same founder as this studio. You paste a URL and it returns a 15 second 1080p motion graphics teaser designed for muted feeds, with an optional music bed, and the first video is free without a card. What it does not give you is the thing the rest of this calendar is about. There is no narrative spine, no visual system your community kit and your announcement frames can inherit, no voice-over and no timeline to edit. For a teaser needed on Thursday it does the job. For a launch that has to still look coherent at week six, it is one asset, not the plan.

The general rule holds beyond that one tool. Automation is good at producing a single asset quickly and bad at producing a system, and a token launch is judged on the system: forty pieces of content over two months that clearly come from the same project.

The week of the listing: capacity, not more files

Once the date is public, production capacity stops being the constraint. Decision capacity becomes it. Teams lose the launch window waiting for approvals, not waiting for renders.

This is also the phase where the crypto calendar breaks plans, which we cover in more detail in our post on [crypto video production](/blog/crypto-video-production). The teams that come out of it well are not the ones with the most assets. They are the ones who can put something good out within hours of a moment they did not schedule.

Opinions, with the reasons attached, from launches we have worked on.

The pattern behind all four: each one spends launch week money on a problem that was cheaper to solve in week minus four. That is the recurring shape of a launch that felt expensive and landed flat, and it is why we sequence engagements the way our [service cards](/#service-cards) describe, narrative and system first, assets after.

We build the narrative and the visual system first, then the launch kit around a date that can still move, for crypto and tech teams.

Most teams commission one announcement graphic the week of the listing. The calendar that works starts four weeks earlier, while the date is still private.

A week by week asset calendar for a token launch, built backwards from a listing date you do not control, and the kit to have ready before it.

Token Launch Marketing: The Asset Calendar

Token launch marketing: the asset calendar, week by week

A marketing lead asks for an explainer video. The studio quotes an explainer video. Everyone agrees on the word, nobody agrees on the film. Six weeks later there is a 90 second animated piece with a voice-over sitting above the fold, where visitors wanted to see the product, and a launch two weeks away with no asset that works in a feed.

The word covers at least three deliverables that share almost no craft decisions. Different lengths, different audiences, different first frames, different budgets. Ordering one and needing another is the most expensive mistake in SaaS video, and it happens before anyone opens a project file.

So the first job is not writing a script. It is deciding which of the three you are buying.

The three films that get called an explainer

They answer different questions. A viewer arrives with one of them already in their head, and the film either matches it or gets closed.

The pattern to notice: only the explainer assumes attention. The other three have to earn it or already have it for other reasons. That single difference sets length, pacing, sound design and whether the first frame can afford to be abstract.

An explainer earns its cost when the product cannot be understood from a screenshot. That is a narrower case than most teams assume.

And when it is the wrong buy: the product is self evident in one screenshot, the real objection is pricing rather than comprehension, or the actual need is something that survives two seconds in a feed. In that last case you want a teaser, and calling it an explainer will get you 90 seconds of animation that nobody on social will ever finish.

A quick test. Read your homepage headline to someone outside your market and ask what the product does. If they get it roughly right, you do not need an explainer, you need a better product film.

The placement sets the length, not the ambition

Length is not a taste question. It is a function of where the video sits and what the viewer was doing one second before it started.

The above the fold row is where most SaaS explainers die. A film built for a dedicated page gets dropped into the hero, where it opens on a logo animation and a slow abstract shape, and the visitor leaves before the product appears. Same file, wrong slot, wasted spend.

What the first ten seconds have to contain

Every explainer that works front loads the same four things. Every one that fails saves them for later, in the belief that setup buys patience. It does not.

Notice that three of the four are visual. An explainer that only works with the voice-over playing is a podcast with pictures, and it will be watched muted more often than not, even on a page where someone chose to press play.

Build one system, cut every format from it

The reason teams end up with the wrong format is sequencing. They commission a single film, discover the gaps at launch, and then commission more films from scratch, each with its own look. Three productions, three visual languages, one incoherent brand.

The cheaper order is to build the visual system first: type, motion behavior, color, how the interface is framed, how numbers appear. Once that exists, the explainer, the product film and the feed cuts are recuts of one build rather than three separate jobs. This is the same logic behind the four decisions in our post on the [product launch video](/blog/product-launch-video), and it is how our [Launch Sprint](/#service-cards) is sequenced: narrative and visual micro system first, assets after.

If what you need this week is only the feed cut, there is a faster route and we should be clear that it is ours: [ShipTeaser](https://shipteaser.com) is a product built by the same founder as this studio. You paste a product URL and it returns a 15 second 1080p motion graphics teaser designed for muted feeds, with an optional music bed and the first video free without a card. It is deliberately not an explainer: there is no voice-over, no screen recording, no timeline to edit, and it will not give you a visual system your other pages can inherit. For a teaser you need on Thursday it is the right tool. For the film that has to make a new category understandable, it is not.

The one page brief that prevents the rework

Before you talk to any studio, freelancer or internal designer, write these five lines. They take twenty minutes and they settle every argument that would otherwise happen during revisions, when changes are expensive.

A studio that gets that page back writes a script that is close on the first pass. A studio that gets "we need an explainer, here is our deck" writes three scripts, and you pay for the two you throw away.

We build the visual system first, then cut the explainer, the product film and the social versions from it, for tech and Web3 teams.

Three different films get ordered under the same word. Picking the wrong one is why a video costs a quarter of the marketing budget and moves nothing.

Explainer, product film or teaser: the three videos SaaS teams confuse, how to tell which one your page needs, and what to brief before production.

SaaS Explainer Video: Which Format You Need

SaaS explainer video: which format your page actually needs

The default reveal video is the same every time. A grid of traits rotates in, pieces flip through variations, a synth track builds, the logo lands, a date appears. It is posted three days before mint and it gets polite engagement from people already in the Discord.

It fails for a structural reason, not a taste one. The loop shows the art, and the art is the one thing a buyer can already scroll through on the mint page. The video spends its entire runtime answering a question nobody had.

The questions people actually have are different, and none of them are answered by watching a JPEG turn.

Put yourself in the timeline of someone who has never heard of the collection. They see nine seconds of stylized characters. Here is the gap between what the film says and what they are deciding.

One row out of five. That is a fair description of most reveal videos, and it explains why they perform the way they do: they are a gallery, and galleries do not convert strangers.

Establish the world before you show the pieces

A collection that reads as valuable reads as a piece of something larger. The film is the cheapest place to establish that larger thing, because motion can imply a world in three seconds where a static grid cannot.

Concretely, that means the first shots are not the assets. They are the environment, the typography, the interface, the rules of the place. The pieces arrive as inhabitants of a world the viewer has already accepted.

A useful test: mute the film and remove every piece of art from it. If what is left says nothing about the project, the film has no spine, only a subject.

The other failure is treating the reveal as the deliverable. A mint is a schedule, and each date on it wants a different asset. Producing them separately is how budgets disappear; producing them from one build is how they stay sane.

Every row here is a reframe or a recut of the same visual system. That is the whole argument for building the system first: the fourth asset costs a fraction of the first one only if the first one was built to be reused.

The film will be watched on a phone, muted, autoplaying between a chart and an argument. That placement is not a constraint to work around afterwards, it is the format itself.

Three honest routes, and the right one depends on whether the collection needs a look that outlives the mint.

In house works when someone on the team has motion skills and enough runway to spend two weeks on it. The hidden cost is that the mint then competes with everything else on their plate, and the reveal is usually what slips.

Automated is worth naming precisely, because we built one: [ShipTeaser](https://shipteaser.com) is our own product, from the same founder as this studio. You give it a URL, it reads the page and returns a 15 second 1080p motion graphics teaser, no voice-over, made for muted feeds, the first one free without a card. For a mint page that already has its art direction settled, that is a fast way to get a competent teaser. It will not invent your world, write your narrative spine or hold a collection together across four launch moments. That is the trade, and it is a real one.

A studio is the call when the collection is meant to be the start of something. That is what a [Launch Sprint](/#service-cards) covers: narrative and visual system first, then the teaser, then the mint page art direction, then the social kit, in two weeks. Past mints and brand work sit on [our work page](/work).

Answer these on one page before anyone opens a project file. Every argument later gets settled by pointing at it.

None of that is a production question. It is all decided on paper, which is exactly why teams skip it and then pay to fix it in the edit, where changes cost the most and help the least.

We build the narrative spine, the reveal film and the full mint asset kit for Web3 collections.

A rotating grid of traits set to a synth track is not a marketing video, it is a screensaver. What a collection reveal has to establish, and what to build around it.

Most collection reveals are a rotating art loop with a synth track. Here is what an NFT marketing video has to establish instead, and the assets a mint needs.

Blog

Web3 & crypto

Crypto community content a Discord will actually repost

Web3 branding that survives a bear market

Token launch marketing: the asset calendar, week by week

NFT marketing video: what to show instead of the art loop

Crypto video production: what changes when the film is for a protocol

How to choose a Web3 marketing agency

Web3 launch video: what actually makes people care

Tech & brand

Teaser video for app launch: fifteen seconds, sound off

Startup video marketing strategy: a quarter planned from one build

Motion design agency: how to brief one so the first cut lands

SaaS explainer video: which format your page actually needs

Product launch video: four decisions that set the film

Brand video for tech startups: the four you actually need