Home
/
Portfolio

Client work

Client work, described by sector

Enterprise implementations usually sit under a non-disclosure agreement. Rather than borrow credibility from a logo wall we cannot evidence, we describe the sector, the problem and the scope of what was delivered.

Discuss a similar project

Sectors

Manufacturing to fintech

Scope

ERP · data · custom build

Naming

Only with permission

Figures

Only where evidenced

How to read this

What we can and cannot show.

Most of our work happens inside finance, plant and operations systems that clients do not want discussed publicly, and we take that seriously. So the pages below describe the situation we were brought into, the work we did and the shape of the outcome, without naming the organisation unless we have written permission.

We have also left out percentage improvements and cost savings unless the client measured them and agreed we could publish the number. Precise-sounding figures are easy to write and almost impossible for a reader to verify, and we would rather be useful than impressive.

If you want detail on a specific engagement, ask during a consultation. We can usually walk through the approach, the architecture and the lessons in a conversation, even where the client cannot be named in public.

Selected engagements

Systems we were brought in to fix or build.

A cross-section of the sectors we work in and the kind of problem that usually starts the conversation.

Manufacturing 01

ERP and plant software across multiple production sites

Finance, materials and production modules implemented site by site rather than in one attempt. Shop-floor confirmation replaced end-of-shift spreadsheets, so consumption and output reached finance from the floor instead of being reconstructed at month end.

SAP Production planning Shop-floor capture Data migration

Phased rollout, one plant proven before the rest

Commercial banking 02

Oracle database hardening and CRM consolidation

A privilege audit and encryption baseline across core databases, run alongside a project to merge three regional CRM instances into a single pipeline with one set of stage definitions.

Oracle Encryption Auditing CRM migration

Privileged access reduced to a justified list

Distribution 03

AI invoice processing feeding ERP posting

Supplier invoices extracted automatically, validated against purchase orders and posted without manual re-keying. Confidence thresholds route anything uncertain to a person, so exceptions get attention and routine documents do not.

Document AI ERP integration Validation rules

Straight-through for routine documents, exceptions to humans

Technology 04

Multi-tenant SaaS platform taken to first release

Discovery through to a released product: tenancy model, billing, role-based access and the deployment pipeline. Built so a second engineering team could pick it up, with documentation and environments handed over at close.

React Node.js PostgreSQL CI/CD

Source, environments and runbooks handed over

Real estate 05

Customer portal over existing enterprise data

A permissioned portal giving clients their own statements, documents and request history, reading from the systems already in place rather than copying data into a second database that would drift.

Portal SSO REST APIs Role-based access

Routine requests moved out of the inbox

Construction 06

Project costing connected to finance

Project, procurement and cost data joined up so committed cost was visible during a job rather than after it closed. The reporting layer was separated from the transactional system so month end stopped competing with day-to-day work.

ERP Project costing Reporting layer

Committed cost visible during the job

Health and fitness 07

Member application with scheduling and payments

A member-facing application covering scheduling, attendance and recurring payments, integrated to the back office so the operations team worked from one record instead of reconciling two.

Custom build Payments Scheduling Integration

One member record across app and back office

How we present client work

Most of this work cannot carry a logo.

Enterprise implementations are usually covered by confidentiality terms, and we treat client information as confidential by default whether or not a separate agreement is in place. That produces an awkward tension for a portfolio page, and the honest resolution is to describe the work rather than to name the client.

So each entry sets out the sector, the systems involved and the scope of what was delivered. Where a client has approved being named, we name them. Where they have not, we do not, and we will not imply a relationship through a carefully placed logo either.

We also do not publish performance statistics. Figures like a percentage reduction in close time depend on baselines only the client can verify, and quoting them without that verification is closer to marketing than to evidence. Describing the mechanism is more useful and can actually be checked in conversation.

If you want to speak to a reference, ask. We approach clients individually for permission rather than keeping a standing list, which takes a little longer and is the reason those conversations tend to be candid.

Credentials

The accreditations behind the work shown here.

Enterprise buyers ask what we are accredited to do and how we handle regulated data. These are the answers, stated precisely.

Oracle

Partner

Delivery across Oracle Database, E-Business Suite and Fusion Cloud, including upgrades, migration and performance work.

Microsoft

Partner

Dynamics 365, Power BI, SQL Server and Azure, from implementation through to reporting and hosting design.

Google

Partner

Google Cloud and Google Workspace delivery, with analytics and measurement configured to the same standard.

FBR digital invoicing

Compliant integrations

Point of sale integrated with the Federal Board of Revenue computerised system for real time reporting, with the invoice number and QR code on the receipt.

HIPAA

Compliant practices

Protected health information handled under HIPAA aligned controls: access limited by role, encryption in transit and at rest, audit logging, and a business associate agreement where we are a business associate.

Client words

What the clients behind this work say.

Comments from the people who own the systems we build, run and hand back.

What sold us was that they argued with our brief. We asked for a reporting layer and they came back saying the reporting was fine, the batch data underneath it was not, and fixing that first would cost less. That turned out to be right. Our first mock recall after go live took an afternoon instead of the better part of a week.

Finance Director Food manufacturing group, Karachi
We had been through one failed implementation already, so we were sceptical of the whole category. The difference here was the migration work. Two full rehearsal loads before the real one, with a reconciliation pack we could check ourselves. Nobody had ever handed us evidence like that and asked us to sign it.

Head of IT Wholesale distribution business
Our cost reports used to show what we had paid, never what we had committed. Once the subcontract orders and approved variations started registering as commitment, the forecast stopped flattering us. It was uncomfortable reading for a month and then it became the most useful number we have.

Chief Financial Officer Construction and contracting firm

Recognise your situation in any of these?

Most engagements start with a problem that sounds specific and turns out to be common. Describe yours and we will tell you how we would approach it.

Book a consultation Browse services