STRATEGIC ADVISORY

Ongoing Fixed Asset Strategic Advisory

Some questions only come along every few years, and they are always the expensive ones. Now there is a new one on every finance team's list: what to do with AI. This is having someone who already knows your environment on the other end of the phone, whether the question is a capitalization call, a system decision, or which AI tools to trust with your fixed asset data and which decisions should stay with a person.

Fixed asset decisions are rare, consequential and painfully hard to unwind. Most organizations do not need a full-time expert in them — they need one who picks up at the moments that matter and is useful in the first five minutes, not the third meeting.

That is what an advisory relationship buys: continuity. Someone who already knows your systems, your policy, your history and which decisions were made under duress, so you are not re-explaining your own environment every time something surfaces.

Increasingly, one of the questions that surfaces is AI: where it belongs in the fixed asset lifecycle, where it does not yet, and how to adopt it without handing judgment to a tool nobody can audit. Advisory now covers that conversation directly.

What advisory covers

Scope and access are defined in the engagement, so the relationship fits how your team actually works.

  • Complex fixed-asset decisions

    Capitalization, componentization, useful lives, impairment, classification and treatment questions that need a defensible answer.

  • Transformation governance

    Oversight of programs already under way, so decisions stay consistent with the design as pressure builds.

  • CIP oversight

    Standing review of aging, closeout discipline and capitalization consistency.

  • Software & implementation decisions

    An independent read on requirements, selection, scope changes, vendor positions and go-live readiness.

  • Data issues

    Triage and direction when the register, the reconciliation or the reporting stops behaving.

  • Policy & process development

    Write, revise and keep current the policies that the process is supposed to follow.

  • Major organizational or transaction events

    Acquisitions, divestitures, restructurings and system consolidations that move large asset populations.

  • Staff transition & knowledge continuity

    Cover and capture the process when the person who held it changes roles or leaves.

  • Roadmap oversight

    Keep the sequence honest as priorities shift and new work arrives.

  • Periodic health reviews

    Re-examine the environment on a defined rhythm, so drift is caught before it becomes a project.

  • AI use cases across the lifecycle

    An independent view on where AI adds real value in your fixed asset process, which use cases to start with, and which to leave alone for now.

  • AI governance & vendor claims

    Separate what an AI feature can actually do from what the demo implies, and decide who keeps the authority when it is in the loop.

SOFTWARE · AI · IMPLEMENTATION

Software and AI decisions

Before, during and after an implementation, independent of any vendor. Software makes a process faster and more consistent; it has never once made a process correct.

  • Turn on AI, buy an agent, or use what you license

    Whether to switch on the AI features in your current system, buy a separate agent, or put the AI licenses your company already has to work, decided against your process, data and controls rather than the demo.

  • Requirements definition

    Translate accounting, reporting, control and operational needs into requirements a vendor can be held to.

  • Software selection support

    Independent evaluation against your actual requirements and complexity, not a feature matrix.

  • Implementation readiness

    Establish what has to be true (data, policy, ownership, decisions) before the project starts.

  • Implementation oversight

    An independent read on scope changes, vendor positions, configuration decisions and go-live readiness as the project runs.

  • Conversion strategy

    Decide how treatment, history and relationships will be handled in the move, so the data work that follows has written rules to work from.

  • Testing & UAT

    Test scenarios built from real business cases and real data, so testing proves something.

  • Post-go-live optimization

    Stabilize, then improve: the configuration decisions worth revisiting once the system is in real use.

The independent seat at the table

Count the chairs in your next implementation meeting. The vendor represents the software. Each internal team represents its own department. The seat that is almost always empty is the one representing the fixed asset lifecycle across all of it: what the accounting has to produce, what the process has to survive, what the data has to support, and what still has to be true three years from now when everyone in the room has moved on.

That is the chair I pull up. The same goes for AI. Most fixed asset platforms now ship with AI features, and most finance teams already have an approved AI tool on every laptop. The question is rarely whether AI can help. It is which route fits, and each route has different consequences for data access, audit trail and who approves what. I help you make that call from the business side, then build it with your team.

IMPLEMENTATION RECOVERY

If an implementation is already in trouble

Recovery is a different engagement from a fresh implementation, and it starts in the same place: working out what is actually wrong. Functionality, configuration, data, reporting, integration, process, training and ownership all produce remarkably similar symptoms, and the difference matters, because it decides who can fix it.

  1. STEP 01 Independent diagnosis first.
  2. STEP 02 Evidence second.
  3. STEP 03 Coordination third.

That order is what turns a stalled project back into a plan.

Where AI earns its place in the fixed asset lifecycle

AI is not one decision. It is a series of smaller ones at each stage of the lifecycle, and the right answer is different at every stage. These are the areas where the conversation usually starts.

Capital planning & requests

Summarizing requests, surfacing comparable past projects and flagging incomplete justifications, so reviewers spend their time on the decision rather than the paperwork.

CIP & project costs

Reading invoices and project charges at volume, suggesting cost categories and flagging aging or stalled projects before they become a closeout backlog.

Capitalization & classification

Proposing asset class, useful life and capitalize-or-expense treatment from descriptions, with a person approving every call that touches the books.

Register data quality

Finding duplicates, inconsistent descriptions, missing attributes and orphaned records across systems, ahead of an audit or a conversion.

Physical verification & tagging

Matching field data, photos and scans back to the register, and pointing inventory effort at the locations most likely to be wrong.

Reconciliation & close

