Who is a citizen developer?
A citizen developer is a person outside the IT department who builds software for their own team, usually with no-code or low-code tools that IT has approved. Typical citizen developers are accounts payable specialists, quality engineers, and operations analysts who know a process in detail. In AI work, they configure assistants, write agent instructions, and connect models to forms, spreadsheets, and business systems through prebuilt connectors. Small automations that would wait months in an engineering queue can be running within days.
Citizen developers in practice
A quality engineer at a plastics molder builds an agent on the company’s approved platform. It reads each supplier certificate of analysis as it arrives, compares the values with the purchase specification, and flags out-of-specification lots for the receiving inspector. IT supplied the connector to the ERP system and a service account with read-only access. The engineer wrote the instructions and tested them against the previous quarter’s certificates before switching the agent on.
What to watch for
- Run citizen-built agents under service identities with least privilege instead of the builder’s personal login.
- Require an approval step and an audit log for any automation that writes to a system of record.
- Give every automation a named owner and a backup, because a tool only its builder understands becomes a risk when that person leaves.
- Building outside the approved platform is shadow AI, so make the sanctioned path the easier one.