Custom B2B customer onboarding software

The user list has arrived. The import has to wait

Say a client is starting to use a data reporting service. They have sent the list of people who will use it. Access to the data source, though, is still waiting for someone in their IT department. The onboarding team has the user list, and cannot yet try the import.

The client should be able to see that their file arrived, and find the open request for access to the source. Next to that request they need to know who should handle it and why it is needed. The person leading the rollout on the client's side can then go to their own IT without another email to the supplier asking about progress.

The onboarding team needs to see, next to the import attempt, that it is waiting for access from the client's IT. That is a dependency between tasks: finishing one lets the other start. When the IT person replies, the onboarding specialist checks the access and can try the import. The coordinator finds the answer on the same matter, without chasing both sides.

Such a view does not need an elaborate panel. For each step, a clear description, the person responsible and what we are waiting for may be enough. The biggest change is in the coordinator's work: instead of rebuilding the status from correspondence, they go back to the same matter the client sees.

Your current tool may be enough for B2B customer onboarding

Dependencies between tasks are available in ready project software. Asana describes marking tasks as blocking another task or waiting on it. When all blocking tasks are complete, the person assigned to the next task gets a notification. Whether the feature is available depends on the plan (Asana's documentation on dependencies).

Before you buy an app, walk through the example above in the system you use. Will the client see that the list arrived and the access matter is still open? Will the onboarding specialist find the reason for waiting next to the import? If so, the work may mainly be tidying the tasks and agreeing who confirms they are done. Having a dependency feature will not create that order if the team records all preparation as one task called “materials from the client”.

Also look at the project from the client's account. Asana lets you work with guests, who see the content shared with them. Sharing a single task gives access to that task, while sharing a project covers all of its tasks (guest permissions in Asana). If the team also writes internal notes there, the way of working has to match what the client should actually see. Look at this view from a guest account.

When the contact on the client's side changes

Go back to the access request. If the IT person passes the matter to a colleague, the new contact needs to see what was requested and what has already been agreed. The coordinator should be able to hand them the open task with its conversation, keeping the earlier answers. The team is still waiting for access to the same data source; a change of person should not force the matter to start from scratch.

Agree with the client whom to hand the task to and whether the previous contact is still part of the rollout. If they are leaving the company, their access has to be removed. The work history should stay with the rollout, so their successor can carry on. Allow for this ordinary situation when choosing a tool, especially when today the whole conversation lands in one mailbox.

We describe work on a shared status and unanswered questions in the offer for AI tools for team collaboration. Involving the client also requires deciding which tasks and conversations may be shared with them. Searching documents alone will not handle the dependency between data access and starting the import.

An extension or a separate app

If the team works well in its project system and the client gets lost in its interface, you can consider a narrow view for the client. It would show their open requests and let them reply on the right task. Internal planning could stay in the current tool. Before choosing such an extension, check whether the available connection will carry replies and task changes across. If the coordinator retypes them by hand, part of today's work remains.

A separate app becomes a sensible candidate when launching the service means combining the client's actions with information from several systems, and current tools do not handle it well. The scope can be limited to the time from the start of onboarding to the service being ready. Sales and later ticket handling can keep running in the products you use. We describe the wider decision on a customer portal connected to the CRM separately.

When comparing offers, also count the work after the tool goes live. Someone on your side will update the onboarding flow when the service changes. The app's supplier needs an agreed scope of support for the connections to other systems and a way of handling errors. Helping clients with access remains part of the service too. These duties affect the cost of your own tool, so they belong in the comparison with a ready product.

When moving to a new tool, onboarding in progress needs the most attention. Open requests should keep the clients' replies and the dependencies, so the team knows where to carry on. Also agree on exporting the history later, access to the code and handing upkeep to another supplier.

A conversation about an onboarding that got stuck

Syntalith builds custom apps. A possible first scope is a view of open requests to the client, linked to the tasks waiting for their reply. On such an example you can judge whether configuring the current product is enough, or whether a simpler interface and an extra connection are needed.

For the first call, it is enough to describe the last onboarding where the client thought they had sent everything and the team was still waiting. Tell us what was missing and where the coordinator recorded the later arrangements. A custom app or automation at Syntalith costs from €3,000 net (pricing).

What a customer onboarding tool costs and when it pays back

Where to start

In the free process review we choose one process and count the team's volume and working time, and within 2 working days you get a written summary with a price. We build as part of AI apps, and we price maintenance separately.