Jump to section
Your board says everything is on track. Your inbox says otherwise.
"Quick one – what's our status?" "Who's doing the security review on our side?" "Can you resend that file?" Running customer onboarding in monday.com, Asana or Notion means answering these by hand, every week, for every client – because the plan lives in a tool they were never meant to open.
Most B2B teams run customer onboarding and implementation in the same place they run everything else – a monday.com board, an Asana project, a Notion database, sometimes a spreadsheet. It works for your work. It stops working the moment the work isn't yours: the customer's tasks, the customer's decisions, the customer's data.
Teams bridge that gap with one of three workarounds: keep the board internal, share a read-only view, or invite the client in as a guest. Each fails for a different reason. You are almost certainly running one of them right now.
Why an internal monday.com or Asana board fails at customer onboarding
This is the default. By a long way.
The implementation plan sits on your side. The customer gets a recap email after each call – or they get nothing, and wait for you to tell them what's next. You are the router. Every status update, every reminder, every chase, every file transfer is a message you write and send by hand.
Nothing the customer does is captured anywhere. You find out a task is blocked by asking. You find out a file is missing by asking. You find out they've gone quiet by… asking.
Picture this. It's Thursday. The kickoff was two weeks ago. Your board says "awaiting SSO details." You don't know if anyone on their side has even started. So you write the same email you wrote last Thursday.
The plan is only as current as your last message. And the customer has no single place to go when they want to know what's next. They search their inbox. They guess. Or they wait for you.
That is the post-sale client experience for a lot of B2B SaaS teams, marketing agencies, and professional services firms. If you have ever run an implementation project in Asana or on a monday.com board, you know the shape of it: tidy from your desk, invisible from theirs. From the client's side, it's just you, writing emails.
Does a read-only monday.com view or shared Notion page work as a client portal?
No – a read-only view is not a client portal. It doesn't notify anyone when something needs their input, it doesn't chase an overdue task, and you cannot tell whether the customer ever looked, so a client who has quietly gone dark looks identical to one who is on track.
Most teams try it anyway. You publish a board view, or a shared Notion page, so the customer can "check progress."
They opened it once. On the call where you showed it.
I know what you're thinking. "At least they have a link."
They do. They also have a view that reads as your internal backlog: your task names, your statuses, your shorthand, your other clients' vocabulary leaking through a filter you forgot to apply. Nobody outside your company was meant to read it. They can tell.
A digital portal for B2B project delivery that nobody opens is not a portal. It's a screenshot with a URL.
Should you invite clients into monday.com, Asana or Notion as guests?
No – and guest access is the workaround that feels most like the fix. That is the guest-access trap: teaching a new customer your project management tool before you can teach them your product, in the exact window where you were trying to build momentum.
The friction is specific.
Their IT stands in the way. A new external account means a vendor request, a security review, sometimes SSO provisioning – on their side, on their timeline, for a tool that isn't yours and isn't theirs. Some customers will simply say no. That is a reasonable answer. Especially in fintech, tax and accounting, and any enterprise where a new SaaS login is a procurement event.
Seats and licences. Guest access is limited or paid depending on the plan, and the limits differ per tool. A typical B2B implementation pulls in 4-6 stakeholders on the customer's side – and the plan limit tends to show up right around the fourth one. You find this out mid-project, when someone new needs access and the plan says no.
Complexity. These tools are built for people who live in them daily. Your customer will open it three times over six weeks. The learning curve never pays back.
Time to value moves the wrong way. Every day spent getting a customer into your PM tool is a day not spent getting them to their first real outcome. That is the opposite of what time to value is supposed to do.
The first experience your new customer has of working with you should not be admin for a tool they didn't buy.
What running customer onboarding in an internal PM tool costs you
Three things, and they compound.
Momentum after signing dies in the gap. The customer said yes. Then they wait for you to translate the plan into an email. Those dead weeks are exactly how customers lose momentum after signing.
You have no engagement signal. A quiet inbox looks the same as a busy week. You cannot see who opened what, so you cannot catch a stalled onboarding until the go-live date has already slipped. Tracking new client progress from your own board only tells you what you did.
Only one side holds the plan. If your champion is out, or leaves, the implementation timeline lives in your tool and their head. Neither is a place the next person can open. Engagement during onboarding is supposed to be visible. In this setup it isn't.
Are you starting to see why the board can look healthy while the client project workflow is already stuck?
What a real client onboarding portal needs to do
Forget tools for a second. What does customer onboarding actually require from a client-facing surface?
- Opens on a link. No account. No password. If the customer needs an account, you've already lost the ones whose IT says no.
- Looks like their project, not your backlog. Their branding, their language, their tasks separated from yours.
- Sends its own reminders. Chasing isn't a person's job.
- Tells you whether they opened it and what they completed. Silence becomes a signal you can see.
- Syncs with the CRM. Onboarding status lives where the account already lives.
- One per customer. Not a shared board with a filter. A surface built for that relationship.
A client-facing portal that still dumps every account into one shared project is just a prettier version of setup one.
This is the job Valuecase is built for. Each customer gets their own branded Space – the single place that customer opens to get onboarded. Plan, tasks, forms, files, behind one link. No login. Your team works in the same Space and sees who opened what.
If what you actually want is a branded room the customer can work in, start with how to create a customer onboarding portal. If you're still in sheets and threads, the honest teardown is replacing spreadsheets and email for onboarding.
Reminders and follow-up don't have to be you. An agent can chase customers on the exact open task, or score onboarding risk across the portfolio. The full set lives on the AI use-case hub.
Do you need to replace monday.com, Asana or Notion? (No.)
Monday.com, Asana, Notion, ClickUp and Trello are strong at the internal half. Resourcing. Capacity. Sprint work. Time tracking. Billable services delivery. Everything your team does among themselves.
Keep them for that.
Client implementations fail in those tools because customer onboarding is the one part of delivery that isn't internal. Internal execution stays in the PM tool. The client-facing portal is its own surface. And the two stay in sync.
You don't need to rip out the board your delivery team lives in. You need to stop asking it to be a portal.
FAQ
Can clients access Asana?
Yes, but only as guests or members with an Asana account. You can invite someone from outside your company domain for free, but they still need to create an account, log in, and learn a tool they didn't choose – before they can see their own onboarding plan. For a customer who needs two quick answers a week, that is a lot of overhead for very little value. It is the guest-access trap in miniature.
Can a client access a monday.com board without a paid seat?
Yes, within limits. monday.com offers free read-only viewers and guest access to shareable boards on its mid and upper tiers – exactly what's included shifts by plan, so check the current tiers. Even when it works, the client still lands in your board: your columns, your shorthand, your other work nearby. Free access is not the same as a portal built for them.
Is a Notion client portal secure enough for enterprise customers?
A shared Notion page can be locked down, and Notion supports guest access with a cap on guest count that varies by plan. But enterprise buyers don't evaluate "can we share a page." They evaluate vendor review, SSO, and whether this is a tool they already approved. Many will refuse a new workspace login for a project they didn't buy. That's a process problem, not a checkbox problem.
Can Asana send a reminder to someone outside my company?
Only if they're in the project. Asana allows free guests – anyone with an email address outside your company's domain – but a guest still needs an Asana account and has to log in for those notifications to mean anything. A reminder that only fires if they already live in your tool is not a reminder for a customer who opens email three times a week.
What should you use instead of monday.com or Asana for customer onboarding?
A purpose-built customer onboarding platform – one that gives each customer their own branded portal instead of a seat in your internal tool. Valuecase does exactly this: each customer gets their own Space with the implementation plan, tasks, forms and files behind one link, no login required, plus engagement tracking and automated reminders. Keep the PM tool for internal delivery and let the two sync.
We track client progress in a spreadsheet – what replaces it?
A shared, per-customer surface both sides work in: the plan, their tasks, forms, and status in one link, with reminders and a signal when they go quiet. That's the replacement for spreadsheets and email – not a prettier internal tracker.
Should the customer see our internal tasks?
No. They should see their project: their tasks, their dates, their next step. Your resourcing, your QA, your other accounts stay in the PM tool. Mixing the two is how a "shared view" starts reading like a backlog they weren't invited to.
Give each customer their own Space. Start a free trial of Valuecase or book a demo.
