{"id":18673,"date":"2026-04-24T10:37:10","date_gmt":"2026-04-24T09:37:10","guid":{"rendered":"https:\/\/www.axpe.com\/?p=18673"},"modified":"2026-04-24T11:10:45","modified_gmt":"2026-04-24T10:10:45","slug":"ia-en-administraciones-publicas-el-modelo-de-contratacion-que-empieza-a-quedarse-atras","status":"publish","type":"post","link":"https:\/\/www.axpe.com\/en\/ia-en-administraciones-publicas-el-modelo-de-contratacion-que-empieza-a-quedarse-atras\/","title":{"rendered":"AI in Public Administrations: the procurement model that is starting to fall behind"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

AI in Public Administrations: the procurement model that is starting to fall behind<\/strong><\/h2>\n

\n<\/p>\n

AI is changing the way software is built and maintained. Public procurement has yet to catch up. At AXPE we have been observing this underlying shift for some time \u2014 and we believe it will directly affect how IT is tendered in public administration.
<\/span>

<\/span><\/p>\n

<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\n\t\t\t\t\t<\/path><\/svg>\t\t\t\t<\/span>\n\t\t\t\t\t\tWhat we are seeing at AXPE. We are not talking about the future. We are living it in real projects. The relationship between team size and delivery capacity is no longer linear \u2014 and that has practical implications for how public IT contracts are designed, valued and awarded.\t\t<\/h5>\n\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

When productivity stops being linear<\/h3>\n

<\/p>\n

<\/p>\n

Until now, across much of the sector, there was a fairly clear relationship between delivery capacity, headcount and service cost. It was not perfect, but it was predictable enough. Today that is starting to change.
Artificial intelligence makes it possible to accelerate tasks that until very recently consumed a great deal of effort: legacy system analysis, component generation, documentation, testing, maintenance support, technical oversight, code review.
This does not mean that talent stops mattering. In fact, the opposite is likely: expert talent will be more important than ever. What changes is that the real capacity of a team no longer depends solely on its size. And if that changes in delivery, sooner or later it will have to change in procurement too.<\/p>\n

<\/p>\n

<\/p>\n

This means going beyond integration with SEPA Instant<\/strong>: it requires a transformation of the banking core<\/strong> and the technological architecture to reduce errors, improve user experience and optimise operational costs.<\/p>\n

 <\/p>\n

<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\"\"<\/figure>

The decoupling: team size vs. real delivery capacity - AXPE analysis\n\n<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

An obvious risk: confusing efficiency with recklessness<\/strong><\/span><\/h3>\n

<\/p>\n

<\/p>\n

At AXPE we believe that one of the most delicate points of this transition will lie in the economic interpretation of bids<\/strong>. If a company manages to deliver better, faster or with less effort thanks to a genuine and structured use of AI, it can submit more competitive offers.<\/p>\n

And there lies a tension we will see more and more: what previously might have looked like an aggressive low bid may, in reality, reflect a more efficient production structure.<\/p>\n

 <\/p>\n

The dilemma:<\/strong> The public procurement system is not always equipped to distinguish between an unviable bid and one built on a different, more efficient operating model.<\/span><\/h5>\n

<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\"\"<\/figure>

The bid dilemma: recklessness or real efficiency? - AXPE estimate<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The impact will be especially visible in recurring services<\/strong><\/span><\/h3>\n

<\/p>\n

<\/p>\n

Where we will notice this change first, in our view, is in the most recurring and structured services:<\/p>\n

 <\/p>\n

    \n
  • Application maintenance and AMS<\/li>\n
  • Quality assurance (QA \/ testing)<\/li>\n
  • Technical offices and technology PMO<\/li>\n
  • Evolutionary support services<\/li>\n
  • Technical documentation and deliverable control<\/li>\n<\/ul>\n

     <\/p>\n

    Why? Because these are areas where historically there has been a significant share of repetitive, traceable and structured activity \u2014 and those are precisely the layers that will undergo the most transformation.<\/p>\n

    Technical offices, for example, will need to shift away from mechanical oversight and focus more on expert control, judgement, decision-making capacity and genuine service governance<\/strong>.<\/p>\n

    <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t
    \"\"<\/figure>

    Public IT services: expected level of transformation by AI - AXPE analysis<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    The current framework is built on a logic that is beginning to strain<\/h3>\n

    <\/p>\n

    <\/p>\n

    A large part of current public tender specifications still respond to an implicit premise: more or fewer people equates to more or less capacity, and cost is explained mainly by the team’s salary structure.<\/p>\n

    But if productivity stops being linear, that premise begins to break down. And when it does, many questions arise:<\/p>\n

     <\/p>\n

      \n
    • How do you size a service with AI?<\/strong> Team size is no longer the only indicator of capacity.<\/li>\n
    • What weight should outcomes carry vs. the team?<\/strong> Tender specifications must incorporate real output metrics.<\/li>\n
    • How do you compare such different bids?<\/strong> An “expensive but efficient” offer may be better than a cheaper one without AI.<\/li>\n
    • Is the LCSP ready for this?<\/strong> The current framework assumes linear productivity. That is starting to fail.<\/li>\n<\/ul>\n

       <\/p>\n

      At AXPE we believe this reflection is not theoretical. It is already beginning to surface in real conversations across the sector.<\/p>\n

      <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t
      \n\t\t\t
      \n\t\t\t\t\t\t\t\n\t\t\t\t\t<\/path><\/svg>\t\t\t\t<\/span>\n\t\t\t\t\t\t\"The question is no longer how many people are needed. The question is what service model makes sense when productivity can change radically without any increase in team size.\"\t\t<\/h5>\n\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      The current framework is built on a logic that is beginning to strain<\/h3>\n

      <\/p>\n

      <\/p>\n

      A large part of current public tender specifications still respond to an implicit premise: more or fewer people equates to more or less capacity, and cost is explained mainly by the team’s salary structure.<\/p>\n

      But if productivity stops being linear, that premise begins to break down. And when it does, many questions arise:<\/p>\n

       <\/p>\n

        \n
      • How do you size a service with AI?<\/strong> Team size is no longer the only indicator of capacity.<\/li>\n
      • What weight should outcomes carry vs. the team?<\/strong> Tender specifications must incorporate real output metrics.<\/li>\n
      • How do you compare such different bids?<\/strong> An “expensive but efficient” offer may be better than a cheaper one without AI.<\/li>\n
      • Is the LCSP ready for this?<\/strong> The current framework assumes linear productivity. That is starting to fail.<\/li>\n<\/ul>\n

         <\/p>\n

        At AXPE we believe this reflection is not theoretical. It is already beginning to surface in real conversations across the sector.<\/p>\n

        <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t
        \"\"<\/figure>

        AI in public administrations: the model that no longer fits<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        <\/p>\n

        This is where the deepest change lies. The tender specifications of the future will need to evolve:<\/p>\n

        <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t
        \"\"<\/figure>

        From valuing people to valuing real capacity - AXPE analysis<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t
        \"\"<\/figure>

        Relative weight of each factor in service evaluation - AXPE analysis<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        At AXPE we are preparing for that scenario<\/h3>\n

        This transformation is not tackled by incorporating AI tools into day-to-day work. It is tackled by genuinely rethinking how the service is delivered<\/strong>, how teams are organised and how all of that translates into a reliable, traceable delivery model that is compatible with the demands of the public sector.<\/p>\n

        The future of these contracts will not depend solely on who has the most people assigned, but on who is best able to combine talent, method, automation, business knowledge and execution capacity<\/strong>.<\/p>\n

        For years, public software procurement has bought, directly or indirectly, people. The market is beginning to move towards a different logic: contracting for capacity, outcomes and real efficiency<\/strong>.<\/p>\n

        Are you debating this change in your organisation? We would love to hear your perspective.<\/strong><\/i><\/p>\n

        <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t
        \n\t\t\t
        <\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

        AI is changing the way software is built and maintained.<\/p>","protected":false},"author":27,"featured_media":18674,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,22],"tags":[],"class_list":["post-18673","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analysis-and-trends","category-press-room"],"_links":{"self":[{"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/posts\/18673","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/comments?post=18673"}],"version-history":[{"count":12,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/posts\/18673\/revisions"}],"predecessor-version":[{"id":18832,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/posts\/18673\/revisions\/18832"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/media\/18674"}],"wp:attachment":[{"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/media?parent=18673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/categories?post=18673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.axpe.com\/en\/wp-json\/wp\/v2\/tags?post=18673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}