“Lots of engineers are builders, lots of designers are builders, lots of marketing folks are builders, and I think ‘builders wanted’ is going to be the big tagline for the next couple of years.”
That is Nikhyl Singhal, founder of The Skip and former product executive at Meta, Google and Credit Karma, speaking on Lenny’s Podcast earlier this year. The clip has been doing the rounds for a reason. It names a shift most organisations can feel but few have said out loud: building is no longer a department.
Building became an aptitude
For decades, the ability to make working software was concentrated in engineering teams, and everyone else queued. AI collapsed that queue. The actuary who understands the pricing problem can now assemble an agent that solves it. The ops lead can wire up the report they always wanted. The marketer can ship the tool, not just the brief for it.
Singhal’s sharper observation in the same conversation is that careers are splitting into builders and managers, and the middle is thinning. The enterprise translation is blunt: your next wave of builders will not arrive through the engineering budget. They are already on the payroll, in every function, waiting for permission and a path.
The poster and the door
Here is the uncomfortable part. “Builders wanted” makes a great poster, and most enterprises have already hung it. Behind the door, the experience is different.
A new builder finds that access to AI tooling is rationed or unofficial. Their prototype works, then stalls, because the path from working demo to governed production runs through quarters of architecture and security review. So they route around the process, and working software accumulates in places the enterprise cannot see. The poster said welcome. The building said no.
None of this is bad faith. Security, compliance and cost control are real obligations. The failure is structural: the organisation invited builders without building for them.
What “builders welcome” actually takes
Three things separate the organisations that mean it from the ones with the poster.
- Somewhere safe to build. Governed, cost-predictable access to AI through managed environments and model gateways in your own cloud, so more builders never means more risk.
- A path that ships. Golden paths that carry a working prototype to governed production, with auth, infrastructure as code and pipelines handled by the platform rather than by every builder becoming a platform engineer.
- Shared context. Builders inherit the why behind the work: the customer pain, the objections, the constraints. Alignment is what stops a thousand builders becoming a thousand directions.
This is the thesis behind the AlisX Platform. Alis Ideate keeps context and consensus flowing so builders start aligned. Alis Build gives them the environment and the flows to ship safely in their own Google Cloud. Democratise the access, pave the path, keep the context moving.
From poster to operating model
Singhal is right about the tagline. “Builders wanted” will be everywhere for the next couple of years. The organisations that benefit will be the ones that treat it as an operating model rather than a slogan, because the builders are already in the building. The question is whether the building is ready for them.
Keep the vibes. Ship the build.