Approach
Three ways to start.
In order of commitment: a conversation, a scoped start, then a capability that stays.
Three doors
Each one asks a little more of you than the last.
A conversation
Tell us what is in front of you, and we will guide you to the right path. It costs nothing and commits you to nothing.
Talk to usA 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. If your pilots already work, we start from them.
Talk to usA capability that stays
Months to years. The four engagement models differ in what your account holds at the end.
See the engagement modelsWho does the work
What stays after the first step is continuity on your account.
Not the same faces for years, but the evaluation suites, the failure catalogs, and the operating knowledge we build in your own repository as the work happens.
Where the work happens and where your data sits are separate questions, and we answer both 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 you can check the effect rather than take our word for it.
Our engineers spend their time on the decisions rather than on the typing.
How we engage
Four ways to engage, 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. We put all five in writing before anything starts, along with where the work happens and where your data sits.
We share indicative ranges on a call rather than publish them, because they move with the shape of the work and where it happens.
- 01Defined projectA fixed scope with a date on it.
- 02Standing teamContinuity on your roadmap, and the context stays in your repository.
- 03Center of ExcellenceWe build and run it, and you can 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 ExcellenceWe build and run it, and you can 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 we stand up and run, 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 length of the project. | 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.You keep the code, the documentation, and the decisions; the working knowledge of the team does not stay, so choose this model knowing that. | On notice. The context stays because we write it into your repository as the work happens. | 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. |