Put AI in the operating rhythm

Revenue organizations run on a rhythm: annual account planning, monthly and weekly business reviews, and customer briefings. These rituals consume enormous amounts of leadership time, and much of that time goes to assembling information rather than acting on it.

At AWS, I built AI into annual account planning, MBRs, WBRs and customer briefings. It was part of the competitive GTM strategy I authored against the Azure/OpenAI partnership, which drove 3x pipeline growth and a 1.5x win rate.

Start with the meeting, not the tool

The mistake I see most often is starting with an AI tool and looking for a place to use it. I start with the meetings and documents the business already depends on, and ask: what in this ritual is assembly, and what is judgment? Assembly is where AI helps.

Account plans that update themselves

Annual account plans are usually stale by the second quarter. With AI-assisted research, plans can be refreshed as signals change, so the plan reflects the customer's current priorities, not last January's.

Business reviews focused on decisions

When the pre-read is assembled automatically, the weekly or monthly review can spend its time on decisions: which deals need help, where to redeploy resources, what risks need escalation.

Briefings that respect the customer's time

Executive briefings are high-stakes. AI can help teams prepare deeper, more specific briefings faster, so every customer conversation starts with an informed point of view.

Guardrails still matter

AI output in a revenue context has to be checked. Forecast numbers, pricing and commitments must come from the system of record and the controls designed with Finance, not from a model's summary. I treat AI as an accelerator for research and preparation, and keep the commercial controls firmly human-owned.

A practical sequence

When I bring AI into a team's operating rhythm, I go in this order. First, the weekly business review, because it happens most often and the time savings show up fastest. Second, customer briefings, because they have the most direct impact on deals. Third, annual and quarterly account planning, because it depends on the research habits the first two build.

At each step, I define what the AI prepares, what the human decides, and who checks the output. That clarity matters more than which tool you pick.

Competing against bigger players

The competitive strategy I authored at AWS was a response to a major partnership that was reshaping how enterprises bought AI. We could not out-spend the competition everywhere, so we focused on being better prepared in every customer conversation. AI-assisted planning and briefings were a big part of that. The result was 3x pipeline growth and a 1.5x win rate.

Mid-market companies face a version of this every day. They are often competing against larger rivals with more people and more marketing budget. Preparation is the equalizer, and AI makes deep preparation affordable.

Adoption is a leadership job

New tools fail when leaders don't use them. If the CRO runs the weekly review off the AI-prepared pre-read, the team will adopt it. If the CRO keeps asking for the old spreadsheet, the AI project will quietly die. I make sure the leadership team models the new rhythm from the first week.

Start small, measure honestly

I would rather run one AI-assisted review well for a quarter than launch five pilots at once. Measure the time saved, the quality of decisions and the effect on pipeline, then expand.

Then expand the rhythm one ritual at a time, so the team builds the habit instead of just tolerating the tool.

For mid-market companies and PE portfolio companies, putting AI into the operating rhythm is often the fastest, lowest-risk way to show measurable GTM productivity gains.