Explaining variances between the subledger, the general ledger and operational systems, so the close starts from an answer rather than a spreadsheet.

Maintenance, impairment & useful life

Using condition and maintenance history to show when useful-life assumptions or impairment indicators need a second look.

Disposal & retirement

Spotting assets that have left operations but never left the register, and linking disposal evidence to the record it closes.

Policy, knowledge & training

Turning policy, procedures and past decisions into something staff can query, so knowledge stops living in one person's head.

Use cases first, tools second

Most AI conversations start with a product. The useful ones start with the process: where the hours actually go, where the errors actually come from, and which decisions carry real accounting or audit exposure. Some of those are excellent candidates for AI. Some need a clean process and clean data first, because automating a broken process only makes it fail faster.

Advisory helps you rank the candidates by value and risk, pilot the right ones, judge vendor claims against your own data, and keep a clear line between what the tool suggests and what a person approves. Capability is not authority: the system can propose a useful life, but someone accountable still has to own it, and the record has to show who did. More on that thinking in The Same Conversation in Every Room and This Market Is Moving. We Move With It.

AI in your advisory relationship

For clients on a monthly advisory retainer, AI becomes part of the standing conversation rather than a separate project:

  • AI tool and vendor decisions. An independent read on new AI features, agents and vendor claims as they arrive, measured against your own data and controls.
  • Prompt and workflow tuning. Reviewing and improving the prompts and AI workflows your team already uses as policy, systems and staff change.
  • Guardrail reviews. A periodic check that the line between what AI may find, draft and decide is still where you put it, and that the record still shows who approved what.

When the work needs more than advice, such as a readiness review, a prompt library or workflows built with your team, it becomes a scoped project that follows how we work: assess, organize, build together, and you own it.

Keeping the know-how

In most organizations, the most important fixed asset process lives entirely in one person's head. It works beautifully, sometimes for decades, and then that person gets promoted, retires or simply has a better offer, and the organization discovers how much of its control environment was really one individual's judgment and goodwill. With accounting turnover rising, that is happening more often, not less.

Half the value of advisory is answering hard questions as they arrive. The other half is making sure the answers, the reasoning and the process end up written down and kept current, so they belong to you and not to whoever happened to be in the room.

What gets maintained over time

  • Desk procedures

    Step-by-step procedures for the recurring fixed asset and CIP work, updated as policy, systems and people change.

  • Prompt libraries

    The tested prompts your team uses, written to your own capitalization policy and revised when the tools or the policy move.

  • Workflows

    The AI and manual workflows built with your team, reviewed so the line between what AI drafts and what a person decides stays where you put it.

  • Decision records

    Treatment calls and the reasoning behind them, captured as they are made, so the next person inherits the why as well as the what.

How it typically works

Defined access

An agreed rhythm and response expectation, so the relationship is dependable rather than ad hoc.

Standing context

Your environment, systems, policy and history already known — no re-briefing before every question.

Documented outcomes

Decisions and reasoning captured as they are made, building institutional knowledge instead of dependency.

Escalation into project work

When something needs more than advice, it becomes a scoped project rather than an open-ended commitment.

Scope

Every advisory relationship is scoped to the organization it serves. Scope, access and response expectations are defined in the engagement, shaped by how often the questions arrive and how much of the process needs capturing.

A short call is enough to work out what that shape would look like for you.

Schedule a call

Common questions

How is advisory different from a project engagement?

A project has a defined scope, deliverable and end. Advisory is continuity: senior expertise available across whatever arrives, with the context already in place. Work that needs a defined outcome is scoped as a project, so the advisory relationship stays what it is meant to be.

Is there a minimum commitment?

Advisory relationships are defined in the engagement, including duration, access and response expectations. The shape follows the need rather than a standard package, and it is agreed before anything starts.

Can advisory follow an assessment?

That is the most common path. The assessment produces a sequenced roadmap; advisory keeps that roadmap honest as the organization works through it, and provides the senior judgment the sequence assumes.

Do you implement fixed asset software, or advise on it?

We work from the business side: readiness, requirements, selection, oversight, testing and post-go-live optimization. We never represent a software vendor. Hands-on data conversion is something we execute in Sage Fixed Assets Depreciation, CIP and Tracking as part of the cleanup and conversion work that follows a Health Assessment; for other platforms we prepare and validate the data alongside the team performing the load.

Our implementation is live and not working. Is it too late?

No, but the first step is diagnosis rather than remediation. Post-go-live problems usually have several contributing causes across configuration, data, process and training. Establishing which is which, with evidence, is what makes the fix sequence and the responsibility clear.

Can you help us decide where to use AI in our fixed asset process?

Yes. Advisory looks at your process, data and systems across the lifecycle — from capital planning and CIP through capitalization, the register, verification, reconciliation and disposal — and identifies where AI is likely to add real value, where it needs groundwork first, and where it should not make the call. The aim is a short, prioritized list of use cases with clear ownership, not a tool purchase.

Do you sell or implement an AI product?

No. The advice is independent of any vendor. That independence is the point: it lets you judge what a platform's AI features actually do against your own data and controls, and decide whether they are worth adopting.

LET'S TALK

Explore a strategic advisory relationship.

If fixed asset questions keep landing on your desk — including where AI should and should not fit — and there is no senior seat to send them to, that is exactly the conversation to have.

Fixed Asset Consultant • Founded by Angela Bolton • angela@fixedassetconsultant.com

Related services

The problem showing up in one area often belongs to another. These are the adjacent engagements that most often turn out to be relevant.

FURTHER READING
All insights