Work & evidence

Show the state of the work—not a polished fiction.

Tembeek separates completed infrastructure, working prototypes, field observations and proposed concepts. Client outcomes will be published only with permission and evidence.

This page distinguishes completed infrastructure, working prototypes and proposed concepts.

CompletedWorking prototypeProposed conceptField observation

Completed

Tembeek public platform

A secure shared-hosting website that operates like a small business system.

Clean URLs, strict security headers, maintenance controls, protected inquiries, Lead Desk, career intake, cache-safe assets and repeatable production smoke testing.

Server-side CSRF and allowlisted intake
Private data outside the web root
Administrator workflow and encrypted backup tooling
Measured deployment checks instead of visual guesswork

Why Tembeek works this way →

Working prototype

Hotel operations

A proposed operating core shaped for independent hotels in Juba.

Interactive concept views demonstrate how rooms, guests, payments, daily reporting and attention items could become visible in one workflow.

Concept interface clearly labeled
Assessment-first pilot model
Local-first deployment assumption
No claim that a finished product already exists

Explore the proposed system →

Field observation

Business records

Manual records often fail at handoffs, not at data capture.

Businesses may record sales, stock and credit in several places yet still lack a current answer management can trust. Tembeek’s assessment approach starts with ownership and reconciliation.

Trace where a number originates
Identify duplicate and missing records
Define the smallest management report
Digitize only the workflow that earns priority

View the service approach →

Proposed concept

Offline-capable delivery

Connectivity should improve a system—not decide whether work can continue.

For operational systems in South Sudan, Tembeek evaluates local operation, protected synchronization, power backup and support capacity as first-class design inputs.

Local workflow during outages
Controlled synchronization after recovery
Explicit conflict and backup handling
Deployment sized to the actual organization

Discuss a suitable architecture →

Publication standard

What will qualify as a case study.

A real starting condition
A named or properly anonymized organization
The actual intervention and limits
Measured or directly observed results
Client permission where identification is possible

Discuss a project →