G2

Verified User in Computer Games

Mid-Market (51-1000 emp.)

10/21/2026

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

"Clean, Focused Partner Delivery Workflows with Great Guest Access and Automations"

4/5

What do you like best about 5day.io?

Honestly, what I love most about 5day.io is how clean and focused it keeps our partner delivery workflows, without all the bloated extra features that just clutter things up. I’m Konik Rozier, Production & Partner Project Coordinator over at San Francisco Interactive Gameworks Inc. Our studio sits at 51–200 people, and my whole job is keeping cross-team production moving, talking to our external art and animation partner studios, tracking asset handoff milestones, and organizing all our internal design docs. I spend a lot of my time testing out SaaS project trackers, CRM tools, and collaboration platforms, so I’m picky about anything that’s going to sit between our internal dev team and outside vendors.

We had a great example a couple months back when we were coordinating character asset deliveries from an overseas partner studio for our new indie title. Before 5day.io, we were bouncing between Slack threads, shared Google Docs, and a messy Trello board. Feedback would get buried, milestone dates would drift, and I’d constantly chase both our internal artists and the external partner to figure out what was done, what was waiting on review, and which assets still needed revisions. Now I spin up a dedicated workspace in 5day.io just for that partner. I set up our delivery milestones: concept lock, base mesh handoff, texture pass, rigging submission, final approval. The best part is the guest access; I can invite the external studio into only that project space. They can see their assigned tasks, upload asset previews, drop feedback, and mark deliveries ready for our review, but they can’t peek at our other game projects, internal roadmap notes or sensitive scheduling stuff. That separation is huge for us.

The built-in workflow automations also save me so much busywork. I set simple rules: once a partner marks an asset pack as submitted, it auto-assigns the review task to our lead artist and shoots a notification out. If a milestone is coming up in two days and nothing’s updated, it sends a gentle reminder to the partner contact automatically. No more me manually sending check-in messages every few days. The timeline and board views work really well side by side too. I can pull up a high-level timeline for the whole production meeting, then flip to the board to dig into individual asset statuses quickly.

I also appreciate that it doesn’t force us to rebuild our whole pipeline to fit the tool. A lot of project trackers I test are built for marketing teams and don’t handle external partner collaboration well at all. 5day.io lets me tailor task fields for game dev: polygon budget, asset variant, version number, review round. Our team picks it up super fast, and the onboarding is straightforward when I roll it out to new contractors or partner teams. Review collected by and hosted on G2.com.

What do you dislike about 5day.io?

The first thing that bugs me is how rigid its custom task fields are. For game asset work, we need to track very specific details: polycount limits, texture map sets, LOD versions, review round numbers, and which platform the asset is targeting. I was hoping I could build flexible fields that our partners can fill out consistently for environment props, character rigs, and VFX passes. But the field types are limited, and there’s no easy way to set conditional logic. For example, if a task is a character rig, I want it to automatically show rig-specific fields, and hide the ones meant for static environment assets. 5day.io can’t do that. So we end up with a ton of irrelevant fields visible on every task card, or we make separate templates for every asset type, which gets messy fast. A few weeks ago, we kicked off a big creature animation package with our overseas partner, and half their team kept filling out the wrong fields because the form didn’t adapt to what they were delivering. It created inconsistent records and extra cleanup work for me.

I also find the notification system inconsistent, which is risky for us with tight delivery schedules. I set up alerts for when partners submit assets or leave feedback, but sometimes those messages get delayed, or they only go to me and not our internal lead artist who’s supposed to do the review. Other times it spams everyone on the project for tiny comment updates that don’t need a notification. There’s no fine-tuned way to set rules: like only notify reviewers when a delivery is marked “Ready for Final Approval”, and skip alerts for draft notes. I end up double-checking the board multiple times a day just to make sure nothing slipped by without anyone noticing.

And one more small thing: it doesn’t play smoothly with the asset pipeline tools we already rely on. We use ShotGrid for our main version control and asset tracking. I was hoping for a clean two-way sync, but the native integration is really basic. It only pushes simple task names back and forth, and won’t carry over asset version links or review notes. That means our artists still have to copy feedback manually between 5day.io and ShotGrid. It doesn’t break the workflow entirely, but it defeats a lot of the reason we wanted a partner hub in the first place. Review collected by and hosted on G2.com.

What problems is 5day.io solving and how is that benefiting you?

Before 5day.io, managing our outside studio partners was a total headache for production here at San Francisco Interactive Gameworks. I’m Konik Rozier, Production & Partner Project Coordinator. We’ve got a team of 51–200 people, and my job is lining up cross-functional production work, keeping in touch with external art and animation vendors, tracking asset delivery milestones, and keeping all our project docs organized. I test tons of SaaS tools all the time, so I’m pretty picky about anything we use to bridge our internal team and outside collaborators. Back before 5day.io, we were juggling updates across Slack, email threads, and a messy mix of spreadsheets. Partner feedback would get buried, deliverydates would drift out of sight, and I was stuck playing messenger nonstop between our devs and overseas studios. If I needed to pull up a history of revisions for a character or environment asset, I’d have to dig through weeks of messages. That’s the main pain 5day.io helped us fix.

What works really well for us is that it’s built specifically for sharing progress with external partners, without exposing our whole internal production stack. When we onboard a new vendor for art or animation work, I spin up a dedicated project space just for them. I can set up milestones like concept approval, base mesh delivery, texture pass, and final sign-off, then send them guest access limited only to that workspace. They can upload asset previews, leave feedback, mark work ready for review, but they can’t peek at our other game projects, internal scheduling notes, or confidential roadmap stuff. That separation was a huge win for us. We ran a big creature animation contract with an overseas partner a couple months back, and this setup kept all their deliverables and review comments in one clean spot. No more hunting through endless chat threads to find which revision we signed off on.

I also like the simple automations and board/timeline views. I set up basic triggers so the right internal reviewer gets notified once a partner submits an asset pack. The timeline view is perfect for our weekly production syncs, so the whole team can quickly see which deliveries are on track and which are slipping. It’s easy for partners to learn too, so I spend way less time walking new vendors through how to use it compared to other project tools I’ve tested.

It’s not replacing ShotGrid, our main asset and version control system, and I never expected it to. It’s just a lightweight hub for our partner workflows. But it cuts down so much of that back-and-forth messaging and chasing updates. That frees me up to keep testing new collaboration tools, maintain our internal documentation, and keep our internal teams aligned, instead of spending most of my day relaying asset feedback back and forth between studios. Review collected by and hosted on G2.com.