G2

Verified User in Design

Mid-Market (51-1000 emp.)

10/22/2026

Guest users or non-business users of the software, not included in G2 scores.

"Clean Deliverable Tracking with Flexible Custom Fields—Ideal for Agency Workflows"

4/5

What do you like best about Swatle?

What I really appreciate about Swatle is how it balances clean task delivery tracking with really flexible custom fields, which is perfect for our design agency’s mix of internal teams and freelance creatives. I’m Pasha Kury, Design-Operation & Project-Delivery Coordinator at Kansas City Creative Collective UG. We’re mid-sized, between 201–500 people, and my plate is full: coordinating client projects, keeping track of creative asset versions, talking to our freelance vendors, managing our studio workflows, and putting together cross-department operational reports every month. I test all sorts of SaaS tools — CRM platforms, document storage, reporting software — so I’m picky about anything that handles deliverable handoffs between our in-house teams and outside contractors.

A good example happened a couple months back on a big brand identity project for a regional retail client. We brought on three freelance illustrators to work on logo variations, brand marks, and supporting graphic assets. Before Swatle, we juggled everything through email threads, Figma comments, and a messy Airtable base. Feedback would get buried, version numbers would get mixed up, and I was constantly chasing people to confirm which round of revisions was client-approved. Now I spin up a dedicated project space in Swatle just for that brand job. I built custom fields tailored to our design workflow: project phase, deliverable version number, client approval status, feedback round, and freelance contract reference. I can invite our external illustrators only into that specific workspace. They can upload previews, log updates, and mark assets ready for our review, but they can’t peek at our other active client accounts, internal budget notes, or unrelated project timelines. That isolation is such a win for us.

I also love how straightforward the milestone automations are. I set simple triggers: once a freelancer marks a deliverable as ready for review, it auto-assigns our senior designer to sign off and sends out a notification. If a milestone is coming due and nothing has been updated, it sends a gentle nudge to the vendor contact automatically. Itcuts down on me sending the same follow-up messages over and over again. The timeline and gallery view work great together too. I can pull up the timeline for our weekly production syncs, then jump straight into the gallery to look at asset previews without switching to another tool.

Swatle isn’t meant to replace Figma or our cloud backup system where we archive final source files, and I don’t treat it that way. It’s just a delivery coordination hub, but it keeps all feedback, version tracking and approval status in one spot. It cuts down the chaos of scattered design files and misaligned revision rounds. That frees up my time to build workflow guides, onboard teams onto new platforms, and pull together our monthly operational reports instead of running back and forth between creatives and account managers for every single asset handoff. Review collected by and hosted on G2.com.

What do you dislike about Swatle?

Our agency relies heavily on Figma, Adobe Creative Cloud libraries, and our centralized cloud archive for all client assets. I was hoping Swatle would plug cleanly into that pipeline, but the available native connections are really bare-bones. It can’t pull live previews linked directly from Figma, and it doesn’t sync version history back and forth. When a freelancer uploads a new mockup round in Swatle, they still have to separately drop the updated Figma link in the comment, and our designers have to jump over to Figma tocheck revisions. There’s no automatic way to tie the deliverable status in Swatle to the actual source file versions. It means two separate sources of truth, which is frustrating when we’re trying to keep our review rounds consistent.

Another thing that bugs me is how clunky its versioning system is. We cycle through tons of feedback passes for brand work, packaging layouts and social assets. Every time we get client feedback, we create a new version. Swatle doesn’t make it easy to group all iterations under one task. You can’t quickly compare round 1, round 2 and the final approved side by side. The only workaround is uploading every new asset as a separate attachment and labeling them manually. A few weeks ago on a packaging project, we went through five feedback loops. By the end, the task was stuffed full of attachments, and it was hard for the account team to quickly find which one was the client’s signed-off version. I ended up adding extra summary notes on every task, which adds more busywork for me.

And one smaller point: the guest user experience has some rough edges for international freelancers we work with. A few of our overseas contractors report occasional timezone confusion on deadlines. The due dates only sh Review collected by and hosted on G2.com.

What problems is Swatle solving and how is that benefiting you?

To start, before we got Swatle, managing deliverables with our freelance creatives was a chaotic mess. I’m Pasha Kury, Design-Operation & Project-Delivery Coordinator at Kansas City Creative Collective UG. We’re a mid-sized agency of 201–500 people, and my job covers coordinating client projects, keeping track of creative asset versions, liaising with outside vendors, maintaining studio workflows, and putting together those monthly cross-department operational reports. I test tons of SaaS tools — CRMs, cloud storage, reporting platforms — so I’m very picky about anything that bridges our internal team and contract designers.

A couple months back, we took on a big brand refresh project for a retail client, with several freelance illustrators handling logo variations and supporting graphic assets. Before Swatle, we were spread across Figma comments, scattered email threads, and a jumbled Airtable board. Revision feedback would get buried, version numbers would get mixed up, and I spent so much of my day chasing people just to figure out what was submitted, what was under review, and what still needed another pass.

Swatle fixed that for us. The best part is the guest access setup. I can spin up a dedicated project workspace just for that client engagement and invite only the relevant freelancers into that space. They can upload asset previews, leave feedback, mark work ready for review, but they can’t peek at our other client work, internal budget notes, or unrelated project timelines. That separation is really valuable for us when working with outside contractors.

I also love its straightforward automations. I set simple rules: once a freelancer marks a deliverable ready for review, it automatically assigns the task to our senior designer and sends out a notification. If a deadline is approaching and there hasn’t been an update, it sends a gentle reminder to the vendor contact. It cuts out all those repetitive check-in messages I used to send every few days. The timeline and gallery views work great side by side too. In our weekly production syncs, I can pull up the high-level timeline for the whole project, then flip to the gallery view to quickly preview individual assets. Review collected by and hosted on G2.com.