Skip to content
Which Client Portal

Guide, 10 Nov 2026, read 10 Nov 2026

The first 30 days after signature: a week-by-week plan a portal can hold

See the rankingAll guides

Why 30 days

The first month is where an onboarding either gets momentum or loses it. The buyer signed because of a plan. If the plan is not visible and moving within a few weeks, the buyer's attention goes back to its own backlog.

The weeks below are a working template written for this site, not a vendor standard. Adjust the days to your product. What does not change is the principle: every item has an owner and a date, and the customer can see both.

Before day one: the handoff

The handoff happens before the first customer call. Flowla's onboarding page says that when a deal closes won in the CRM, its agent builds the onboarding plan from the sales call notes, ready in the room before the kickoff call. Where your portal does not do that, the account executive does it by hand in the 48 hours after signature: the deal goals, the stakeholder list, the commitments and the go-live date go into the customer's plan.

The weight for this step is the heaviest on the site. See what passes from sales to onboarding for the twelve items.

The four weeks

Each row is explained below.

WeekGoalPortal feature to lean on
1Kickoff held, owners named on both sides, plan agreedSecure link in the welcome email (GUIDEcx), shared plan the customer can edit (Dock)
2First customer tasks done: access, data, security formsTask reminders before, on and after the due date (Dock); nudges to the right person (Flowla)
3Configuration or first delivery complete, first review callCall summaries and next steps added to the room (Aligned); overdue flags (GUIDEcx)
4Go-live or first named result, plus a surveyCSAT at milestones (Rocketlane); customer-completed tasks syncing back (HubSpot)

Week 1: kickoff and owners

GUIDEcx says a customer reaches its portal by a secure link in the project welcome email, with no login required. Dock's onboarding page says customers can update implementation plan tasks, comment and upload files in the same plan. Together those describe the aim of week 1: the customer opens the plan on day one without asking for access, and edits it.

Put one name on the customer side against every task due in the first two weeks. A task owned by "the customer team" is owned by nobody.

Weeks 2 and 3: tasks the customer has to do

Most delays in weeks two and three are customer tasks: access, data, a security review. Dock's help center says reminder notifications can be set before, on or after a due date. Flowla says its agent nudges the right person before a call or deadline slips. Aligned's help center says that after each call, a summary and next steps from the CRM are added to the room, and that clients can be emailed when a summary is added.

Aligned says its Meetings tab does this; the feature reads the call summary on the linked CRM record, not the recording. Say "call summaries" to your customer, not "calls", so no one expects a recording in the room.

Week 4: first result and first survey

By day 30, one thing the buyer named in the deal should have happened, or a dated reason should be recorded. Rocketlane's pricing page lists built-in CSAT surveys at project milestones, which fits a short survey at the end of week 4. HubSpot's help article says customers can view and complete onboarding plan tasks in the customer success space of the portal, with changes syncing both ways, on Service Hub Professional and Enterprise.

If the first result slipped, write the new date into the plan the same day and tell the sponsor. A date the customer can see and a reason beside it keep trust. A date that moves quietly does not.

When a customer task stalls

Every onboarding has a task that sits. Rocketlane's help center describes automations that watch due dates and notify the project owner when a task is overdue. Trumpet's mutual action plan page says signals are pushed to Slack, Teams or the CRM when a buyer checks off a step. Both describe the same habit from two ends: the seller learns when something moves, and when it does not.

Decide in advance what a stall means. Three days past a customer's due date, the CSM calls. Seven days past, the account executive who sold the deal joins the call, because the sponsor listened to that person during the sale. Fourteen days past, the plan's go-live date is rewritten with the customer and the reason is recorded.

These thresholds are ours and you should change them. The point is that they are written down before the first stall, not invented during it.

Sources

  1. Flowla: Vendor onboarding page says that when a deal closes won in the CRM, REX builds the onboarding plan from the, read 10 Nov 2026
  2. GUIDEcx: Vendor says customers reach the portal by a secure link in the welcome email, with no login., read 10 Nov 2026
  3. Dock: Vendor's onboarding page says customers can update implementation plan tasks, comment and upload files in the, read 10 Nov 2026
  4. Dock: Vendor help article says automatic reminder notifications can be set before, on or after task due dates in a, read 10 Nov 2026
  5. Aligned: Help center Meetings tab: after each call, summary and next steps from the CRM are added to the room; with, read 10 Nov 2026
  6. Aligned: Help center: Aligned reads only the linked CRM record and uses the call summary, not the recording., read 10 Nov 2026
  7. GUIDEcx: Vendor’s product example shows customer tasks flagged as overdue, with the task and the number of days., read 10 Nov 2026
  8. Rocketlane: Pricing page lists built-in CSAT surveys at project milestones., read 10 Nov 2026
  9. HubSpot Sales Hub: HubSpot (Service Hub Professional and Enterprise, adjacent to Sales Hub) lets customers see and complete, read 10 Nov 2026
  10. Rocketlane: Help center describes automations that watch due dates and notify the project owner when a task is overdue., read 10 Nov 2026
  11. Trumpet: Vendor MAP page says signals are pushed to Slack, Teams or the CRM when a buyer checks off a step., read 10 Nov 2026

Last reviewed 10 Nov 2026.