Inside the Builder.ai Scandal and Its Financial Fraud

The viral claim that Builder.ai faked its artificial intelligence (AI) product by using 700 human engineers to impersonate software is false. The actual Builder.ai scandal centered on severe financial misconduct, including inflated revenue numbers and alleged round-tripping transactions, which ultimately forced Builder.ai into bankruptcy in May 2025. While social media posts spread rumors about human coders secretly typing out automated responses, the documented legal and financial records show that the collapse stemmed from accounting fraud and unsustainable cloud debts rather than a mechanical Turk scheme.

What the Builder.ai Scandal Was About

The Builder.ai scandal drew widespread coverage after the company unraveled in early 2025. Builder.ai was a United Kingdom-based software startup that promised to automate mobile and web application creation through an AI assistant named Natasha. Customers were told they could describe an application in plain English, and the software would assemble the necessary components quickly and cheaply.

Venture capital firms poured hundreds of millions of dollars into Builder.ai based on rapid revenue growth and software automation claims. At its height, Builder.ai achieved a private market valuation of roughly $1.5 billion. Builder.ai raised between $445 million and $455 million in total funding from global investment firms, including tech giant Microsoft, which provided an investment reported at $20 million in April 2024 as part of that total.

The public narrative surrounding Builder.ai shifted dramatically when financial disclosures revealed that the business was misstating its actual revenue. Instead of a high-margin software business powered by automated development tools, Builder.ai was burning massive amounts of cash while circulating funds to fabricate commercial activity. When lenders moved to recover their capital, Builder.ai ran out of money, could not pay its cloud infrastructure bills, and entered insolvency proceedings.

Debunking the Myth of 700 Engineers Faking AI

The viral story alleging that Builder.ai employed 700 engineers who secretly pretended to be an AI assistant gained widespread traction online, but documented reporting has proven the rumor false. An extensive investigation published by The Pragmatic Engineer, written by technology analyst Gergely Orosz, established that the automated code generation system was real and did not rely on hidden humans pretending to be software. Reporting by the Financial Times traced the origin of the 700 engineers rumor to an unverified post on social media written by a self-described cryptocurrency enthusiast who possessed no journalistic credentials or direct sourcing inside Builder.ai.

The viral rumor conflated two entirely separate divisions within Builder.ai. Builder.ai operated a real engineering team that built software tools, while separately maintaining contracts with hundreds of external workers who delivered custom design work for paying clients. Observers on social media merged these two groups into a single sensational claim, asserting that the contractors were sitting in back rooms typing out code to fool customers who thought they were chatting with an automated bot.

While companies in the tech sector have occasionally used human workers to preview or supplement automated features, Builder.ai did not use human engineers to impersonate its core software assistant. The false rumor obscured the genuine wrongdoing inside Builder.ai, which involved corporate accounting, misleading governance, and false sales metrics rather than hidden workers puppeteering an interface.

How Natasha AI Worked

Natasha was designed as an AI-powered project manager and software builder that created functional applications using pre-existing code modules and modern algorithms. The software did not require a vast, hidden army of coders to produce text or basic application templates. Instead, the real technical architecture was built and maintained by a dedicated engineering group inside Builder.ai.

Reporting indicates that the core technical team responsible for Natasha consisted of roughly 15 to 30 engineers at peak operational capacity. This engineering team constructed Natasha using standard modern software infrastructure:

• A Python orchestrator that coordinated commands and managed backend workflows.
• A Ruby on Rails backend to handle system logic, account management, and database records.
• A React frontend that provided the customer-facing user interface.
• Commercial Large Language Models (LLMs), including GPT models from OpenAI and Claude models from Anthropic, to generate application code snippets and interpret customer specifications.

Alongside this small software team, Builder.ai employed hundreds of outsourced contractors to build customer applications. Reported contractor figures ranged from 500 to 1,000 workers across several specialized outsourcing firms, including Globant and TatvaSoft. These developers were based in countries including India, Vietnam, Romania, Ukraine, and Poland.

These contract workers were not pretending to be Natasha. Instead, these engineers used custom Integrated Development Environment (IDE) tools provided by Builder.ai to finish, customize, and deploy software applications for business clients. Builder.ai openly advertised a hybrid delivery model where automated templates handled repetitive tasks while human software developers handled final client customizations. The technical operation functioned as designed, but the financial model behind it was deeply distorted.

