No, a client portal isn't what makes MSP onboarding feel fast
No, a client portal isn't what makes MSP onboarding feel fast
Key takeaways
- Onboarding feels slow when the client is waiting on you, and the waits are nearly always paperwork: a scope nobody has confirmed, an agreement stuck in someone's inbox, a first invoice that has to be built by hand.
- A portal only shortens those waits if the agreement, the device count and the first invoice live in the same place the client logs in to.
- If you need RMM sync, ask which direction the data moves and how often. "Integrates with" can mean a scheduled read, a button you press, or a one-time import.
- The cheapest portal is the one you don't end up paying for twice. Price it alongside the e-signature, renewal tracking and invoicing you would otherwise buy separately.
A week that went fine and still felt slow
A 25-person accounting firm signs on with you on a Monday. You set up their portal that afternoon. Logins go out. On paper, onboarding has started.
Tuesday, the office manager sends a spreadsheet of devices. It lists 25 workstations. Your RMM agent rollout finds 31, because the spreadsheet forgot the two front-desk machines, the scanner PC and three laptops that live in a partner's car. Somebody has to decide which number goes in the SOW. That takes until Thursday.
The SOW goes out Friday. The office manager can't sign it, so she forwards the PDF to the managing partner, who is out until the following Wednesday. It comes back signed eight days after kickoff.
Then someone on your side opens the signed PDF and types the line items into the billing tool. They type 25 instead of 31. Nobody notices for four months.
The portal was ready on day one. None of the waiting happened in it.
Where onboarding time actually goes
When you trace a slow onboarding back, the same four steps keep showing up:
- Agreeing on scope. How many users, how many devices, which sites. This is where RMM data helps most, because it replaces a client's guess with a count.
- Getting the signature. Not the click itself, but finding the person allowed to make it and getting the document in front of them.
- Producing the first invoice. If the invoice is rebuilt from the PDF, it is slow and it is where errors start.
- Handing over access. Credentials, contacts, escalation paths. This is the step a portal genuinely speeds up.
A portal is good at step 4 and at being a tidy place to find things afterwards. Steps 1 to 3 are where the days go, and they are contract problems, not login problems.
The three kinds of tool called an "onboarding portal"
| Kind of tool | Built around | Good at | Where onboarding still stalls |
|---|---|---|---|
| Service desk portal (CloudRadial, DeskDirector) | Tickets and a service catalog | Requests and self-service after go-live | The agreement and first invoice happen in another tool |
| Project onboarding tool (Rocketlane) | Tasks, milestones, stakeholders | Long rollouts with many people involved | Not built around MSP agreements or recurring billing |
| Contract-led portal (XClause) | The signed agreement | Scope, signature and first invoice from one record | Not a ticketing tool; you keep your PSA for that |
None of these is wrong. They answer different waits. If your clients get onboarded quickly but then drown your techs in emailed requests, a service desk portal is the fix. If your clients wait a week for a signature and your first invoice is retyped, it is not.
If you need RMM sync
Ask three questions of any tool that says it syncs with your RMM.
Which direction? Most of the value for onboarding is inbound: device counts flowing from the RMM into whatever drafts the SOW. A tool that only pushes data out does nothing for scope.
How often? A count read once at signing is stale within a month. A scheduled read keeps the comparison honest.
What does it change? This is the one people skip. If device counts silently change what the client is billed, you are invoicing amounts nobody agreed to. The safer design shows you the gap and lets you amend the agreement.
For what it's worth, here is how XClause answers those. It reads devices from NinjaOne every 6 hours and whenever you press Sync all, and it never writes back to NinjaOne. It reads SuperOps assets when you press Sync now, and device edits you make in XClause can push back to SuperOps. Those counts are compared against what the signed agreement covers. Invoices still bill the agreement, not the live count. It does not connect to Datto RMM, N-able or Kaseya VSA today. Pulling in device counts and running the comparison need the Pro plan; Starter does not include integrations.
What it costs
Two pricing models dominate. Per-client or per-seat pricing grows every time you sign someone, which means the tool gets more expensive exactly when things are going well. Flat pricing doesn't move.
XClause is flat per company. Starter is $99.99 a month for up to 15 clients. Pro is $199 a month with no client limit, and Pro + White-Label is $248 a month if you want the portal and documents under your own brand. The client portal and e-signature are included on all three. Every plan has a 7-day free trial.
When you compare, add up what you'd otherwise buy: a separate e-signature subscription, whatever you use to track renewals, and the time spent turning a signed PDF into an invoice. A cheap portal that still needs all three is not cheap.
Renewals and invoices
Most MSPs don't lose money at onboarding. They lose it eighteen months later, when an agreement auto-renews at last year's rate, or when the invoice has been one device short since month one.
Both trace back to the same thing: the agreement isn't connected to anything. XClause sets renewal reminders on each agreement, any mix of 90, 60, 30, 15 and 7 days out, sent to your team, the client, or both. The invoice is drafted from the signed SOW, one line per managed unit at the agreed rate, and you review it and send it. Signing doesn't fire an invoice on its own, which is deliberate.
So what should you pick?
Start with where your clients actually wait. If it's the ticket queue after go-live, buy a service desk portal. If it's a twelve-week implementation with five departments, buy a project tool. If it's scope, signatures and the first invoice, the portal you want is the one sitting on top of the agreement.