What Does an Implementation Consultant Do? A Guide for SaaS Hiring Managers
By Daniel Bryant · 7 June 2026
You Closed the Deal. Now What?
The contract is signed. The AE is celebrating. The customer is expecting the product to be live in six weeks.
And then nothing happens. Because there is nobody to do the work.
The Implementation Consultant is the person who turns a signed deal into an activated customer. They sit between Sales and Customer Success, owning the most critical window in the customer lifecycle: the gap between “yes” and “live.”
Get it right and the customer is sticky from day one. Get it wrong — or leave the seat empty — and you are burning the goodwill your sales team spent months building.
The 7-Phase Implementation Lifecycle
Every SaaS implementation follows the same arc. The IC owns each phase, either directly or as the accountable project lead.
1. Discovery
Understanding what the customer actually bought versus what they think they bought. Mapping stakeholders, documenting business processes, and identifying the gap between their current state and the platform’s capability.
2. Scoping
Translating discovery into a project plan. Defining what is in scope, what is out, what needs custom configuration, and what requires integration work. This is where the IC protects the timeline — and the margin.
3. Configuration
Building the customer’s environment. Workflows, permissions, custom fields, automation rules, reporting structures. This is not admin-level checkbox ticking. A strong IC understands the platform deeply enough to configure it in a way that scales with the customer’s business.
4. Data Migration
Moving the customer’s historical data into the new platform. CRM records, contact lists, transaction history, document repositories. This is where implementations live or die. A botched migration destroys trust faster than any product bug.
5. UAT (User Acceptance Testing)
Running the customer through their own workflows on the configured platform. Catching edge cases before go-live. Making sure the thing actually works the way the customer expects it to — not just the way the IC built it.
6. Training and Go-Live
Getting end users comfortable with the platform. Running training sessions, building documentation, and managing the go-live cutover. The IC is the face of the company during this phase. Their composure under pressure sets the tone for the entire relationship.
7. Handover to Customer Success
Transferring ownership to the CSM with a proper brief: what was configured, what workarounds are in place, what the customer’s expansion triggers are, and where the risk sits. A clean handover is the difference between a CSM who can drive value from day one and one who spends the first quarter re-discovering the account.
What Good Looks Like: The Trifecta
The best ICs have three capabilities in equal measure.
Configuration depth. They do not just know which buttons to click. They understand the platform architecture well enough to design solutions that do not create technical debt. They can explain why they configured something a certain way, not just that they did.
Migration skills. They have personally owned data migrations end to end. They understand ETL, data mapping, validation rules, rollback plans, and the difference between a clean migration and one that leaves orphaned records everywhere.
Client PM accountability. They run the project. They own the timeline, manage stakeholder expectations, escalate blockers early, and do not hide behind “the customer was slow to respond.” They treat the implementation like their own project, not a ticket queue.
When you find someone with all three, hire them immediately. They are rare.
The Screening Question That Cuts Through
Ask this in every IC interview:
“Walk me through the last data migration you owned end to end. What was the source system, what was the target, how did you handle data mapping, and what was your rollback plan?”
This question separates the ICs who have done the work from the ones who have watched someone else do it. Listen for specifics: data volumes, transformation logic, how they validated post-migration, what went wrong and how they recovered.
If they cannot answer this with specifics, they have not done it.
Red Flags in IC Candidates
Never owned a migration. They have always had a technical team handle it. That is fine for junior roles, but if you are hiring a mid or senior IC, they need to have been hands-on.
Cannot explain a rollback plan. If the migration fails at 2am on a Sunday, what happens? If they have never thought about this, they have never run a high-stakes cutover.
Only done admin-level configuration. Creating users and setting permissions is not implementation consulting. You are looking for someone who has designed workflows, built automation, and configured integrations — not someone who followed a setup wizard.
No client-facing project management experience. An IC who cannot run a steering committee, manage scope creep, or deliver hard news to a customer is an IC who will need constant supervision.
The Market Right Now
As of May 2026, there are approximately 830 active SEEK listings in Australia that map to the Implementation Consultant function — including titles like Implementation Manager, Onboarding Consultant, and Deployment Specialist.
Contract rates sit between $900 and $1,500 per day depending on platform complexity and seniority. Permanent salaries range from $95,000 to $170,000 base, with the top of that range reserved for enterprise-grade platforms like Workday, SAP SuccessFactors, and Salesforce.
Demand is concentrated in HCM, construction tech, and fintech — verticals where the implementation is complex enough that you cannot automate it away.
Have an Implementation Backlog?
If your signed customers are sitting in a queue waiting to go live, that is a revenue problem disguised as a hiring problem.
Zionic places pre-vetted Implementation Consultants within 5 business days. Contract or permanent. We know the role because we have built the platform they would be implementing.