How long implementation takes and how much work it asks of you
The late-stage objection is not the product: it is the fear of a months-long project. Whalemate implementation does not install software on the endpoint. It asks for read access to the directory, an allowlist for sending, and a contact. The concrete calendar is confirmed at kickoff. Here are the phases, the owners, and an honest range —not a day count CX has not validated.
Implementation phases, with an owner
Owners: Whalemate analyst and the client contact. You load industry, countries, languages, what audit expects, who approves a send, and the notice model. The kickoff wizard writes that down. The calendar for the next phases is confirmed here, not on a landing page.
Owner: client IT, with People if scope must be validated. Read permission. SCIM or the matching connector. Whalemate checks that the roster comes in —names, emails, area—. Without this step there is no campaign. Timing depends on your IdP, not on a published number.
Owner: IT or the mail team. Sending domains must be allowed. A test goes to a small cohort. If the simulation does not reach the inbox, the program has not started. Whalemate brings the list; the client applies it. The first weeks usually suffice when the mail ticket does not sit still.
Owner: security or the program sponsor. Admin access is created, who sees what is agreed, and what the analyst may decide is written down. If there will be SSO, it is this stretch. The Trust Center and DPA should already be on legal’s table; they are not invented at kickoff.
What has to be put in: platform, service and content
Platform
From the client: read-only directory access to sync the roster —joins, leaves, area— and the allowlist so the simulation does not die in spam. From Whalemate: account setup, SSO if it applies, and…
Service
The account analyst runs kickoff and the kickoff wizard: contact, languages, off-limit windows, the authorization model for template and date. Whalemate does not guess the owner. If IT does not grant…
Content
The first campaign comes from the catalog —or from the custom quota if the plan already has one and the brief is ready—. You do not wait for a branded pack to “show value.” You wait for a complete…
How much work go-live asks — and whose it is
If you already saw the platform —or you are in the last round with
Who connects the directory, who enables sending, who names the contact, when the first campaign can go out. If you are still choosing Smart, Growth, or Enterprise, that is another table. If the block…
IT will ask about ports, agents, and write access to the directory
The answer is the same as on integrations: API and a read permission, no endpoint agent. People validate the roster. Security names who touches the first campaign. The kickoff wizard loads owners…
There is no published SLA in business days for every account
Every roster and IdP takes a different time. On the client side the typical technical work is hours —permission, whitelist, a contact— not a months-long rollout. The first weeks get the directory in…
What implementation is not
What has to be put in: platform, service and content
Platform Service Content
What implementation is not
It is not a professional project quoted as a separate line in the plans copy: go-live is not sold as an extra in that table. It is also not an endpoint rollout… It does not include custom, branded work, or Advanced Attack. Those quotas live in the contracted tier and are planned once the roster is in. Implementing…
A start that was measured, not an endless rollout
A logistics operator with more than a thousand employees started from internal emails, with no visibility into who read them. Go-live was not installing anything in the branches: it was connecting a roster and putting…
Questions about how long implementation takes
Is the objection the go-live work?
The conversation looks at your IdP, who the contact will be, and what a real kickoff looks like. The calendar is confirmed there, not here.