Every studio we talked to before building Mollydob described the same problem in three different ways, without realizing it was one problem.
The designer said their inbox was where projects went to die — proofs buried between newsletter signups and spam, client feedback scattered across three email threads because nobody remembered to reply-all. The studio owner said tracking payments felt like guesswork — invoices sent, half-remembered, followed up on a week late because there was no single place that showed who still owed what. And the account manager said the worst part of their week was the moment a client asked "did you get my note about the logo?" and they genuinely didn't know.
Different words. Same root cause: proofing, feedback, and payment were living in three separate tools that never talked to each other.
The email thread problem
Email is a terrible place to review a design. Attachments get compressed into unreadable JPEGs. Feedback arrives as a paragraph of prose describing where on the page a change should happen, instead of just pointing at it. Version 3 and version 4 look identical in your inbox until you open both and compare pixel by pixel.
We didn't want to build another chat app or another file-sharing tool. We wanted the proof itself to be the conversation — click exactly where the logo looks too big, leave a note right there, and let your client see precisely what you mean instead of guessing from a paragraph of text.
Approval shouldn't be a mystery
The second half of the problem was just as important: once a client approves a proof, that decision should mean something. It should move the project forward, tell your team what to build next, and — when money's involved — tie back to what's been paid and what's still owed. An approval that lives in someone's inbox and nowhere else isn't really an approval. It's a good intention waiting to be forgotten.
That's the whole shape of Mollydob: review, revise, approve, and get paid — one flow instead of four disconnected habits.
Built for studios who'd rather be designing
We're not trying to replace your creative tools. We're trying to remove the administrative tax that sits between finishing the work and getting it approved — so the time you'd spend chasing a reply, resending a file, or wondering if an invoice got lost goes back into the work itself.
That's still the goal, and it's why every feature we build starts with the same question: does this make the gap between "I sent it" and "it's approved" a little smaller?