Betterfolio
Betterfolio team
The first 30 days on mission: securing the placement after the signature
A signed contract isn't the end of the sales cycle. Most missions that end early are decided in the first month. An onboarding protocol that protects margin and the client relationship.
In short
Most consulting missions that end early fail on integration, not on technical skill. The consultant already passed the client interview: the level was validated. What breaks afterwards is misaligned expectations, a scope different from the one sold, or the absence of a named contact.
- The highest-risk window is weeks 1 to 4, not month 6.
- The single most effective control point is a 20-minute call at the end of week 1, which catches scope drift while a conversation can still fix it.
- Structured follow-up over the first quarter costs about two hours per mission, against twenty to thirty hours for a replacement.
- The 30-day review is both a quality control and the best commercial opening you will get on that account.
The placement isn't the finish line
In IT consulting, the whole commercial machine converges on one moment: the signature. Sourcing, dossier, client interview, negotiation. Once the purchase order is issued, attention moves to the next requirement.
That is precisely where part of the hard-won margin leaks away. A mission interrupted after six weeks costs the full acquisition cost, the bench time that follows, and a share of credibility on the account, often the most expensive of the three.
The reason for an early break is almost never technical competence. The consultant passed the interview: the client validated the level. What breaks afterwards is integration: misaligned expectations, a scope different from the one announced, no available contact, or a cultural mismatch nobody addressed.
Where missions are actually lost
| Period | Dominant cause of failure | Who can prevent it |
|---|---|---|
| Week 1 | Gap between the need sold and the real role | Sales, upstream |
| Weeks 2–4 | No onboarding on the client side | Delivery, by chasing |
| Months 2–3 | Consultant isolation, no feedback | The firm, through cadenced follow-up |
| Month 4+ | Client reorganisation or budget | Largely outside your control |
The first three rows are largely preventable. That's where the leverage sits.
Before day 1: what gets prepared during the notice period
Onboarding doesn't start on Monday morning. It starts at signature, during the two to four weeks of notice when many firms do nothing at all.
The pre-mission checklist
- Confirm the real scope with the operational manager, not the buyer. The specification and the day-to-day need almost always diverge.
- Get the name of a technical contact on the client side, with their email and their availability in week one.
- Verify access logistics: badge, VPN, workstation, application accounts. A consultant who spends three days without access already starts at a credibility deficit.
- Agree the presence rhythm in writing: days on site, team hours, mandatory rituals.
- Give the consultant the dossier that was sent to the client. They need to know exactly what was claimed on their behalf.
The step most often skipped
The fifth. A consultant who discovers in an informal conversation that their dossier led with an expertise they consider secondary is caught off balance in week one. Aligning the story upfront costs fifteen minutes; recovering from it afterwards costs the mission.
Week 1: Remove uncertainty
The first objective isn't productivity. It's to eliminate the questions that occupy the consultant's attention: who do I go to, what is expected of me, what does a good first week look like.
The three conversations to force
| Conversation | With whom | What it must produce |
|---|---|---|
| Mission framing | Client manager | Three deliverables expected within 30 days |
| Technical onboarding | Technical contact | Access, environment, first ticket |
| Firm-side checkpoint | Sales or delivery | Gaps observed vs. the need sold |
The third is the one firms skip most often. A twenty-minute call on the Friday of week one catches scope drift while it can still be fixed by a conversation rather than a replacement.
The week 1 warning signal
"They've put me on something else in the meantime."
That sentence, heard at the first weekly checkpoint, precedes a significant share of six-week breakdowns. It means the need sold wasn't ready, and that the consultant occupies an unbudgeted slot in the manager's mind. It calls for immediate commercial intervention, not for waiting until "it settles down".
Weeks 2 to 4: Establish proof
After the first week, the stake shifts: the consultant needs to produce a visible signal of value before the end of the first month. Not a masterpiece, but a result the client manager can identify.
What builds trust quickly
- A short, concrete deliverable by week two: documenting an existing system, fixing a known irritant, mapping an unclear scope
- Speaking up in a team ritual, being identified as a member, not a passing supplier
- A well-framed question on an architecture point: showing you read the context before proposing
- A commitment kept on a small deadline rather than an ambitious promise missed
What destroys it
- Waiting for perfect instructions before acting
- Criticising the existing technical setup in the first two weeks
- Staying invisible while remote as the team organises on site
- Escalating to the firm on topics the client expects to be handled directly
The firm-side follow-up rhythm
| Moment | Format | Duration | Objective |
|---|---|---|---|
| End of week 1 | Call with consultant | 20 min | Detect scope drift |
| End of week 2 | Short message to client | n/a | Check the manager's perception |
| End of week 4 | Joint review, consultant + client | 30 min | Validate fit, adjust |
| End of month 3 | Formal review | 45 min | Prepare the renewal |
This rhythm looks heavy. It amounts to under two hours across the first quarter, against the full cost of a replacement.
The 30-day review: the highest-return meeting of the mission
A structured review at one month turns passive follow-up into a commercial instrument. Three questions to the client manager are enough:
- "Does the scope match what we framed?": corrects drift before it becomes a grievance.
- "What would have saved you time in the first two weeks?": improves onboarding for the next placements on this account.
- "Do you see other needs coming over the next few months?": that's the commercial question, asked at the moment your credibility peaks.
A consultant who has just delivered a visible result opens a short window where the manager talks willingly about upcoming needs. Many firms never use it.
What the 30-day review documents for later
Every mission that goes well produces usable material: context, real scope, technologies practised, client feedback. Captured while fresh, that material feeds the consultant's dossier for their next placement. Reconstructed six months later, it will be approximate, and an approximate dossier sells for less.
Common objections, and how to answer them
"Once they're placed, it's the client's problem, not ours"
Legally, perhaps. Commercially, no: a mission cut short stays in your supplier history, and the buyer takes it into account at the next framework review.
"Our salespeople don't have time to follow placed consultants"
The follow-up described here is roughly two hours per mission across three months. A replacement costs twenty to thirty, before counting bench time. The arithmetic rarely favours doing nothing.
"The client finds our check-ins intrusive"
That's a question of format, not principle. A short factual message ("quick check on the start, is everything in place on your side?") reads as professionalism. A disguised sales call does not.
"Our consultants tell us everything is fine"
Often because the question asked is "is it going well?", to which the only answer is yes. Prefer questions that require a factual answer: "what did you deliver this week?", "who validates your work?".
Frequently asked questions
Why do consulting missions end early?
Early terminations are rarely caused by technical shortfall: the client already validated the level at interview. The dominant causes are a scope that differs from the one sold, no onboarding on the client side, and the absence of a named technical contact in the first week.
When is the riskiest moment of a mission?
Weeks 1 to 4. Week 1 exposes any gap between the requirement sold and the actual role; weeks 2 to 4 expose whether the client organisation has actually made room for the consultant. Beyond month 4, breakdowns are usually driven by client reorganisation or budget, which you cannot control.
How much follow-up does a placed consultant need?
About two hours spread over the first quarter: a 20-minute call at the end of week 1, a short client message at week 2, a 30-minute joint review at week 4, and a 45-minute formal review at month 3. That is an order of magnitude less than the cost of a replacement.
What should be checked before the first day?
Five things: the real scope confirmed with the operational manager rather than the buyer, a named technical contact with their availability, access logistics (badge, VPN, accounts), the presence rhythm agreed in writing, and the dossier sent to the client shared with the consultant.
How do you turn onboarding into a commercial advantage?
Use the 30-day review. Once the consultant has delivered a visible result, ask the manager what would have saved them time and whether other needs are coming. Credibility peaks at that moment, and the answers both improve your next onboarding on the account and surface requirements before they reach a formal RFP.
Bringing in tooling without losing the human link
| Step | What the tool speeds up | What the firm keeps |
|---|---|---|
| Pre-mission | Milestone reminders, access checklist | The framing conversation with the manager |
| Week 1 | Scheduling follow-up checkpoints | Reading the weak signals |
| Month 1 | Capturing context and deliverables | Analysing the real fit |
| End of mission | Updating the consultant's dossier | The repositioning decision |
A dossier management tool doesn't replace follow-up. What it prevents is the material produced during the mission (context, scope, results) being lost between one placement and the next. That's what lets you present a consultant twice as well documented as they were six months earlier.
Key takeaways
The first 30 days aren't delivery's problem alone: they extend the sales cycle. A secured mission means margin preserved, an account reinforced, and a richer dossier for the next placement.
Three habits that get you there:
- Prepare during the notice period: scope confirmed with the operational manager, access validated, dossier shared with the consultant.
- Force the end-of-week-1 checkpoint: that's when a scope gap is still fixable by a conversation.
- Use the 30-day review as a commercial appointment as much as a quality control.
Selling a mission takes weeks. Losing one takes six.
Read next
Enterprise RFPs: industrialising your response without standardising the profiles
Answering an RFP fast and answering it well are contradictory demands, unless what you standardise is the process, not the content. A method for holding both.
Defending your day rate: what a competency dossier changes in the negotiation
Price is rarely negotiated on price. It is negotiated on proof. How to build a dossier that justifies a rate gap without falling back on a discount.
Skills mapping: from reactive to proactive staffing in ESN
When a client need lands, the race is already on. Structuring an internal skills repository helps you anticipate, pitch earlier, and spend less time searching the bench.