Founder @Kreatli. Helping video teams unify media review, frame-accurate feedback, and project management into one system built for real production workflows.
the long-awaited day has come.
we are launching @kreatli on product hunt NOW!
we help creative teams streamline and simplify post-production workflows. no more juggling multiple platforms.
please support our launch here -->
https://t.co/f7AsKQiYX8
things you gotta check out after you've upvoted and left a comment:
1. our sick platform: https://t.co/uW8ZQqoJVd
2. our sick launch video: https://t.co/Y2HMMzsOq1
3. our sick platform demo: https://t.co/LtdSFhEVyD
a special gift for all the supporters:
20% off on the Pro Plan for 2 months – valid for 48h after the launch.
@kreatli has been almost 9 months in the making so we consider it our baby.
please give it as much love as we gave it - hope it'll bring value to all the content teams out there!
cheers,
@georgegiom & @_saidwhat_
Video production teams have been running their workflows on tools built for software developers.
Frame. Notion. Google Drive.
The industry just adapted.
We stopped adapting and built Kreatli from scratch — specifically for video production.
Frame-accurate review.
Production Kanban.
Version history.
Client delivery with no login required.
Lifetime deal live now on @AppSumo 👇
Video production teams have been running their workflows on tools built for software developers.
Frame. Notion. Google Drive.
The industry just adapted.
We stopped adapting and built Kreatli from scratch — specifically for video production.
Frame-accurate review.
Production Kanban.
Version history.
Client delivery with no login required.
Lifetime deal live now on @AppSumo 👇
The problem isn't your team. It's your stack.
We just shipped a lot on Kreatli:
→ Ingest
→ Approvals
→ Producer Queue
→ Exports
→ Notifications
→ Centralized dashboard
→ Media folders + status + owners
→ Side-by-side version compare
→ Gantt + List deliverable views
Brief → production → review → delivery. One platform.
https://t.co/uW8ZQqphKL
Tasks & Boards just launched on Kreatli 🚀
Not another to-do list.
Board columns ARE your project stages. Move a task = progress updated.
Tasks link to media. Review feedback becomes tracked work.
One owner per task. No confusion on who's responsible.
Briefing → Production → Client Review → Delivered — all in one place.
Built for creative teams, not generic workflows.
See it → https://t.co/JodDCd7PIs
Client approved your work 3 days ago.
You just found out this morning
How: Client approved in Frame Friday 4pm. Notification → producer's email.
Producer offline for weekend. Email buried Monday under 47 messages.
Now 3 days behind. Client thinks you're ignoring them.
The approval black hole: Approvals in one tool. Notifications in email. Nobody checks consistently. Progress stalls.
The pattern:
→ Client approves Friday evening (miss until Monday) → Approves during your meeting (lost in email)
→ Goes to wrong person
→ Multiple stakeholders (don't know when you have full approval)
One agency tracked: Average delay approval→action = 38 hours. Not because slow. Because don't know it happened.
Fix: Approvals visible, not buried. Status updates real-time. Team sees immediately. Next steps trigger automatically. Nothing waits for email check.
Test: Time between last client approval and when you knew?
Same day? Next day? Longer? 👇
---
Read more on our site: https://t.co/jlt3kxFQ4G
Your team has 3 versions of the same file.
Nobody knows which is final.
This shouldn't be possible in 2026.
How it happens:
Version 1: Google Drive (designer uploaded)
Version 2: https://t.co/jEw8rqpNLJ (client review)
Version 3: Producer's downloads (emailed to client)
Same project. Three locations. Zero clarity.
The question nobody can answer: "Which is the approved final?"
Designer: "Drive is latest"
Producer: "I sent from downloads"
Client: "I approved in https://t.co/jEw8rqpNLJ"
Are they the same? Nobody's sure.
What this costs:
→ Editor works 2 hrs on wrong version
→ Client gets wrong file, asks "where's my changes?"
→ Designer re-exports because nobody trusts any version
→ Producer plays detective for 30 min
Multiple times per week.
Why: Files live where tools put them, not where workflows need them. Review tool stores one. Cloud has another. Email creates third.
Fix: One file. One location. One truth. When client approves in review system = final. Same file designer uploaded. Same file delivered. No copying. No confusion.
Reviewed 47 creative agency workflows.
Every. Single. One. Had the same broken step.
The broken step: Client approves. Then nothing happens automatically.
Should happen:
Approve → Files delivered → Invoice sent → Project complete → Team notified (automatic)
Actually happens:
Approve → Producer notified → Manual download → Manual email → Manual invoice → Manual tracker update → Manual team notification
One approval. Six manual steps.
Insane part: Automated the hard part (approval). Left easy part (delivery) manual.
Self-driving car that requires manual parking.
One agency: Approval-to-delivery = 2.3 DAYS. Should take = 2.3 SECONDS.
The fix: Approval triggers everything downstream. Files→inbox, invoice→accounting, status→complete, team→notified. Automatic.
Human = creative. System = coordination.
Set up a call with me and I can show you how we help companies do exactly that: https://t.co/S5MWjcyCtv
Question that reveals everything about your workflow:
"If your producer took a week off, would projects keep moving?"
Asked 12 creative teams.
11 said no.
Not because producer is irreplaceable. Because they're the only person who knows: where everything is, what stage projects are in, what's blocking, who's waiting, what's next.
They're not producing. They're a human database.
The test: Producer goes on vacation Monday.
Can team find latest brief?
See what's approved?
Know who's working on what?
Answer client questions?
Deliver finished work?
If "probably not," you don't have a workflow. You have a person holding it together.
What this means:
Workflow lives in someone's head, not your system. When they're gone: info inaccessible, status unclear, handoffs break, projects stall.
The fix: Systems over heroes.
When workflow lives in platform, not head: anyone finds status, handoffs automatic, context visible, projects move without orchestration.
Stop building workflows that require heroes. Build systems that work without them.
Could your team operate a week without your producer/PM? Be honest 👇
https://t.co/lAQL20h0UU
The most expensive words in creative production:
"I thought you already did that."
Editor spent 4 hours color grading. Beautiful work. Problem: Producer already hired a colorist.
Two people. Same task. Zero communication. 4 hours wasted.
This happens constantly:
→ Designer creates assets (animator already made them)
→ Editor cuts B-roll (junior finished yesterday)
→ Producer writes brief (AM sent last week)
Why: Task tools show assigned/in-progress/complete. Don't show what someone's working on RIGHT NOW. People duplicate in parallel.
Cost: 5-10% of billable hours. $500K team = $25K-50K waste/year. Not incompetence. Invisibility.
Fix: Real-time work visibility.
Editor opens file → "Sam color grading Nike spot." Ambient awareness. No Slack needed.
---
Learn more: https://t.co/p4JyMkb1Gi
The most expensive words in creative production:
"I thought you already did that."
Editor spent 4 hours color grading. Beautiful work. Problem: Producer already hired a colorist.
Two people. Same task. Zero communication. 4 hours wasted.
This happens constantly:
→ Designer creates assets (animator already made them)
→ Editor cuts B-roll (junior finished yesterday)
→ Producer writes brief (AM sent last week)
Why: Task tools show assigned/in-progress/complete. Don't show what someone's working on RIGHT NOW. People duplicate in parallel.
Cost: 5-10% of billable hours. $500K team = $25K-50K waste/year. Not incompetence. Invisibility.
Fix: Real-time work visibility.
Editor opens file → "Sam color grading Nike spot." Ambient awareness. No Slack needed.
---
Learn more: https://t.co/p4JyMkb1Gi
Most creative teams think they have a feedback problem.
They have a handoff problem.
Real example: Client approves video Tuesday morning. Friday: "We never got the final file."
Approval happened. Delivery didn't. Because they lived in two different tools with a manual step between them.
The same gap exists everywhere:
→ Brief → Project setup (manual copy/paste)
→ Feedback → Revisions (manual Slack message)
→ Completion → Invoice (manual data gathering)
At 5 projects: You catch the gaps.
At 15 projects: You miss them.
At 25 projects: You stop being surprised.
The fix isn't better communication. It's eliminating the handoffs.
When approval automatically triggers delivery, nothing falls through the cracks.
Not because your team improved. Because the system doesn't rely on memory.
How many manual handoffs between approval and delivery?
Drop a number 👇
How to audit your creative workflow in 30 minutes:
Step 1 (5 min):
Pick one typical completed project from last 30 days
Step 2 (10 min):
Map every tool touchpoint
Example: Email → Doc → Asana → Slack → Feedbock → Email → WeTransfer → QuickBooks = 12 interactions
Step 3 (10 min):
Count manual handoffs (when info manually moves between tools)
Example: Email→Doc, Doc→Asana, Drive→Slack, https://t.co/jEw8rqpNLJ→Email = 5 handoffs
Step 4 (5 min):
Estimate coordination time (checking status, routing info, following up)
Most teams: 4-8 hours per project
Results:
Low friction: <8 interactions, <3 handoffs, <2 hrs
High friction: 12+ interactions, 5+ handoffs, 5+ hrs
Breaking point: 15+ interactions, 8+ handoffs, 8+ hrs
High friction means 20-40% of project time is coordination, not creation.
Run this. Drop your numbers:
Tool interactions: __
Manual handoffs: __
Coordination hrs: __
Is this sustainable as you scale?
Read more on our Blog: https://t.co/ab4x9K0osA
Your workflow works at 5 projects. Breaks at 15.
Talked to a video studio last week.
At 5 projects: clear status, quick answers, organized files.
At 15 projects: producer only answers questions, messages lost, files everywhere.
Same tools. 3x volume. Everything broke.
The problem:
Slack scales communication (not context).
Drive scales storage (not organization).
Feedback tools scale review (not orchestration).
Each tool's FUNCTION scales. The CONNECTIONS don't.
At 15 projects with disconnected tools:
all-day meetings, 15-min status checks, 20% time creating value.
At 15 projects with production management:
actual project work, 30-sec status checks, 70% time creating value.
Same volume. Different system.
Will your workflow scale with your ambitions? 5 → 15 → 30 projects?
Tool collection won't. Production management will.