What does the 2026 Build Economy report mean for UK public sector L&D?

Lovable's May 2026 Build Economy report is the first substantive look at who is now making software. 50 million projects built; 4 in 5 builders are non-technical; the UK is the third most active country. But 82% of builders are men, and the public sector has barely entered the conversation. This piece sets out what the findings imply for UK public sector L&D, including the cost-saving opportunity that procurement and operating processes have not yet caught up with.

Lovable published its Build Economy report on 22 May 2026: the first substantive look at who is now making software. 50 million projects built. 4 in 5 builders are non-technical. The UK is the third most active country. For UK public sector L&D, the report has three implications worth naming directly.

What the report shows

The report draws on platform data from January 2025 to May 2026 and a survey of more than 14,300 users. The central finding is that the people now making software are not, in the main, professional developers. They are domain experts. Founders, designers, sales professionals, operations leads, consultants — 80% identify with non-technical roles. Two in three come from outside the technology sector altogether. 55% have eleven or more years of professional experience. They are building what they know: businesses, internal tools, dashboards, websites, e-commerce, productivity tools.

The pattern is recognisable across professional life. Software creation is increasingly part of professional routines (30% more activity on weekdays than weekends) rather than a hobbyist evening activity. Half of builders are working on a business; another quarter are turning side projects into monetisable products. Three in five plan to monetise. The barrier to going from an idea to a working tool has compressed from months to days, and from large budgets to small ones.

This isn't a hypothetical shift. It is happening at scale, in more than 180 countries, and the UK is a significant part of it.

The gender gap matters

The report is candid about a finding that should not be passed over: 82% of builders identify as men, 14% as women. Lovable points to its SheBuilds programme but acknowledges there is more work to be done.

This matters for two reasons. The first is that software, by definition, encodes the perspectives, priorities, and assumptions of the people building it. A build economy that is 82% male will produce tools that reflect that demographic, including in what gets built (and what doesn't), how problems get framed, and which users are designed for. The Plinq example in the report — a Brazilian platform for women to run background checks before relationships — is a reminder of what gets built when women are the ones building. A lot of that is not yet being built.

The second is that the barrier-removed argument doesn't hold equally for everyone. The barriers Lovable describes as having 'all but disappeared' (code, capital, credentials, connections) were never the only barriers. Confidence, permission to experiment, time outside core responsibilities, exposure to people already doing this work: these are barriers too, and they fall unevenly. Public sector L&D, where the workforce skews female and where the dominant culture is service rather than entrepreneurial experimentation, is exactly the kind of context where creating active space for women to build, prototype, and explore is essential.

The practical move is to design L&D programmes that include AI-assisted building as a deliberate strategic capability for women working in the sector, with the time, permission, and supportive supervision that this kind of skill development genuinely requires.

Catching up public sector creation processes

The second implication is the cost-saving opportunity that has not yet been engaged with at scale.

UK public sector budgets are operating under sustained pressure. L&D budgets specifically are usually one of the first lines under review when the fiscal environment tightens. At the same time, the Build Economy report shows that internal tools, dashboards, training platforms, and assessment systems can now be built by domain experts directly, in days, often for less than the procurement cycle alone would cost.

The public sector creation process has not caught up with this. A police force needing a simple training tracker, a dashboard for supervisor capacity, or an internal assessment platform still goes through full procurement, vendor selection, contracting, and delivery cycles. The cost of that process, before any software is built, can exceed the cost of building the tool internally with AI assistance.

This isn't a call to bypass procurement governance, which exists for good reasons (security, data protection, accessibility, audit). It is a call to update the operating model so that small internal tools, where the data is internal and the risk is contained, can be built by the people closest to the problem in the same way the report describes is happening across the private sector. Forces that work this out first stand to recover real budget capacity at a time when every line is under pressure.

The pieces that need to be in place are operational, not technological:

• A clear internal pathway for L&D leads to propose, prototype, and approve internally built tools
• A security and data protection review process that is proportional to the scope of the tool, not the same review applied to enterprise procurement
• A small group of trained AI-assisted builders inside the L&D function (or in operations alongside it) who can support practitioners with confidence
• Honest internal evaluation of when an internally built tool is enough and when commercial procurement is genuinely needed

This is governance work as much as technology work, and it benefits from being approached as such.

What this means for L&D specifically

Three further implications for L&D leaders.

The L&D function is well placed to be an early adopter. L&D specialists are typically non-technical, domain-expert, and used to designing for specific user needs. The Build Economy report describes exactly this profile as the dominant builder demographic. L&D teams that develop internal AI-assisted building capability will produce better, more targeted tools faster than waiting for vendor solutions to land.

Training on building is itself a strategic capability. Equipping L&D specialists, supervisors, and operational staff to build internal tools with AI assistance is a programme in its own right. It is not covered by the police reform white paper's mandated programmes. It also is not the kind of capability that comes from a one-day workshop. It requires sustained practice, guided experimentation, and supportive supervision, much like any other operational skill.

The 'people closest to the problem' principle applies powerfully in operational contexts. Officers, staff, and L&D specialists who understand the work can now build tools that fit it. The historical pattern, where operational practitioners describe what they need to a vendor and receive a tool that approximates it months later, has an alternative. That alternative is not a replacement for major systems; it is a complement to them, for the smaller-scale tools that vendors are not well placed to build and that internal teams have always needed.

Honest constraints

The public sector context introduces constraints the private sector doesn't carry in the same way, and these deserve attention.

Data protection and security review are non-negotiable. Any tool that handles personal data, operational data, or anything covered by force vetting requirements has to meet the standards expected of any other system in the force. The AI-assisted building advantage doesn't remove this; it changes what the review covers.

Procurement governance exists for legitimate reasons. The risk of bypassing procurement to build internally is that the resulting tools become unmanaged shadow IT. A clear internal framework is the answer, not absence of oversight.

The skills required are not just technical. They are about scoping, problem framing, user research, and operational judgement — exactly the skills L&D practitioners often have. But they also require some new ones, and the time and supportive supervision to develop them well.

Where this lands

The Build Economy report describes a shift that has already happened in the private sector. UK public sector L&D has not yet entered the conversation in a meaningful way. The opportunity is large, particularly for cost recovery in a tight fiscal environment and for actively creating space for women in the sector to build and explore. The constraints are real but navigable. The work is to update operating processes to match what is now possible, and to invest in capability so that the people closest to the problem are equipped to act on it.