Work that stands up to scrutiny.

A selection of engagements across regulated charity, large-scale commercial, and government environments — where platform decisions carried real consequences.

Case Study
Regulated Charity / Public Sector
End-to-End Member Data Automation
A five-layer ingestion architecture eliminating all manual data imports for a membership organisation serving 20,000–30,000 civil servants.
100%
manual imports eliminated
25%
infrastructure cost reduction
2+ yrs
sole technical authority
Read the case study →
 Case Study
Large-Scale Commercial
Gym Estate Integration at Scale
Zero-touch deployment architecture connecting 500+ gym sites, replacing a legacy system and integrating 10+ data sources without manual intervention.
500+
sites connected
10+
integrations delivered
Zero
touch deployments
Read the case study →

What they have in common

Different sectors. The same standard.

Each of these platforms was carrying real weight: member data a regulator could ask about, pricing that reached every site in a national estate, records other systems depended on. The brief was never just to make it work. It was to make it hold up to audit, to growth, and to the day the people who built it are no longer around.

  • Senior people only. The person who designed the architecture built it. No junior staff learned on the client's platform.
  • Decisions written down. Architecture choices, trade-offs and the reasons behind them are documented, so the next team inherits understanding rather than guesswork.
  • Handed back, not held onto. Each platform runs on the client's own tooling and pipelines. The measure of the work is what the team can do without us.

More outcomes from our delivery

  • 40kusers served by a live reporting platform in central government
  • 4mcustomer records consolidated from nine separate databases
  • 3,000sites served by one real-time CRM and dialler integration
  • £0.5mannual running cost removed for a national charity

Figures from engagements led by Edson Santos and Demis Sousa, including work delivered before Consult Code Create. Clients are not named.

Common questions

Why don't you name your clients?

Most of the organisations we work with are regulated or publicly accountable, and their platforms hold sensitive data. We describe the problem, the architecture and the outcome in detail, without naming them.

What kind of Power Platform projects do you take on?

Platforms that have to stand up to scrutiny: rebuilding implementations that didn't deliver, integrating Dynamics 365 and Dataverse with the systems around them, and replacing legacy platforms without taking the organisation offline.

Who actually does the work?

Senior specialists only, each with at least 20 years' experience. The person who scopes the work is the person who builds it. Where an engagement needs a second specialist, they are named before the contract is signed.