Use case · Transition and ramp plan
Turn the signed SOW
into a ninety-day plan
The paper already says what was sold, where, in how many languages and by when. AnyCRM writes the ninety days from it, assigns both sides, and finds the date that belongs to somebody who has not agreed to it.
- Written from the signed SOW
- Owners on both sides
- Dependencies traced, not assumed
Delivery
Sample dataOpen
AnyCRM. Delivery.
Read
The plan comes out of the paper, signed SOW, nothing retyped. Three service lines, two sites, one language pair, As scoped in the SOW. Go-live date fixed, Named in the commercial terms
Plan
Milestones with owners, both sides, ninety days, in phases. Phase one, knowledge capture, Owner Priya Raman, weeks one to three. Phase two, agent training and shadowing, Owner Priya Raman, weeks three to seven. Phase three, phased volume transfer, Owner client operations, weeks seven to twelve Forty-one tasks created. Owners on both sides
Risk
Phase two depends on a client system date nobody has agreed. Agent training needs their case system provisioned, and the SOW names the go-live but not the provisioning date. Every week that slips there lands on your ramp, not on theirs. Unowned dependency.
Your call
Three moves offered: Ask their programme lead to commit the provisioning date; Reorder so knowledge capture absorbs the wait; Raise it as a change note against the go-live. The plan does not pretend the dependency is not there.
Resolved
Provisioning date committed for week two, Confirmed by their programme lead in writing. Phase two unchanged, Training starts on the week it was planned for. The ramp has no silent dependencies left. Every milestone owned. Go-live date still holds.
Deliverables
Transition plan, Phases, milestones, owners and dependencies. Forty-one tasks, On the account, assigned and dated. Read-only link, For the client programme lead. Filed on Ellersby Group, activity logged, the provisioning date tracked as a dependency.
Close
Signature to plan, without a workshop.
Ellersby Group, signed on a Friday, with Priya Raman owning transition and a client system date nobody had agreed.
How it works
Four steps, and none of them is typing.
- 1
The plan is read out of the paper.
Ellersby Group
Sample- Clause 3
Three service lines, two sites, one language pair
As scoped in the SOW
- Clause 9
Go-live date fixed
Named in the commercial terms
Service lines, sites, languages and the go-live date come from the SOW clauses that agreed them. Nothing is retyped and nothing is remembered.
- 2
Phases with owners on both sides.
Ellersby Group
SamplePhase one, knowledge capture
Owner Priya Raman, weeks one to three
Phase two, agent training and shadowing
Owner Priya Raman, weeks three to seven
Phase three, phased volume transfer
Owner client operations, weeks seven to twelve
Forty-one tasks createdOwners on both sidesKnowledge capture, training and shadowing, then phased volume transfer, each with a named owner on your team and on theirs, and tasks created on the account rather than in a document.
- 3
An unowned date, raised in week one.
Ellersby Group
SamplePhase two depends on a client system date nobody has agreed.
Unowned dependencyWhen training waits on a client system date the SOW never named, every week it slips lands on your ramp. Ask their programme lead to commit the date, reorder so an earlier phase absorbs the wait, or raise it as a change against go-live.
- 4
Both sides read the same plan.
Documents
SampleTransition plan
Phases, milestones, owners and dependencies
Forty-one tasks
On the account, assigned and dated
Plan published
The transition plan, the task list and a read-only link for the client programme lead, filed on the account with the dependency tracked.
The risk beat
When something turns, it tells you and shows you the moves.
Here the turn is: Phase two depends on a client system date nobody has agreed. Three moves were offered and a person took one: ask their programme lead to commit the provisioning date.
Risk beat · AnyCRM AI
Sample data- 1
Detection
Phase two depends on a client system date nobody has agreed.
- 2
Explanation
Agent training needs their case system provisioned, and the SOW names the go-live but not the provisioning date. Every week that slips there lands on your ramp, not on theirs.
Unowned dependencyTraced from the training milestone - 3
Options
- Ask their programme lead to commit the provisioning date
- Reorder so knowledge capture absorbs the wait
- Raise it as a change note against the go-live
- 4
Human choice
Ask their programme lead to commit the provisioning dateA person presses one. Nothing is sent or written until then.
- 5
Resolution
The ramp has no silent dependencies left.
Each milestone names the thing it waits on and the person who owns it, so a slip is a conversation in week two rather than a surprise in week seven.
Every milestone ownedGo-live date still holds
Where the answers come from
The record you already have.
The plan does not need a workshop to exist. The signed SOW already contains the scope, the sites, the languages and the date everything has to work by.
The signed SOW
Scope, sites, languages and the commercial dates
The proposal
What was promised before the paper was drawn
Meeting transcripts
Constraints the client named out loud
The output
The transition plan
Every line points back at one of these.
Your delivery model
How long each phase actually takes in practice
Client-side owners
Who on their team holds each dependency
The account record
The people, the sites and the history on both sides
What you receive
Documents, not a dashboard.
A plan the delivery team can start on in week one, with every task already on the account and every dependency pointing at a person.
See the full CS Teams page- Tasks
The transition plan
Phases, milestones, owners and dependencies
- Tasks
Tasks on the account
One per milestone step, assigned and dated
The dependency list
The dependency list
Everything waiting on somebody outside your team
- LinkRead-only. Revoke any time.
A read-only link
For the client programme lead
Why BPOs need this
What we heard, in their words.
The problem
We spend week one in a workshop rebuilding what the SOW already said.
A delivery lead
The problem
The client system date slipped and the ramp absorbed it silently.
A transition manager
The problem
Half the plan has an owner and the other half has a team name.
An operations director
Questions
The honest answers.
Does it replace the transition workshop?
It replaces the part of the workshop that reconstructs the SOW. What the workshop is actually for, agreeing the hard dates with the client, starts from a drafted plan instead of a blank wall.
How are dependencies found?
By tracing each milestone to what it waits on. Anything waiting on a date the paper does not contain is raised as unowned before week one.
Do tasks live in the CRM or in a project tool?
They are created on the account with owners and dates, so delivery and the deal record are the same record rather than two.
What if the client cannot commit the date?
Then the plan reorders around it or the change is raised against go-live. What it does not do is leave the date silently inside a milestone.
Give your team the unfair advantage.
Full deal intelligence from day one. No credit card required.