top of page
soft.jpg

Assessment

The application is in place, but no one can give a straight answer about why it is still causing problems.

Get a clear view of how the application was set up, how people are actually using it, and where the problems are showing up across process, data, reporting, integrations, automation, and security.

Start the Conversation

Starting at

$4,500

The application may be in place, but people are still relying on workarounds to get the job done.

Reports get rebuilt in spreadsheets. People keep their own notes or trackers because they do not trust what is in the system. Automations fail or no longer match the process. Data does not line up. Configuration added over time becomes difficult to follow.

​

At some point, someone has to work out whether the problem is the process, the way the application was set up, the data, or a combination of all three.

Process fit

Does the application still support the way the work is done today?

Configuration and customization

Are configuration, customizations, or automation helping the process or getting in the way?

Data and reporting

Can people rely on the data and reports without rebuilding them somewhere else?

Priority and direction

What should stay, what needs attention, and what should be addressed first?

Understand what is causing the problems before deciding what comes next.

An Assessment starts with the problems people are running into in their day-to-day work. We look at where the process breaks down, what people do outside the application, and how the system is supporting the work today.

​

From there, we review the configuration, data, integrations, permissions, and other areas tied to those problems to see where the issues are actually coming from.

01

Start where people are having problems

Identify where people repeat work, rebuild reports, wait for information, leave the application, hit errors, or use another tool to finish the job.

02

Trace those problems through the process and application

Review how the work moves from person to person and system to system, then look at the configuration, customizations, data, reporting, integrations, automations, permissions, and user habits involved.

03

Put the issues in the order they need to be handled

Separate what is working from what is not, define the requirements behind the issues, and identify which items need attention first.

Choose the Assessment for the Microsoft application you already use.

Each Assessment looks at how the business uses the application today, how it has been configured, and where the current problems are coming from.

​

That review covers process, configuration, data, reporting, integrations, automation, permissions, and user adoption where they are relevant to the issue being investigated.

Business Central Assessment

Dynamics 365 Sales Assessment

Dynamics 365 Customer Service Assessment

Dynamics 365 Customer Insights Assessment

Dynamics 365 Field Service Assessment

Dynamics 365 Project Operations Assessment

Business Central Assessment

Question the Assessment answers

Why is Business Central no longer supporting finance and operations the way the business needs, and what should be addressed first?

What Alliason works through with your
team

How finance and the affected operational processes work today

Where people rely on spreadsheets, reconciliations, duplicate entry, or manual steps

How Business Central is configured for the areas being reviewed

Which extensions, customizations, workflows, and automations affect the work

Data quality, reporting, permissions, integrations, existing documentation, and how people actually use the application

What leadership will know

Which problems come from process, configuration, customization, data, integration, permissions, or application use

What is working and can stay

Which issues are creating the most manual work, reporting problems, or business risk

Which requirements need to be addressed and in what order

The backlog and measurable outcomes that can guide the work that follows

What the Assessment asks of your team, and what you receive.

You do not need to approve another set of changes before you understand what is going wrong. We review the business process and the parts of the application tied to the problem.

​

The findings show what is working, what is not, and what needs attention first.

Starting Investment

$4,000

We confirm the scope and fixed fee after a short conversation about the application, the problems being investigated, and the areas that need to be reviewed.

Typical Timeframe

2 weeks

Most Assessments are completed within two weeks. Timing depends on access to the application, available documentation, and the availability of the people who know the work.

Customer Time

2 to 4 hours per person

Participants are involved where their knowledge of the process, application, or problem is needed.

Participants

The people who use, manage, and depend on the application

Participants may include the executive sponsor, application owner, IT, department leaders, subject matter experts, managers, and users who understand the affected work.

01

Start with the question you need answered.

We begin with the problems people are seeing. That might be a report no one trusts, a process people work around, an integration that keeps failing, low adoption, repeated manual work, or a part of the application that no longer fits the way the business operates.

02

Review what already exists

We look at available process documentation, system documentation, reports, backlog items, requirements, configuration information, and other material that helps explain how the application was intended to work and what has changed over time.

03

Talk to the people who use the application

Stakeholder and user interviews show how the work happens in practice, where people leave the application, what information they cannot get, what they do instead, and where the same problem keeps coming up.

04

Review the application and the systems around it

We look at the affected business processes, configuration and customizations, data and reporting, integrations and automations, security and permissions, and how people use the application.

05

Document what is causing the problems

We compare what people are experiencing with what we find in the process and application. The findings are documented as recommendations, defined requirements, measurable outcomes, and a prioritized backlog.

06

Walk through the findings

In a 1-hour Executive Findings Call, we review what is working, what is not, what is causing the problems, what should stay, and what should be addressed first.

​

The Assessment is diagnostic only. No changes are made to the live application as part of the Assessment.

What clients say about working with Alliason.

​

Highlight Health first brought Alliason in for a second opinion on a Dynamics 365 implementation that had gone off course. The Assessment showed what could still be used and what needed to change instead of assuming the existing work should be thrown away.

​

“They did not tell us to tear everything out and start over. They helped us build from what was already there and make it fit our needs.”

Alan M., Vice President, IT, Highlight Health

Questions buyers usually ask before starting an Assessment

Before anyone makes another decision about the application, make sure you understand what is causing the problems.

Bring us the application and the issues people are dealing with. We will review the process, the application, and the systems around it, then show what is working, what is causing problems, and what should be addressed first.

bottom of page