For most managed service providers, onboarding a new client for phishing simulations takes one to two hours of MSP effort, spread over one to two weeks of elapsed time. The elapsed time is dominated by two things that have nothing to do with the platform: getting the client to confirm the user list, and getting the first campaign scheduled. The technical setup itself is the fast part.
TL;DR
- One to two hours of MSP effort per client; one to two weeks elapsed.
- Elapsed time is dominated by client-side inputs — confirming the user list, picking a campaign date — not platform configuration.
- Auto-enrolment integrations (HR systems, SSO) cut elapsed time by removing the manual user-list export.
- White-labelling and templated campaign settings let each new client start from a proven baseline rather than a blank page.
Where the one to two weeks actually goes
Break the elapsed time into its parts and the picture is clear:
| Stage | Typical effort | Elapsed time |
|---|---|---|
| Client confirms user list | 15-30 min | 2-5 business days |
| Platform setup (tenant, users, campaign) | 30-60 min | Same day |
| Whitelabel + sender domain checks | 15-30 min | 1-3 business days |
| First campaign scheduled and sent | 10 min | Day 7-14 |
The pattern is the same across MSPs: the MSP's own work is under two hours, and the elapsed week is the client confirming names and the vendor confirming sender domains.
Step by step: the actual workflow
- Collect the user list. Most MSPs start with a CSV export from the client's M365 or Google Workspace admin console. The manual path takes minutes; the reliable path is an auto-enrolment integration so joiners appear automatically.
- Confirm the list with the client. The list always contains something the MSP cannot judge — a contractor mailbox, a shared mailbox, a recently departed staff member still licensed. The client confirms it.
- Configure the tenant. Upload the list, set the campaign schedule, pick a template family (an NZ/AU-appropriate one — see the article on localised phishing templates for why the local flavour matters).
- Set up sender domains. The simulation sender domain needs SPF/DKIM records the client's IT team adds to their own DNS — this is the step that most often stalls, because it sits with someone who does not know it is on the critical path.
- Schedule and send the first campaign. Once domains verify, the first campaign runs on schedule and the reporting starts.
Steps 1 and 4 are the only ones where elapsed time commonly stretches past a day — everything else is minutes of work inside the platform.
What separates a fast onboarding from a slow one
- Auto-enrolment beats CSV. A client on an HR-integrated platform adds new joiners without a re-export, so the user list never goes stale.
- White-label once, reuse everywhere. An MSP that sets up its own branded reporting and sender domain as a reusable profile applies it to every new client in minutes.
- Templated campaign settings. A proven baseline — one localised and one generic template family, a monthly cadence, standard reminders — beats a blank configuration page per client.
- Client-side engagement is the real variable. The MSP controls its own hours; it does not control how quickly a client's IT contact adds DNS records or confirms a user list.
What MSPs charge for it
Onboarding effort is one-time and front-loaded. Most MSPs either bundle it into the first month's fee or charge it as a one-off setup line — the effort is small enough that padding it out feels dishonest to the client, and the ongoing value is the monthly cadence and reporting, not the setup. Check the security awareness training page for the platform side of that offer.
FAQ
How long does it take to onboard a new MSP client for phishing sims? One to two hours of MSP effort, one to two weeks elapsed — most of the elapsed time is the client confirming the user list and adding sender-domain DNS records, not platform configuration.
What slows onboarding down the most? Two client-side steps: confirming the user list (contractors, shared mailboxes, departed staff) and adding SPF/DKIM records for the simulation sender domain. Neither is hard; both sit outside the MSP's direct control.
Can onboarding be faster? Yes — auto-enrolment integrations remove the manual CSV export, a reusable white-label profile removes per-client branding setup, and templated campaign settings remove the blank-page problem. With those in place, elapsed time can compress to under a week.
Do we need the client's IT team involved? For one step only — adding the simulation sender domain's DNS records to the client's domain. Everything else runs inside the MSP's platform access.
How many staff do we need to run the first campaign? Any size from a handful upward. The platform pricing is per seat, so a 10-person client works the same way a 400-person one does — just smaller.
One last thing
The MSPs that onboard fastest are not the ones with the most technical skill — they are the ones with a reusable onboarding profile and a client checklist that puts the DNS step and the user-list confirmation on the critical path from day one.