The Financial Fraud and Round-Tripping Allegations

The core of the Builder.ai scandal was an aggressive revenue inflation scheme that deceived investors, board members, and lenders. As reported by eWeek, Builder.ai restated its revenue downward by hundreds of millions of dollars after internal accounting records were scrutinized. The company had claimed $220 million in revenue for 2024, but financial auditors later slashed that number to between $50 million and $55 million. That adjustment represented an inflation of approximately 300 percent above the actual business revenue.

Auditors uncovered similar misrepresentations in earlier financial reporting. For 2023, Builder.ai had originally reported $180 million in annual revenue. Subsequent reviews determined that the actual revenue for that year was only roughly $45 million. By claiming massive revenue totals, Builder.ai was able to justify its $1.5 billion valuation and secure substantial venture financing rounds.

Much of this artificial revenue was generated through alleged round-tripping transactions between 2021 and 2024. In a round-tripping scheme, a business sends money to an external partner through consulting agreements, vendor contracts, or reciprocal purchases, and that partner routes the money back as purported customer revenue. Builder.ai conducted these circular transactions with VerSe Innovation, a technology company based in India. These transactions allowed Builder.ai to book artificial software revenue without generating genuine customer demand.

Builder.ai's Bankruptcy and Collapse

The financial deception triggered a rapid liquidity crisis once financial partners discovered the accounting discrepancies. Venture lender Viola Credit took immediate action to protect its capital, seizing approximately $37 million directly from Builder.ai bank accounts after the fraud allegations came to light. The sudden loss of cash left Builder.ai unable to meet its immediate payroll obligations or pay its corporate infrastructure bills.

Builder.ai also accumulated massive liabilities with cloud service providers to keep its systems operational. At the time of its collapse, Builder.ai reportedly owed approximately $85 million to Amazon for web hosting services and roughly $30 million to Microsoft for cloud infrastructure. These hosting debts overwhelmed the remaining assets of Builder.ai, leaving little room for a restructuring agreement.

Executive leadership changed rapidly as the company unraveled. Founder and long-time Chief Executive Officer (CEO) Sachin Dev Duggal had previously served as the public face of Builder.ai, even winning the World Entrepreneur of the Year award from Ernst & Young (EY) in 2024. In early 2025, Manpreet Ratia took over as CEO as the company attempted to manage the growing crisis. The leadership change could not save Builder.ai from insolvency.

Builder.ai officially filed for bankruptcy and insolvency proceedings in May 2025. Nearly 1,000 employees were laid off as operations ceased, and published reports indicated that several workers went unpaid during the final weeks of operation. As of this writing, legal and regulatory investigations into the accounting practices of Builder.ai remain ongoing, with no specific court verdicts, criminal convictions, or formal civil judgments officially finalized against company executives.

Lessons From the Builder.ai Scandal for the Broader Tech Industry

The collapse of Builder.ai provides a cautionary lesson about the risks of automated software hype and speculative investment cycles. Venture firms were eager to fund any organization that claimed proprietary breakthroughs in automated programming, often overlooking basic accounting discrepancies and aggressive revenue growth claims. The failure of Builder.ai highlights how easily genuine technical development can be weaponized to distract from severe operational deficits.

When organizations market automated tools, the public and investors must separate genuine technical capabilities from corporate marketing narratives. Builder.ai possessed a functioning engineering team and used real language models, but its underlying business fundamentals were fabricated. The sudden liquidation of Builder.ai left hundreds of employees without work and suppliers with millions of dollars in unpaid bills, echoing patterns documented in our analysis of widespread AI layoffs across the tech sector.

This case also demonstrates the extreme cloud computing costs associated with running large-scale software systems. When software companies incur tens of millions of dollars in infrastructure debts to hyperscale providers, financial sustainability becomes impossible without real customer revenue. This structural spending pressure mirrors the financial fragility documented in our review of the AI data center bubble, where massive capital expenditures frequently fail to generate matching commercial returns.

The public skepticism that followed Builder.ai is part of a broader consumer and investor movement demanding accountability from technology vendors. Readers interested in how communities and workers challenge automated software claims can read our guides on the growing AI backlash and how citizens are fighting back against corporate misconduct. To track other companies facing similar scrutiny over AI claims, see Ban the Bots' guide to the AI data center bubble, or read our tracker on AI layoffs tied to automation claims that did not hold up.