Should I create one Project per client or have all clients in one single Project?

I am considering using Asana for my account mangement workflow. I manage a portfolio of 20-25 accounts for a highly technical software company that requires a lengthy “implementation phase” lasting anywhere between 3-6 months. During this phase, there are various “mini projects” we will work on, like Migration, Data Structure, Feature Implementations etc. Each of these mini projects will have their own follow up tasks and milestones etc. and all are required before a “Go Live” milestone.

With this is mind, I am wondering if I should have 20+ individual Projects with different sections or if I should have one single Project containing sections for each client.

Does anyone have experience using Asana for a multi-client management workflow like this?

I suggest grouping the projects by team. You can get “teams” activated by creating an organization workspace. This does not require a paid subscription, only a corporate domain e-mail. This will enable you to create projects relating only to that client, as well as share each client or project with specific members or your organization. (optional) I use the team groups for my roles or areas of focus and don’t share with anyone. It’s up to you how you want to utilize it. :slightly_smiling_face:

2 Likes

Hi @Barnett_Williams1,

I do similar type of work using Asana.

Each client, is a new team. Then I may have just 1, or multiple projects per client.

It does make a long sidebar list, which I can help organize by adding open projects as a favorite so they display at the top.

2 Likes

We use Asana for several workgroups in our law firm. We have some workgroups that use separate projects for each client and others that do one project for their entire portfolio.

I suggest grouping the projects by team. You can get “teams” activated by creating an organization workspace. This does not require a paid subscription, only a corporate domain e-mail. This will enable you to create projects relating only to that client, as well as share each client or project with specific members or your organization. (optional) I use the team groups for my roles or areas of focus and don’t share with anyone. It’s up to you how you want to utilize it. :slight_smile:

@Lindsay_Kirsch thanks for your reply! Out of curiosity, what do your projects look like within each client (team)? Do you use Kanban, or lists? Generally wondering the template style you use assuming you on-board and manage client implementations. Thanks!

1 Like

It really depends on the client.

I keep one project that I call “master project” for each client, and it’s private to me. This is where I keep track of next contract renewal dates, invoice dates, as well as my time tracking.

Each project is then it’s own project. A retainer is a project.

I use list style - mostly out of preference. I just don’t like kanban as much.

I help keep track of active projects (since you can’t archive workspaces) but making them favorites so they always stay on top.

1 Like