ProjectsStudioNews
Contact
Start a project
Engineered, designed and run by one accountable team.

Relix CRM · sales operations

Protection, assurance and compliance your auditors can follow.

Sophos & Fortinet OEM partner

A senior product team on demand, managed by us.

Software development as a service

Platforms built around the way your organisation works.

Custom software development

Research, journeys and interfaces people adopt.

Product design & UX

Integrations, APIs and cloud that hold under load.

Cloud & API engineering

Sophos & Fortinet firewalls and endpoint protection.

Cybersecurity OEM solutions

Find the way in before an attacker does.

VAPT & threat assessments

Know where sensitive data lives, and stop it leaving.

Data loss prevention (DLP)

Monitoring and reporting your regulator can audit.

AML & compliance engineering

Controls, integrations and evidence for regulated institutions.

Banking & Finance

Clinical workflows that protect patient data and keep care moving.

Healthcare

Orders, stock, payments and delivery that agree with each other.

Commerce & Logistics

Citizen services that run end to end, with an audit trail.

Public Sector

Admissions, fees and results that hold up in peak season.

Education

Payment flows, monitoring and reconciliation built for scale.

Fintech & Payments

The Relix CRM sign-in screen: workspace access requires an accountRelix CRM, sales operationsFeatured project

Citizens need a completed service, not another portal. Connect applications, approvals and accountable records.

Public service software that carries applications through to decisions

Aerial view of a Lagos bridge and waterfront district

Why it matters

Agencies need auditable service decisions, accountable procurement and lawful personal-data handling. Citizens need accessible transactions that finish on realistic connections, with clear ownership when an application stalls.

The problem

A portal is only useful when the service gets completed.

Why digital services still end in paper

Agencies need auditable service decisions, accountable procurement and lawful personal-data handling. Citizens need accessible transactions that finish on realistic connections, with clear ownership when an application stalls.

The traps

01 / 04
  1. Trap 0101 / 04

    A launch, not a service

    Paper behind portals

    Citizens apply online but carry paper between offices. Connect approvals and document status.

  2. Trap 0202 / 04

    Queues without owners

    Unclear ownership

    Applications stall between departments. Assign decisions, escalation routes and service ownership.

  3. Trap 0303 / 04

    Citizen data exposed

    Excessive access

    Broad permissions expose records beyond the task. Limit access and log sensitive record changes.

  4. Trap 0404 / 04

    Access assumed

    Connectivity ignored

    Heavy pages fail on unreliable connections. Test essential tasks on affordable devices and weak networks.

Public Sector, in figures

The UN indices compare public-service capability, infrastructure and participation. They do not measure website design alone. Use them as context for accessible transactions, accountable decisions and reliable service ownership.

  • E-government global rank

    144th

    Nigeria ranked 144th of 193 in the UN E-Government Development Index, 2024.

  • E-government development score

    0.4815

    Nigeria's rounded EGDI score, combining services, infrastructure and human capital; UN, 2024.

  • E-participation index score

    0.3699

    Nigeria's e-participation index score for information, consultation and decisions; UN, 2024.

  • Breach notification

    72h

    Notify NDPC within 72 hours of awareness where a breach risks individuals' rights or freedoms; NDPA 2023 / GAID 2025.

Sources: UN: Nigeria EGDI rank, 2024; UN: Nigeria EGDI score, 2024; UN: Nigeria e-participation score, 2024; NDPC, NDPA 2023 / GAID 2025 (72-hour risk-based notification).

03

Public sources behind the figures on this page

  1. 01UN: Nigeria EGDI rank, 2024
  2. 02UN: Nigeria EGDI score, 2024 and related sector figures
  3. 03NDPC: GAID 2025 and breach notification

Figures retain their source periods and scope. They describe sector conditions and legal duties, not Sparkr project outcomes.

How we work with your team

Start with the workflow, then test the controls

We map applications, approvals and interdepartmental handoffs. Together we agree owners, acceptance criteria and the evidence needed before delivery starts.

  1. Step 01

    Scope & Discovery

    We map critical tasks, system boundaries and risk with your delivery and operational owners.

    ScopeRisk review

  2. Step 02

    Architecture & Controls

    We define access rules, data flows and failure handling before implementation decisions are fixed.

    AccessData flows

  3. Step 03

    Workflow Design

    We prototype critical tasks and review them with users before building the full workflow.

    UXTask testing

  4. Step 04

    Build & Test

    We implement in reviewed increments, testing permissions, integrations and exception handling.

    EngineeringControl tests

  5. Step 05

    Release & Operational Handover

    We agree release checks, recovery procedures and support ownership, then hand over evidence.

    Release readinessHandover

Selected work

Related work and delivery capabilities

Designed for

Software and controls for everyday operational pressure.

  • Operational workflows
  • Access reviews
  • Reconciliation
  • Audit evidence
  • Recovery planning

FAQ

Got a question? We answer it here.

How do you scope public sector work?

We start with the workflow, system boundaries and the evidence your team needs. The scope records users, integrations, data categories, access roles, operational risks and acceptance criteria. We then agree delivery phases and commercial terms. We do not publish a fixed price before reviewing complexity, dependencies, migration needs and the controls that must be tested.

Can you work with our existing systems?

We review available APIs, data ownership and integration constraints before proposing changes. The plan includes failure handling, reconciliation where relevant and a staged release. We agree what stays, what changes and who owns each dependency rather than assuming a full replacement is necessary.

How do you protect sensitive records?

We define role-based access, encryption needs, data handling rules and audit trails with your owners. Test environments should use appropriate masked or synthetic data. Retention, exports and privileged access need explicit decisions, not default permissions.

Can you help us evidence our obligations?

We help translate applicable requirements into controls, workflows and reviewable evidence. Your compliance and legal teams confirm applicability. Delivery may include access reviews, incident records and control tests; it does not constitute regulatory approval or a guarantee of compliance.

How do you agree delivery timescales?

Timescales follow scope, integration access, data quality and review availability. We agree milestones after discovery, with clear acceptance criteria and dependency owners. A staged release can prioritise essential workflows without hiding unfinished controls.

What related work can we review?

We have not presented a public-sector case study here. The linked service capabilities describe how we would scope software and security work with agency owners; they are not claims of completed government deployments.

Further reading

Practical reading on software and control design.

Other industries

Back to all industries
WhatsApp us