Skip to content
InteliSense IT — Navigating Change, Delivering Value

How we help

Start with what is happening.
Not with a product name.

ConfusionDirection

You may be planning something new. You may already be implementing it. The platform may be live but underperforming. You may be considering a different partner. Start with your situation and we will help you find the right route.

Find your starting point

The platform does not define the engagement by itself. The right intervention depends on what is actually happening.

Three questions that are not the same question

Situation, capability and context are separate decisions.

Situation decides the commercial starting point. Capability identifies what may be required. Context changes how the answer should be designed.

  • 01 Situation

    What intervention is appropriate?

    Situation decides the commercial starting point. It is the only question that has to be answered first.

  • 02 Capability

    What technology or delivery capability may support it?

    Capability identifies what may be required. It is selected after the commercial situation is understood.

  • 03 Operating context

    What industry, complexity or specialist system changes the answer?

    Context changes how the answer should be designed. It rarely changes the commercial route on its own.

Find your starting point

Three questions. A possible starting point.

This is guidance rather than qualification. It points at a sensible place to start, and a person still reviews anything that follows.

1. What is happening?
2. Where are you today?
3. What systems are involved?

The systems question tells us what is involved today. It is context, not a recommendation to buy anything.

Your possible starting point

Answer the first question and a possible commercial starting point appears here, along with any capability that may support it. The second and third questions add context.

Commercial routes

Seven starting points. One connected relationship.

These are not a rigid sequence. Organisations enter wherever the pressure is and move between routes as the situation changes.

  • Possible starting point

    Assessment

    We are not sure what the real problem is.

    The organisation knows there is a problem, risk or decision, but the cause or the correct route is not yet established.

    Explore Assessment
  • Possible starting point

    Transform

    We are planning major change.

    The future operating model still needs defining before any platform is configured.

    Explore Transform
  • Possible starting point

    Standard Implementation

    We know what we need and are ready to implement.

    The target operating model and platform are sufficiently understood and conventional governed implementation is appropriate.

    Explore Standard Implementation
  • Possible starting point

    Recover

    Our project is in trouble.

    An active implementation has lost control, confidence or credible delivery status.

    Explore Recover
  • Possible starting point

    Optimise

    Our live platform should work better.

    A live platform works, but it should work materially better.

    Explore Optimise
  • Possible starting point

    Support

    We need dependable operational support.

    Agreed live capability needs dependable operational support and clear ownership.

    Explore Support
  • Possible starting point

    Partner Transition

    We are considering changing Microsoft partner.

    The platform may remain, but partner responsibility needs to move in a controlled way.

    Explore Partner Transition

Delivery method, not a commercial route

RAPID

Implementation requirementDelivery qualificationStandard Implementation or RAPID

Standard Implementation

Use where the requirement is understood but complexity, dependencies or readiness require conventional governed delivery.

RAPID

Use only where strict fit, scope, readiness, standardisation and decision velocity support accelerated delivery.

Acceleration depends on fit, readiness and decision velocity. A clear requirement is necessary for RAPID, but it is not sufficient on its own, and a defined requirement does not automatically qualify.

Explore RAPID qualification

After go-live

Support operates. Customer Success governs. Optimise executes.

Support
Operate the agreed live capability dependably.Explore
Customer Success
Post-live governance of value, priorities and improvement decisions. Support operates. Customer Success governs. Optimise executes justified improvement.Explore
Optimise
Execute improvement once it is justified.Explore

Capability

Capability supports the route. It does not choose it.

Useful when the platform area is already settled. If the operating problem is still unclear, start with the situation instead.

Data and intelligence

Capability used inside Assessment, Transform, Implementation, Optimise, Support and Customer Success. Not a commercial route on its own.

Connected delivery

The disciplines that decide whether a route succeeds.

  • Integration

    System boundaries, ownership of data and what happens when a connection fails.

  • Data Migration

    What moves, what does not, and what the business is asked to accept.

  • Implementation and delivery assurance

    Governed delivery, decision control and evidence of progress.

  • Adoption

    Whether people can actually work the new way once it is live.

  • Security

    Identity, access and assurance across human and non-human identities.

  • Licensing

    Licence hierarchy, entitlement and a date-stamped decision record.

Not sure which ERP?

Do not choose the platform first if the operating problem is still unclear. What process needs to work differently? What complexity exists? What needs to connect? What future operating model must the platform support?

Compare ERP options
Business Central
May fit where the operating model can remain relatively standard and connected without unnecessary enterprise complexity.
Finance & Supply Chain
May fit where deeper enterprise complexity exists across legal entities, supply chain, warehouse, manufacturing, governance or global operations. Complexity decides this, not company size.

Operating context

