Set Up Asana for Consultants: Client Portfolios That Hold

Consulting is the one PM use case where the org chart and the software model disagree. Your client is not a department — they are an outside party who must see progress but must not see your other engagements, your rates, or your internal notes. Almost every Asana setup failure in a small consulting practice traces back to modelling the client as a project instead of as a boundary.

This guide builds the boundary first. It is written for a solo consultant or a firm of two to eight people, and it assumes you have already decided on Asana — if you have not, our Asana review and the agency PM software roundup are the two pages to read first. If you are weighing Asana against ClickUp specifically for client-facing work, that comparison exists too: Asana vs ClickUp for agencies.

TL;DR

• Model each client as a Portfolio, not a project. Portfolios hold projects; the client boundary is what keeps engagement A invisible to client B.
• Three project types per engagement — Scope & Proposal, Delivery, and Closeout — beat one giant project. The delivery project is the only one your client ever sees.
• Asana’s published prices are Personal $0, Starter $10.99/user/mo, Advanced $24.99/user/mo billed annually, or $13.49 / $30.49 billed monthly. The Advanced upgrade buys portfolios across teams, goals, and workload — of which portfolios are the only thing a small consulting practice usually needs, and are available on Starter.
• Unlimited free guests on paid plans is the single feature that makes Asana the default consulting tool. That is what lets you invite a client into their project without paying a seat for them — provided the client’s email domain differs from yours.
• Best for: 1–8 person consultancies with three or more concurrent clients and any client who expects to see progress without a weekly call. Skip it if: you bill hourly and need timesheets integrated with invoicing — that is Avaza or Paymo territory, not Asana.

Step 0: settle the plan before you build

Get this right and everything after it is structure; get it wrong and you will rebuild in month two.

Plan	Price (billed yearly)	Price (billed monthly)	What consultants actually use
Personal	$0 (1–2 people)	$0	Task lists, one project at a time. No guests beyond a handful.
Starter	$10.99 / user / mo	$13.49 / user / mo	Portfolios, timeline, unlimited free guests, AI included
Advanced	$24.99 / user / mo	$30.49 / user / mo	Everything in Starter plus goals, workload, advanced reporting, cross-team portfolios
Enterprise / Enterprise+	Custom quote — Asana does not publish these prices	—	SAML, SCIM, data residency

Verified against Asana’s official pricing page on 2026-10-24. Prices are per user per month in USD; the annual figures reflect the 18% annual discount Asana advertises.

The team-view decision: if you are a solo consultant or a two-person practice, buy Starter and stop. The correct reason to move to Advanced is not “more features” — it is that you are running workload planning across people who report to you, or that you have a client demanding goal-level reporting. A consultant billing $150/hour who spends $14.99/user/month extra on workload views for a team of two has bought a reporting layer for a firm that does not have a resourcing problem yet.

Where Advanced does earn its price: a five-person consultancy with three consultants sharing delivery capacity across eight engagements, where over-booking is the actual business risk. At five seats the delta is $75/month, which is less than one hour of billable time. That is the honest test — is the Advanced delta smaller than one hour of your billing rate per month? If yes, and you have real resourcing contention, buy it. If no, do not.

Step 1: build the client boundary first

Before creating any project, create the container that defines the client:

1. Create one Portfolio per client, named for the client’s legal name (Acme Industrial), not the engagement (Acme Q4 Ops). Portfolios are the client record; engagements come and go.

2. Set the Portfolio owner to you. Portfolios are internal by default. Clients will see projects you explicitly share with them, and nothing else.

3. Keep a single “Client Directory” project in a Practice team. That project holds one task per client with your standard fields: account owner, contract end date, billing model (retainer / fixed-fee / hourly), and renewal date. This is the only place you should ever need to look to answer “who are we working for and when does it renew.”

Two things this buys you that a folder-per-client does not:

• A portfolio rolls up status across engagements. When Acme has three live projects and you need one sentence for the Monday call, the portfolio view is the sentence.
• The client boundary is explicit. Sharing is a deliberate act per project, which means the default failure mode is “client sees nothing,” not “client sees everything.”

Step 2: three project types, not one

Use Asana’s project templates to standardize the three shapes every consulting engagement takes. Build each once, then instantiate.

Project type A — Scope & Proposal (internal only)

Sections: Discovery → Draft → Internal Review → Sent → Decision.

The value here is not task tracking; it is the decision log. Put the final scope, the assumptions, and the exclusions in the project overview. When a client later asks “why isn’t X included,” you have a dated answer one click away, inside the same tool where the delivery project lives.

Project type B — Delivery (shared with the client)

Sections: Kickoff → In progress → Client input needed → Review → Closed.

Four rules make this project worth sharing:

