The Delta logo
September 7, 2022

The 7 Low-Code Tools Every Founder Needs To Know

Image of author
Written by
Jono Hart
Venture Manager
Woman sits at laptop smilling
Image of author
Written by
Jono Hart
Venture Manager
Book a call
LinkedIn logoTwitter logoFacebook logo

The seismic shift to low- and no-code

Low-code has been around for longer than most think. In fact, as early as 2011, research firms and advocates of the agile movement expressed a need for ‘test-and-learn’ tools that would allow developers to spin up products extremely quickly and put them in front of customers, reusing common components from other projects.

A year later, Bubble launched, allowing people to build web applications through ‘visual programming’ i.e. dragging and dropping elements to create logic, workflows, and UI components, instead of writing any code. They were shortly followed by Webflow in 2013, which allowed people to create beautiful websites with visual programming as well.

In 2014 the term ‘low-code’ was officially coined, in 2018 the market hit a valuation of $6 billion, and as of 2024 this market is expected to be worth $52 billion (that’s an annual growth rate of 42.32%).

But what is the hype around these applications? What is the exact distinction between no-code and low-code? And what are the limits of low-code, at least at the moment?

The hype: It used to be that startups needed a technical co-founder and a tech team very early on, to be able to build their MVP. Airbnb took at least 10 months to get from ideation to the first version of the website, and in those 10 months the three co-founders spent all their savings and thousands of hours to get a basic platform up - they also sold boxes of cereal to make a living.

It was several more years before they had features like user profiles, online payments, a smart listing algorithm, booking management, reviews, an escrow system, and a mobile app.

With low-code, you can build Airbnb, with most of those features, in a day.

This is because marketplace platforms are well understood, and most low-code platforms have templates for a marketplace app. You just need to find an unmet need where supply can be matched with demand over an online marketplace, and then you can repurpose these low-code templates to your use-case, and within hours you can have an MVP up and running from which you can test, gain traction, and raise for your venture.

And it works: companies like Bloom Tech (formerly Lambda School), Makerpad, and Plato have raised dozens of millions of dollars in venture capital for products they initially built with low- or no-code platforms. Some have gone on to develop their own custom software, and some have persisted with their low-code stack.

Ultimately, you can go from pre-seed funding all the way to Series A with a good idea, great execution, and a low-code product. And in the future, perhaps some unicorns-turned-public-companies will still be running on low-code.

The terminology: By now you’ve noticed that I’ve used the terms no-code and low-code fairly interchangeably, but there is a difference:

  1. No-Code: Tools that allow you to build a product or workflow entirely through visual programming/drag-and-drop e.g. Wix, Bubble, Webflow.

  1. Low-Code: Tools that combine visual programming with predefined blocks of editable code, or allow for entire sections of custom code to be written that integrate fairly seamlessly with the rest of what has been built e.g. Retool.

Platforms that require some form of coding to get off the ground are quite rare (like Retool). Instead, most platforms allow quite a lot to be achieved without code (like Bubble), but then have opportunities for developers to write custom code and go deeper.

While a certain tool might be used in a no-code fashion, if you are binding several tools together to make your product, some of which are low-code, your entire ‘stack’ can be seen as low-code.

The limitations: The flexibility enabled by most low-code platforms only goes so far.

Foremost, many predominantly no-code tools don’t have templates for every common element (requiring custom code as a result), and then hide custom-code/low-code functionality behind expensive paywalls.

Secondly, you can’t fill out every gap with custom code. Many of the rules behind where custom code can exist have to be defined by the low-code company, and because it’s impossible for a company to foresee every use-case of their product, there’s a chance you’ll be unable to implement certain functionality. If this is the functionality that the next version of your product needs, you’ll be forced to try alternative low-code platforms, or go the (expensive) custom software route.

Thirdly, these tools often integrate with a lot of other popular software that you may want to integrate into your product, but sometimes the platform you’ve chosen might not have considered certain integrations yet, or might not have partnered with the companies providing the software you want to link up to.

