Work
-
Home
-
Work
Showing 13–13 of 13 records
Records published today
-
- Evidence level
- Case study: named, measured results
- Service
- Custom Product Engineering
-
- Evidence level
- Case study: named, measured results
- Service
- Custom Product Engineering
-
- Evidence level
- Case study: named, measured results
- Service
- Custom Product Engineering
-
- Evidence level
- Case study: named, measured results
- Service
- Custom Product Engineering
-
- Evidence level
- Case study: named, measured results
- Service
- Custom Product Engineering
-
- Evidence level
- Case study: named, delivery duration recorded
- Service
- Legacy Application Modernization
-
- Evidence level
- Portfolio record: named, delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: named, delivered scope, with a phase stated as planned
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: named, delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: named, delivered scope, delivery duration recorded
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: delivered scope, delivery duration recorded
- Service
- Technical Audit Sprint
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Legacy Application Modernization
-
- Evidence level
- Portfolio record: delivered scope
- Service
- AI Workflow Automation
-
- Evidence level
- Portfolio record: delivered scope
- Service
- AI Workflow Automation
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Custom Product Engineering
-
- Evidence level
- Portfolio record: delivered scope
- Service
- Custom Product Engineering
This table is the whole of what is published here, not a selection from a longer list. Ten of the nineteen name their client, and five of those ten report measured results.
Two rest on a vendor's own published facts too: the Netztech migration followed Adobe ending extended support for Magento 1 on 1 June 2020, and the WhatsApp chatbot record runs on Meta's own WhatsApp Business Platform, built for businesses to automate customer messaging.
Evidence levels
The level is set by one question: does an attested figure exist for this project? Whether the client may be named is settled separately.
-
Case study
- Client
- Named
- What the record reports
- Delivered scope, and the measured results recorded for that client, each carrying the period its source states
-
Client story
- Client
- Described but not named
- What the record reports
- Delivered scope, and an outcome only where the source records one
-
Portfolio record
- Client
- Named or not, as permitted
- What the record reports
- Delivered scope only
Where a client may be named and no result was recorded, the record reports delivered scope and, where recorded, delivery duration. No figure is borrowed from another project, and where two materials disagree, the lower figure is published. The methodology page sets out how claims here are sourced and reviewed.
How to read a record
Each record answers the same questions:
-
Context
What kind of organisation needed what kind of system, identified only as far as its evidence level allows.
-
Netbase role
What Netbase was responsible for.
-
Delivered scope
The features and delivery steps recorded in the project documents.
-
Evidence level and limitations
Where the information comes from and what it does not support.
-
Lessons for a similar project
The decisions a buyer should make before scoping comparable work.
Why a record moves up a level
Until 25 September 2026 every record here was a portfolio record; a record moves to a higher level only with the client's permission and evidence for the figures. That rule has not changed, and both conditions are now met for part of the portfolio: Netbase holds a list of clients who agreed to be named, with attested figures for several, each carrying the period it was measured over.
A record can also be named without moving up a level: four are named on Netbase's own authority as supplier, where no confidentiality obligation covers the work and the owner has authorised publication. None records client consent; any client can have its name removed on request.
Why no screenshots, and when logos and figures appear
Interface screenshots stay out of every record: they show client systems and private information inside them, and no client has given that permission.
Logos and figures are governed separately, one by consent, one by evidence. A figure is published only where attested and attributed, carrying the period its source states. A logo is shown only where that client's permission is on record; showing a logo is never permission to attach a project to a name. Where neither permission nor authority holds, the project stays anonymised, and images on these pages are illustrative only.
What is not shown here
Netbase has delivered other projects not published here. A project appears only once its scope is checked against the source documents and its claims registered — that check is the gate, not a target number of records.
Is a Work record the right evidence for your decision?
| Looking for | Good fit when | Look elsewhere when |
|---|---|---|
| Delivered scope | The feature list and delivery steps matter most | You need a measured business outcome |
| A measured result | The record is a case study with a named client | No case study exists for this workflow yet |
| A sector match | Published work close to your sector exists | The workflow matters more than the sector label |
Questions about these records
Why is a result missing from some records? It is published only where the source documents recorded one; a missing figure is not evidence that no result occurred, only that none is registered here.
Can I ask for more detail on a record? The page states what its evidence level supports; a first review can say whether a closer record or a reference exists beyond what is published.
Does an anonymised record carry less weight than a named one? It carries the same evidence requirements; anonymisation reflects the client's consent, not a lower evidence level.
Planning something similar?
If one of these records is close to what you need, mention it in your brief; it helps the first review focus on the decisions that matter for your version of the problem. The project delivery page explains how a new project is planned. Submit a project when ready. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.