Work
Review one owned programme and five legacy portfolio accounts. Every page separates the technical narrative, relationship boundary and status of each outcome claim.
Client logos and borrowed project imagery are not used. The five legacy accounts retain their technical narrative while the precise contracting relationship, client naming permission and supporting outcome evidence remain visibly unverified.
An internal programme to replace the previous WordPress marketing site with an accessible, statically deployable consultancy website whose content and evidence boundaries can be reviewed in Git.
This case study covers only Nexel Byte’s owned website, repository and associated enquiry function. It does not provide evidence for any legacy client relationship, outcome or asset.
Review the case studyThe previous portfolio presents this as the modernisation of a public-facing health and social care information service. The source narrative describes API, frontend, data and Azure delivery contributions.
Only the contribution narrative from the previous portfolio is reproduced. The repository does not verify whether Nexel Byte was the direct supplier, a subcontractor or the employer of an individual contributor. The embedded-specialist label is a descriptive classification, not a verified commercial engagement model.
Review the case studyThe previous portfolio presents this as work on a high-traffic retail platform. The source narrative describes backend, data, server-rendered journey and interactive frontend contributions.
Only the contribution narrative from the previous portfolio is reproduced. The repository does not verify whether Nexel Byte was the direct supplier, a subcontractor or the employer of an individual contributor. The embedded-specialist label is a descriptive classification, not a verified commercial engagement model.
Review the case studyThe previous portfolio presents this as a global digital platform for customers, partners and internal stakeholders. The source narrative describes backend, frontend, accessibility and delivery-pipeline contributions.
Only the contribution narrative from the previous portfolio is reproduced. The repository does not verify whether Nexel Byte was the direct supplier, a subcontractor or the employer of an individual contributor. The embedded-specialist label is a descriptive classification, not a verified commercial engagement model.
Review the case studyThe previous portfolio presents this as modernisation of access to statistical datasets and reports. The source narrative describes server-side, data, React, visualisation and delivery-pipeline contributions.
Only the contribution narrative from the previous portfolio is reproduced. The repository does not verify whether Nexel Byte was the direct supplier, a subcontractor or the employer of an individual contributor. The embedded-specialist label is a descriptive classification, not a verified commercial engagement model.
Review the case studyThe previous portfolio presents this as an energy-management platform working across varied data sources. The source narrative describes backend, microservice, data-integration and Angular frontend contributions.
Only the contribution narrative from the previous portfolio is reproduced. The repository does not verify whether Nexel Byte was the direct supplier, a subcontractor or the employer of an individual contributor. The embedded-specialist label is a descriptive classification, not a verified commercial engagement model.
Review the case studyStart with clarity
Tell us the capability and context. We can explain what is verified, what is reported and which supporting evidence is available.