Fourthly, whatever you have built is often hosted on servers by the low-code company, which can affect scalability when these companies are trying to service hundreds of other products that have been built off their infrastructure. If you are on a free tier you might also get the worst service. These are fairly young companies who are experiencing explosive growth, so there’s also a risk of outages which could shut down your product for some time. Is the product you have in mind something that can afford an outage?

Finally, there are some tech products whose baseline level of functionality can’t even be created with low-code. While a lot of well-understood types of tech products can now be rapidly reproduced with low-code platforms (e.g. marketplaces, eCommerce stores, internal tools, resource directories, landing pages), a lot of problems that tech teams are solving today won’t have templates for some years to come.

So, if your idea is not just a new spin on an existing technology (e.g. Airbnb for minimalists, Fiverr for handymen), and rather something radically new that very few have solved yet, then you may need a technical co-founder, or to hire a technical team, so that you can create custom software.

Despite the above, low-code tools are still wildly useful, especially if you pick the right ones.

Our favourite low- and no-code tools

Given that it’s such an emergent space, with the number of low-code startups/platforms probably numbering in the hundreds by now, choosing the one to start with is no easy feat.

Additionally, with the amount of disruption in this space, you might fear that any tool you choose could become outdated in a matter of months.

Fortunately, we’ve been curating a list of go-tos that seem to be standing the test of time. These tools range between 3 and 12 years old, are all venture-backed, and have fervent user-communities.

Most importantly, they stay relevant by continually iterating on their product, staying agile and following the principles of the movement that birthed them.

They are:

  1. Webflow: An amazing tool for building stunning websites, with a great collection of templates to start off from (Hint: the page you’re reading right now was built in Webflow). Best for landing pages, eCommerce, and sites that focus on content, rather than functionality. They’ll soon be adding workflows that will make the sites more interactive and help bridge the gap between where they are now and where application-focused tools like Bubble are.
  2. Retool: The most powerful software we’ve come across for rapidly spinning up internal tools or proof-of-concepts for new business ideas (our entire internal operating system at The Delta runs on Retool). However, its focus has been on functionality over form, which is why it’s marketed as a tool to build internal tools, rather than something you would want to put in front of a customer - though that doesn’t mean you can’t build your MVP with it, just make sure your user is tolerant of less-aesthetic interfaces.
  3. Airtable: A great product for building a low-code backend/database. At first glance, Airtable looks like Excel/Google Sheets on steroids (which is a good enough selling-point), but that’s barely scratching the surface. It’s an integration-packed tool perfect for collecting and storing data, project management, and it can even be used as a CRM. With its new Interface Designer feature, you can build user-facing apps with Airtable as well.
  4. Typeform: A form-builder that is both highly aesthetic (supporting images, videos, and bold colour palettes) and highly functional (supporting branching logic, many question types, and loads of upon-submission integrations). Typeform is ideal for surveys and quizzes, but can also be used for lead-capture forms and user sign-ups, making it a good alternative to building a custom sign-up flow in your early product. Typeform’s spinoff product VideoAsk ramps up the level of interactivity possible in a form, so they form a good pair.
  5. Zapier: The automation platform to rule them all. Zapier smartly positions itself at the centre of all the tools mentioned, as well as many more. It automates the flow of data within tools and between tools with custom ‘Zaps’ that users can set up: when X happens, do Y e.g. when a Typeform is completed, send data to Airtable. With its thousands of integrations and simple, transparent pricing, it becomes the obvious choice for glueing together your low-code stack and saving a heap of time.
  6. Softr: A no-code, visual programming tool that allows you to easily spin up fairly interactive frontend applications with Airtable or Google Sheets as the backend - it also has a great marketplace of off-the-shelf platforms that you can customise to your use-case. The functionality is a bit more powerful than Airtable’s Interfaces feature, making Softr and Airtable a powerful combination for low-code builders, especially those looking to build an MVP.
  7. Bubble: Somewhere between the visual fidelity of Webflow and the functionality of Retool, Bubble is the oldest and most dominant low-code platform on the market, and (with good reason) probably the best tool for building customer-facing web applications. It has had years to sort out the kinks of a low-code ecosystem, it is very well-supported, and it has a great community of low-code builders. It has a higher learning curve than something like Softr, but if you want to build things along a similar vein to Airbnb, Fiverr, and Uber, Bubble is your best bet.

