A customer portal, an internal tool for order planning or an automation between CRM and accounting: in the past, this needed a development team and several months. With no-code and low-code, companies now build solutions like these with visual tools, often within a few weeks. This article explains what the terms mean, what you can build with them, where the limits are and how a no-code project works in an SME.
What is no-code and what is low-code?
No-code means developing software without programming. You build applications, databases or automations in a visual interface by configuring and connecting ready-made building blocks. Examples include monday.com for workflows, Make for automations and Webflow for websites.
Low-code works on the same principle but allows your own code in certain places, for example for a special calculation or an interface that isn't available as a ready-made building block. This makes low-code more flexible but requires some technical understanding.
In practice, the line is blurred. Many tools such as Xano or WeWeb are no-code at their core but allow code where it's needed.
What you can build with no-code
No-code is suitable for far more than simple websites. These are the applications SMEs build most often today:
- Workflows and internal tools: project planning, order management, CRM or HR processes, for example with monday.com or Airtable
- Automations between systems: transferring data between CRM, ERP, accounting and project management, with Make or n8n
- Customer portals and web apps: portals where customers submit requests or view data, with WeWeb as the interface and Xano as the backend, or with Bubble
- Websites and landing pages: with Webflow, including a CMS for blogs and multilingual content
You'll find an overview of the most important tools and an introduction to automation in these articles:
No-code, low-code, vibe coding or traditional development?
Since 2025, AI app builders such as Lovable have offered a fourth route: you describe what you need in a chat and the AI generates the code. The four approaches differ mainly in who builds the solution and who can maintain it later.
| No-code | Low-code | Vibe coding | Traditional development | |
|---|---|---|---|---|
| How the solution is built | Configuring building blocks visually | Building blocks plus your own code in places | Description in a chat, AI generates the code | Programming from scratch |
| Knowledge needed | Process understanding, no programming | Basics of code and data models | Clear requirements; code understanding for operation | Software development |
| Speed | Days to weeks | Weeks | Hours to days for a prototype | Months |
| Day-to-day maintenance | By trained business users | By business users with technical support | By someone who understands the code | By the development team |
| Typical tools | monday.com, Make, Webflow, Airtable | Xano, WeWeb, n8n, Retool | Lovable | Custom software |
We explain the difference between no-code and vibe coding and how AI and no-code work together in these articles:
What no-code actually does for companies
The biggest difference from traditional development is speed. Because many building blocks are ready-made, a first usable version is available within days or weeks. The team can test it with real data before larger investments are made.
On top of that, the solution stays closer to the business teams. Whoever knows a process best can adjust it themselves in a no-code tool: a new status stage, an extra field, a changed notification. This doesn't need an IT ticket or any waiting time.
For start-ups and small teams in particular, no-code is often the only realistic way to their own software. A founding team without developers can build a customer portal or an internal tool, test the idea on the market and decide later whether larger development is worthwhile.
Three typical time drains that no-code solves
Manual reporting from several systems
Month-end is coming up. Someone exports invoice data from the ERP, marks open deals in the CRM and copies everything into an Excel list. Just before sending, a project is missing because the invoice only came in yesterday. With an automation in Make and a dashboard in monday.com, the figures come together automatically and are always up to date.
Cognito Treuhand GmbH has automated its invoicing with Make and monday.com. Month-end closing now takes minutes instead of a day.
.png)
Systems that don't talk to each other
The project status is in an Excel list, the discussion in a Teams channel, the customer data in the CRM. Anyone who wants to know the current status searches three tools and still doesn't find everything. With a central platform and integrations between systems, there's a single, up-to-date data source.
For the market research company Kantar Verian, Blinno automatically combined data from SAP Sales Cloud and HubSpot. The result is consistent customer data and measurable campaigns.
Unclear responsibilities and resources
Sales has won three new deals, but the project team doesn't know yet. According to Excel, a colleague is available; according to Slack, she's fully booked. With a CRM that automatically hands deals over to project delivery and a resource view across all projects, everyone can see who is working on what.
For the Zurich media company Ron Orp, Blinno implemented a CRM and resource solution in monday.com that brings together communication, task allocation and capacity planning.
.svg)