ENGINEERING

I don’t just build interfaces. I build the systems behind them.

My engineering work centres on .NET and C# — web applications, membership platforms, CRM integrations, Web APIs, SQL Server databases, payment services and the maintenance of business-critical systems in production.

/01

.NET & C#

.NET, .NET Core and C# application development.

/02

Web Applications

Responsive, browser-based applications built around business requirements.

/03

CRM

Microsoft Dynamics CRM and membership-focused CRM work.

/04

APIs

Web API and REST API design, development and consumption.

/05

Database Development

SQL Server, SQL and Entity Framework.

/06

Third-Party Integrations

Connecting applications to external platforms and services.

/07

Payment Systems

Worldpay, Sagepay and GoCardless integrations.

/08

CMS

Umbraco, WordPress and RiverCMS platforms.

/09

Testing

Software testing, troubleshooting and quality assurance.

/10

Azure DevOps

Delivery, version control and development workflow.

/11

Legacy Systems

Modernising and supporting existing business-critical applications.

/12

Technical Troubleshooting

Investigating and resolving production issues.

WORDPRESS

WordPress is one of the platforms I use to build real-world digital experiences.

WordPress isn’t separate from my broader development experience — it’s one of the tools I reach for when it’s the right shape for the job: organisational, business, non-profit, corporate and personal-brand websites, and content-driven platforms.

Organisational websitesBusiness websitesNon-profitsPersonal brandsCorporate websitesContent-driven platforms

END TO END, WHERE APPLICABLE

CONTENT STRUCTURE→DESIGN / FRONTEND→CUSTOMISATION→INTEGRATIONS→HOSTING / DNS / SSL→MAINTENANCE

See it in practice: CARE Nigeria → or the WordPress portfolio →

CRM & SYSTEM INTEGRATION

Systems rarely exist in isolation.

I’ve worked on integrations involving Microsoft Dynamics CRM, OOMI, CIVI, MemberBase and Eudonet — connecting membership platforms and websites to the CRM systems organisations run on, so information moves between them reliably.

The diagram is conceptual — it shows the kind of ecosystem I work across, not the architecture of any specific client system.

PAYMENTS & THIRD-PARTY SERVICES

Worldpay · Sagepay · GoCardless

Integrating payment services into real-world applications is more than connecting a checkout form — it involves handling transactions, callbacks, status changes, failures and data synchronisation.

BACKEND & DATA

C# · .NET Core · SQL Server · Entity Framework

FRONTEND→BUSINESS LOGIC→API→DATABASE→EXTERNAL SYSTEMS

Need your CRM connected to another platform? An application fixed or modernised?

Let’s discuss it → My professional experience →