While these are the ones we most commonly use, there is an ocean of players out there. Even Big Tech has entered the space, with Google's AppSheet and Microsoft’s Power Apps - and every day you can monitor directories like Product Hunt to see the new tools coming out.

But now that you have an idea of the low-code landscape, let’s discuss the possibilities of low-code when it comes to experimenting.

Low-code case studies

You should think of building a low-code product as a form of experimentation - perhaps, even, the final validation experiment you should run before you know your business is solid.

If you read my previous post on five of the products we validated through experimentation, you might recall that some of the experiments included simple landing pages and manual Wizard of Oz or Concierge approaches. Some of these products were invalidated early on, way before anything needed to be built.

However, all of them could have been built in low-code, had we decided to go to the next level of effort and build something with the intention of getting paying customers (the final and ultimate form of validation).

Allow me to illustrate how:

1. Market research platform

We wanted to build a survey platform that allows businesses to set up a survey and then have it distributed, via WhatsApp, to an audience of low-income customers - to conduct market research on them.

How could you build this?

  • Clients list their survey requirements using a Typeform (or Airtable form).
  • Form submissions are sent via a Zap to an Airtable.
  • A team member manually creates a survey in Landbot (a great low-code tool for building chatbots) and then distributes it to the WhatsApp audience, also via Landbot.
  • Survey responses are exported to CSV, uploaded into Airtable, and a dashboard is created for the client using the Airtable Interface designer.
  • Being even scrappier, you could even get clients to list their survey requirements via a Landbot WhatsApp bot, then get a team member to look at the CSV output and create the participant-facing Landbot WhatsApp survey, and then send the results CSV back to the client on WhatsApp - running the entire business with WhatsApp and Landbot!
  • Down the line, consider allowing people to create surveys in Retool or Bubble (depending on how polished it should look), and then sending survey results back to them in a Retool/Bubble dashboard.

2. Local discounts application

We got quite excited by the thought of an application that would let people ‘recharge’ after a long week by giving them large discounts to a bunch of weekend-only, local experiences.

How could you build this?

  • Add all the experiences (details, images, discount percentages) into an Airtable backend.
  • Connect this backend to a Softr frontend using a marketplace template (e.g. this one).
  • Allow new experience-providers to dynamically add new experiences by completing an Airtable form which will automatically reflect on the frontend.
  • Make it free and without sign-up for users to view the directory of experiences, or use Softr’s functionality to have them sign-up and possibly pay to see the experiences.
  • Whenever a user needs to be notified of something (they’ve been inactive, there’s a special discount on, there’s a weekly update), combine an Airtable script with Google Apps Script to send them a personalised email with their data in the Airtable backend.

3. Gamified donations platform

We worked on a gamified-donations platform that would reward people for donating to worthy causes, by entering them into prize draws.

How could you build this?

  • Ad traffic (e.g. Facebook ads) can send users to a Webflow landing page which lists prizes and charities that are hosted in the Webflow CMS.
  • Users make their selections via an embedded form and then go to checkout, using one of Webflow’s integrated solutions like Stripe or Shopify.
  • Upon successful payment, users get a nice email about the donation they’ve made, which is possible with Webflow.
  • User details can be extracted from the payments provider, stored in an Airtable, and an Airtable script can be used to randomly pick winners.
  • Alternatively, the Webflow CMS and form solution can be ditched for Webflow eCommerce where picking a prize/charity can be treated like a product purchase.

