Skip to main content

    For existing customers

    Your service continues.

    You have seen a new name. Nothing you depend on is moving. The same team runs the same service, to the same levels, under the same agreements. Reign is the name on what we build next. This page explains the difference.

    Nothing on this page requires you to do anything.

    What is not changing

    The service you run today.

    Specifically, and in plain terms.

    • The same team. The same named people, the same engineers, the same escalation contacts. Nobody has been reassigned because of a brand.
    • The same service levels. Your agreed levels stand as written. They are not being restated, reinterpreted or replaced.
    • The same operating model. The same change process, the same maintenance approach, the same way work is raised, approved and reported.
    • The same agreements. Your contract is unchanged. Scope, term and terms remain exactly as signed.
    • The same invoices. Same billing entity, same format, same route. Nothing about how or when you are invoiced changes.
    • The same support routes. The same address, the same ticket path, the same escalation ladder. Continue to use what you use now.

    If you were to change nothing at all after reading this page, you would be doing the right thing.

    What is changing

    The name on what we build next.

    And the shape of the product line.

    Reign is a product brand of iTmethods. It is not a new company, not a spin out and not a merger. The company you hold an agreement with is the company that has held it. The domain stays. The logo stays. The invoicing entity stays.

    What is new is that the work we do is now described as four motions rather than as a list of services.

    • Reign Ops. Operate. Available today.
    • Reign Factory. Build. Available · Beta Release.
    • Reign Gateway. Govern. Available today.
    • Reign Assurance. Assure. Co-design development.

    The line has one promise: we state the stage every time, and we do not describe a motion as finished before it is.

    One thing to be clear about. Reign Factory is being productized toward commercial availability. It is not part of your current service, it is not being added to it, and nothing in your agreement changes because it exists.

    The questions you will actually ask

    Answered directly.

    If your question is not here, write to us and ask it.

    Does my contract change?

    No. Scope, term and terms remain as signed. If anything ever needs to change, it changes the way it always has, in writing and with your agreement.

    Does my invoice change?

    No. Same entity, same amounts, same format, same route. You will not see a new line item because of a brand.

    Do I need to buy anything?

    No. Nothing on this site requires a purchase. The new motions are separate from the service you run today, and you can ignore them without consequence.

    Does my support route change?

    No. Same address, same ticket path, same escalation ladder, same people at the end of it. Keep using what you use now.

    Is my existing service being renamed?

    Your service continues under the name you know it by. Reign Ops is how we describe the operating motion across the product line. Nothing on your side is relabeled without you agreeing to it first.

    What we need from you

    Nothing.

    There is no action here.

    There is no migration, no upgrade, no form to complete and no meeting you have to attend. Your service carries on whether or not you read past this line.

    If the new work interests you, the route is the same address as everything else: reign@itmethods.com. Say which motion you are asking about and we will answer the question rather than book a demonstration.

    If you would prefer to raise it with the people you already speak to, do that. They know about it.

    If you want to talk

    Ask us anything about this.

    We would rather answer a direct question than have you read between the lines of a rebrand. Nothing you ask changes what you already have.