The Abstraction Question: Where to Live on the Build Stack

The pattern across member projects

In the last quarter, the cohort has split roughly into three camps. Members who live in Make.com or Zapier and wire prebuilt integrations. Members who run n8n on their own server. Members who have moved to Claude Code and are vibe coding small custom tools instead of using orchestration platforms at all.

There is no consensus on which is right, because the right answer is per member. The framing that is helping is not “which tool is best” but “what layer of the stack do I actually want to own”.

The ladder, with tradeoffs

From most abstract to least:

1. Finished SaaS products. You ship nothing custom. You also have nothing to maintain. Right answer when the product does exactly what you need.
2. Make.com. Visual workflows, hundreds of prebuilt connectors, light scripting available. Right answer when your workflow is mostly stitching together existing services.
3. n8n. Same shape as Make.com, more flexibility, you can self-host. Right answer when you want the visual model and need data sovereignty or custom code blocks.
4. Claude Code or similar agent CLIs. You direct an AI through building software for you. Right answer when the workflow is novel enough that no platform has a connector for it, and small enough that a 200-line script will do.
5. Raw code. Right answer when you have software engineers, or when you are one.

What members are getting wrong

The most common failure mode the cohort has seen is members picking a layer based on aspiration instead of capacity. They want to be vibe coders, so they jump to Claude Code, get stuck on a Docker error, and stall for three weeks. Or they want to be no-code operators, so they wire something complex in Make.com that would have taken twenty lines of Python and is now impossible to debug.

The honest move is to pick the highest layer of abstraction that does what you need, not the lowest. The lower you go, the more flexibility you get and the more you have to maintain.

The Kasimir caveat

Kasimir built a working interface in an hour with Claude Code. He also reported that what came out of the session sometimes did not work, and that he had to dig into formatting issues that broke the interface. The lower rungs of the ladder do come with sharper edges. The floor is closer than it used to be, but the edges are still real.

What to do this week

Look at the last three things you built. For each, ask, did I pick the right layer of the stack for that job. If you used Make.com for something that should have been a fifty-line Python script, notice. If you vibe coded something that a Zapier zap would have handled in five minutes, notice. The pattern across three projects will tell you where you actually live, not where you wish you lived.