Polimake

How agencies can integrate freelancers without losing files, context, or margin

A guide to onboarding freelancers into an agency with clear scope, access, feedback, versions, deliveries, and project closure.

· Founder

Founder of Polimake, YouTuber.

Updated:
How agencies can integrate freelancers without losing files, context, or margin

An agency requests a quote for four “simple” videos. Then three formats per video, subtitles, four cameras, and client comments across several channels appear.

The problem is not working with an agency. It is beginning production before defining how context, files, decisions, and money will move.

Assign every role

Identify who writes the brief, supplies material, consolidates feedback, approves, contacts the end client, resolves missing decisions, and archives delivery. If everybody can request changes, nobody controls scope.

Quote the system, not a piece count

Clarify duration, formats, source material, selection, graphics, music, subtitles, channel variants, editable files, review rounds, urgency, rights, credit, dates, and payment. A vertical cut is not free merely because it shares footage with the horizontal version.

Build a minimum onboarding package

Provide objective, audience, deliverables, brand guidance, approved examples, source material, known rights, dates, owners, naming conventions, feedback location, and delivery requirements. Do not open the entire historical archive “just in case.”

Choose temporary or persistent access

A controlled link may be enough for a short review. Recurring collaborators may need accounts with access only to the relevant projects. Polimake supports link sharing and account collaboration with synchronized changes. Confirm exact permissions before designing a sensitive workflow.

A shared creative DAM prevents onboarding from becoming a trail of expiring transfers and attachments.

Consolidate feedback

Do not accept simultaneous changes through email, chat, calls, and client comments. Every request should identify the reviewed version, affected moment or element, desired change, decision owner, and required date. The freelancer should not have to arbitrate the agency's internal disagreement.

Protect margin as work evolves

Track variants, rounds, and time lost to incomplete material. When new work appears, state its impact on cost, date, or another task. Twenty “small” changes form a genuine scope increase.

Deliver so someone else can continue

Include agreed masters and variants, editable files, permitted sources and dependencies, opening instructions, licensed material, the approved version, and known limitations. The agency should not need to reconstruct your computer.

Close access and preserve context

Confirm approval, upload final assets, record rights, remove unnecessary access, preserve useful decisions, and close invoicing and credit.

The relationship works when the freelancer can focus on creating while the agency retains control of the client, context, and archive. Efficiency is not unlimited availability. It is collaboration that does not depend on chasing files or guessing decisions.

Oli Ser, founder of Polimake