Citizen Developer

A citizen developer is someone without a formal software engineering background — typically working in operations, marketing, sales, HR, or finance — who builds functional applications, automations, or internal tools using no-code or low-code platforms, rather than by writing traditional code. The term was popularized by Gartner in the 2010s to describe a structural shift: as no-code/low-code tools matured, the population capable of "building software" expanded well beyond people with computer science degrees or professional developer titles. Why it matters for SaaS/AI builders: citizen developers are both a major customer segment for no-code platforms (Bubble, Airtable, Zapier all market heavily to this audience) and an organizational phenomenon IT departments increasingly have to manage — the rise of "shadow IT," where business teams build and depend on tools outside formal engineering oversight, creates real value (faster iteration, domain experts building exactly what they need without translating requirements to a dev team) but also real risk (unmaintained automations breaking silently, sensitive data flowing through unvetted third-party tools, no code review or security audit process). How it works in practice: citizen development typically happens inside a "guardrails" model at mature companies — IT or platform teams pre-approve a set of sanctioned no-code/low-code tools (e.g., "you may build internal tools in Retool and automations in Make, but connecting to the production database requires IT approval"), provide reusable components or templates, and retain oversight of anything touching sensitive data or customer-facing systems, while giving citizen developers free rein within that sandbox. Worked example — a marketing ops citizen developer, with no coding background, builds an event-registration-to-CRM pipeline: they use Typeform (form builder) to collect event signups, connect it via Zapier (trigger: new Typeform response) to HubSpot (action: create/update contact with a "Webinar Registrant" tag), and add a Filter step so that responses from company domains already in the CRM as "Enterprise" tier route to a different action (notify the AE via Slack) than free-tier signups (add to a nurture email sequence). This entire pipeline — genuinely useful production infrastructure — was built without writing a single line of code or filing an engineering ticket, exemplifying both the promise (speed, domain-expert ownership) and the governance question (who reviews this before it touches the CRM of record) that citizen development raises. Some organizations formalize this with a "Center of Excellence" model — a small internal team of experienced no-code/low-code builders who publish standards, review higher-risk automations, and act as a resource citizen developers can consult, rather than either blocking citizen development outright or leaving it entirely unmanaged.