Extensions & ISVs

When standard gets you most of the way.

Microsoft should do as much of the work as possible. Where a genuine gap remains, we look at the simplest sustainable answer: a proven ISV, existing InteliSense IP, integration, automation or a carefully engineered extension.

Explore the options How we decide

If standard functionality already solves the problem, we will use it.

How we approach a gap

Standard, then ISV, then integrate, automate or extend.

Start with what Microsoft already provides. Add something only when the business case justifies it.

Most requirements are a configuration question. If Dynamics 365 already does it, that is the answer and there is nothing to buy.

Catalogue

What we have built, what we partner on, and what is simply Microsoft.

Every card states where the capability comes from, which Microsoft system it applies to and what it does not do. Filter by system if you already know where you are working.

InteliSense IP

When two systems still need to behave like one process.

InteliSense IDM provides controlled integration between Microsoft Dynamics and external operational systems, so the other platform can stay where it genuinely earns its place.

Hill & Smith Infrastructure

Reflow remained the operational platform while Dynamics 365 remained responsible for finance, projects, stock and core data. IDM connected the processes between them.

See the customer story How IDM works

Evidence

When standard isn't enough

Some of the most valuable work happens in the gaps between standard software and the way a business actually operates. The important decision is whether to configure, buy, connect, automate or build.

Targeted extension
When customer certification does not match the invoice
Hill & Smith needed an Application for Payment process that could deal with certification, project accounting, revenue recognition, provisions and partial certification inside Dynamics 365 Finance and Operations.
FSCM · Finance · Projects
See the customer detail
Business extension
When the stock you can sell is not under one item number
Different carpet widths were held as separate items even though they represented the same underlying product. We extended Business Central so sales users could see related widths and manufacturing blends together, including available and reserved stock.
Business Central · Inventory
See the customer detail
Integration
When the warehouse sits outside the ERP
Eland Cables needed Dynamics 365 Finance and Operations to work with its external ATMS warehouse platform without losing control of despatch, receipt or master data. Azure Logic Apps and Dynamics data management connected the two.
FSCM · Azure · WMS
See the customer detail

How we decide

Before we add anything, we challenge it.

Every extension carries licence cost, upgrade impact and support responsibility. Those costs should be visible before the decision, not after it.

Can Microsoft already do it?
Configuration comes first. If the platform covers it, we stop there.
Is there a proven product?
Buying mature capability is often better than building it from scratch.
Will it still make sense in three years?
Licence, support and upgrade cost all outlive the go-live date.
Does it genuinely need engineering?
Build only where the requirement warrants it, and name who owns it afterwards.

RAPID Learning Portal

Training should create capability, not attendance.

Go-live does not prove adoption. Implementation training should not consist only of workshops delivered before go-live, so we provide a structured learning environment users can return to, while giving appropriate management stakeholders visibility of learning progress and assessment information.

Learning does not end at go-live.

One structured journey, in two phases.

Implementation

Learn
Workshop
Practise
Assess
Reinforce
Readiness

Live service

Self-learning
Refresher learning
New starters
Support knowledge
Continued assessment

Management visibility of learning progress and assessment information, across both phases where the portal supports it.

Training
Capability
Adoption
Continued learning

Explore RAPID Learning Portal

Across the methodology

Learning runs through delivery, not beside it.

Where the portal is used, it operates across the stages of our hybrid implementation methodology rather than appearing as a training week near the end.

Understand
Early process learning, before design decisions harden.
Design and playback
Users build an understanding of the future processes.
CRP
Learning against representative end-to-end processes.
Prepare
Structured role and process learning for the people who will work in the system.
Assess
Check understanding rather than record attendance.
Go live
Learning available at the point of need, while real work is happening.
Stabilise
Reinforce the areas where difficulty is actually showing.
Support
Continued self-learning and refresher content.

Partner ISVs

Sometimes the right answer already exists.

Where a proven specialist product solves the requirement properly, we would rather use it than recreate the capability unnecessarily.

Have a requirement that doesn't fit?

Start with the problem, not the extension.

Tell us what the business needs to do. We'll work out whether standard Microsoft capability, an ISV, integration, automation or targeted engineering is the most sensible answer.

See customer stories

When standard gets you most of the way.

Standard, then ISV, then integrate, automate or extend.

What we have built, what we partner on, and what is simply Microsoft.

RAPID 10

RAPID 30

RAPID 90

Charity Unified & Gift Aid

Crisis & Resilience Management System

Clinical Management System

3PL Integration

Home Builder

QualiCore

SmartCut

TexCore

Predictive Intelligence

AI Intelligent Apps

IoT & AI Services

Power BI & Microsoft Fabric

Azure Data Lake

Azure Synapse Analytics

D365 Copilot for Sales

Power Platform

IDM

IIT Access Flow

SharePoint Connect

Product Configurator

I-HIM hybrid implementation model

CDM Tool

Heartbeat proactive monitoring

RAPID Learning Portal

Licence Estimator

Partner ISV ecosystem