The problem with time as revenue
Traditional IT services revolve around time, capacity and projects. Consultants are hired at an hourly rate, developers are sold as capacity, and every new question comes with a quote. That can work fine. But the interests do not automatically align: the client wants faster results, less complexity and lower costs, while a supplier that sells hours earns more when more work is needed.
AI widens the gap
Suppose an experienced architect uses AI to solve in two hours what used to take two days. For the business, that is excellent. In an hourly model, it is a problem for the supplier: there are only two hours left to invoice. The more productive the technology, the less attractive the hourly model for whoever sells it.
Our choice: the IT department, not the supplier
We become the external IT department of the business, for a fixed monthly fee. That fee explicitly does not stand for a number of hours. There are no hours "left over" at the end of the month, and no consultant who has to be kept billable. You get access to expertise that larger organisations spread across several roles:
- IT management;
- enterprise and solution architecture;
- AI;
- software development;
- vendor management.
What that delivers
- No dependency on one supplier or one person. Everything is documented and remains transferable.
- Continuity of knowledge. We do not have to get to know your business again for every project.
- Aligned interests. It is in our interest that solutions stay simple, that existing technology is put to use and that bad investments are prevented early.
- Efficiency is a gain for both. If we work faster thanks to experience and AI, that is an advantage, not a loss.
New development is not covered by the monthly fee; we agree on it per backlog item via the backlog.
The core
Not: how much IT can we sell? But: how do we make sure this business achieves more with fewer people, resources and less complexity?
Updated on