4. Fine-dining delivery service

We envisioned a service that would allow people to have multiple-course, fine-dining meals delivered to their doorstep in time for dinner, allowing customers to enjoy a fine-dining experience from home during the pandemic, while supporting local fine-dining chefs.

How could you build this?

  • Create a site with Webflow and add all the fine-dining menus as products via Webflow’s eCommerce functionality.
  • Enable payments with Stripe or Shopify.
  • Orders are sent via a Zap to an Airtable database with a uniquely generated order code.
  • An Airtable script combined with Google Apps Script emails all new orders to the restaurants and delivery partners, as well as order confirmations to the customers.
  • It’s then on the restaurant and delivery partner to fulfil the order.
  • The delivery partner could mark an order as complete on an Airtable interface, which then sends the customer a satisfaction survey (Airtable form) to complete.
  • New restaurants could upload their menus via an Airtable form which then sends the data to the Webflow CMS via a Zap, so that it instantly appears on the list of products.

5. Personalised nutrition product

We designed a personalised nutrition service that would allow young customers to take a short quiz, get a recommended blend of ingredients suited to their unique circumstances, and then order a custom supplement powder containing all those ingredients, to their doorstep; with the option to resupply in a month’s time.

How could you build this?

  • The quiz can be created in Typeform.
  • Results can be extracted to CSV and used to manually compute a recommendation.
  • Sharing results, collecting payments, and arranging for delivery from the supplier can be done via email.
  • This can all be juiced up by using Bubble to build the quiz, support user accounts, take payments, and send delivery instructions to the supplier.
  • Instead of manually calculating recommendations, a Zap could send them to a Google Sheet where a Solver computes the optimal blend to the customer.
  • A Typeform can still be used instead of a custom form made in Bubble, though there would be more control over the look and feel of the form if made in Bubble.
  • If look and feel is less important, and you would rather calculate the recommended blend in a rules-based way rather than with an optimiser, the whole thing could be done in Retool too.

Now you know a whole assortment of our favourite low-code tools, and how to creatively stitch them together to build some fascinating products.

This was the last instalment in my series on experimentation. In it, we’ve covered:

When you truly understand experimentation, it makes you realise that a business you thought would take months or years to build, can be approximated in a matter of days or weeks through the wide array of experiments available to founders. Some are quick and cheap, and some a bit more hefty, but you can always figure out a sequence of experiments that bridges the gap between what is manageable today, and the polished product you want to have in the market months from now.

The moral of the story is that you can start today, and I hope my guide has convinced you of the merits of experimentation, while also equipping you with both the theory and practical tools to get started.

Remember, it can save your business, or it can kill your business - and sometimes that’s a good thing! 

Even though these tools are powerful, effective, and accessible, they’re not always a walk-in-the-park to use, especially when it comes to strategically binding several of them together to build a great product.

At The Delta we’ve validated hundreds of ideas for early-stage entrepreneurs and unicorns alike, in many instances using low-code. It’s what has helped us curate a venture portfolio worth more than €5.3bn.

If you’re a founder, startup, or scaleup with a great idea for your next business, feature, or product, and are unsure about how you can get running with it today, talk to us and get a free consultation with one of our top strategists.

Validated your idea already and ready to build something? Reached the limits of low-code and need a partner to help you embark on the custom software development route? Explore how we take ideas through design, development, and then eventually launch them to the market and scale them.

Download our free ebook

How to Validate Your Startup in 2022

The definitive guide for founders to build a lean startup.

Get the best of our insights, and more.

Thanks for signing up!

Oops! Something went wrong while submitting the form.

Relevant insights

May 9, 2023
From our experts: Low-code vs. Custom build
Read more
April 3, 2023
Founder Foundations: The Pillars of a Strong Venture
Read more
Product strategy
October 6, 2022
Why Founders Should Strive For ‘Market-Product Fit’ Instead of ‘Product-Market Fit’
Read more