Atlas
  • All-in-one
  • Solutions
  • Compare
  • Pricing
PricingGet started
  1. Atlas
  2. Guides
  3. The First Ninety Days of a New Engagement
August 30, 2026·11 min read·engagement management, delivery, client relationships, consulting

The First Ninety Days of a New Engagement

A client forms their view of a firm in the first six weeks and spends the rest of the engagement confirming it. Very little of that view comes from the deliverables.

The opening period of an engagement is disproportionately consequential, and firms tend to staff it as though it were ordinary. The people are still arriving, the plan is still theoretical, and the deliverables are months away, so attention goes elsewhere. Meanwhile the client is deciding whether this team is competent, whether they listen, and whether they can be trusted with something difficult.

This guide sets out what to establish, what to prove, and what to be measured on, month by month, and the drift signals that appear well before anything shows up in a status report.

Month one: establish

The first month is about removing uncertainty rather than producing insight. Almost everything that goes wrong later is traceable to something left ambiguous here.

  • Who decides what, on the client side, at what value, and who deputises when they are away.
  • What the deliverables are, in enough detail that acceptance is checkable rather than negotiable.
  • Which of the firm's assumptions the client would dispute, found by reading them out rather than by circulating them.
  • The rhythm: when the status report lands, when the governance meeting sits, and what each is for.
  • One early, visible piece of work that the client did not expect and did not have to ask for. This is the single most reliable way to establish competence, and it costs less than the goodwill it earns.

Month two: prove

The second month is when the firm demonstrates that it can do the thing it was hired for, and when the relationship survives or does not survive its first disagreement. Both are worth preparing for.

Produce something real and put it in front of the client earlier than feels comfortable. A partial analysis discussed in week six is worth more than a complete one presented in week twelve, because it converts the client from an audience into a participant and surfaces the misunderstanding while it is still cheap. Firms resist this because early work is imperfect; the imperfection is the point, provided it is labelled honestly.

Expect the first disagreement in this window and treat it as a design problem rather than a relationship problem. What matters is not being right but being clear: state the position, state what would change it, and give the client a decision rather than an argument.

Month three: be measured

By the third month the client is forming a settled view, and it will be based on three things: whether dates held, whether surprises were rare, and whether the team understood their business well enough to be useful without being briefed each time.

The third is where firms most often fall short and where the effort is most repayable. A team that has read the client's last two board packs, understands their reporting calendar and knows the names of their major customers is treated as an insider. A team that asks the same context question in month three as in week two is treated as a vendor, whatever the quality of the analysis.

The drift signals

These appear weeks before any measure moves, and each is actionable on the day it is noticed.

  • The sponsor starts sending a deputy to the governance meeting. Attention has moved elsewhere, and so has the engagement's political cover.
  • Questions arrive by email that used to be asked in the room. The relationship is becoming transactional.
  • The client's team stops volunteering context and starts answering only what was asked.
  • Deliverable comments become about wording rather than about substance, which usually means the substance is no longer being read.
  • Meetings are rescheduled more than once. This is the earliest and most reliable indicator of all, and the easiest to explain away.

The ninety-day review that is worth holding

Hold a deliberate review with the sponsor at the end of the first quarter, separately from any status meeting, and ask three questions: what has been most useful, what has been least useful, and what would you change about how we work together.

The value is in the second and third answers, and they only come if the first is asked first. Very few sponsors will volunteer criticism, and almost all will give it when asked directly in a conversation framed as improving the work rather than defending it. Whatever comes back, change something visible within two weeks, because a review that changes nothing teaches the client not to bother next time.

Keep reading

  • How to Write a Weekly Status Report a Client Actually Reads
  • Client Onboarding for Advisory Firms: The First Two Weeks
  • Deliverable Acceptance Criteria That Hold Up
  • Fixed Fee versus Time and Materials: How to Choose
  • How to Close an Engagement Properly
  • How to Measure Engagement Health Before It Goes Wrong
  • Free PDF tools
  • The all-in-one work OS

FAQ

Questions, answered.

What should be established in the first month of a consulting engagement?
Who decides what on the client side and at what value, what the deliverables are in checkable detail, which of the firm's assumptions the client would dispute, and the reporting and governance rhythm. Adding one early, visible piece of unasked-for work is the most reliable way to establish competence, and it costs less than the goodwill it earns.
When should a firm show a client work in progress?
Earlier than feels comfortable, typically around week six. A partial analysis discussed early is worth more than a complete one presented late, because it turns the client into a participant and surfaces misunderstandings while they are still cheap to correct. Label the state of the work honestly rather than polishing it first.
What are the earliest signs an engagement is drifting?
The sponsor sending a deputy to governance meetings, questions moving from the room to email, the client's team no longer volunteering context, deliverable comments turning to wording rather than substance, and meetings being rescheduled more than once. Each appears weeks before any measure moves.
How do you run a useful ninety-day client review?
Hold it separately from any status meeting and ask what has been most useful, what has been least useful, and what the client would change about how you work together, in that order. Then change something visible within two weeks. A review that changes nothing teaches the client not to give honest answers next time.

Ready when you are

One workspace, not ten.

Atlas replaces the stack with one platform for tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics. Start free.

Get started freeSee pricing
AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus