G2

Samantha V.

Project Manager

Marketing and Advertising

Mid-Market (51-1000 emp.)

7/11/2026

"Basecamp keeps projects simple, organized, and easy to follow"

4.5/5

What do you like best about Basecamp?

I've used more powerful project management tools, but a lot of them start feeling heavy the moment you bring clients or external people into the process. Basecamp is different in that sense. Clients usually understand pretty quickly where to leave comments, where to find files, and which tasks are still open. That quick adoption saves a lot of unnecessary explaining. I also haven't run into any major issues that made me want to look for another platform. Most of the questions we've had are easy to solve with clear documentation or helpful support responses. On the Pro Unlimited plan, priority support and personal onboarding can also make a real difference when you're moving a full team or several clients into the same workspace. With Basecamp 5, subtasks have been a nice improvement too. Before, some tasks became too broad and we had to break them down manually in a way that felt a bit messy. Now it's easier to keep the main task clear while still tracking the smaller steps underneath it. Review collected by and hosted on G2.com.

What do you dislike about Basecamp?

I wouldn’t say Basecamp is trying to be the tool for every kind of project management. If you need advanced controls, complex dashboards, or detailed resource planning, it can definitely feel a bit limited. But if what you’re looking for is clarity, strong communication, and something people can adopt quickly, it delivers that really well. Review collected by and hosted on G2.com.

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

We had a client change several priorities in the middle of a project that was already moving. It wasn't a massive change, but it was enough to affect the schedule, approvals, and some content we had already prepared. In other projects, that kind of update usually turns into a long chain of emails, screenshots, and messages asking what stays, what moves, and what needs to be redone. This time, we opened a thread in Basecamp, explained the change, kept the new decision there, updated the related To-dos, and uploaded the correct version of the files that were still valid. The useful part was that nobody had to guess what had changed. The designer checked the thread before touching the assets, the client confirmed everything in the same place, and the content team could see exactly which deliverables were still moving forward. The following week, when someone asked why a task had been moved to a different date, we didn't have to rebuild the whole conversation from memory. The answer was already inside the project, with the full context around it. Review collected by and hosted on G2.com.