One institution, one mandate, one system built to it.

The other half of the studio. Not a bigger version of a Ko product. A different business, bought through public procurement, and won on whether we can carry a mandate-critical system rather than on a catalogue.

Before an officer opens it
Validated on intake
Every figure
Traceable to its source
Filed on schedule
Practice · custom build

Regulatory reporting platform

Energy regulation

A single pipeline for how every distribution utility reports.

A uniform reporting platform for a sector regulator: filings collected to the framework's own shape, validated before a case officer ever opens them, and every published figure traceable back to the submission it came from.

Templates exact to the published framework
Validation before anything reaches an officer
Case-officer review workflow
Exception queues with named owners
Filing calendar across every reporting period
An audit trail behind every figure
Who uses itCase officers and reviewers; utility compliance filers
TenancySingle-tenant. There is one such pipeline in the country
How it's boughtPublic procurement against a Terms of Reference

Described by what we build.

Systems design & architecture

The shape of the thing before anyone writes it: data model, tenancy, integration surface, failure modes.

Platform build & integration

Delivery against the mandate, wired into the systems the institution already runs rather than replacing them wholesale.

Regulatory-grade data pipelines

Collection, validation and audit trails built so a published figure can be traced to its source years later.

Implementation & change management

Getting it actually used: training, migration, and the unglamorous months after go-live.

Sector research & feasibility

Market scoping and feasibility studies: the measuring work that decides whether a build should happen at all.

Utility reporting (working name) The same core that carries one national pipeline could serve every distribution utility that files monthly. In development: not yet a product, and not yet for sale.

The product sells. The deployment proves.

SerbisKo is the product; a named province is the deployment. We keep those separate on purpose: a platform named after its first client quietly tells every other province that it belongs to someone else.

Deployment of SerbisKo

One province, seventeen towns

One resident profile across seventeen municipalities and three islands, so nobody crosses the sea to line up. Municipal and provincial editions of the same platform, with the archipelago services the mainland never needs: inter-island ferry manifests, off-island health referral, tourism accreditation.

In procurement
Current stage
17
Municipalities
3
Islands
Deployment of IslaKo

An island tourism network

The first network: accredited operators and guides on a fairness-weighted rotation, itineraries planned around the mainland sailings and the open-sea crossings that cancel them, and a benefit-sharing ledger the provincial tourism office can actually show its own operators.

In design
Current stage
Fair
Guide rotation
Local
Commission retained

See the one that fits you.

Tell us which institution you're with and we'll show you the product for your sector, with your own numbers in it.