
One week.
That’s how long it took me to turn a simple idea into a live product on the internet.
But the idea didn’t start with code.
It started with confusion.
Small video agencies are growing fast.
2–10 editors.
20+ videos in progress.
Deadlines everywhere.
And one simple question kept causing stress:
“Who is editing what?”
Not a complicated problem.
But somehow, always messy.
Tasks were floating in WhatsApp.
Spreadsheets were outdated.
Some editors were overloaded.
Others were waiting for work.
No one had a clear view.
And I kept thinking:
Why is this still so chaotic?
Most tools focus on deadlines.
But agencies don’t struggle with dates.
They struggle with distribution of work.
An editor has 8 hours in a day.
A YouTube video might take 6 hours.
Another Instagram reel might take 3 hours.
That’s already 9 hours.
But no system tells you that clearly.
That’s when it clicked.
What if planning was based on capacity instead of just deadlines?
That idea became EditFlow.
This was my first project at Entrext.
And I built it solo.
Frontend was hard.
Backend was confusing.
Deployment was stressful.
Everything felt difficult in the beginning.
There were moments where I didn’t know how to structure the planner.
How to calculate capacity properly.
How to design the workflow.
But slowly, step by step, I figured it out.
Every small bug fixed gave me confidence.
Every working feature felt like progress.
In just one week, the MVP was live.
On the internet.
That feeling? Unreal.
EditFlow is not a complicated tool.
It does one thing very clearly:
It shows who is editing what and how much space is left.
Here’s how it works:
• Each editor has daily capacity (like 8 hours)
• Each video has estimated hours
• You drag the task into a day
• If it exceeds capacity — it stops you
No overbooking.
No guesswork.
Just clarity.
There’s also:
• An unassigned backlog
• Client request intake
• Clean workflow: Backlog → Assigned → In Progress → Review → Approved
• View-only client link
• Planned vs actual time tracking
But the heart of it is still capacity.
Because the issue wasn’t about creating tasks.
It was about understanding workload.
Most tools show lists.
They show deadlines.
They show statuses.
But they don’t clearly show who has space and who doesn’t.
They don’t show daily capacity in a way that prevents overload.
And the more advanced systems?
Too complicated.
Too heavy.
Too much for a small creative team.
What agencies really needed was something in between.
Simple.
Visual.
Capacity-aware.
Nothing extra.
Nothing overwhelming.
Just clarity.
Honestly?
Everything.
It was my first real end-to-end project.
Frontend logic.
Backend structure.
Database design.
Deployment.
At the start, it felt overwhelming.
But the biggest lesson I learned:
You don’t need to know everything.
You just need to solve the next small problem.
And slowly, the product started taking shape.
Not the features.
Not the UI.
But the fact that an idea turned into something real.
From a simple thought:
“Agencies must be facing this confusion.”
To:
A live MVP people can use.
That transformation is powerful.
The MVP is live.
It exists.
It works.
And it solves a real problem.
Right now, it’s focused only on small video agencies.
No big expansion plans.
Just solving this one problem properly.
Small problems are worth solving.
Clarity beats complexity.
Shipping fast teaches more than planning forever.
The first project is always the hardest — but the most important.
EditFlow isn’t trying to change the world.
It’s trying to reduce stress for small creative teams.
And sometimes, that’s more than enough.
If you're building something right now:
Ship it.
You’ll figure it out along the way.
1
7
0