Blog /Accounting

New Controller First 90 Days: A Plan for an AI-Forward Company

Deepak Anchala

Deepak Anchala

Co-Founder and CEO, Adopt AI

18 November 2026

Engraved illustration of a hand checking off items on a project list

You start on a Monday, the previous controller left three weeks ago, and the close is due in eleven days. The new controller first 90 days problem is deciding what to do first, with a team watching to see what kind of boss you will be and far more tasks than days.

This plan is for a controller joining a company that already uses, or wants to use, AI in finance. It splits the 90 days into three stretches: learn, fix, and set up. You can adapt the dates to your own close calendar.

Days 1 to 30: learn the close as it is

Resist the urge to change anything in the first month. Your job is to understand the process, the people, and the numbers.

Run one close without changing it. Sit beside the people who prepare it. Write down every task, who does it, what system it touches, and how long it takes. The month-end close checklist gives you a template to compare against.

Meet the people the close depends on. That list includes your CFO, the staff accountants, the AP and AR leads, the external auditors, and whoever owns the ERP. Ask each person one question: which step breaks most often?

Read the last two audits and the open findings. Auditor comments tell you where controls are thin before anyone else says so.

Collect a baseline. Record the number of business days to close, the number of manual journal entries, and the number of unreconciled accounts on day five. You will need these numbers on day 90 to show what moved.

Days 31 to 60: find the bottleneck and fix the cheap things

With a baseline in hand, look for patterns.

  • Where do items wait? A task that sits for two days before someone touches it points to a handoff problem.
  • Which reconciliations take the longest? Bank and credit card reconciliations often lead the list. Our bank reconciliation guide shows the steps.
  • Which errors repeat? Duplicate invoices, missing support, and coding mistakes recur because nothing stops them upstream.

Fix what costs nothing first: a close calendar with owners and due dates, a rule for how support gets attached, and a cutoff time that everyone knows. These changes tend to win your team's trust faster than any tool.

Then write a one-page list of the three biggest time sinks, ranked by hours. That page drives the rest of your plan.

Days 61 to 90: set review standards and pick a first workflow

The last month turns your findings into a plan.

Define what review means. In an AI-forward company, the controller's team moves from preparing work to reviewing it. Write down what a reviewer checks, what counts as an exception, and who signs off. A review step that nobody defines becomes a rubber stamp. Our AI controller job description describes how the role shifts.

Choose one workflow to automate. Take the biggest time sink from your list. Reconciliation is a common pick, since the work is repetitive and the source documents are clear. Run an agent beside your current process for one or two closes. Nothing should post to your books without a named reviewer's approval, and every number should link back to the transaction or document behind it. Adopt works this way, and the same standard applies to any tool you evaluate. For a structure to follow, see the 90-day pilot plan.

Measure exceptions, not hours saved. Count how many items needed a person and why. That list shows which skills your team needs next, and it gives your CFO something concrete.

Tell your team the order of the story. Lead with the outcome: a close that finishes sooner. Then the role: people run the agents, and they move from doer to reviewer to builder. Our piece on upskilling your accounting team for AI covers the training side. If the first thing your team hears is "automation," they will hear "layoffs."

What to bring to your day 90 review

Bring your CFO a short document:

  1. The baseline and the current numbers for days to close and unreconciled accounts.
  2. The three fixes you made and what they changed.
  3. The workflow you chose, the pilot results so far, and the exception count.
  4. A proposal for the next quarter, with the reviewers named.

A document like this shows judgment. It also gives your CFO a way to describe your first quarter to the board.

Mistakes to avoid

  • Buying a tool before you know the process. You cannot judge a vendor without a baseline.
  • Starting with the hardest workflow. Pick one with clear inputs and a clear owner.
  • Skipping the auditors. Tell them early what you plan to change. They will tell you what evidence they need.
  • Measuring only speed. A fast close with errors costs more than a slow one without them.

Where to start

On day one, open the checklist and sit beside the person who prepares the first reconciliation. By day 90, you will know which workflow deserves an agent. To see agents prepare a close you already finished, with nothing posting to your books, book a pilot.

FAQs