Skip to main content
Parousia Group

What we have built

Programmes, platforms and deployments

The group and its companies operate what they build. The programmes below are described by what was engineered, not by what was promised.

Selected programmes

  • Telecommunications

    A national transport backbone with an operations centre

    The constraint
    Long-haul capacity existed on paper but had no single operator accountable for it end to end, so faults were diagnosed by argument between vendors.
    What was engineered
    Global Technology Africa took the transport layer, the monitoring and the operations centre as one scope: one team, one alarm correlation, one escalation path.
    What it changed
    Faults are now attributed to a span rather than to a supplier, and restoration begins before the customer reports the outage.
  • Financial services

    Payment switching with an agent network behind it

    The constraint
    Digital payments failed at the point where a customer needed cash out, and an agent without liquidity is a broken service.
    What was engineered
    PAGpay operates the switch and the agent network together, so liquidity is managed as part of the platform rather than left to the agent.
    What it changed
    Cash-in and cash-out are treated as part of the payment product, not as somebody else’s problem.
  • Retail and commerce

    Marketplace, settlement and delivery as one chain

    The constraint
    A marketplace with no settlement and no delivery is a catalogue, and buyers had no reason to trust a first transaction.
    What was engineered
    Afrika Plaza, PAGpay and PAGexpress operate the storefront, the money and the parcel inside the same group, with escrow between them.
    What it changed
    A first purchase becomes a reasonable risk for a buyer who has never met the seller.
  • Government and public sector

    Sovereign hosting where the institution keeps the keys

    The constraint
    Public institutions were asked to choose between a modern platform and legal control of their data. Most chose neither and stayed on paper.
    What was engineered
    The group hosts within the governing jurisdiction and hands key custody to the institution, so no group operator can read the data it stores.
    What it changed
    Modernisation stops requiring a sovereignty concession, which removes the reason the decision was deferred.
  • Education

    Connected classrooms with shared devices

    The constraint
    Learning platforms assumed one device per learner and continuous connectivity. Schools had neither, so licences went unused.
    What was engineered
    INTIC delivers curriculum that works offline on a shared device and keeps individual progress; the group supplies school connectivity and hosting.
    What it changed
    A platform that fits the classroom that exists rather than the one the licence assumed.
  • Transport and logistics

    Last-mile delivery without street addresses

    The constraint
    Route planning built on street names fails where addressing is informal, and every failed delivery is paid for twice.
    What was engineered
    PAGexpress routes on landmarks, zones and recipient contact rather than on postal addresses, and records what worked for next time.
    What it changed
    Delivery attempts succeed on the first visit more often, which is the only figure that moves last-mile cost.

On naming clients

Client names and operational figures are published only with the client’s written consent and once the figures are verified. Where consent has not been given, the programme is described without naming the client — the engineering is disclosable, the relationship is theirs.

Industries

Talk to the team for this sector

Tell us the constraint you are working against. A group engineer answers, not a form.

Contact the group