Understand
Business clarification and process mapping before a single decision about technology. We ask uncomfortable questions early.
Services
Six things we do properly.
We are deliberately narrow. Everything below sits inside the Microsoft business applications stack, and everything below is work we have done at scale before.
01 — Business applications
Dynamics 365 CE, designed as a product.
Sales, Customer Service and bespoke XRM built on Dataverse — designed as a product with a lifespan, not a project with a deadline.
Implementation & rollout
Business clarification, process mapping, data modelling, configuration and custom development through to user testing, rollout planning and execution.
Custom development
C# plugins, custom workflow activities, TypeScript client scripting, PCF controls and model-driven app design — reviewed, tested and maintainable.
Migration & modernisation
On-premise CRM and legacy XRM platforms moved to the cloud, including data migration with SSIS and KingswaySoft, and brown-field refactoring.
02 — Low-code
Power Platform, properly bounded.
Low-code is only cheap if someone senior draws the boundaries. We decide what belongs in a canvas app, what belongs in Dataverse, and what should never have been low-code in the first place.
Power AppsPower AutomateDataverse
Power BIPower FxCopilot Studio
Model-driven & canvas apps
Applications designed around the domain model, with a clear split between configuration, low-code and pro-code so the solution stays supportable.
Process automation
Power Automate flows with proper error handling, idempotency and monitoring — replacing the fragile automations that quietly fail at month end.
Reporting & insight
Power BI models built on a Dataverse structure that can actually answer the questions the business asks, rather than a report per request.
03 — Cloud & integration
Azure & integration, built to hold.
Where Dynamics programmes most often break. We build the integration layer as a first-class system with its own architecture, monitoring and failure behaviour.
Azure FunctionsService BusLogic Apps
API ManagementKey VaultApp InsightsBicep
Event-driven integration
Queues and topics over Service Bus, Functions handling volume and concurrency, retries and dead-lettering designed rather than discovered in production.
API strategy
REST APIs and webhooks behind API Management, with well-defined interfaces so multiple vendors can work against the same platform without collisions.
Security & secrets
Key Vault, managed identity, Azure AD B2C and a security model that stands up to a GDPR review instead of being patched before one.
04 — Architecture
Solution architecture, decided early.
The expensive decisions are made in the first six weeks. We make them explicitly, write them down, and stay accountable for them through delivery.
Domain modelling
Domain-driven design applied to Dataverse: entities that reflect how the business actually works, and boundaries that hold as scope grows.
Target architecture
A documented target state across CE, F&O, Azure and the surrounding estate, with a migration path that can be delivered incrementally.
Technical due diligence
An honest second opinion on an existing platform, vendor proposal or estimate — what the risk actually is, and what it would take to fix.
05 — Governance
ALM & governance, made routine.
Regulated environments do not reward improvisation. We set up the routines that make releases boring and audits short.
Azure DevOps & pipelines
Environment strategy, solution segmentation, build and release pipelines, and branch policies that match the size of the team using them.
Refinement routines
Templates and guidelines for epics, features and user stories, so business and development are working from the same definition of done.
Quality & compliance
Testing methodology and scope, user acceptance testing, GDPR-compliant data handling and the documentation to evidence all of it.
06 — Leadership
Delivery leadership under pressure.
Sometimes the architecture is fine and the delivery is not. We have been put into failing programmes as a task force and taken them to go-live.
Programme rescue
Establishing a common understanding between stakeholders and developers, investigating where the hours have gone, and rebuilding a credible plan.
Technical leadership
Leading development and architecture teams, cross-team coordination across vendors, and status reporting with real risk and issue management.
Capability building
Mentoring your architects, developers and product owners deliberately, so the platform outlives the consultancy engagement.
How we work
Small team, senior only.
Architect
A written target architecture and a delivery plan you can hold us to, sized to what the organisation can absorb.
Deliver
Hands-on. The people who designed it build it, review the code, and sit in the refinement sessions.
Hand over
Documentation, routines and mentoring, so your team owns the platform rather than renting it from us.
Get in touch
Tell us what you are building.
A short conversation is usually enough for both of us to know whether there is a fit.