After the WordPress site launches: how agencies close video and motion approvals
By Heorhi Talochka
A WordPress agency’s calendar is honest about pages and dishonest about video.
The theme is chosen. The header is configured. The shop, the bookings, the blog, the multilingual pack—those have tickets, staging URLs, and a definition of done. Then someone remembers the homepage has a 45-second film, the product pages need clips, and the client’s founder recorded a talking-head that must replace the stock poster.
That work does not live in the theme customizer. It lives in exports, Drive folders, and a thread titled “quick thoughts on the video.” The site can be “launched” while the motion is still in committee. Visitors see a poster image. The agency still has a round of notes with no timestamp.
If you ship a production-grade WordPress theme, you already sell a complete site. Video is part of complete. It needs a close as boring and reliable as “page approved on staging.”
Launch is not the last deliverable
Clients experience the site as one object. Agencies split it into disciplines: WP, design, copy, SEO, video. The split is reasonable for production. It is fatal for sign-off if only the WP part has a workflow.
Typical leftovers after a theme launch:
- Hero background video that still shows an old logo
- Product loops that were transcoded too hard and look muddy on retina
- A founder video that legal has not cleared
- Social cuts that were never reviewed on mobile
None of those are theme bugs. All of them make the theme look unfinished. Your support inbox will still catch the blame—“the homepage feels off”—because the visitor cannot tell a layout from a late MP4.
Put video on the same launch checklist as forms and redirects. Picture lock is a date. Hosting the file on the site is a later date. Do not merge them.
Why WordPress project tools fail video
Agencies already have places for work: Trello, Asana, ClickUp, a client portal, email, WhatsApp. Those tools are good at “this task is open.” They are bad at “this exact frame is wrong.”
A ticket that says “fix the video” is the WP equivalent of a ticket that says “fix the site.” You would never accept that for a layout. You would send a screenshot, a URL, and a browser.
Video needs the equivalent of a screenshot: a time, a picture, and a sentence. Comments in a task description drift. Attachments multiply. The editor downloads v3 while the producer comments on v5. Staging WP has version control for templates; the MP4 in the Media Library does not.
There is also a people problem. The person who approves the theme is often not the person who approves the film. Brand, founder, and agency producer all need to see the same player. Inviting them into your PM tool so they can type on a card is how notes get shorter and vaguer.
Put the cut in a reviewer, not a ticket
The review surface should be a player with a timeline, not a ticket with an attachment.
Send one link. Ask every stakeholder to watch that link. When they comment, the note sits on the cut. When you upload v2, the thread is still about the work, not about who has which file.
A video reviewer is that player: the agency and the client watch the same timeline in a browser. Kreatli is the workspace behind it when the site build and the film need to stay in one project instead of a stray Drive folder.
Practical rules for WP retainers:
- Do not put the master file in the Media Library until it is approved. Use a review link during the round.
- Do name the library file with the approved version after lock, so a future editor does not replace it with an old export.
- Do decide who can comment (brand, legal) versus who is FYI. Open threads with twelve people recreate email.
- Do review on phone if the theme’s hero is mobile-first. Most clients will still watch on a laptop unless you ask.
Collect feedback like you collect content sign-off
You already have a pattern for copy. The client comments in a Google Doc or a staging page. You do not accept “make the about page nicer” without a paragraph. Video deserves the same bar.
A video feedback tool is for collecting those notes: timestamped comments, optional drawings on the frame, a guest link so the client does not need a WordPress login or a project-management seat. That last point matters. Site stakeholders should not have to learn your stack to say the logo appears too late.
Map it to the way you already run content:
| Site content | Video equivalent |
| Comment on a heading on staging | Comment at 00:04 on the hero film |
| Screenshot of a broken margin | Drawing on the frame where type collides with a face |
| “Approved” on the page | Written picture lock on that version |
| Rollback a page revision | Keep vN in review history; do not overwrite blindly in Media |
When a note has no time, send it back. You would bounce a design comment that does not name a page.
A default for retainers
WordPress agencies that live on retainers need a default they can paste into the kickoff deck.
- Scope the film like a template. Duration, aspect ratio, where it plays (hero, product, popup), and who signs off.
- One review round included. Extra rounds are change requests, same as extra homepage concepts.
- Guest link, no new account for the client. If they cannot comment in five minutes, they will email you a paragraph with no times.
- Technical pass after lock. Compression, captions, poster image, and the actual file in WP or a CDN. The review player is not the CDN.
- Launch criteria include motion. “Site live” means the approved file is in place, or a documented poster-only launch with a date for the film.
You can still use demos and prebuilt layouts to move fast on the site. Speed on the theme is wasted if the hero video is a stock loop the client hates and nobody can point to the second it goes wrong.
Theme craft got agencies out of rebuilding headers from scratch. Review craft gets them out of rebuilding films from Slack. After the WordPress site launches, the work that still leaks is almost always the moving picture. Put it on a timeline, collect notes like you collect copy, and do not call the project done until the cut has the same kind of yes you already require for the page.
About the author
Heorhi Talochka is the founder of Kreatli, a video collaboration and review platform for creative teams. He works with agencies that already ship serious WordPress sites and still lose time on video sign-off.
Leave a Reply