# A services-heavy plan treats the buying and the delivery as one project with phases and a staffing plan

Template, Services-heavy implementation deal, read 10 Nov 2026

**The short answer.** Fourteen steps spanning the sale and the first delivery phase. The template includes resourcing on both sides, a scoping workshop, a statement of work and a signed phase plan, so the customer sees what the services team will deliver before the contract is signed.

## When to use it

Use when services, configuration or integration work is a large part of the deal and the customer must provide staff, data or access.

## The plan, step by step

Day 0 to day 95

| Day | Step | Owner | Side | Done when |
| --- | --- | --- | --- | --- |
| 0 | Agree the outcome and go-live driver | Buyer: executive sponsor | buyer | The outcome and the event that sets the date are on the plan. |
| 7 | Run the scoping workshop | Both: solutions architect and business lead | both | A scope document lists in-scope and out-of-scope items. |
| 10 | Name the customer project team | Buyer: project lead | buyer | Named people and their hours per week are on the plan. |
| 12 | Name the delivery team | Seller: services lead | seller | Named roles and their hours are on the plan. |
| 18 | Draft the statement of work | Seller: services lead | seller | The draft covers scope, deliverables, dates and assumptions. |
| 24 | Review assumptions and dependencies | Both: project lead and services lead | both | Each assumption has an owner and a date to confirm. |
| 30 | Complete security review | Buyer: IT or security lead | buyer | Findings are closed or accepted. |
| 40 | Approve the statement of work and contract | Both: legal contacts | both | The final documents are agreed. |
| 48 | Obtain signature | Buyer: economic buyer | buyer | The signed contract is on record. |
| 50 | Create the project plan from the deal | Seller: project manager | seller | Phases, milestones and owners are copied from the deal plan without re-entry. |
| 55 | Hold the kickoff | Both: project lead and project manager | both | The project team has attended and access requests are sent. |
| 65 | Deliver customer inputs | Buyer: project lead | buyer | Data, access and decisions are supplied by the planned dates. |
| 90 | Complete the first phase | Both: project manager and project lead | both | The phase exit test is met and signed off. |
| 95 | Review the plan and risks | Seller: project manager | seller | The plan is updated and risks are logged with owners. |

## Where plans like this stall

- Selling a delivery date before the customer has staffed the project.
- Retyping the deal commitments at handoff, which loses detail.
- Leaving customer tasks out of the project plan.

## Running it in a tool

The [MAP Tool Matrix](/tools/) shows which tools keep the plan where the buyer already is, send nudges and sync to the CRM; [the tool ranking](/platforms/) weighs the plan at 30 of 100.

## Sources

- Rocketlane help center: project plan: https://help.rocketlane.com/support/solutions/articles/67000699280-project-plan (read 10 Nov 2026)
- GUIDEcx: Salesforce integration and project templates: https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)
- Accord: implementation use case: https://inaccord.com/use-case/implementation (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://themutualactionplan.com/templates/services-heavy-implementation/
