About Dusken
Where great work
gets finished.
The name comes from dusk, the final hour before something ships.
This started at an agency
For years I ran a small web development agency. Small team. High-craft work. Clients who cared about the output. Or at least said they did until the feedback started coming in.
The work would go out looking sharp. The notes would come back as a paragraph in an email, a voice memo recorded in a moving car, a screenshot with an arrow drawn in the wrong direction. Sometimes all three, about the same frame, contradicting each other.
We would do the revisions. Send it back. Get more notes. The file would get worse. The deadline would get closer. Nobody could explain exactly why it wasn't right yet. They just knew it wasn't.
Per-seat pricing was another frustration, especially when dealing with external clients and guest reviewers, but pricing was never the real issue. The real issue was the loop itself: agency to client to feedback to editor to revision to client again. Every handoff in that chain lost something in translation.
The problem isn't the client. The problem isn't the team. The problem is that there is no good way to point at something and say this, right here. This is what I mean.
The gap that kills quality
Creative feedback is not a text problem. When something is off, you feel it before you can name it. The grade is too warm. The transition is too abrupt. The logo needs more air.
That feeling is immediate and specific. But by the time it travels through an email thread, a Slack message, a reply-all, a call to explain the Slack message, it has lost its timing, its context, and half its meaning.
The editor opens the file and tries to reconstruct what someone meant. They guess. They revise. They send it back. The cycle continues.
This is where quality dies. Not in the making, in the handoff.
Feedback back on the frame
Dusken puts feedback back on the frame where it belongs. You upload a video, invite your team, and everyone comments directly on the frame. Timestamped, precise, pinned to the exact moment they mean.
Voice comments, video recordings, drawn annotations. No email threads. No version confusion. When the work is right, you approve it. One action. Done. Everyone knows.
Typing is always an option, but it shouldn't be the only way to communicate feedback. Stop writing paragraphs to explain a two-second change. If speaking with push-to-talk, circling an element on the frame, or recording a quick video reply explains the thought faster, use that instead. Tone lands, the point is clear, and the note stays attached to the work.
Review at the level of the cut
Video review isn't just watching a cut from start to finish. If you're checking a two-second transition or an audio pop, you need to inspect a few frames.
Dusken lets you switch between timecode, frames and standard time, change playback speed, and use keyboard shortcuts to move quickly through the footage. You can set an in and out point to loop a specific section, and attach a range comment directly across those frames so the editor knows exactly which stretch you're talking about.
Four things we believe
Unlimited reviewers are free at Dusken.
Per-seat pricing punishes collaboration. Every Dusken plan includes unlimited external reviewers: clients, stakeholders, anyone whose input matters. You pay for your internal team, not for the people you're trying to hear from.
Plain English, everywhere.
Everything in Dusken has a name you already know. A comment is a comment. An annotation is an annotation. Approved means done: locked, delivered, on the record. No invented vocabulary to learn.
Async by design.
Great feedback does not require a scheduled call. It requires the right tools. Dusken is built so your whole team can move through a review without being in the same room, or the same timezone.
The interface gets out of the way.
The work is the thing.
Creative directors, editors, motion designers, freelance colorists. Teams of two to five people running high volumes of active work. People who have felt that gap between what they see and what gets communicated, and are tired of losing quality in the middle.
Built by someone who was there
Dusken is built by Salman: founder, developer, designer. The agency taught me where the review process breaks. Dusken is what I wished existed while it was breaking.
I have 14+ years of experience building software systems. Over those 14+ years I've worn many technical hats across backend architecture, backend engineering, frontend engineering, APIs, databases, infrastructure, application development and product engineering. Dusken is built with that technical foundation and product experience.
Have questions or want to see how Dusken fits your workflow?
Dusken is founder-led, so support is close to the product. We are happy to talk through your agency setup, NLE export workflows or custom requirements.