Stop 08 · Systems & Technical UnderstandingTopics · 9/9

No-Code / Low-Code Tools Overview

Part of the Business Analyst Roadmap

In short

Some problems don't need a dev team and three sprints. A form, a sheet and an automation can fix a messy manual process this afternoon. Knowing these tools makes you dangerous, in a good way.

Tools that let a BA prototype, automate, or even build small internal solutions without waiting on engineering time — increasingly relevant as these platforms mature and expand what's possible without code.

The purple blob holds up a small spice packet in a kitchen, with a stone grinder and spice bowls on the counter.

Think of it like this

Ready-made masala packets

Grinding your own garam masala gives perfect control, but takes time and skill. A ready-made packet gets dinner on the table in 20 minutes. Great for most nights. For a special family recipe, though, you may still need to grind your own.

Watch it happen

A leave-request process, no code needed

Form
Sheet
Automation
Notify

1/4An employee fills a Google Form or Microsoft Form: dates, type of leave, reason.

The big ideas

What you need to know

No-code vs low-code

No-code tools are click and configure. Low-code adds small bits of formulas or scripts for more control.

Common types

Forms, databases like Airtable, app builders like Power Apps or AppSheet, automation like Zapier, Make or Power Automate.

Great for prototypes

A working mock-up built in a day often clarifies requirements better than any document.

Know the limits

Check data security, user limits, costs as usage grows, and who maintains it when you leave.

Save yourself the pain

Common mistakes

Oops

Building a critical business process in a personal free account.

Do this instead

Use company-approved tools and accounts, and check with IT about data and access rules.

Oops

Treating a no-code prototype as the finished system.

Do this instead

Agree upfront if it's a throwaway prototype or a supported tool, and document it either way.

Your mission

Automate a tiny process

~35 min

Quick check

When is a no-code tool usually a poor fit?

Go deeper

  1. 1Try building one small automation (e.g. via Zapier/Make) connecting two tools you use.
  2. 2Explore a no-code app builder to prototype a simple internal tool idea.
  3. 3Learn where no-code hits its limits — usually scale, complex logic, and true customization.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge