Correcting the claim that Builder.ai used no AI
A former employee’s account describes both AI systems and human developers, so the viral shorthand needs care.
Originally posted · Published here · 1 source · Resume reading
Our original caption presented Builder.ai as a service whose supposed AI was actually hundreds of developers. The available firsthand evidence does not support reducing its operation to that claim.
What a former employee described
In June 2025, former employee Andrew Gorton wrote that Builder.ai used AI for requirements, prototypes, planning, code and tests, while also matching customers with developers to customize or extend components. He explicitly disputed the assertion that the company had no real AI [1].
That is an account from someone who worked there, not an independent audit of every company claim. It also does not verify the exact headcount in our caption. The correction is to distinguish a mixed human-and-AI delivery process from an allegation that all automation was fabricated.
Ask what a service actually delivers
For an app-building service, ask which steps are automated, which need people and who reviews the result. Confirm who owns the source code, how it is exported and what happens if the provider becomes unavailable.
A demonstration can show a working screen without explaining the delivery process behind it. Request a small, inspectable deliverable and clear responsibilities before committing an important project. Human involvement is not itself evidence of deception; the relevant question is whether the service accurately explains the work it performs.
Keep this guide
Filed under AI agents
Sources
- Andrew Gorton: firsthand account of working at Builder.aiandrewgorton.uk
Next in this stack
Keyword LOOP
Five rules for building an AI agent that works
Keyword STARTER
Write skill metadata an agent can recognize
Keyword SIMPLEFIRST
Choose an AI workflow before building an agent