The same technology behaves differently in different operating models.

Industry gives the operating context. It does not determine the platform on its own.

Purpose-built solutions

Some service problems need more than a generic CRM starting point.

Each purpose-built solution keeps its parent industry context. They are qualified within that sector rather than offered as generic answers.

  • CRMS

    Crisis and Resilience Management System

    Qualified within Public Sector.

    • Crisis support
    • Hardship and community support
    • Request
    • Assessment
    • Case
    • Funding and support
    • Partner coordination
    • Evidence
    • Reporting
    Explore CRMS
  • CMS

    Clinical Management System

    Qualified within Healthcare & Care.

    • Referral
    • Person context
    • Service coordination
    • Capacity
    • Cases and incidents
    • Communication and reporting
    Explore CMS

CRMS supports crisis, hardship and community support coordination. It is not an emergency command, emergency planning or business continuity management system.

The technology may be the same. The right intervention can be completely different.

Two organisations may both run Dynamics 365 Finance. One needs Recover. The other needs Optimise. Two organisations may both need Business Central. One needs Transform. The other may qualify for an accelerated implementation.

How we approach the decision

Sometimes the useful answer is not the one you expected.

Fit matters more than forcing the sale. More technology is not automatically a better answer.

  • You ask for a replacement.

    We may recommend keeping and optimising the current platform.

  • You ask for a large transformation.

    We may recommend Assessment first.

  • You ask for a new implementation.

    We may recommend Standard Implementation rather than RAPID.

  • You ask us to take over support.

    We may recommend Partner Transition first.

  • You ask for AI.

    We may recommend reporting, workflow or ordinary automation.

  • You ask for Finance & Supply Chain.

    We may recommend Business Central, based on operating complexity rather than size.

No change is a valid result.

Qualification may conclude that the current platform, process or partner should remain unchanged. Not every conversation needs to become an InteliSense project.

Illustrative examples

  • We have selected Business Central and have an agreed scope.

    Possible starting point: Standard Implementation

    RAPID qualification may then be considered as the delivery method.

    Explore
  • We want RAPID but have several complex integrations and uncertain data.

    Possible starting point: Implementation qualification

    RAPID may not fit. A governed implementation may be the responsible answer.

    Explore
  • Our platform works but we want a different Microsoft partner.

    Possible starting point: Partner Transition

    Changing partner does not automatically require changing platform.

    Explore
  • We are live and stable but do not know which improvement creates the most value.

    Possible starting point: Customer Success review

    No change may be a valid outcome for this period.

    Explore
  • We are three months from go-live and nobody trusts the data.

    Possible starting point: Recover

    Establish what is true before another date is published.

    Explore
  • We want earlier warning of where tomorrow's warehouse backlog will form.

    Possible starting point: Optimise or Assessment, depending on current state

    Capability: Data & AI, including Predictive Intelligence. The capability does not set the commercial route.

    Explore

These scenarios are fictional and illustrative. They are written to explain how routing works, not to describe named customers.

Evidence

Current published customer evidence.

Published customer material, in their words rather than ours.

Our current published customer evidence does not cover every route or capability shown on this page. The Customer Stories hub shows what each item is currently verified to support.

  • Customer video

    Hill & Smith

    We transformed our business practices in just 5 months

    Hill & Smith describe their Dynamics 365 implementation with InteliSense in their own words.

    Verified industry
    Manufacturing
    Verified platform
    Dynamics 365
    • Transform
    • ERP

    What it does not prove: Does not establish Recovery, RAPID, Optimise, Support classification. No measured outcome is published with this evidence.

  • Customer video

    British Society of Lifestyle Medicine

    Implementing D365 for the British Society of Lifestyle Medicine

    A membership organisation describes implementing Dynamics 365 with InteliSense.

    Verified industry
    Membership organisation
    Verified platform
    Dynamics 365
    • Transform
    • CRM

    What it does not prove: Does not establish Recovery, RAPID, Optimise, Support classification. No measured outcome is published with this evidence.

  • Customer video

    InteliSense customers

    Hear our customers talk about InteliSense

    Several customers describe working with InteliSense, in their own words.

    Verified platform
    Dynamics 365
    • Transform
    • ERP
    • CRM

    What it does not prove: Does not establish Recovery, RAPID, Optimise, Support classification. No verified industry classification. No measured outcome is published with this evidence.

Not ready to talk?

Understand the problem first.

Pulled from the shared resource library, so nothing here is duplicated or left to go stale.

Where to start

Questions buyers ask about where to start.

Still not sure?

Describe the situation. We will help find the starting point.

You do not need to choose an InteliSense service before speaking to us. Tell us what is happening, where you are today and what systems are involved. We can work out the route from there.

See customer evidence