Agency collaboration without the extra rounds
The expensive part of agency work is round four. Melp puts every stakeholder's feedback in one thread against one current version, so contradictions surface early.
One campaign, and where the margin actually goes
In most of these phases the friction is a coordination artefact rather than a creative disagreement — which is why it is fixable.
Brief
Email and attachmentsA brief document, then three clarifying email threads with different subsets of stakeholders. The agency starts work against a composite nobody has confirmed.
In MelpThe brief lives in the shared workspace with version history, and clarifications happen in one thread all stakeholders can see.
Review rounds
Email and attachmentsFive stakeholders comment separately. Two contradict each other, and nobody is certain which version each comment refers to.
In MelpAll feedback lands in one thread against one current version, so contradictions are visible to the stakeholders themselves and resolved on the client side before work resumes.
Asset handover
Email and attachmentsFinal files sent by transfer link. Two years later the brand needs the working files and the agency relationship has ended.
In MelpDeliverables and working files live in the shared brand folder throughout, so handover is a permissions change rather than an archaeology project.
What makes agency work run cleanly
Each addresses a specific, recurring cost — not a general aspiration about alignment.
Multi-client operations, and the freelance bench
An agency has an access problem its clients rarely think about: freelancers touch client work, which makes this a three-party relationship rather than a two-party one.
Structural separation between client accounts
The professional risk in an agency is material from one client appearing in another's context. Folder discipline manages it until the week someone is under deadline pressure.
In Melp: each account is a separate workspace with its own search surface.
Freelancers scoped to the work, not the account
A freelancer engaged for one campaign should not gain access to a client's whole history, and the client is entitled to know who is working on their material.
In Melp: they are added to specific topics, with membership visible to all parties.
Client-visible and internal work genuinely separated
Internal discussion about resourcing or margin must not sit with client-facing work — and maintaining two parallel systems is how things get posted in the wrong one.
In Melp: topic membership keeps internal threads invisible inside the same workspace.
Melp is not a digital asset management system or a project-management tool. Rights management, campaign taxonomy and resource scheduling belong in those.
Questions from brands and agencies
Including how this coexists with DAM, project management and proofing tools.
Related use cases
Agency relationships sit close to several others.
Consolidate the next review round
Put one campaign's review into a shared workspace and count the rounds. It is the cheapest experiment available to either side of an agency relationship.