“A client project kicks off Monday.. Something that used to take 30 minutes took 30 seconds. They looked at the old way and couldn't believe they'd tolerated it. That was the aha.”
When I'm a client project kicks off monday, I want to run client projects with a clear, consistent structure that doesn't require explanation, so I can keep client communication in one place instead of across email, Slack, and documents.
A small agency owner, studio founder, or remote team lead with 3–20 people who chose Basecamp because they were tired of configuring project management tools. Basecamp's opinionated structure — message boards, to-dos, schedules, docs, campfire — is not a limitation to them. It's the point. They didn't want to design a system. They wanted to use one. They've been on Basecamp for 2–6 years. They've recommended it to other agency owners who are drowning in Notion setups and Jira configurations. Some of them listened.
To make basecamp the system of record for run client projects with a clear, consistent structure that doesn't require explanation. Not aspirationally — operationally. The kind of intention that shows up as a daily habit, not a quarterly goal.
The tangible result: run client projects with a clear, consistent structure that doesn't require explanation happens on schedule, without manual intervention, and without the anxiety of the gap between Basecamp's intentional simplicity and the features competitors have added. basecamp has earned a place in the daily workflow rather than being tolerated in it.
A client project kicks off Monday. The project manager creates a new Basecamp project. They set up the sections: a Welcome message explaining how the project will run, a to-do list for the first sprint, the project schedule, and a shared docs folder. They add the client — two people — and their own team — three people. They post the first message. The client replies by end of day. Nothing is in email. Nothing is in Slack. Everything that matters about this project will live here for the next 4 months. This is how they run every project. It works.
Runs 4–12 client projects simultaneously in Basecamp. Has been using Basecamp for the same account for years — project history goes back to projects completed in 2018. Uses Basecamp's client access feature to give clients a view of their project only. Uses message boards for async updates and decisions. Uses to-dos with assignments and due dates. Reviews Hill Charts weekly. Has a project template they copy for new client work. Does not use email for project communication. Has had to explain this to clients once per engagement. Most clients appreciate it after the first week.
They've stopped comparing alternatives. basecamp is open before their first meeting. Run client projects with a clear, consistent structure that doesn't require explanation runs on a cadence they didn't have to enforce. The strongest signal: they've started onboarding teammates into their setup unprompted.
Not a feature gap — a trust failure. The gap between Basecamp's intentional simplicity and the features competitors have added happens at the worst possible moment, and basecamp offers no path to resolution. They open a competitor's signup page not out of curiosity, but necessity. Their belief — a tool that's calm by design produces calmer work — and calmer clients — has been violated one too many times.
Pairs with `harvest-primary-user` for the project management-to-time-tracking agency workflow. Contrast with `asana-primary-user` and `clickup-primary-user` to map the opinionated-simple vs. configurable-powerful PM tool spectrum. Use with `loom-primary-user` for remote agencies using async video to replace status meetings inside Basecamp projects.