Cycle 24

Week 3 of 6

18 working days left

Open navigation
Appetiter24

Multi-harbour accounts, shaped and ready for the table

The problem, the appetite, the rabbit holes named and the no-gos written down.

P-5ShapedBig batch6w

Appetite

6weeks

Six weeks. A port with four harbours is our largest account shape and the workaround is now a spreadsheet somebody maintains by hand. Two weeks would buy a shared login and nothing else, which is the half that does not solve the invoice.

Falmouth Port runs four harbours through us. Every one of them is a separate workspace with its own login, its own threshold list and its own invoice. Their operations manager keeps a spreadsheet mapping which login sees which harbour, and last month a threshold change went into the wrong one.

Ines KaurShaped by Ines Kaur, 2 days ago

Solution

Three places, drawn as a breadboard. Enough to argue about, not enough to be a design.

  1. 1

    Organisation switcher

    One account holds many harbours. The switcher sits where the harbour name is today, so nothing else on the page moves.

  2. 2

    Shared threshold sets

    A set belongs to the organisation and a harbour opts into it. A harbour that opts out keeps its own list, unchanged.

  3. 3

    One invoice, itemised by harbour

    Billing moves to the organisation. The invoice keeps a line per harbour so the port can still recharge internally.

Places connect in order. Nothing here fixes a layout.

Rabbit holes

Named so nobody falls in

  • Per-harbour permissions. One role per person per organisation, and that is the whole model this cycle.

  • Migrating the three ports that already have separate accounts. We build the shape first and move them in cooldown.

  • Threshold set versioning. If a set changes, harbours get the change. No history, no rollback.

No-gos

Out of scope on purpose

  • No single sign-on. It comes up in every enterprise conversation and it is not this bet.

  • No harbour-level billing addresses. One address per organisation.

  • No transfer of an existing harbour between organisations.

Why it matters

A no-go is a promise. It is what keeps the appetite honest when week four gets hard.

Decision for C-25

10 of 12 team-weeks are already bet

This pitch wants 6 weeks and only 2 are uncommitted. Something already on the table has to come off first.

Circuit breaker

A bet that will not fit gets broken and the pitch returns here. Nothing rolls over automatically.