HomeWhat we buildHow we workOur workAboutContact
(About Pocco)

A small team, deliberately, with an unusually wide bench

We are small on purpose. It means the people who designed your system are the people who build it, and the people who answer when you call.

The Pocco team at an industry showcase
The team on site at the industry showcase where the REEF Operations Platform was presented.
Software engineeringNetwork engineeringCloud engineeringInformation securityProject managementInformation systemsSoftware engineeringNetwork engineeringCloud engineeringInformation securityProject managementInformation systems
(The story)

We started from a frustration

Operating businesses were being sold one of two things. A rigid template they had to bend their process around, or a licensed platform that held their information and set their limits. Neither is how a serious business should have to work, and both produce the same result: a system that almost fits, that nobody can change, and that everybody quietly works around.

So Pocco builds the third option. A system designed around how your operation actually runs, that your people have a hand in shaping, that we keep running and keep improving as the business changes.

We are a South African company, registered as K2026888828, working with businesses that operate something real.

85%Average across the team's Computer Science degrees
10Disciplines covered in house
1Team from first conversation to live system
0Projects handed between three suppliers
The Pocco team
(The bench)

Breadth is the point

A spread of disciplines that rarely sits in one small team. It is why we can carry a project from the first conversation on a plant floor all the way to the infrastructure it runs on, without handing you between three suppliers who each blame the other two.

Build

Software engineering

The applications themselves, front to back, written to be read and maintained by somebody other than the person who wrote them.

Web applicationsMobileAPIsAutomated testing
Structure

Information systems

How information moves through a business, where it is held, and how a system fits the process rather than fighting it.

Data modellingProcess mappingRequirementsBusiness analysis
Run

Cloud and network engineering

The infrastructure underneath, sized properly, monitored, and recoverable when something goes wrong at an inconvenient hour.

HostingNetworkingMonitoringBackup and recovery
Protect

Information security

Access designed deliberately rather than added later, with personal information handled the way the law requires.

Access controlThreat modellingSecure developmentData protection
Deliver

Project management

Phases with something to judge at the end of each one, a named decision maker on both sides, and honest reporting when something slips.

Phased deliveryScopingRisk managementClient reporting
Shape

Experience design

Designing for the person in gloves at six in the morning, not for a screenshot. Tested with the people who will actually use it.

Interface designUsability testingAccessibilityPrototyping
(What we believe)

Four things we will not trade away

01

Say the uncomfortable thing

If the scope is wrong, the deadline is unrealistic or we are the wrong fit, you hear it from us early rather than discovering it late.

02

Adoption over features

A system nobody uses is a failed system regardless of what it can do. We measure the build on whether people reach for it.

03

Accountability stays human

Whatever tools we use, a named person has read, tested and approved every change before it reaches anything of yours.

04

Build for the long run

Documented, tested and structured so it can be carried forward, not rewritten the moment the first person moves on.

Want to meet the people who would build it?

That is the whole point of a first call. You talk to the team, not a salesperson who hands you over afterwards.

Start a conversation