About InteliSense
Trust is built in the difficult parts of transformation.
ClaimsEvidence
Business applications programmes are judged in the moments where scope moves, data is worse than expected, a date is at risk or something goes wrong. How a partner behaves then is the real proposition. This page explains who we are, how we work, what each side owns and exactly what evidence sits behind the claims on this site.
Evidence matters more than adjectives.
Who we are
A Microsoft business applications partner, working where the operating model meets the platform.
InteliSense works as a Microsoft business applications partner across Dynamics 365, Power Platform and the Microsoft data estate.
Plan and implement change
Define the operating model, then deliver it under visible governance.
Recover programmes that have lost control
Re-establish facts, scope and decisions when confidence has gone.
Improve live platforms
Remove worthwhile friction from systems that are already running.
Keep agreed capability supported
Dependable operational support with clear ownership boundaries.
Use data, automation and AI
Where they improve a real decision, and only where they can be governed.
We do not claim a designation, competency or specialisation on this site, because those claims should be verifiable. The company facts we can evidence today are set out further down this page, alongside the ones we cannot yet publish.
Why we work this way
Promise carefully, then earn the next conversation.
The disciplines needed to recover a difficult programme should exist before a new one gets into trouble.
Promise carefully
Say what we can evidence, and nothing beyond it.
Qualify before committing
Test fit, scope, readiness and responsibility first.
Make responsibility explicit
Both sides should know what they own before work starts.
Deliver under visible governance
Decisions, risk, scope and change stay in the open.
Prove the operating outcome
Demonstrate the business position, not the configuration.
Support the live platform
Keep agreed capability operating with clear ownership.
Improve where evidence justifies it
No change is a valid outcome of a review.
Earn the next conversation
The relationship continues on the strength of the last one.
Evidence over adjectives
Evidence matters more than adjectives, on this site and in delivery.
Problems that can be managed
The objective is not a project with no problems. It is a project where problems can be managed.
Bad news does not improve with age
Late, wrong, unclear, over budget, blocked or at risk should all become visible early.
Activity is not progress
Do not confuse activity with progress. Effort is not the same as a working outcome.
Silence resolves nothing
An unresolved question does not disappear by staying quiet.
Change has a consequence
Every change has a consequence somebody has to accept.
Two realities, one truth
Delivery reality and commercial reality should never drift apart.
Certainty is not pretence
Certainty does not mean pretending nothing will change.
What difficult programmes reinforce
Recovery is a discipline, not our origin story.
Working on programmes where confidence has already been damaged reinforces which behaviours matter. These lessons shape how we deliver new work.
Validate assumptions early
Test the real process before it becomes a go-live risk.
Distinguish activity from progress
Movement on a plan is not the same as a working outcome.
Surface uncertainty
An unresolved question does not disappear by staying quiet.
Understand the data sooner
Data readiness decides more timelines than design does.
Involve users earlier
Belief in the solution has to be built, not announced.
Control change
Every change has a consequence somebody has to accept.
Make decisions visible
Decisions should be dated, owned and recorded.
Connect delivery and commercial reality
The plan and the commercial position should describe the same project.
Decision points
We use explicit decision points before commitment, build, go-live and material expansion so confidence comes from evidence rather than optimism.
Bad news does not improve with age.
The objective is not a project with no problems. The objective is a project where problems can be managed.
What customers should expect
Before commitment, during delivery, at go-live, afterwards, and when something goes wrong.
The expectation model is the same whichever commercial route applies.
When something goes wrong
Acknowledge
Say it out loud, early.
Establish facts
Understand what actually happened.
Own what is ours
Separate our responsibility from everyone else's.
Make impact visible
Show the business consequence, not just the cause.
Agree action
Decide the route with the customer.
Communicate
Keep people informed while it is being resolved.
Resolve
Close it properly.
Learn
Change how we work so it is less likely next time.
Shared responsibility
We do not transfer accountability for delivery to the customer.
We make the responsibilities required for the business outcome explicit on both sides. Outcome realisation depends on both sides meeting what they agreed to own.
The customer owns
- Business decisions
- Policy
- Process ownership
- Subject-matter expertise
- Data truth
- Priorities
- User acceptance testing
- Organisational adoption
InteliSense owns where agreed
- Professional advice
- Platform and solution design
- Delivery commitments
- Implementation quality
- Technical quality
- Transparency
- Risk visibility
- Agreed testing
- Agreed cutover and delivery responsibilities
Outcome realisation
Outcome is not a marketing word. It should be something the organisation can define, baseline and review.
Outcome
Define what the organisation is trying to change.
Baseline
Establish the current position before the work starts.
Agreed change
Agree what will change and what will not.
Capability
Deliver the capability that makes the change possible.
Adoption
The capability has to be used to matter.
Evidence
Measure against the baseline, not against opinion.
Review
Decide what happens next, including doing nothing.
The relationship
Go-live is a milestone in the relationship, not the definition of its success.
Customers can enter at different points. This is a relationship model, not a claim that every customer follows the same sequence.
Understand
Understand the situation before proposing a route.
Qualify
Test platform fit, scope, assumptions, readiness and responsibilities.
Deliver
Implement agreed change under visible governance.
Stabilise
Prove the live operating position and settle the first release.
Support
Keep agreed supported capability operating.
Improve
Prioritise worthwhile change using evidence.
Expand
Extend capability where the business case justifies it.
Advocate
Earn recommendation through the experience of the relationship.
After go-live
Four distinct things, deliberately kept separate.
No change remains a valid review outcome. Expansion happens only where the business case supports it.
Where a relationship can start
A commercial route answers one question: what situation are we dealing with?
The route follows the situation. The technology decision comes afterwards.
Where RAPID fits
RAPID is an accelerated route for bounded situations where platform fit, scope, readiness, standardisation and decision velocity support it.
It is a qualified delivery method rather than a commercial route of its own, and it is not the default for new implementations. Speed is a consequence of control, not a substitute for it.
Microsoft capability
One business rarely fits inside one Microsoft product.
Capability answers a different question: what technology or discipline may support the answer? The important question is not which product we can sell, but which combination of capability solves the business problem.
Implementation is not the end of the technology conversation
Choose the simplest capability that improves the decision.
Operate
Run the process reliably.
Understand
See what is actually happening.
Automate
Remove the effort that adds nothing.
Predict
Identify what may need attention earlier.
Assist
Support the person making the decision.
This is a possible evolution, not a mandatory ladder. Predictive Intelligence evidence on this site remains demonstration-led rather than verified customer outcome evidence. We continue to explore and develop AI assistance, predictive and agentic workflows where they improve a defined business decision and can be governed responsibly. That is a development direction, not a maturity or deployment claim.
Industries
Industry context matters because the operating model changes platform fit, scope, data, integration and delivery risk.
Eight primary industry contexts are published, each with its own qualification, architecture and evidence position.
The people behind the work
The team shape follows the problem.
These are delivery disciplines, not a claim about team size or the resource mix used on every engagement.
Architecture
Whether the solution holds together across the landscape.
Functional consulting
Finance, supply chain, warehouse, manufacturing, sales and service process knowledge.
Technical consulting
Extensions, integrations and the engineering behind the configuration.
Development
Building what standard capability cannot reasonably cover.
Programme and project management
Scope, plan, governance, risk and the visibility of decisions.
Support
Ownership of live operation and the route from issue to outcome.
Data & AI
Reporting, data platforms, automation and predictive capability.
No named leadership profiles are published yet, because none have been approved for publication. Rather than show a gallery of job titles, the Leadership page explains how accountability, escalation and decision ownership work.
How leadership accountability worksOperating principles
The right answer is not always another project.
These are expectations customers can hold us to, not a claim that we never get anything wrong.
We will not force platform fit.
We will not force RAPID.
We will not hide uncertainty.
We will not use AI because it is fashionable.
We will not turn every problem into a large transformation.
We will not present prediction as certainty.
We will not invent proof.
We will not treat go-live as the end.
Evidence
What we can actually evidence, and what we cannot.
Evidence types are kept distinct so a demonstration is never mistaken for a customer outcome.
Company evidence
80%
of our business comes from existing customers and referrals.
That statement combines existing customers and referrals. It does not tell you why every organisation chose to work with us, and on its own it does not evidence repeat business, retention, renewal or how long relationships last.
It does show why the quality of existing relationships and recommendations matters commercially to InteliSense. We have left the interpretation there deliberately.
Customer evidence
Published customer video is one of the strongest forms of evidence currently available on this site, because the customer describes the engagement in their own words. These videos evidence the engagements they describe. They are not published as evidence of Recovery, Support, Optimise, relationship duration or repeat work, because the central evidence model does not verify those claims.
Customer voice
Customer stories.
Customer voices
InteliSense customers
Hear our customers talk about InteliSense
Evidence types
Company evidence
An approved company-level statement, such as the business-mix figure.
Customer evidence
Published customer material where the customer describes the engagement.
Relationship evidence
Repeat work or relationship duration. Only published where explicitly verified.
Measured outcome
A quantified result. Only published where the measurement is verified.
Product demonstration
Capability shown in a demonstration. Evidence of capability, not of a customer outcome.
Proposition evidence
A developed proposition. Evidence of intent and design, not of a customer outcome.
Company facts we can verify
- Trading name: InteliSense IT
- What we do: Implement, recover, support and improve Microsoft business applications: ERP, CRM, Power Platform and the data estate.
- Microsoft relationship: We work as a Microsoft business applications partner. No specific designation, competency or specialisation is claimed on this site.
- Business mix: 80% of our business comes from existing customers and referrals.
- Published customer evidence: Three published customer videos, listed in full on Customer stories.
Company facts we will not publish yet
Each of these needs a verified source before it appears anywhere on this site. Certification images existing in a repository is not evidence of a current, in-scope certificate held by the current legal entity.
- Registered legal entity and company number: Companies House record confirmation
- Established date and years operating: Verified founding date
- Registered office and delivery geography: Approved location wording
- Microsoft designation, competency or specialisation: Current Microsoft partner record
- ISO 27001: Certificate, certification body, scope and validity dates
- ISO 9001: Certificate, certification body, scope and validity dates
- Cyber Essentials: Certificate, covered entity and validity period
- Named leadership profiles: Individual approval, role, photograph and LinkedIn URL
- Team size, offices and years of experience: Approval for public use
Common questions
Questions people ask about InteliSense.
Every relationship starts somewhere
You do not need to know which route you need.
Tell us what is happening. Something you are planning, a project in trouble, a live platform that needs improving, a support relationship that is not working, a partner change you are considering, or a decision you want to understand better. We will help work out the right place to start.