Selecting or replacing a system
Understand what the business needs before comparing software products or speaking to vendors.

Turn what your business knows into clear requirements for better systems.
I work directly with your team to understand how your business operates, uncover what a new or changing system needs to support, and turn that knowledge into clear, structured requirements.
Independent · Direct access · No large consulting engagement
My name is Evert Hoff. I conduct the interviews, analyse what I learn, identify gaps and contradictions, and structure the findings between sessions.
There is no hand-off to a junior analyst or delivery team. The person you speak to is the person doing the analysis.
Companies often reach the point where an existing system needs to be replaced, a new system needs to be introduced, or an important business process needs better support.
The people inside the business usually know what matters — but that knowledge is spread across different people, processes, workarounds, exceptions and assumptions.
That's where I help. I work with the people who understand the business, discover what the system really needs to support, and turn that knowledge into requirements that can be reviewed, discussed and used to make decisions.
The same discovery discipline is useful at several points in the life of a business system.
Understand what the business needs before comparing software products or speaking to vendors.
Give developers, vendors or implementation partners a clearer understanding of the problem they are being asked to solve.
Discover how people actually use a legacy or problematic system, including workarounds, exceptions and unmet needs.
Understand the current process, identify friction and clarify what needs to change before deciding how technology should support it.
I primarily use private one-to-one interviews with the people who understand each part of the business.
Individual conversations make it easier to explore how work really happens — including exceptions, workarounds, frustrations and differing perspectives that can be difficult to uncover in a large workshop.
Between sessions I analyse what I learn, identify gaps and contradictions, and use that understanding to guide the next conversations.
The exact outputs depend on the project. The aim is to capture the information needed for the decisions and work ahead — not to produce documents for their own sake.
What you are trying to achieve, why it matters and where the boundaries lie.
How work happens today, including important variations, exceptions and workarounds.
What the organization needs a system or solution to enable.
The capabilities and behaviours needed to support those business needs.
What is essential, what is desirable and what the solution has to work within.
Missing information, conflicting expectations and decisions that still need to be resolved.
Start by building a useful body of discovery without committing to a large consulting project.
The people, topics and outputs depend on your situation. The engagement is designed around discovery rather than a fixed questionnaire.
The initial engagement is designed to create a useful first body of discovery — not to pretend every business can be fully analysed in a fixed number of meetings.
If we have achieved what you need, we stop there. If further analysis would be valuable, we will have a much clearer understanding of what remains and can agree on the next piece of work before continuing.
My role is to understand the business problem, processes and requirements before steering the work toward a particular solution.
Occasional emails about requirements discovery, business processes, system selection and making better software decisions.
Tell me what system or business problem you're working through. We'll discuss what you need to understand, whether business-analysis support would help, and what a sensible next step looks like.
Business Requirements Discovery — $1,000
Seven private 45-minute working sessions. Preparation and analysis between sessions included.