1. One section named exactly “Client input needed.” This is the highest-leverage field in the whole setup. Every engagement where the consultant is blocked waiting on the client should be visible as a number, and this section is that number. In the weekly call, “how many items are sitting in Client input needed” is the question that replaces twenty minutes of status narration.
2. Custom fields named for the client’s language. Not “Priority: P1/P2/P3” — use “Impact: High/Medium/Low” if that is how the client speaks. The client should never have to learn your vocabulary.
3. Every task has an owner. A shared project where tasks are unassigned reads, to a client, as a project where nobody is responsible. If a task is on the client’s side, assign it to a guest.
4. Milestones carry dates; tasks carry durations. Milestones render on the timeline as diamonds and are what a client actually tracks.

Project type C — Closeout (internal only)

Sections: Deliverables accepted → Invoice → Retrospective → Archive.

This is the project that pays for itself twice. It is where you remember to invoice, and it is the only place where “what did we learn on this engagement” survives to the next one. Without it, closeout is an email thread and a memory.

Step 3: guests — the economics that make Asana the default

Asana’s pricing page states the mechanic directly: “Unlimited free guest seats let clients and contractors collaborate without increasing your license count.”

That sentence is worth reading carefully, because it has a boundary:

• A guest is someone outside your email domain, invited to specific projects. They are free and unlimited on paid plans.
• A member is someone in your domain with workspace access. They consume a paid seat.
• The same person can be a guest on one project and invisible everywhere else, which is exactly the consulting model.

Practical rules:

Invite the client to the Delivery project only. Never to the Practice team, never to the Scope project. Asana guests see the projects they are invited to and their own tasks; a guest who can navigate to a portfolio learns more about your business than you intended.

Use the client’s own domain, always. If a client insists on using a personal Gmail, that still counts as external and remains a guest. What breaks is inviting them with a @yourfirm.com alias “for convenience” — that makes them a member and a paid seat.

Decide what “done” means before inviting. A guest who can comment and complete tasks is a collaborator. A guest who needs only to read can be given comment-only or view access, which keeps the Delivery project’s activity feed from filling with client-side noise.

For the maths on a real practice: three consultants on Starter at $10.99 = $395.64/year, plus unlimited guests at $0. Ten concurrent clients cost you nothing extra in seats. Compare that to any tool that charges per external collaborator and the argument is over before it starts.

Step 4: the weekly rhythm that keeps it honest

Structure without a rhythm decays in three weeks. The minimum viable rhythm for a small practice:

• Monday, 15 minutes, your own portfolio view. One row per client, status rolled up. Decide which two clients need attention this week; ignore the rest.
• One shared update per client per week — not a call, an Asana project status update. Asana’s project status lets you mark On track / At risk / Off track with a short note, and it is visible to guests. This replaces the “just checking in” email and creates an audit trail that is useful at renewal.
• Friday, 10 minutes, Client input needed across all delivery projects. Every item sitting there is a client dependency, and a client dependency that is three days old is a scope-creep conversation waiting to happen. Save the list; it is your evidence if you ever need to renegotiate a deadline.

Warning on the automation temptation: do not automate status updates. An auto-generated “On track” every Monday trains clients that your updates carry no information. Automate task assignment and due-date reminders; keep the judgment human.

What this setup does not do

Three gaps a consultant will hit, stated plainly so you can plan around them:

• No timesheets and no invoicing. Asana has no native billable-hours model. If your revenue depends on tracking hours against a rate and turning that into an invoice, you will run Asana plus a time tool, and you should price that second subscription into the decision. Our time tracking in PM tools guide covers the integration patterns; Avaza covers the all-in-one alternative.
• No branded client portal. Asana guests use Asana’s interface with your project’s colour. If a client-facing branded portal is a contractual requirement, that is a different product class.
• No contract or rate fields with permissions. Store commercial terms in your CRM or accounting system, not in Asana. Every field in a shared project must be safe to show a client.

Conclusion: the build checklist

A consulting practice’s Asana, built in about two hours:

1. One Portfolio per client, named for the client.
2. A Client Directory project with renewal and billing-model fields.
3. Three project templates: Scope & Proposal, Delivery, Closeout.
4. Delivery project has a “Client input needed” section and client-facing custom fields.
5. Client invited as a guest on Delivery only, on their own domain.
6. Monday portfolio scan, weekly project status update, Friday dependency review.

If your practice is closer to an agency with creative review rounds, our Asana workflow for agencies covers proofs and approval cycles; if you are evaluating the wider consulting-firm tool landscape, best PM software for consulting firms compares Asana against Rocketlane and Kantata, both of which are built for the services-delivery model Asana sits adjacent to.

---

How this content was prepared

Transparency note: This article is based on Asana’s official pricing page, publicly available product documentation, and our editorial analysis. It is not sponsored, and no vendor paid for or influenced the recommendations.

We do not claim to have independently tested every feature end-to-end, and this guide is not a record of a hands-on build we ran. Where a step reflects operator judgment — the three project types, the “Client input needed” section, the Starter-versus-Advanced test — it draws on published documentation and editorial analysis rather than a comparative hands-on trial. Pricing is dated in the metadata above.