AI Behavior Index
☰
Home/By Use Case/Non-Developer Coding with AI: Citizen Developers
By Use Case

Non-Developer Coding with AI: Citizen Developers

The biggest shift in who writes code isn’t happening among developers — it’s happening among everyone else. A majority of people using AI “vibe-coding” tools now identify as non-developers: marketers, operations managers, salespeople, founders, and designers building software for problems they understand better than any engineer. Forrester counts 16.2 million active citizen developers worldwide, and Gartner expects them to outnumber professional engineers four-to-one by 2028. The economics explain the rush: AI has dropped the cost of building a functional SaaS product from roughly $200,000 to about $5,000, and compressed timelines from months to weeks. But democratization has a sharp edge. AI-generated code carries security vulnerabilities at high rates, the overwhelming majority of vibe-coded apps contain traceable flaws, and real incidents — exposed user data, a deleted production database — show what happens when non-experts ship ungoverned code. This page maps who’s coding now, which roles, the new economics, and the governance gap underneath the boom. Several role-level figures draw on adjacent low-code/no-code and vibe-coding data — labeled where directional.

4 visualizations 5 sources Last updated June 2026 Free to embed
Loading chart...
Source:  Hostinger Vibe Coding Statistics 2026; Forrester. Most vibe-coding users identify as non-developers.
Loading chart...
Chart 1 · Who’s coding now

Non-developers are most vibe-coding users

Most AI vibe-coding users are non-developers

Loading chart...
Source: Hostinger Vibe Coding Statistics 2026: 63% of vibe-coding users identify as non-developers — product managers, marketers, founders, and designers. Forrester estimates 16.2 million active citizen developers worldwide, and Gartner predicts they’ll outnumber professional engineers 4:1 by 2028. Coding is no longer gated by a CS degree.
Chart 2 · Which roles

Common citizen-developer roles

Who the citizen developers are (directional)

Loading chart...
Source: Forrester / Gartner (via Searchlab) 2026: among citizen developers, the most common roles are Operations Managers (24%), Marketing Managers (19%), and Sales Managers (16%); 41% of enterprise employees are now “business technologists,” and 68% of marketers use no-code tools daily. Role mix is for low-code/no-code builders broadly — directional for pure AI coding.
Chart 3 · The new economics

AI collapsed the cost of building software

AI collapsed the cost & time to build software

Loading chart...
Source: Keyhole / Y Combinator data 2026: the cost of building a functional SaaS product dropped from ~$200,000 to ~$5,000, and timelines from ~6 months to ~6 weeks. 25% of Y Combinator’s Winter 2025 startups have codebases that are 95%+ AI-generated; app builders like Lovable hit $100M ARR within months. The barrier to building software has nearly vanished.
Chart 4 · The governance gap

Democratization meets a security problem

The governance gap: democratization meets security

Loading chart...
Source: Security research / Caspio 2026: the catch — ~45% of AI-generated code contains vulnerabilities, and 91.5% of vibe-coded apps have AI-traceable security flaws. A Lovable audit found 170 of 1,645 apps exposed user data; in one incident, Replit’s AI agent deleted a production database. 61% of IT leaders cite ungoverned AI use as their top security barrier. Democratization without governance is risky.

About this data

This page examines non-developer (citizen-developer) coding with AI, drawing on Hostinger’s 2026 vibe-coding statistics, Forrester and Gartner citizen-developer research, Keyhole Software’s vibe-coding analysis, Y Combinator cohort data, and security research compiled by Caspio and others.

The AI Behavior Index is the research arm of OneChat AI, an integrated multi-model AI platform. We compile and analyze data from primary research sources to make AI adoption and market trends more accessible to journalists, researchers, and decision-makers.

A note on adjacent data and labeling: there’s no single clean survey of “marketing/ops/sales people writing code with AI,” so we anchor on the closest robust data — vibe-coding user surveys (63% non-developers) and low-code/no-code citizen-developer research (role mix, 16.2M figure). The role-share chart (Operations 24%, Marketing 19%, Sales 16%) is from low-code/no-code research and is directional for pure AI-coding specifically; we label it as such rather than implying a precise AI-only measurement.

Methodology notes: the 63% non-developer figure is from vibe-coding user data; the 16.2M and 4:1 figures are Forrester/Gartner estimates. Role percentages describe low-code/no-code citizen developers broadly — a reasonable proxy for AI-assisted non-developer coding, but not a direct measurement of it, so we mark them directional. Economic figures (build cost, timelines) are widely-cited industry estimates. The security figures (45% vulnerable, 91.5% with flaws, the Lovable/Replit incidents) are from security research and are the essential counterweight to the democratization story.

Sources used on this page:

Corrections or suggestions: research@aibehaviorindex.org

Related topics in By Use Case

By Use Case

AI Coding Productivity Studies

Updated recently
By Use Case

AI for Academic and Research Writing

Updated recently
By Use Case

AI for Blog Posts and Article Writing

Updated recently
By Use Case

AI for Code Generation (Greenfield)

Updated recently
By Use Case

AI for Code Review and Debugging

Updated recently
By Use Case

AI for Coding: Adoption Overview

Updated recently
For Journalists & Researchers

Use this data in your work.

Every statistic, chart, and graphic in this index is free to use and cite, with full source attribution. Can’t easily find what you need? Use our search bar to search by keyword, topic, or category.

✉️
Talk to our research team
Need a specific cut of data, an interview, or a quote? Email us — we typically respond within one business day.
research@aibehaviorindex.org →

How the data works

Every statistic shown is sourced from a publicly available study, survey, or report. We aggregate, organize, and contextualize this data — but the underlying research is conducted by the cited sources. Click any source link to access the original methodology. If you run into any issues or have a study to suggest, contact us at research@aibehaviorindex.org.