Review whether the leader understood the buyer and funnel, named the main constraint, made explicit tradeoffs, established owners and set measurable next tests. Look for evidence and collaboration, not just a polished plan. Long-cycle pipeline and revenue may not yet be mature enough to judge.
Revisit the original problem
Start with the problem you hired the leader to solve. If the brief was “qualified demos are falling”, ask what evidence they examined and what they now believe causes the fall. If the answer is only a list of completed tasks, the diagnosis may be missing. The first-90-days guide helps place month-one work in a longer sequence.
Inspect decisions and owners
List what the team decided to continue, stop, test and defer. For each, note the evidence, decision owner, maker and review date. Good leadership can reduce the number of competing projects. A new dashboard or campaign calendar is useful only if it changes what the team does. Ask sales and product whether the leader has understood their constraints.
Check execution readiness
Can the planned tests actually ship with the available people and budget? Are claims approved, tracking defined and approvals timely? A leader may correctly diagnose a problem yet fail to set up the people who must act on it. Conversely, a first month spent on customer access and measurement repair may be necessary before a campaign result is possible.
Make a fair next decision
For a hypothetical enterprise SaaS with a six-month sales cycle, judge the first month on buyer insight, a buying-group map and a useful proof plan. For a D2C brand with daily paid spend, expect faster observation of channel economics. Continue, narrow or stop the engagement based on the agreed job and evidence, not an imported universal deadline.
Score the first month in four dimensions
Use a simple one-to-three scale for evidence quality, decision clarity, execution readiness and working relationship. For evidence quality, look for direct buyer or deal observations rather than platform screenshots alone. For decision clarity, ask whether the team knows what to stop and why. For execution readiness, inspect owners, budget and measurement. For working relationship, ask whether sales, product and the marketer can raise contradictions safely and receive a clear response.
Write an example beside every score. “Two recent lost deals changed our initial ICP hypothesis” is stronger evidence than “the strategy feels better”. A low score should lead to a specific repair: provide missing data, narrow the scope, change the decision rhythm or stop. A high score does not guarantee eventual revenue. It just shows that the leader is building a functioning way to learn and act. Revisit the score after enough time for the first tests to mature.
Frequently asked questions
What should exist by the end of month one?
Usually a documented diagnosis, agreed priorities, metric definitions, responsibility map and the first executable tests, adjusted to the actual engagement scope.
Should I stop the engagement if revenue has not risen?
Not on that fact alone. Compare the sales cycle and starting conditions with the agreed evidence standard; stop or rescope if the leader cannot explain the work and next decision.
Does the first month feel busy without a clearer direction?
Bring the initial scope, decisions made and work in motion. We can assess whether the engagement is solving the right problem.
Talk through the problem ↗See how we could work together
