Skip to content

About InteliSense

The technology matters. The judgement behind it matters more.

InteliSense helps organisations implement, recover and improve Microsoft business systems. The work spans ERP, CRM, data, integration, automation and AI, but the principle behind it is simpler: understand the business problem, make the right technical decision and be accountable for what happens next.

We would rather have a difficult conversation early than a difficult project later.

Our story

We started with ERP. The problems got broader.

InteliSense was established in 2010 by three colleagues with roots in ERP, manufacturing and complex business systems. We started there because that is where many of the hardest operational problems lived.

Over time those problems stopped ending at the ERP boundary. Orders arrived from ecommerce platforms. Warehouses ran specialist systems. Sales teams needed CRM. Finance needed better data. Customers wanted automation rather than another manual process. More recently, AI has added another layer of both opportunity and risk.

Our capability grew around those problems rather than around a product list.

  • 2010

    Established

  • 50+ colleagues

    Team

  • 170+

    Projects delivered

  1. 2010

    InteliSense begins

    Three colleagues start a consultancy around ERP and the operational systems that run production, stock and finance.

  2. Business Applications

    The work widens beyond ERP

    CRM, Customer Engagement and Power Platform join the practice as customer problems stop ending at the ERP boundary.

  3. Data and integration

    Data becomes the hard part

    Migration quality, mapping and connected systems turn into disciplines of their own. CDM and IDM come out of that work.

  4. Today

    ERP, CRM, data, automation and AI

    The same practice, organised around three situations: transformation, recovery and getting more from a platform that is already live.

What experience has taught us

Five things we now treat as non-negotiable.

Not values. Positions we have arrived at because ignoring them has cost somebody money.

How we make technology decisions

Not every problem needs development.

Sometimes the right answer is to configure Dynamics. Sometimes it is to leave a specialist system exactly where it is and connect it properly. The order below is deliberate.

  1. Configure: Use standard Microsoft capability where it meets the requirement. It is cheaper to own and it survives the next update.
  2. ISV: Use a proven specialist product when buying is more sensible than building.
  3. Integrate: Keep a specialist system where it already does its job well, and connect it properly.
  4. Automate: Remove unnecessary manual work around the process rather than rebuilding the process.
  5. Extend: Add focused capability where there is a genuine gap in the standard product.
  6. Build: Create something new only when the requirement genuinely justifies carrying it.

Problems we have actually solved

Some problems do not fit neatly into a product brochure.

Three pieces of customer work, chosen because each one led to a different decision.

  • Hill & Smith Infrastructure

    Hill & Smith Infrastructure

    When certification did not match the invoice

    Work is delivered, an application for payment goes in, and the customer certifies a different amount to the one claimed.

    Built application for payment handling into Dynamics 365 so certification, part-certification and the accounting behind them are handled in the finance system rather than in spreadsheets.

    Bespoke extensionAutomation
  • Eland Cables

    Eland Cables

    When the warehouse needed to stay outside Dynamics

    Warehouse execution runs in ATMS, a specialist external system, while stock and financial control belong in Dynamics 365.

    Integrated Dynamics 365 Finance and Operations with the ATMS warehouse management system on Azure, using the Dynamics data management framework for structured, recoverable message exchange.

    Standard Microsoft functionalityIntegration
  • National Floorcoverings

    When the stock figure was not enough

    The same carpet exists in different widths, lots and manufacturing blends, so a simple stock figure does not answer the question being asked.

    Built a consolidated stock lookup in Business Central that shows availability across widths, lots and blends in one view, so sales can answer a customer without opening several screens.

    Bespoke extension

A selection of customer work currently documented on the site. More customer stories and delivery evidence are being prepared and added.

One customer. More than one problem.

Hill & Smith Infrastructure

  • Projects
  • IDM
  • Procurement
  • Subscription billing

Project accounting, field integration, rental pricing and supplier self-billing. Four separate problems inside one finance estate, each answered differently.

The people behind the work

Customers are trusting people, not a logo.

A customer should always be able to name who owns the next decision on our side. These are the people who usually hold it.

  • ERP and finance

    Andrew Rumney, solutions director. Jake Huebner, senior solution architect

  • CRM and Power Platform

    Usayd Javed, head of ce / power platform. Chris Spencer, senior solution architect

  • Data and development

    Durga Reddy, development manager

  • Delivery and operations

    Rachel Chico, head of operations

Amo Khan, Managing Director at InteliSense

Managing Director

Amo Khan

The commercial position, what InteliSense commits to in writing, and the direction of the business.

Capability created from experience

When we solve the same problem repeatedly, we try not to start again.

Some of our most useful capability exists because we got tired of solving the same problem from scratch. Each of these came out of delivery, not a product plan.

  • IDM

    Accelerator

    Mapping legacy fields to a new platform by hand was slow, undocumented and difficult to review.

    Intelligent Data Mapping: accelerates and documents source-to-target mapping so decisions are visible and repeatable.

    Data migration and integration design.
  • RAPID 10, 30 and 90

    Accelerator

    Bounded requirements were being priced and governed as though they were full transformation programmes.

    Pre-configured, fixed-scope delivery routes for CRM, Business Central and Finance & Supply Chain where fit, readiness and decision velocity allow.

    Qualified implementations with bounded scope.
  • I-HIM

    Methodology

    Structured delivery gives control but resists discovery. Iterative delivery gives discovery but loses control. Programmes were forced to choose.

    A hybrid implementation methodology that runs structured governance and iterative build together, converging at defined confidence gates.

    Every governed implementation, and the backbone of the delivery system.

On I-HIM

Structure where it matters. Flexibility where it helps.

Enterprise projects need governance, decisions, controls and clear milestones. They also need enough flexibility to learn as the design becomes real. I-HIM combines those two needs rather than pretending every project fits a pure delivery methodology.

Built around the Microsoft business platform

Credentials matter. Turning the platform into a working business process matters more.

These capabilities increasingly overlap. Our job is to understand where one should stop and another should begin.

  • ERP

    Business Central where a single integrated application fits, Finance & Supply Chain Management where financial, supply chain or manufacturing complexity requires it.

  • CRM and Business Applications

    Sales, service and case working around the customer relationship, with Power Platform where a full ERP module is the wrong answer.

  • Data & AI

    Power BI, Microsoft Fabric, the data estate behind them, and predictive capability positioned as decision support.

  • Delivery and live service

    Assessment, implementation, recovery, partner transition, support, customer success and optimisation.

InteliSense is a Microsoft Dynamics 365 Solutions Provider for ERP, CRM and AI automation, working across Dynamics 365, Power Platform and the Microsoft data estate. Independently certified to ISO 27001 and ISO 9001, and holding Cyber Essentials.

What trust looks like during a project

Four behaviours you can actually observe.

  • Say when something does not fit

    We would rather lose the argument early than force the wrong platform into the requirement.

  • Surface problems early

    A red project shown as green does not become safer. It becomes more expensive.

  • Explain the trade-off

    Standard, ISV, integration and extension each carry a consequence. Somebody has to own it knowingly.

  • Leave evidence behind

    Decisions, designs, testing and governance should still make sense after the project team has moved on.

Implementing a new system is one kind of experience. Walking into a programme where confidence has already been lost teaches something different.

Explore Recovery

Common questions

Questions people ask before they ring us.

Start with a conversation

Tell us what is difficult.

You do not need to know whether the answer is ERP, CRM, integration, automation, data or AI. Start with the business problem. We can work out the technology afterwards.

See customer stories