Is this a sales call?
It is a working session about your situation. Where we are not the right people we say so, and say who might be.
Book a briefing · Reign Factory
Discuss one defined delivery backlog.
One repository. One delivery path. Rules and measures agreed before anything runs, and a written recommendation at the end to continue, narrow or stop. The ask is deliberately small, and you can end it.
- A plain answer on fit, including when we are not the right people.
- What we would look at first: your delivery path.
- A working session on your situation, not a product demo.
Reign Factory is available today as a single-tenant instance, on Reign Dedicated or in your own AWS or Azure account.
- Two decades operating regulated & SDLC platforms
- SOC 2 Type II on Reign Ops
- Dedicated and single-tenant
- FINOS member
After you send it
Three steps, and the first is a person.
A person reads it
Not a rule that files it under a topic. A question about how a platform is operated is answered by the people who operate it.
We reply within one business day
To propose a time, or to say we are not the right people and who might be. You can decline.
A 30-minute working session
One repository and one delivery path. Nothing is booked, bought or committed until you decide.
What to bring
Choose work with a clear owner and definition of done.
Bring something that is already on someone's list and already costing you something.
Why we ask for real work
A demonstration repository is built to be finished. It has no history, no exceptions, and no owner who is inconvenienced if the change is wrong.
Real work carries the constraints that decide whether a delivery path holds: a review path with a person at the end of it, a release window that belongs to someone else, a dependency nobody wants to touch, a rule that is written down and enforced. Those constraints are the test. Everything else is theater.
01A remediation backlog
Findings that have been open long enough to feel normal.
The work is understood, the fix is agreed, and nobody has had a clear run at it. This shape suits us because done has already been defined by someone else.
AskWhich of these items has been reopened after being closed?
02An upgrade or migration
A version move, a platform change, or a dependency that is now a constraint on everything built near it.
The work is repetitive, the risk sits in the review, and the review stays with you.
AskWhat is the oldest thing you are still paying to keep alive?
03A commitment that has slipped
A delivery date that has moved more than once, for reasons that are known and unglamorous.
Bring the part that is blocking it rather than the whole program.
AskIf one piece of this moved first, which piece would it be?
We work inside your repository and your review process, on the SDLC tools you already run: GitHub, GitLab, Jira or Linear. A named iTmethods engineer runs the engagement alongside your reviewer.
Readiness
What has to be true before we start.
An honest checklist. If an item is missing, we would rather find out now. These four are the whole entry requirement; there is nothing to install on your side and nothing to procure in order to have the conversation.
1
A repository we can be given access to
Under your controls. Your identity provider, your permissions, your network rules. We do not ask you to relax any of them, and we do not take a copy elsewhere.
2
A definition of what done looks like
Written by you, and specific enough that a reviewer can say yes or no to it without calling a meeting.
3
A named reviewer on your side
One person who is accountable for accepting or rejecting the work, and who has the authority to do it.
4
Agreement on what will be measured
The baseline is recorded before the first change, not reconstructed afterwards. If we cannot agree a measure, we do not claim one.
If one of these is missing. We will say so at the start rather than discover it later. Where a condition cannot be met, we will tell you what we would do instead, or we will tell you that we would not start.
What you get back
Work, measures, and a recommendation.
Three things, at the end, in writing.
At the end
The three things
In your own systems, not a separate report to be reconciled
Completed work in your own approval path. Changes arrive for review in the repository you gave us. Your named reviewer approves or rejects. We do not merge and we do not release.
Measures against the baseline you agreed. Reported against the definition set before the work started, with the record of what was done and by what path.
A written recommendation to continue, narrow or stop. With the reasoning, so your own people can argue with it.
Stated up front
The boundaries of this engagement
The limits, in the same voice as the offer
Stop is a real outcome. If the evidence points there, we will write it down and say why. A recommendation that can only ever say continue is not worth reading, and it is not what we are offering.
Our figures are ours. The only figures we publish are measured on our own engineering, in our own internal environment. That is our work in our environment. It is not a projection for your estate and we will not present it as one.
Commercial terms are separate. There is no agreement, no statement of work and no commercial terms in place by reading this page or by writing to us.
Next step
Send us one repository.
One repository, one definition of done, one named reviewer. If the answer at the end is stop, you will have that in writing and you will have lost very little getting it.
Before you write
Questions people have first.
What should I bring?
One repository, a definition of done and a named reviewer. "What to bring" above lists the kinds of work that suit a first engagement.
Who will I speak to?
The people who operate and build Reign, not a booking queue.