No-Code · Low-Code
No-code / Low-code
What is no-code?
- Assembled on screen with little to no coding
- Build apps and automations fast
- Non-developers can build
The biggest change is the gate known as the 'IT request.' Moving a process that ran on a few spreadsheets into a system used to mean writing a proposal, securing a budget, and waiting months in the development queue. With this approach, a large share of those cases finish inside the business unit. For small-scale work with 30 users or fewer and five or six screens, there is no longer any reason to join the development queue at all. The role of IT also shifts from 'the team that builds it for you' to 'the team that opens up the tools and governs them.'
The line between no-code and low-code is blurry in practice. A no-code tool starts to look like low-code the moment it allows a formula or a line of script, and low-code platforms build most screens by drag and drop. In practice, it is more useful to split them by whether the builder is a business user or a developer. Tools generally fall into four groups: business app builders, workflow automation, web and form builders, and RPA. Pricing is often a monthly fee per user, so costs rise in steps as more people start using them.
Deciding in advance when to move to traditional development reduces incidents. When concurrent users climb into the hundreds, accumulated data passes several hundred thousand records, three or more external systems are connected, or overnight batches and settlement logic come in, that is the point to consider migrating. Conversely, data the company is held accountable for if something goes wrong, such as payroll, performance evaluations, and customer personal information, should get a security review from day one, regardless of scale.
The most common misconception is “no coding means no maintenance.” When the employee who built an app changes departments or leaves, it becomes a black box nobody can open, and changing a single approval line can bring work to a halt. Data piled up in a personal-account spreadsheet can also vanish when accounts are cleaned up, and this really happens. That is why a rule to register the builder, data location, and billing cap in a registry should be set when the very first app is built. Managing just these three things prevents most shadow IT.
Seolyeong ParkGenerative AI and AX training expert with 17 years of hands-on experience and 200+ lectures, who gets non-specialists using AI right away
John KimJohn Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”Emerging in the 2010s as a way to build business apps without coding (the term low-code dates to around 2014), it is now spreading fast as it combines with AI.
Consider a hypothetical case: Company A, an auto parts manufacturer with 320 employees and annual revenue of about KRW 90 billion (≈ US$67,335,000). Foremen took equipment maintenance requests over KakaoTalk and Excel, so 12% of 400 monthly requests were never logged, and average response time was 9 hours. With only two people on the IT team, a formal development request meant an eight-month wait before work could even start.
- Kim, a manager on the production management team, built an equipment maintenance request form with a no-code builder in three days. It started with a thought: "If I wait for the dev team, this won’t get done before year-end."
- The IT lead set three conditions: log in with company accounts only, no personal-data fields, and data stored in the company’s shared database, not in personal accounts. “Build what you like, but we get to see the data.”
- When a request comes in, a notification goes to the responsible foreman’s phone. If it is not handled within four hours, it automatically escalates to the maintenance team lead. They ran a two-week pilot on three lines.
- Within three months, users grew to 180, and per-user billing of KRW 12,000 (≈ US$9) a month climbed to KRW 2.16 million (≈ US$1,620) a month. They moved the 120 view-only users to free viewer permissions and cut the monthly cost to about KRW 900,000 (≈ US$675).
- Six months later, missed requests had fallen from 12% to 1%, and average response time from 9 hours to 3.5 hours. Of the 40 simple requests per month that used to go to IT, 28 were now built by business users themselves, cutting an eight-month wait down to three weeks.
- Quick prototypes and internal tools
- When non-developers build it themselves
- When standard features are enough
- Complex, high-performance, large-scale systems
- When you need fine-grained customization
- Core systems where platform lock-in is a risk