Build a 90-Day Client Account Plan Before You Pitch Another Product

Good clients still get managed one transaction at a time

A client buys connectivity. The order installs. Everybody moves on. Three months later, someone notices a security renewal, a new location, or a contact center problem and starts another sales conversation from scratch.

The advisor may know the account well. The trouble is that the knowledge lives in call notes, inboxes, contract files, supplier portals, and memory. Nobody can see the next ninety days as one set of client decisions.

That creates two bad habits. You either wait for the client to ask for something, or you pitch the next product that looks adjacent to the last one. Both are easier than account planning. Neither makes you much of an advisor.

A useful account plan is smaller than most teams think. It does not need a thirty-slide strategy deck or a complete three-year roadmap. It needs a clear view of what changed, which dates matter, who cares, where the current environment is creating friction, and which decision deserves attention next.

Ninety days is long enough to prepare for a real decision and short enough to keep the plan honest.

Start with the client's current priorities

Do not begin with your supplier catalog. Begin with what the client is already trying to do.

Maybe the company is opening two locations. Maybe finance wants fewer vendors. Maybe the IT director is rebuilding the support model after a leadership change. Maybe nothing dramatic is happening and the priority is simply to finish the projects already underway.

Capture the priorities in the client's language. "Improve network" is weak. "Open the Raleigh site by October without extending the current firewall contract" gives the team something it can plan around.

Limit the active plan to the few priorities that can change a decision during the next ninety days. A long list is usually a sign that nobody chose what matters. If the client has not confirmed a priority, mark it as an assumption and assign a conversation to validate it.

Your earlier technology advisor discovery process should give you the first version of this context. Account planning keeps it current after the first opportunity closes.

Put every contract event on the same timeline

Account plans get expensive when contract timing is treated as back-office data.

List the next events that can narrow the client's options: notice deadlines, renewal dates, price changes, installation commitments, service migrations, equipment end dates, and open amendments. Use the signed agreement for exact terms. A CRM field is useful for sorting, but it should not become a substitute for the contract.

Then work backward. If a service has a notice deadline in 120 days, the next ninety days may need discovery, inventory validation, supplier performance review, and an agreed renewal path. If you wait until the deadline appears in a thirty-day report, the plan has already failed.

The technology advisor renewal playbook covers that operating motion in detail. In the account plan, you only need the contract events that could change the next client decision.

Map the people who can move or stop the decision

A company record with twenty contacts is not a stakeholder map.

For each active priority, identify the person who owns the business outcome, the technical evaluator, the financial approver, the person affected by implementation, and anyone who can quietly stop the work. One person may fill several roles. The point is to understand the decision, not force every contact into a box.

Record what each stakeholder cares about and the last confirmed interaction. Do not write fiction such as "CFO supports project" because someone copied the CFO on an email. Write what you know: "Operations director confirmed the opening date on July 28. Finance approval process is still unknown."

This is also where relationship gaps become visible. If your entire account depends on one friendly contact, the next step may be earning a broader conversation rather than proposing another service.

Advisor OS CRM connects contact roles, organization history, activities, tasks, deals, contracts, and renewals. The software can hold the context. The advisor still has to separate a known fact from a hopeful assumption.

Find service gaps without manufacturing a cross-sell

A service gap is not every category the client has not bought from you.

Look for evidence. A gap may be an unresolved support pattern, duplicated spend, a contract that no longer fits current locations, an implementation dependency nobody owns, or a business priority the current stack cannot support. Sometimes the gap is operational rather than technical. The client may have the right tools and no clear owner.

For each gap, write the evidence, the impact, and what still needs to be verified. That keeps the account plan from turning into a collection of convenient sales theories.

Some gaps should not become opportunities. The impact may be small. The timing may be wrong. The client may have a capable incumbent and no reason to change. Good account planning gives you permission to leave a service alone.

Choose one client decision for the next ninety days

Most small advisory firms do not need five active plays per account. They need one credible next decision.

Compare the priorities, contract events, stakeholder readiness, service evidence, and delivery capacity. Then choose the decision that deserves attention now. It might be to renew an incumbent, validate a second-site design, consolidate invoices, investigate a support failure, or pause a proposed migration until the client finishes another project.

Write the decision as something the client can agree to, reject, or change. "Discuss cybersecurity" is a topic. "Decide whether the client should run an independent security assessment before the insurance renewal" is a decision.

Attach a next external action, owner, and date. If the action is internal research, say what client conversation it is preparing. If no external conversation is planned, you probably have an internal wish list rather than an active account plan.

Use a one-page account plan

Your team should be able to review the plan without rebuilding the account. Keep one page or one operating view with these fields:

• Client priorities confirmed for the next ninety days, plus any assumptions still waiting for validation.
• Contract and delivery events that can narrow the client's options.
• Stakeholders, their decision roles, and the latest confirmed contact.
• Current services and evidence-backed gaps worth investigating.
• The one client decision the advisor is advancing now.
• Next external action, accountable owner, due date, and proof that the action happened.
• Risks that could stop the decision, including missing data, supplier dependencies, budget limits, and delivery capacity.

Add links to the underlying contract, activity history, opportunity, proposal, or task. Do not paste every fact into the plan. The plan should tell the team where the account is going and point to the evidence behind it.

Review plans by exception, not by calendar theater

A plan does not become useful because the team labels a meeting "account planning." Review it when something changed.

That change could be a stakeholder departure, a new location, a missed supplier commitment, a signed order, a contract date entering range, or a client priority that no longer matters. Update the plan when the facts move.

During your weekly advisor operating review, surface only account exceptions that require a firm-level decision. Give the deeper account conversation its own time. The operating review chooses which plan needs attention. It should not become a ninety-minute tour of every client.

At the end of ninety days, ask a blunt question: did the plan help the client make a better decision? If the only output was more product activity, the plan served you better than it served the account.

Build the plan before the pitch

A strong account plan may lead to a proposal. It may also lead to a renewal, a delayed project, a supplier escalation, or a decision to leave the current environment alone.

That is the point. The advisor should earn the next conversation by understanding the account, not by finding another product to mention.

Pick five active clients this week. Build one ninety-day view for each. Confirm the priorities, dates, stakeholders, evidence, and one next decision. If your team cannot do that without searching several systems and asking the founder what happened, run the free Advisor OS agency scorecard. The gap is probably bigger than account planning.