Kumushbek T.
KT
Senior UX & Brand Design Lead
Design
Mid-Market (51-1000 emp.)
"Feedback Attached to Every Deliverable Keeps Client Reviews Clear and Fast"
4/5
What do you like best about Digital Pigeon?

What leaves the studio is heavy. A forty-page brand book, a ninety-second product film, a dieline with print specifications — three hundred megabytes to two gigabytes, moving every week, to clients whose IT departments occasionally block whatever the last agency used.

The feature that changed our process is that feedback attaches to the file. A client watching the film stops it at thirty-eight seconds and writes "the type jumps here"; a marketing director opens the brand book and comments on page twelve about the logo lockup. Previously those arrived as an email describing a timestamp, a marked-up PDF that had been printed and photographed, and occasionally a voicemail.

For a project with five stakeholders, that consolidation matters more than the transfer itself. One thread per version, and the version is the one they were shown — not a copy somebody saved in March.

The measurable effect is on rounds. Before, a third revision was usually not a design change but a misunderstanding of a comment, and we absorbed it. On a brand identity project last quarter we ran two rounds where three had been budgeted, and the saving went into the photography rather than into the margin.

Presentation is a smaller benefit. The delivery page carries our mark and the client's, so the file arrives as a deliverable rather than as a link to a folder. Clients notice this more than they admit, particularly the ones who forward our work to their own board.

It is not the tool we use while designing; Figma comments still handle that, badly and constantly. This is for the moment a file leaves and an opinion comes back. Review collected by and hosted on G2.com.

What do you dislike about Digital Pigeon?

Versions. A client is looking at the third delivery and wants to recall why the mark moved; the second is a separate page with its own thread, so comparing them means two browser windows and a good memory. In a brand project that conversation happens weekly, and there is no way to place two versions side by side.

Comments do not leave. When a project closes, feedback is archived into the project record — for the next designer picking up the account, and occasionally for a dispute six months later about what was approved. The thread lives on the delivery page and cannot be exported in any useful form. We screenshot it, or retype it into a document, and the timestamps, which are the point, disappear in the process.

Tablet review is the third problem. Art directors review on an iPad during meetings. Pinch-zooming a forty-page PDF to read a caption is workable; placing a comment accurately on a spread is not, and comments land two pages from the intended target. On a print project that surfaces as a correction at proof stage, which is the most expensive moment to find it.

Notifications go to everyone on the delivery. A thread involving five stakeholders generates an email per comment, and two of those people mute it by the second day, so they miss the decision that mattered. We now nominate one person per client to hold the thread, which works until that person is on leave.

Uploading large files is slow on studio bandwidth, and a two-gigabyte package has to be started early in the day rather than at four in the afternoon.

The transfer itself is dependable. What surrounds the file is thinner. Review collected by and hosted on G2.com.

See what 138 reviewers think of Digital Pigeon

4.7 out of 5 · Verified reviews from real users

Read all reviews