Skip to content
Writing
·4 min read·Explainer

Vibe coding: build the tool you keep wanting

Drafted through my n8n + AI pipeline, edited by me.

Vibe coding is building software by describing what you want in plain English and letting an AI write and refine the code. The term is barely a year old, and it has already changed who gets to build a tool: not just engineers, but the person who actually understands the problem.

What vibe coding actually is

You describe the tool you want, the AI generates a working version, you try it, and you tell it what to fix. No syntax, no setup, just a conversation that ends in software. A request like 'a form that logs jobs to a sheet and texts me' becomes a real app in an afternoon. By some counts, a large share of new small software projects in 2026 are built this way.

Why it matters for a small business

Most businesses have a list of small tools they never built because hiring a developer for each was not worth it: a custom intake form, a tiny dashboard, an internal tracker. Vibe coding collapses the cost of those from a project to an afternoon. The bottleneck was never the idea. It was the distance to a working version.

Flow: describe the tool in plain English, the AI generates a working version, you try it and tell it what is wrong, then ship the internal tool.

  1. 01Trigger

    Describe it

    in plain English

  2. 02Action

    AI generates a version

  3. 03Human

    Try it, say what's wrong

  4. 04Record

    Ship the internal tool

Vibe coding turns a description into a working tool, in a loop.

What I'd build first

  • A custom intake form that writes straight into your sheet or CRM.
  • A small internal dashboard for the one number you check daily.
  • A tracker for the thing you currently manage in a messy spreadsheet.

Where it breaks

Vibe coding is a gift for small, internal, low-stakes tools. It is a trap for the things that need to be right: anything touching payments, customer data, or your core operation. AI-generated code can look perfect and hide a security hole or a silent bug. Build the throwaway tools this way. Bring in a person for the load-bearing ones.

Bring me the tool you keep wishing you had, and I'll tell you whether to vibe-code it yourself or build it properly.

Building something this should run inside?

Book a systems call