T21 Client onboarding hub

Client onboarding hub

A client onboarding call on a laptop

Onboarding: Northstar 3 items need you Kickoff complete Week of Sep 22, 2026

Everything Lantern RevOps needs from Northstar to start your RevOps build, in one place, and what happens once you provide it. This page is your single source of truth for onboarding; we keep it current so you never have to search email threads for the latest ask.

Welcome

Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.

Live example from the Dashboards app, shown with Bellwether Health's demo data.

Start here

We are currently in the access and data step. The three items below are what move us to brand handover.

What we need from you this week

The list below is our live client action list. It shows every onboarding item across our clients that is Requested or Waiting on the client, soonest deadline first. Your three Northstar items are summarized in the table underneath for quick reference.

Before you share this page with a client

This view lists action items for every client we are onboarding, not only Northstar. Before sending this page to anyone outside Northstar, switch the embed to a view filtered to Northstar, or copy the page and filter that copy.

Item	What we need	Required by	Status
Source data export	Export of open orders and the customer list from your ERP	Sep 30, 2026	Requested
Brand asset handover	Logo files, fonts and your brand guide	Sep 25, 2026	Waiting on you
Legacy website admin login	Admin login for the legacy website, before we map redirects	Sep 21, 2026, overdue	Waiting on you

Blocked: legacy website admin login

The only admin account for your legacy website is held by your former agency, not by your team. Consequence if this stays open: our redirect map stays incomplete, and old URLs may break when the new site launches. What we need: ask your former agency to transfer or share admin access, or grant us a new admin account if you still control the domain. Owner: Ruth Okafor, due Sep 21, now overdue.

Your Lantern RevOps team

Why we ask for the access level we ask for

We request the minimum access level each task needs, never more. Read access is enough for reporting; admin access is only requested when we must configure a system ourselves, such as the legacy site redirect mapping. Every access grant is logged on this page and can be revoked by you at any time.

How an item moves through onboarding

stateDiagram-v2
    [*] --> NotStarted
    NotStarted --> Requested
    Requested --> WaitingOnClient
    WaitingOnClient --> Ready
    Ready --> InProgress
    InProgress --> Verified
    Verified --> Complete
    Complete --> [*]

Verified means we tested the access or data ourselves, not just that you told us it was ready. That is what moves an item to Complete.

Questions we hear most

Why do you need our old website login before the new site is even built?

We map every existing URL to its new destination before launch, so links from search results, bookmarks and partner sites keep working. Without admin access to the old site, we cannot export the full list of live URLs to build that map.

What happens once we provide the legacy admin login?

We export the URL list, build the redirect map, and remove our access unless you ask us to keep it for ongoing maintenance. You will see this step move to Verified once the export is confirmed.

How long does onboarding usually take?

For a build like yours, four to six weeks from kickoff to launch once access and data are provided. Delays on access items are the most common cause of a slower timeline.

How to use this template

Duplicate this page once per new client and update it as items move through onboarding. Replace these values; if a required value is missing, show Needs review instead of guessing.

Variable	Meaning	Required
`{{client.name}}`	Client this onboarding hub is for	Required
`{{sponsor.name}}`	Named project sponsor on the client side	Required
`{{item.required_by}}`	Date each open item is required by	Required
`{{item.status}}`	Current status of each open item, from the onboarding tracker	Required
`{{blocker.owner}}`	Who on the client side owns a blocked item	Required when an item is Waiting on client
`{{launch.target_date}}`	Target go-live date	Optional

Never mark an item Verified without testing the access or data yourself; a client saying "it's done" is not verification.