The person responsible for your platform is the person who builds it.

Over twenty years, Edson has built and architected systems across the full Microsoft stack — Power Platform, Dynamics 365, Azure, and the backend integrations that hold enterprise platforms together. He has delivered inside regulated government environments, at commercial scale for global operators, and within charities where public trust is the platform's most important dependency.

The work spans architecture decisions that carry long-term consequences, complex Dataverse models designed for auditability and change, Power Apps built to survive organisational growth, and C# and Azure integrations where the platform boundary matters. Not configuration. Not shortcuts. Deliberate engineering.

It also means saying no. On a recent enterprise engagement the client had already settled on an event-driven pattern for reporting — publishing records purely to trigger a downstream sync. Edson showed why that corrupts event semantics and ties business logic to reporting cadence, and replaced it with a pull-based architecture the reporting team consumes on their own schedule. The value of an independent specialist is the decision they are willing to argue with you about.

The approach is straightforward: the person who scopes the work is the person who does it. Where an engagement genuinely needs a second specialist, that person is named before the contract is signed — never a resource allocated afterwards. No junior developers billing time while learning the platform, no project management overhead inflating the cost of outcomes. What large consultancies charge for coordination and margin, Consult Code Create puts into senior time and considered delivery.

The organisations that benefit most from this are those where platform decisions carry real weight — where a wrong architecture choice today becomes an expensive constraint in two years, where systems are scrutinised by auditors or regulators, and where the person responsible for the platform needs to be able to account for every decision made within it.

See how this works in practice →

Demis has spent over twenty years designing, customising and integrating CRM platforms across telecoms, financial services and the third sector. His specialism is the connective layer: Azure Service Bus, Logic Apps, Power Automate, SSIS and web service integration between Dynamics 365 and the contact-centre, billing and legacy systems a business actually runs on.

The work has run at genuine scale. He architected the integration between a global workspace operator's CRM and its contact-centre dialler, putting live customer data in front of agents across a three-thousand-centre estate, then built the Service Bus and SSIS layer that carried that organisation into Dynamics 365 and shaped the roadmap to retire the legacy platform entirely. The migration was the easy half. Keeping two systems truthful to each other while it ran was the hard half.

He has also worked the other side of delivery — leading business analysis on a cross-border banking programme, owning requirements, architecture alignment and change control across four countries. Integration work fails on unclear requirements far more often than it fails on code, and he has seen it from both ends.

Demis joins engagements where the integration surface is the risk: contact-centre platforms, billing systems, legacy CRM estates being decommissioned, or a migration where the data turns out to be older and messier than anyone admitted at the outset.