The Implementation Manager agent runs every rollout from kickoff to go-live. It builds the project plan, chases owners on both sides, checks each step is really done and reports progress every week.
Example: kickoff to first status report
From signed contract to first status report.
Here’s how the agent starts every rollout.
01
Kick off
When a deal is marked won in your CRM, the agent builds the project plan from your template and the deal details.
02
Confirm
Emails the customer’s stakeholders the plan as Excel and PDF, and asks them to confirm owners and dates.
03
Check
Checks progress against the plan in product data, like SSO configured or users invited.
04
Report
Every Friday, sends a status PDF to the customer’s sponsor and a summary to your team in Slack.
Trains every team that needs it.
Sessions for each group
Admins, managers and end users each get training on the parts of the product they’ll use.
Booked around them
The agent offers times by email and runs the session by voice or chat on their screen.
Training tracked in the plan
Who has been trained, and who still needs it, is part of the weekly status report.
Live session
04:12
Implementation Manager
Goal: train the finance team
You’re on the approvals page. Let’s approve one invoice together so you see the whole flow.
Got it. Can managers approve on mobile?
Mic on
Sharing screen
Chat
Checks migration data before it causes problems.
Every upload checked
When the customer uploads a migration file, the agent checks columns, formats and required fields.
An error report, not a failed import
The customer gets a clear list of what to fix, row by row, by email.
Signed off in the plan
When the file is clean, the step is marked done and the next owner is told.
Every owner chased, on both sides.
Follow-ups that never slip
The agent checks the plan every day and nudges each owner by email or Slack when a step is due.
Checked in the product
Steps are confirmed from product data, so the plan shows what’s actually done.
Blockers raised early
When a step stalls, your team hears about it with the owner and the reason, before it threatens go-live.
Goal: live by end of month
Step 3 of 6
Done
Workspace and roles set up
Done
Data migrated and checked
Now
Chasing IT for SSO setup
Working from
Rollout plan
Product data
CRM
Checking who owns the next step…
Weekly status update
Sent
Done
Data migration signed off
Blocked
SSO waiting on the customer’s IT team
Next
Training for end users
Attached
status.pdf
plan.xlsx
Owners
Sent to the customer and your team
Status updates that write themselves.
Every week the customer’s sponsor gets a status PDF and your team gets a summary in Slack: what’s done, what’s blocked and what’s next.
Progress across every rollout
See where each implementation stands without chasing your team for updates.
One plan both sides trust
The customer and your team read the same status, every week.
Clean handover to CS
At go-live, the agent writes up the setup, the owners and the open items for your CS team.
No rollout left to drift
Handles long, multi-team projects
Kulu stays with a rollout for weeks, across admins, IT and end users, until it goes live.
Progress checked, not assumed
Steps are confirmed from product data, not just ticked off a list.
Logged and reviewable
Every follow-up, report and plan change is recorded for your team.