No-code vs code for a first SaaS

You can build a first SaaS three ways in 2026: a no-code builder, AI writing most of the code, or you typing it yourself. Forums will argue which one is “real.” That argument does not take a payment. The right pick is the one that gets a named buyer to a price this week.

Tereza Tizkova wrote that you can vibecode your own SaaS instead of paying someone $50 a month for theirs. Pieter Levels said in June 2026 that everyone can build apps with AI, and almost nobody has an audience, ad money, or a free way to get seen. Building got cheap. Charging did not.

Indiecity is for one person or a team under twenty. You do not need a perfect stack. You need a thin product someone will pay for. Then you get the first ten customers.

Three paths, same job

Name the paths by the tool you open on day one.

• No-code: Bubble, Softr, Glide, Webflow plus a backend. You drag screens, wire workflows, and publish on their host.
• AI code: Cursor, Claude Code, Copilot, or a prompt-to-app tool. You (or the model) produce real files you can host.
• Hand code: you write and own the repo without leaning on a model for every function. Still common for people who already ship that way.

Levels put the old split well in 2019: code is the pro camera, no-code is the phone. Most photos are fine on a phone. Some jobs still need the DSLR. In 2026 the middle path is AI code. It is not no-code and it is not typing every line. Levels said in May 2026 he had not written code in months. The products still ran. The work moved to telling the tools what to build, and selling the outcome.

Your job does not change with the path. Ship something a buyer can use, put a price on it, and ask them to pay.

Choose by time to a charge

Stack religion says: “real founders own the code,” or “no-code does not scale,” or “AI code is fake.” Ignore that. Ask how many days until a real person can finish the painful step and pay you.

Write three dates on a notepad.

1. Day I can show the core outcome to one buyer.
2. Day I can take a card (Stripe link is enough).
3. Day I can fix the first “this broke” message without a two-week rebuild.

Pick the path that makes those three dates earliest for *you*, with the skills you have this month. Not the path a thread said is superior. Not the path you wish you already knew.

You can't wait for users to come to you. You have to go out and get them.

Graham’s line is about recruiting users by hand. It also kills the excuse of waiting for a “proper” codebase. A sheet and a form count if someone pays. A Bubble app counts. A PHP file counts. Levels’s Photo AI is a huge single PHP file. Ugly to purists. Fine to the people who pay.

When no-code is the right first move

Use no-code when you cannot confidently review generated code, or when auth, roles, and workflows would eat your week. Zapier’s 2026 roundup of no-code app builders still puts Bubble in the slot for building almost anything and for MVPs. Softr is the beginner pick. Glide is the simple mobile-friendly pick. Those tools already handle accounts, data, and publish. You spend time on the offer, not on TLS certificates.

No-code is also right when the product is mostly CRUD: login, a few records, a dashboard, a payment. That is most first SaaS products. You are not inventing a new database engine. You are removing one painful step for one buyer.

Know the trade. Your logic lives on their platform. Bubble bills on plans and workload as usage grows. You cannot zip the app and host it elsewhere the way you can with a repo. That is the fee for shipping before you can hire help. Accept it until a paid customer forces a rewrite.

When AI code is the middle path

Use AI code when you can read a diff, run the app locally, and spot a broken permission. You get a real repo, real hosting choices, and speed that used to need a teammate. You also inherit the model’s mistakes.

Zapier’s same 2026 piece is blunt about vibe-coded apps: hallucinations while editing, database leaks, open APIs that spike costs, and users skipping payment. Any one of those will sink a first charge. Before you put a price live, walk the happy path as a stranger: sign up, hit the paywall, pay, see the outcome, log out, log back in. If you cannot explain who is allowed to read which row, do not take a card yet.

AI code is a bad fit when you will spend the week fighting deploy, env vars, and CORS instead of talking to buyers. If that is you, go back to no-code for the first version. Own the code after someone pays.

When hand code still wins

Hand code (with or without light AI help) still wins when you already ship that way in your sleep, when the product is the technical system (infra, parsers, agents, weird data), or when compliance and ownership rules bar a hosted builder. It is not more moral. It is sometimes faster *for you* because you already know the stack.

It loses when “I will just scaffold auth and billing” becomes two quiet weeks. If you have never shipped Stripe subscriptions alone, copy a template or use a builder for that layer. The first SaaS is a sales test with software attached, not a portfolio piece.

A decision you can finish today

Answer these out loud. First honest yes wins.

1. Can I review and fix code the model writes without freezing? If no, start no-code.
2. Is the first version mostly forms, tables, roles, and a payment? If yes, no-code or a boring template is enough.
3. Does the core value need custom logic, files on disk, or a host I control on day one? If yes, AI code or hand code.
4. Will I still be configuring the stack in seven days instead of messaging buyers? If yes, cut scope or change path.

Then freeze the choice for two weeks. Switching stacks mid-build feels productive. It is usually fear of asking for money.

I will ship the first chargeable version on [no-code / AI code / hand code]. I will not switch tools until ten people have seen a price, or until a paid customer is blocked by the platform.

What to build (and what not to)

Whatever path you picked, the first version only needs four things.

• One login (or a magic link) so each buyer sees their own data
• The one workflow that removes their painful step
• A way to take money (link, checkout, invoice)
• A way for them to reach you when it breaks

Cut the rest. Team roles, public API, dark mode, AI chat widget, admin analytics: later. Jack Builds wrote on Indie Hackers in July 2026 after four months of solo building: polished landing page, onboarding, features, then launch day with zero paying customers and zero signups. He had never talked to a buyer before he shipped. The next move was not a better framework.

If you only remember one line from that thread, make it Mickael’s: building is kind of easy now, especially with AI, and finding customers is still hard. Pick the stack that leaves you hours to find buyers.

A one-week ship plan

1. Day 1. Write the offer in one sentence, with a price. Name 30 people who might buy. Pick no-code, AI code, or hand code with the freeze rule. A weekend is enough if you cut to the one job.
2. Days 2 to 4. Build only the four pieces above. Use a template or the builder’s AI for screens. Do not redesign the landing page twice.
3. Day 5. Run the stranger path yourself. Pay with a real card if you can. Fix auth and checkout only.
4. Days 6 to 7. Send ten personal notes with the price. Book calls. Take the first payment the same day someone says yes.

If day 7 arrives and you are still choosing libraries, you spent the week on the wrong job. Delete half the scope and ship the painful step alone.

After someone pays, the stack question comes back in a useful form: what did they ask for that this tool cannot do? Rebuild that piece, not the whole product, unless the platform is blocking revenue.

What to stop doing

• Waiting to “learn React properly” before you talk to a buyer.
• Rewriting a working no-code app because a podcast mocked no-code.
• Shipping vibe-coded checkout you have not walked through as a stranger.
• Adding a second builder or a second framework in the same week.
• Measuring progress in commits, workload units, or components instead of paid customers.
• Hiding in the editor because asking for money feels worse than another feature.

Then go sell it

The stack is just a way to ship. The business is ten people who pay. When the thin product can take a card, stop polishing the architecture and get your first 10 paying customers without ads. Write the offer. Name the list. Send the notes.

If you ship, charge, and want to put your name on how you chose the path, send us the story. When the product is real, put it on the map. You can join Indiecity while you build. That gives you people to talk to. It does not pick the stack for you.

Pick a path today. Freeze it. Charge someone this month.