Approach
Three ways to start.
In order of commitment: a conversation, a scoped start, then a capability that stays.
Three doors
In order of commitment.
Read the work
No form and no meeting. Find the problem closest to yours and ask for the detail behind it, including the parts that did not go to plan.
Browse the engagementsA scoped assessment, or one pilot
A few weeks, paid, deliberately small. We run discovery, rank where AI is worth the effort here, and get one thing working in production conditions before anyone commits to scale.
Book a discovery callA capability that stays
Months to years. What separates the four models is what your account is left holding at the end.
See the engagement modelsWho does the work
What you buy after that is continuity on your account.
What you buy after the first step is continuity on your account. Not the same faces guaranteed for years, which no services company can honestly promise, but the evaluation suites, the failure catalogs and the operating knowledge built up in your own repository as the work happens.
Where the work happens and where your data sits are separate questions, and both are answered in writing before anything starts.
AI in the delivery
What AI changes in the build.
We test it on our own work before it reaches yours: generating tests, reading unfamiliar code, drafting requirements, and measuring what the agents produce so the effect can be checked rather than claimed.
It means the same people spending their time on the decisions rather than on the typing.
How you buy it
Four ways to buy, and the same five questions for each.
How it starts, who staffs it, what you own at the end, what it is priced on, and how it ends. All five are in writing before anything starts, along with where the work happens and where your data sits.
We do not promise the same people for years, because no services company honestly can. What stays is what was written down as the work happened.
Indicative ranges are shared on a call rather than published, because they move with the shape of the work and where it is done.
- 01Defined projectA fixed scope with a date on it.
- 02Standing teamContinuity on your roadmap, and the context stays in your repository.
- 03Center of ExcellenceBuilt and run by Trantor, with the option to take it in-house on agreed terms.
- 04Managed runWe take on what is already live, with the route back defined at the start.
| Question | 01Defined projectA fixed scope with a date on it. | 02Standing teamContinuity on your roadmap, and the context stays in your repository. | 03Center of ExcellenceBuilt and run by Trantor, with the option to take it in-house on agreed terms. | 04Managed runWe take on what is already live, with the route back defined at the start. |
|---|---|---|---|---|
| How it starts | A scoped statement of work against an outcome you can describe. | A team shaped to your roadmap rather than to a scope. | A center stood up and run by Trantor, hiring against your standards. | A transition period where we learn the system while you still hold it. |
| Who staffs it | A named team from our offices, held for the duration. | Engineers from our own offices, working to your roadmap. | Our people, recruited for the account. | A run team, with escalation paths named before day one. |
| What you own | The code, the documentation and the decisions. All of it, at the end. | Everything they produce, continuously. | The capability, and the option to take the center in-house on agreed terms. | The system. We own the running of it. |
| Priced on | The scope. | The team. | The center. | The service and the levels agreed. |
| How it ends | On the date, with a handover you can act on.This is the model where the capability leaves with us, and you should choose it knowing that. | On notice. The context stays because it was written into your repository as the work happened. | By transfer or by notice.The transfer path is the reason to choose this over a standing team. | On notice, with a reverse transition defined at the start rather than at the end. |