Start with the business. Establish what is true. Then decide.
A consultancy engagement should reduce uncertainty. The work is structured around the question the business needs answered, not around selling a predefined stack of products.
A simple sequence, applied properly.
The detail changes with the assignment. The underlying approach does not: understand the business context, establish the facts, explain the choices and stay involved where implementation benefits from continuity.
What needs a clearer answer?
We start with the trigger for the enquiry, the outcome you want and the constraints around the business.
What is actually happening?
Review the relevant systems, information, controls, process and people rather than assuming the stated design matches reality.
What should change?
Set out the options, priority, cost implications, limitations and what does not need changing.
Did the change work?
Where useful, stay involved with the implementation so the original business purpose is not lost.
The first conversation is for orientation, not selling.
Tell me what has prompted the enquiry, what you are trying to improve and where the uncertainty sits. You do not need to know the technical cause. A proposed purchase, a concern raised by a client or a process that is not working well can all be enough to start.
The initial conversation is free. It is also a chance to establish whether I am the right person to help.
The scope and price are agreed before work starts.
The assignment should have a clear question, a defined boundary and an agreed output. If the requirement changes materially, we discuss the effect on the work and cost before proceeding.
I prefer a piece of work that answers the important question well over an open-ended engagement that grows because the brief was never clear.
Recommendations are not tied to licence or product sales.
I receive no commission from product or licence sales. That matters because the right answer may be to configure what you already own, change a process, delay a purchase, run a small trial or decide that a proposed project does not justify the effort.
The recommendation should be something you can challenge. I explain the reasoning, trade-offs and limitations so the business can make its own decision.
Your existing IT provider can remain part of the solution.
They know the environment and day-to-day requirements. I can provide an independent assessment, help set the desired outcome and work with them on the agreed changes. That division is often healthier than asking the same supplier to define the problem, specify the solution, sell it and then assure the result.
The output should be usable by management and by the people doing the work.
Depending on the assignment, that can mean a concise findings document, a prioritised action plan, an implementation design, decision notes for leadership or direct working sessions with your technical team or supplier.
The aim is not to maximise documentation. It is to leave the business with a clearer position, an agreed direction and enough detail to act.