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.
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.
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.
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.