06 / Who we are

Two rivers, two cities.

Two Rivers started as two cousins, one in Copenhagen and one in Cairo, and the name is literal — the practice runs between the two cities, and between them the two time zones cover most of a working day.

That is the proposition, not a logistics footnote. European engineering standards: a written design constitution, tests, a system still coherent after a year of changes and a hundred of them. Applied to how an Egyptian operation actually runs: cash on delivery, Arabic and Franco-Arabic in every free-text field, a Cairo warehouse behind several storefronts, a courier who loses parcels in one district and not another. Most software gets one of those halves. This needed both.

The platform was built inside real operations before it was turned into a product, not the other way round. That order matters, and we intend to keep it.

Gudenå

Copenhagen

Architecture, platform, design system

The Nile

Cairo

Operations, the ground truth, the working day

How we build

Five things we hold to.

  1. 01

    Learn the operation before writing anything

    The most valuable module we ever built started as fourteen expense lines with an order number buried in Arabic free text. Nobody would have asked for it. You only find that by going through how the week actually runs, instead of taking a feature list and building it.

  2. 02

    If it is a business rule, it is a setting

    New features need us. New values and rules never should. When it is unclear which one something is, the default is to make it configurable and ask.

  3. 03

    Read-only until trust is earned

    We connect your live data and change nothing, and every automation ships switched off. You decide when the system is allowed to act on its own — per channel, per action, reversibly.

  4. 04

    Deepest value first, in increments you use

    Scoring and rules before reports. The daily routine before the dashboard. A module nobody has used yet is a guess, so nothing waits for a launch.

  5. 05

    Write it down

    Every engagement has a living document with the decisions dated and attributed and the open questions numbered. It is what stops a custom build turning into an argument six weeks in.

Is this the part you need?

The fastest way to find out is to tell us what this part of your operation currently costs you in people and mistakes.

Start a conversation