Skip to main content
    iTmethodsStart a conversation

    Tell us what you are working on, and we will tell you what we would do.

    Four motions, four different conversations, and one thing in common: the scope is written down before anything runs, and the recommendation at the end is allowed to say stop. Pick the track that fits, or write to us without picking one.

    Nothing on this page is a purchase, a commitment or a meeting in your calendar. It is a first message.

    How far each one is four different stages
    Not one offer. Four, at four distances. Reign Ops Your tools & platforms Reign Gateway One traffic path AVAILABLE TODAY Reign Factory One backlog you defer AVAILABLE · BETA RELEASE Reign Assurance One named population CO-DESIGN DEVELOPMENT NEARER TO SOLD NOT SOLD What we can promise depends on where it sits NOTHING HERE IS A PURCHASE
    Reign Assurance is drawn dashed because it is in co-design and is not sold. The other three are.
    Which conversation

    Four motions, and they are not at the same stage.

    Each one asks for something different at the start, and each one is a different distance from being sold. Pick the one that matches the work you have.

    Reign Ops · available today
    You already run an engineering toolchain and an open source estate, and version currency keeps losing to whatever is more urgent. Bring the estate and the platforms, and we will say what we would take on first and what we would leave alone.
    Talk about your estate →
    Reign Gateway · available today
    Your agents and applications reach models, and nobody can account for the calls afterwards. Bring one traffic path and the person who owns the policy behind it.
    Bring us one traffic path →
    Reign Factory · Available · Beta Release
    You have work that is understood, unstarted and already costing you something. Bring one repository, one definition of done and one named reviewer.
    Bring us meaningful work →
    Reign Assurance · Co-design development
    You have regulated work that has to be defended, and the record it produces is decided by people who are not in the room when it is designed. Bring one named population and the control people who would have to rely on it.
    Co-design it with us →

    None of these, or more than one? Write to us at the foot of this page and say so. Contact lists the six subjects that already have an owner, including procurement, a suspected vulnerability, press and partnership.

    What is the same in all four

    The track changes. The way it runs does not.

    Whichever conversation you start, these four hold. They are the part worth reading before you decide whether to write.

    01Scope is written down first
    What is in and what is out, agreed before anything runs.

    If the scope grows, that is a new conversation rather than an assumption. Work outside it is not started, and the rule that refused it is visible to you.

    02A named person on each side
    One person accountable on yours, one named engineer on ours.

    Not a team address and not a rota. The engineer sits close enough to the work to see the real conditions rather than the described ones.

    03Measures agreed before, not reconstructed after
    The baseline is recorded before the first change, not assembled once there is something to report.

    If we cannot agree a measure with you, we do not claim one. That is the same rule that governs the only figures published anywhere on this site.

    04A recommendation that is allowed to say stop
    In writing, with the reasoning, so your own people can argue with it.

    Stop is a real outcome. A recommendation that can only ever say continue is not worth reading, and it is not what any of these four conversations is offering.

    After you send it

    It reaches a person, not a queue.

    Five steps, and the fourth one is the one most companies leave off the page.

    01In
    Your note arrives

    Your name, a work email, and what you are working on

    02Read
    A person reads it

    Rather than a rule filing it under a topic and leaving it

    03Owned
    It goes to whoever owns the answer

    A question about how a platform is operated is answered by the people who operate it

    04Or not
    Sometimes the answer is that we are not the right people

    We would rather say so, and say who might be

    05Out
    A straight answer, or a proposal you can decline

    Nothing is booked and nothing is sequenced

    The ask, and the cost

    Small on purpose, and you can end it.

    If the ask feels large, we have described it badly. Here is the whole of it.

    What we ask for. Access to one real piece of work, under your controls, and time with the people who own it. Not a budget, not a transformation program, not a signature on a multi-year plan, and nothing to install or procure in order to have the conversation.
    What it commits you to. Nothing. Writing to us does not place a meeting in your calendar and it does not begin a sequence. Where a conversation looks worth having we will propose one, and you can decline it without that being awkward.

    The four motions sit at four different stages, and one page states which is which without softening any of them. If a page anywhere on this site reads as more confident than that one, that one is correct. Product status →

    Next step

    One message, in your own words.

    Tell us the work, who would have to accept it, and what is currently stopping it. If you do not know all three yet, write anyway and say which one is missing.